-
Notifications
You must be signed in to change notification settings - Fork 0
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
[DC-698] Upgrade from workflow-dispatch
to workflow-call
#170
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,16 +1,12 @@ | ||
name: Integration Tests | ||
|
||
on: | ||
workflow_dispatch: | ||
workflow_call: | ||
inputs: | ||
environment: | ||
type: choice | ||
type: string | ||
description: 'environment to run test in' | ||
required: true | ||
options: | ||
- staging | ||
- alpha | ||
- dev | ||
default: 'dev' | ||
snf2ye marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
env: | ||
|
@@ -35,14 +31,9 @@ jobs: | |
|
||
dispatch-trivy: | ||
needs: [ build ] | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Fire off Trivy action | ||
uses: broadinstitute/workflow-dispatch@v1 | ||
with: | ||
workflow: Trivy | ||
token: ${{ secrets.BROADBOT_TOKEN }} | ||
uses: ./.github/workflows/trivy.yml | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the point of running trivy as its own workflow was so that its failure didn't fail the build, because all trivy failures we've seen so far were issues with the base image and out of our control. If it's run this way, will it fail the build? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it is run as a separate workflow still. |
||
secrets: | ||
token: ${{ secrets.BROADBOT_TOKEN }} | ||
|
||
test-env: | ||
runs-on: ubuntu-latest | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
name: Tag | ||
on: workflow_dispatch | ||
on: | ||
workflow_call: | ||
secrets: | ||
token: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If this is
be
|
||
required: true | ||
|
||
jobs: | ||
tag-job: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
name: Trivy | ||
on: workflow_dispatch | ||
on: | ||
workflow_call: | ||
secrets: | ||
token: | ||
required: true | ||
|
||
jobs: | ||
trivy: | ||
|
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.
I thought this was used by the GitHub action UI to show the possible values, to see what I mean go to https://github.com/DataBiosphere/terra-data-catalog/actions/workflows/integration-tests.yml and select Run Workflow
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.
Choice seemed to not be an option for workflow_call - maybe I was misunderstanding the API docs though and there's another way to specify it?