-
Notifications
You must be signed in to change notification settings - Fork 2.6k
[GHA] Added build-images step into ci-test workflow #7821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
19de925 to
289e87a
Compare
| runs-on: ubuntu-latest-xl | ||
| continue-on-error: false | ||
| needs: prepare | ||
| if: ${{ github.event_name == 'push' && needs.prepare.outputs.test-rust == 'true' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice this is a good way to prevent prs from trying to use secrets.
.github/workflows/ci-test.yml
Outdated
| key_password: ${{ secrets.DOCKERHUB_KEY_PASSWORD }} | ||
| - name: pre build docker images | ||
| run: | | ||
| if [[ ! "$CHANGES_TARGET_BRANCH" =~ "^release-[0-9|.]+$" ]] && [[ ! "$CHANGES_TARGET_BRANCH" =~ "^gha-test-[0-9|.]+$" ]] ; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you probably want to build if the target branch is master so you can use the images in cluster test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh yes, this step is copied from docker-publish workflow which has some other branches we need to filter. Actually we do not need this step here because ci-test and LBT both be triggered by auto and canary by push only. Thx for pointing out
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, as long as the step is not triggered on prs we're fine.
| continue-on-error: false | ||
| env: | ||
| TAG: github-1 | ||
| DOCKERHUB_ORG: libra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good fix
| - name: setup_aws_erc_login | ||
| - name: setup_aws_ecr_login |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ahh a name fix. nice.
|
/canary |
|
Cluster Test Result Repro cmd: 🎉 Land-blocking cluster test passed! 👌 |
|
☀️ Canary successful |
|
/land |
|
Cluster Test Result Repro cmd: 🎉 Land-blocking cluster test passed! 👌 |
split current docker publish workflow into 2 parts:
Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/diem/diem/tree/master/developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well