-
Notifications
You must be signed in to change notification settings - Fork 375
[WX-1136] Docker Build Test #7151
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,37 @@ | ||
| name: 'Docker Build Test' | ||
|
|
||
| # This test verifies that we can successfully build the same docker images that we release. | ||
| # Includes `cromwell`, `womtool`, `cromiam`, and `cromwell-drs-localizer` | ||
| # See chart_update_on_merge.yml for the actual release workflow. | ||
|
|
||
| run-name: ${{ github.actor }} Docker Build Test | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
| push: | ||
| merge_group: | ||
|
|
||
| permissions: | ||
| contents: read | ||
|
|
||
| jobs: | ||
| sbt-build: | ||
| name: sbt docker build | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Clone Cromwell | ||
| uses: actions/checkout@v2 | ||
| with: | ||
| repository: broadinstitute/cromwell | ||
| token: ${{ secrets.BROADBOT_GITHUB_TOKEN }} | ||
| path: cromwell | ||
| - uses: olafurpg/setup-scala@v10 | ||
| with: | ||
| java-version: adopt@1.11 | ||
| # The following invocation should be as similar as possible to the one in chart_update_on_merge.yml | ||
| # To state the obvious: This test should not publish anything. It should simply verify that the build completes. | ||
| - name: Build Cromwell Docker | ||
| run: | | ||
| set -e | ||
| cd cromwell | ||
| sbt -Dproject.isSnapshot=false -Dproject.isRelease=false docker | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Is
sbt [...] dockerequivalent to callingIf so, very cool and TIL
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.
Almost, but not exactly equivalent. In my understanding
sbt dockerwill build everything it can find at the project level, whilesbt womtool/dockerwill build only the subprojectwomtool.^ Isn't quite the same since it starts up/shuts down the
sbtenvironment each time you call the command, which is significantly slower than doing everything in the same go. The end result is the same, though.The same goes for tests:
sbt testwill run all unit tests, butsbt server/testwill run only the server tests.