-
Notifications
You must be signed in to change notification settings - Fork 238
Preserve environment variables when building #2060
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
Conversation
|
Seems to fix the Linux build. Is |
In my opinion, this is relatively safe because the build is happening in a fresh GitHub Actions environment where you know all the environment variables that have been set because there is relatively little happening before the build. If you aren't comfortable with preserving all of the environment, we could replace this with a few instances of However, I think this is less neat and also more subject to future breakage if we change the set of environment variables we use (although I expect the |
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 happy to accept this PR as-is. The package building script is not used by people who are just compiling their own copies of Jamulus.
pljones
left a comment
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.
Accepting as is.
|
Oh, I should have asked @edoardopirovano to provide changes and contributors updates, too. |
Sorry, I'm not sure what you mean by that? |
You should be added as contributor here: Line 491 in 3444763
Not sure about the "changes" part. Probably the ChangeLog? |
Short description of changes
This PR changes the building script to pass the
--preserve-envoption todebuild. This ensures the environment variables needed by CodeQL during the build are present.Context: Fixes an issue?
Fixes: github/codeql-action#760
Does this change need documentation? What needs to be documented and how?
It does not - no changes to the project itself, only to the build script used in CI.
Status of this Pull Request
Working implementation.
What is missing until this pull request can be merged?
Ready to merge.
Checklist