-
Notifications
You must be signed in to change notification settings - Fork 594
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
Fix deprecations in Github Actions #8241
Conversation
lbergelson
commented
Mar 14, 2023
•
edited
Loading
edited
- Change actions v2 -> v3
- Fixing deprecated set-output usage see https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
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.
This all looks good (i'm assuming the V3 actions release is at least one more version better)... the bigger concern i have is to make sure those ::set-output ....:: commands are still doing what they were intended to do. Did they change the for output variables being visible to other jobs recently or did we simply chose a confusing way of doing it in the first place?
Most of the ones you changed are related to the logs URL variables, can you check to be 100% sure that those links work now?
@@ -32,15 +32,15 @@ jobs: | |||
env: | |||
GCP_CREDENTIALS: ${{ secrets.GCP_CREDENTIALS }} | |||
if: "${{ env.GCP_CREDENTIALS != '' }}" | |||
run: echo "::set-output name=defined::true" | |||
run: echo defined=true >> $GITHUB_OUTPUT |
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.
These still work for outputs? I remember I had to use those eldrich invocations as messy as they were to pass variables across jobs.
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.
It seems to work. The jobs are passing...
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.
Bleh the report upload link looks broken now?
https://storage.googleapis.com/hellbender-test-logs/build_reports/8241/merge_4420157996.1/tests/testOnPackagedReleaseJar/index.html
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.
Well on the plus side it looks like it was already broken to follow the index.html link posted by a run job...
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.
The variables that went into displaying that link and upload location look right... something is wrong however but thats not the fault of this branch
c031bdc
to
6ace50c
Compare
All warnings are gone now. Going to merge this. |