Skip to content

Conversation

@yantosca
Copy link
Contributor

@yantosca yantosca commented Aug 7, 2025

Overview

This PR does the following:

  1. Removes the Microsoft Azure Dev Pipelines workflow files:

    • .ci-pipelines/Dockerfile
    • .ci-pipelines/build-testing.yml
  2. Adds a GitHub Action to run the C-I tests using GCC compiler versions 9, 10, 11, 12, and 13. (GCC 14 is not yet available on the ubuntu-latest 22.04 that is used.)

    • ./github/workflows/run-ci-tests.yml
  3. Adds a GitHub Action to scan other actions for security issues and other problems:

    • ./github/workflows/lint-ci-workflows.yml

Advantages:

  • We no longer need to maintain an external Azure Dev Pipelines account
  • We can run the C-I tests on multiple compilers
  • GitHub Actions has enough memory to run all C-I tests, including those for MCM (Azure did not)
  • The "Lint" Action will flag any security issues in with the C-I test GitHub action

.github/workflows/run-ci-tests.yml
- GitHub Actions workflow that will compile KPP and run C-I tests
  using several GNU GCC compiler versions

.ci-pipelines/Dockerfile
.ci-pipelines/build-testing.yml
- Removed these Azure Dev Pipelines workflow config files

CHANGELOG.md
- Updated accordingly

Signed-off-by: Bob Yantosca <[email protected]>
.github/workflows/lint-ci-workflows.yml
- Added "Lint" GitHub action to check other Actions for security
  and other issues

CHANGELOG.md
- Updated accordingly

Signed-off-by: Bob Yantosca <[email protected]>
@yantosca yantosca added this to the 3,3,1 milestone Aug 7, 2025
@yantosca yantosca requested a review from RolfSander August 7, 2025 13:59
@yantosca yantosca self-assigned this Aug 7, 2025
@yantosca yantosca added feature New feature or request CI / testing Related to continuous integration or other testing methods labels Aug 7, 2025
@yantosca yantosca modified the milestones: 3,3,1, 3.3.1 Aug 7, 2025
Copy link
Contributor

@RolfSander RolfSander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! It's great to see that GitHub Actions has enough memory for the
MCM tests.

However, I don't know much about C-I tests, so I cannot provide a
detailed review :-( Anyway, if the MCM passes the tests, I'm happy :-)

@yantosca
Copy link
Contributor Author

yantosca commented Aug 7, 2025

Thanks @RolfSander, I'm also happy the MCM works!

docs/source/tech_info/06_info_for_kpp_developers.rst
- Updated the documentation for C-I tests to remove references to
  Azure Dev Pipelines and add doc for GitHub Actions.

Signed-off-by: Bob Yantosca <[email protected]>
@yantosca yantosca force-pushed the feature/github-actions branch from fe7ff9c to 5e42cbe Compare August 7, 2025 14:54
@yantosca yantosca merged commit 2f0eeff into dev Aug 7, 2025
11 checks passed
@yantosca yantosca deleted the feature/github-actions branch August 7, 2025 17:32
@yantosca yantosca modified the milestones: 3.3.1, 3.4.0 Oct 9, 2025
@yantosca yantosca linked an issue Oct 27, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI / testing Related to continuous integration or other testing methods feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate C-I tests from Azure to GitHub actions

3 participants