-
Notifications
You must be signed in to change notification settings - Fork 20
Artifact Passing from Automate-Metrics to Build-Book #415
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
31 commits
Select commit
Hold shift + click to select a range
c9e7baf
first pass at artifact passing
jukent 530be5a
missed one
jukent 5106b7f
pass 2
jukent 315c76b
revert changes to nightly-build (to not deploy or get metrics), and s…
jukent bf828c4
rename build step
jukent 2449155
reorder
jukent 7804088
new placeholder code
jukent 5bdc288
edit colorbar width, one more pass at publish-site metrics
jukent df27a32
does download of artifact happen inside build action?
jukent 5a13bda
revert changes to automate metrics step
jukent 4966b5f
fix zip job
jukent 01927e7
oops indent
jukent b993a79
zip needs runs on, but then will it lose the metrics files?
jukent b135376
add zip step
jukent b10a4a5
rename
jukent b2b70b6
add automate metrics back to trigger-preview
jukent a163052
make strings
jukent bd38a4d
placeholder triggerbookbuild.yaml file
jukent fd7a2fc
fix inputs
jukent 2f8e5da
rm curly brackets
jukent 8f1e474
Merge pull request #129 from jukent/recovery-branch
jukent dbcbb0e
trigger_workflow input to book-build
jukent f9ba49d
comment out new input
jukent 5728a8f
no ! # just #
jukent 6ccd292
rm trigger-book-build
jukent e60716b
fix upload path
jukent 7f3ec92
remove comment to use new build-book input
jukent 85db33e
just try a full path for trigger_workflow
jukent a15092f
rm full path
jukent 61ee7ad
use soon to be new workflow_conclusion as empty, rather than default …
jukent 02ce165
Update .gitignore
jukent 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
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
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
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.
I am hesitant about this removal, i.e. I think keeping the "automate-metrics" job in the "trigger-preview.yaml" workflow would still be valuable to see how the Metrics page would render in the preview of any PR. This is because right after any PR is merged into main, there will be a publish-site workflow run, which will update the metrics on the website.
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 think I was confused about each action a bit. I agree and will re-introduce this - but my attempts at introducing an artifact have broken the actions on my branch.
I think it might be better for me to focus on getting one action working (the publish-site), and then the knowledge I gain should transfer to setting up the trigger-preview to use automate-metrics again.
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.
Okay I added this back for now, but I know it won't work yet and I'm not sure if it can work.
I think this because the trigger-preview is grabbing a book-build artifact.
artifact_name: book-zip-${{ needs.find-pull-request.outputs.number }}
that is zipped from the trigger-site-build action (which is triggered by a PR and thus does not have access to the secrets necessary to run the metrics collection). And in turn the trigger-preview is triggered by the trigger-site-build.There seems to be a possible work around with trigger-preview being allowed to access secrets, so we could rebuild the book in that step, but that seems computationally expensive. I have to think about this more.
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.
Removed again per our discussion
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'm wondering if there is a benefit to moving the automate-metrics step to Cookbook-Actions even though we don't intend for it to be re-usable across repositories. It seems that if it existed as a re-usable workflow there are different permissions. For example, it could access secrets that live in the Cookbook-Actions repo and be triggered by a PR in the portal, zip up it's artifact and pass that back to the trigger-preview workflow. It would be a bit of an overall, and would be the next step after the artifact passing is functioning and well understood.
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.
Maybe we can revisit this in the future?