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

tar.gz file is not added to GitHub release during tagged build #3570

Open
6 tasks done
gep13 opened this issue Nov 20, 2024 · 0 comments
Open
6 tasks done

tar.gz file is not added to GitHub release during tagged build #3570

gep13 opened this issue Nov 20, 2024 · 0 comments
Labels
Bug BuildAutomation NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product.

Comments

@gep13
Copy link
Member

gep13 commented Nov 20, 2024

Checklist

  • I confirm there are no unresolved issues reported on the Chocolatey Status page.
  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my problem.
  • I have verified this is not an issue for a specific package.
  • I have verified this issue is not security related.
  • I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

One of the steps that is performed during a tagged build is to generate a tar.gz file that contains the Chocolatey CLI artifacts, which have been built using Mono on a Linux system, and for that file to be uploaded to the GitHub release.

This step is performed here:

curl \
-X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer %env.GITHUB_PAT%"\
-H "X-GitHub-Api-Version: 2022-11-28" \
-H "Content-Type: application/octet-stream" \
https://uploads.github.com/repos/chocolatey/choco/releases/%env.CHOCOLATEY_VERSION%/assets?name=chocolatey.v%env.CHOCOLATEY_VERSION%.tar.gz \
--data-binary "@code_drop/Packages/Chocolatey/chocolatey.v%env.CHOCOLATEY_VERSION%.tar.gz"

But it is not completing successfully, and adding the artifact has to be done manually.

What is Expected?

The tar.gz file should be updated, without any manual intervention.

How Did You Get This To Happen?

  1. During the last couple tagged builds, the build log has been inspected and the output shows the following:
{"message":"Not Found","request_id":"1E0B:23EA90:F337E:108301:6733EDFD","documentation_url":"https://docs.github.com/rest"}
00:08:30  

System Details

N/A

Installed Packages

N/A

Output Log

{"message":"Not Found","request_id":"1E0B:23EA90:F337E:108301:6733EDFD","documentation_url":"https://docs.github.com/rest"}

Additional Context

N/A

@gep13 gep13 added Bug BuildAutomation NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product. labels Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug BuildAutomation NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product.
Projects
None yet
Development

No branches or pull requests

1 participant