Skip to content

stage container build on merge#132

Merged
vab merged 1 commit intomainfrom
ghwf-change
Feb 13, 2025
Merged

stage container build on merge#132
vab merged 1 commit intomainfrom
ghwf-change

Conversation

@vab
Copy link
Contributor

@vab vab commented Feb 13, 2025

Purpose and background context

The stage-build.yml is still configured to build and push an ECR image when a PR is opened; it should push an ECR image when there is a push to main, as would happen after the PR is approved and merged. This way, if more commits are added during the PR review process, they will end up in the final ECR image deployed to Stage. Currently stage-build is triggered in the same way as dev-build meaning that any extra commits would not make it to the Stage image.

How can a reviewer manually see the effects of these changes?

Modifies the build gh workflow to build the prod container on PR merge rather than commit.

Includes new or updated dependencies?

NO

Changes expectations for external applications?

NO

What are the relevant tickets?

https://mitlibraries.atlassian.net/browse/IN-1175

Developer

  • All new ENV is documented in README
  • All new ENV has been added to staging and production environments
  • All related Jira tickets are linked in commit message(s)
  • Stakeholder approval has been confirmed (or is not needed)

Code Reviewer(s)

  • The commit message is clear and follows our guidelines (not just this PR message)
  • There are appropriate tests covering any new functionality
  • The provided documentation is sufficient for understanding any new functionality introduced
  • Any manual tests have been performed or provided examples verified
  • New dependencies are appropriate or there were no changes

Why these changes are being introduced:

This commit addresses the following issue:
The stage-build.yml is still configured to build and push an ECR image when a
PR is opened; it should push an ECR image when there is a push to main, as
would happen after the PR is approved and merged. This way, if more commits
are added during the PR review process, they will end up in the final ECR
image deployed to Stage. Currently stage-build is triggered in the same way
as dev-build meaning that any extra commits would not make it to the Stage
image.

How this addresses that need:

Modifies the build gh workflow to build the container on merge rather than
commit.

Side effects of this change:

None

Changes to be committed:
      modified:   .github/workflows/stage-build.yml
@vab vab self-assigned this Feb 13, 2025
@vab vab requested a review from a team as a code owner February 13, 2025 15:28
@vab
Copy link
Contributor Author

vab commented Feb 13, 2025

Coveralls is currently down. So, the failure is with the service not this code.

Copy link
Contributor

@ehanson8 ehanson8 left a comment

Choose a reason for hiding this comment

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

Thanks Alex!

@vab vab merged commit 5f0dc6f into main Feb 13, 2025
1 of 2 checks passed
@vab vab deleted the ghwf-change branch February 13, 2025 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants