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 ci-release.yml perms #4097

Merged

Conversation

joe-elliott
Copy link
Member

Release CI is currently failing with:

image

Currently testing this change in my fork

Signed-off-by: Joe Elliott <number101010@gmail.com>
@joe-elliott joe-elliott requested a review from a team as a code owner December 8, 2022 20:12
@codecov
Copy link

codecov bot commented Dec 8, 2022

Codecov Report

Base: 97.15% // Head: 97.16% // Increases project coverage by +0.01% 🎉

Coverage data is based on head (d9e358f) compared to base (47ef1da).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4097      +/-   ##
==========================================
+ Coverage   97.15%   97.16%   +0.01%     
==========================================
  Files         295      295              
  Lines       17413    17413              
==========================================
+ Hits        16918    16920       +2     
+ Misses        399      397       -2     
  Partials       96       96              
Flag Coverage Δ
unittests 97.16% <ø> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...lugin/sampling/strategystore/adaptive/processor.go 100.00% <0.00%> (+0.61%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@yurishkuro yurishkuro merged commit 23eb573 into jaegertracing:main Dec 8, 2022
@@ -9,7 +9,7 @@ on:
# and https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
permissions:
deployments: write
contents: read
contents: read,write
Copy link
Member

Choose a reason for hiding this comment

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

oh-oh

The workflow is not valid. .github/workflows/ci-release.yml (Line: 12, Col: 13): Unexpected value 'read,write'

Copy link
Member

Choose a reason for hiding this comment

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

maybe this needs an array syntax ["read","write"]?

Copy link
Member Author

Choose a reason for hiding this comment

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

I believe just write running a test now in my fork to see:

https://github.com/joe-elliott/jaeger/actions/runs/3652192298/jobs/6170292688

Copy link
Member

Choose a reason for hiding this comment

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

yeah, would expect write to include read

Copy link
Member

@yurishkuro yurishkuro Dec 8, 2022

Choose a reason for hiding this comment

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

but also curious what "content" this is writing, because content seems to refer to the source code itself - https://docs.github.com/en/rest/overview/permissions-required-for-github-apps?apiVersion=2022-11-28#contents

Copy link
Member

Choose a reason for hiding this comment

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

probably this: PATCH /repos/{owner}/{repo}/releases/assets/{asset_id} (write)

@joe-elliott joe-elliott mentioned this pull request Dec 8, 2022
yurishkuro pushed a commit that referenced this pull request Dec 8, 2022
This correctly sets the `contents` permission to `write`. This allowed
CI on my fork to move past the "Upload Binaries" step. This fixes the
change here: #4097

Signed-off-by: Joe Elliott <number101010@gmail.com>
shubbham1215 pushed a commit to shubbham1215/jaeger that referenced this pull request Feb 22, 2023
Release CI is currently failing with:


![image](https://user-images.githubusercontent.com/2272392/206558115-b7b9f51d-66b8-482b-b66b-9decd5c231ee.png)

Currently testing this change in my fork

Signed-off-by: Joe Elliott <number101010@gmail.com>
shubbham1215 pushed a commit to shubbham1215/jaeger that referenced this pull request Feb 22, 2023
This correctly sets the `contents` permission to `write`. This allowed
CI on my fork to move past the "Upload Binaries" step. This fixes the
change here: jaegertracing#4097

Signed-off-by: Joe Elliott <number101010@gmail.com>
shubbham1215 pushed a commit to shubbham1215/jaeger that referenced this pull request Mar 5, 2023
Release CI is currently failing with:

![image](https://user-images.githubusercontent.com/2272392/206558115-b7b9f51d-66b8-482b-b66b-9decd5c231ee.png)

Currently testing this change in my fork

Signed-off-by: Joe Elliott <number101010@gmail.com>
Signed-off-by: shubbham1215 <sawaikershubham@gmail.com>
shubbham1215 pushed a commit to shubbham1215/jaeger that referenced this pull request Mar 5, 2023
This correctly sets the `contents` permission to `write`. This allowed
CI on my fork to move past the "Upload Binaries" step. This fixes the
change here: jaegertracing#4097

Signed-off-by: Joe Elliott <number101010@gmail.com>
Signed-off-by: shubbham1215 <sawaikershubham@gmail.com>
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.

None yet

2 participants