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

Give the build commands the env of run_id #194

Merged
merged 1 commit into from Sep 19, 2022
Merged

Give the build commands the env of run_id #194

merged 1 commit into from Sep 19, 2022

Conversation

smarr
Copy link
Owner

@smarr smarr commented Sep 19, 2022

The build scripts may need some environment, which may have been defined for the executor or suite.
The current use case is as simple as having a Makefile that needs to be able to access utils on the standard PATH.

The current solution takes the environment from the run_id, and there’s a risk that this env might be contaminated/be specific to the run. Though, for now, it's good enough. And if it turns out to be problematic, we can fix it later.

@tolauwae this is for you. It should fix your immediate issue of not being able to specify any environment.

This PR is an extension of #174.

The assumption here is that the build needs some environment, which may have been defined for the executor or suite.
Though, there’s a risk that the env is contaminated for a specific run.

Signed-off-by: Stefan Marr <git@stefan-marr.de>
@smarr smarr added the Bug label Sep 19, 2022
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.04%) to 80.51% when pulling a1dc220 on build-empty-env into 49ce5dc on master.

@smarr smarr merged commit 446841e into master Sep 19, 2022
@smarr smarr deleted the build-empty-env branch September 19, 2022 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants