Skip to content

chore(ci): docker images are published with release tags#15076

Merged
mpfirrmann merged 1 commit intomagma:masterfrom
mpfirrmann:pr/tags_container
Feb 27, 2023
Merged

chore(ci): docker images are published with release tags#15076
mpfirrmann merged 1 commit intomagma:masterfrom
mpfirrmann:pr/tags_container

Conversation

@mpfirrmann
Copy link
Copy Markdown
Contributor

@mpfirrmann mpfirrmann commented Feb 24, 2023

Summary

Magma debian packages are released for every merge to master and release branches. They are tagged with latest plus either commit hash (master branch) or release version number (release branch). This behavior is mimicked here for magma containers. At the moment, they are only published with the latest tag and commit hash.
Closes #15040.

Test Plan

The GitHub action was adapted to only perform the tag handling and executed on my fork (see the adapted test via the commit hash on the links)

Additional Information

The final output tag is written into $GITHUB_OUTPUT in a different step now.

@pull-request-size pull-request-size bot added the size/S Denotes a PR that changes 10-29 lines. label Feb 24, 2023
@github-actions
Copy link
Copy Markdown
Contributor

Thanks for opening a PR! 💯

A couple initial guidelines

Howto

  • Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
  • Checks. All required CI checks must pass before merge.
  • Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

If this is your first Magma PR, also consider reading

@github-actions github-actions bot added the component: ci All updates on CI (Jenkins/CircleCi/Github Action) label Feb 24, 2023
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 24, 2023

DP Lint & Test

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0

Results for commit c339d53.

♻️ This comment has been updated with latest results.

@mpfirrmann mpfirrmann marked this pull request as ready for review February 24, 2023 14:19
@mpfirrmann mpfirrmann requested a review from a team as a code owner February 24, 2023 14:19
@mpfirrmann mpfirrmann requested review from LKreutzer and talkhasib and removed request for talkhasib February 24, 2023 14:19
Copy link
Copy Markdown
Contributor

@LKreutzer LKreutzer left a comment

Choose a reason for hiding this comment

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

Should we also refactor the build-containers-ghz job since it also publishes?

@mpfirrmann
Copy link
Copy Markdown
Contributor Author

mpfirrmann commented Feb 27, 2023

Should we also refactor the build-containers-ghz job since it also publishes?

I adapted the build-containers job to use the same tag as the build-containers job. See the adapted links to the tests.

@mpfirrmann mpfirrmann requested a review from LKreutzer February 27, 2023 10:15
@mpfirrmann mpfirrmann merged commit 51292e2 into magma:master Feb 27, 2023
@mpfirrmann mpfirrmann deleted the pr/tags_container branch February 27, 2023 11:25
lucasgonze pushed a commit to lucasgonze/magma that referenced this pull request Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: ci All updates on CI (Jenkins/CircleCi/Github Action) size/S Denotes a PR that changes 10-29 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure that Docker images in .github/workflows/agw-build-publish-container.yml are published with release tags

2 participants