Skip to content
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

Merged
merged 6 commits into from
Mar 23, 2023
Merged

Conversation

lbergelson
Copy link
Member

@lbergelson lbergelson commented Mar 14, 2023

@lbergelson lbergelson marked this pull request as ready for review March 14, 2023 21:04
@lbergelson lbergelson requested a review from jamesemery March 14, 2023 21:04
Copy link
Collaborator

@jamesemery jamesemery left a 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
Copy link
Collaborator

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.

Copy link
Member Author

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...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

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...

Copy link
Collaborator

@jamesemery jamesemery left a 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

@lbergelson lbergelson force-pushed the lb_fix_deprecation_in_actions branch from c031bdc to 6ace50c Compare March 22, 2023 20:11
missed a v
@lbergelson
Copy link
Member Author

All warnings are gone now. Going to merge this.

@lbergelson lbergelson merged commit 148dd33 into master Mar 23, 2023
@lbergelson lbergelson deleted the lb_fix_deprecation_in_actions branch March 23, 2023 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants