Skip to content

Expose ENV variable to build environment for build step #1863

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

Closed
agjohnson opened this issue Dec 14, 2015 · 4 comments
Closed

Expose ENV variable to build environment for build step #1863

agjohnson opened this issue Dec 14, 2015 · 4 comments
Labels
Improvement Minor improvement to code Needed: design decision A core team decision is required

Comments

@agjohnson
Copy link
Contributor

agjohnson commented Dec 14, 2015

Expose the current build step to the build environments. This would allow for step detection and executing commands during specific build steps.

On starting to execute the command, we'll post a new command to the API, then post command execution we finally PUT to the created command.

There are two uses for this:

  • Streaming output: which I don't care about much
  • Showing the command that is currently executing so that in the cases where the build fails due to timeout/memory/generic failure, the user sees the command that it failed on.
@agjohnson agjohnson added the Improvement Minor improvement to code label Dec 14, 2015
@humitos
Copy link
Member

humitos commented Dec 29, 2017

@agjohnson can you explain this issue a little more?

BTW, is this issue still relevant?

@humitos humitos added the Needed: more information A reply from issue author is required label Dec 29, 2017
@agjohnson
Copy link
Contributor Author

Updated the description. I think this is probably a valid feature, but low priority

@agjohnson agjohnson removed the Needed: more information A reply from issue author is required label Mar 31, 2018
@agjohnson agjohnson added this to the Build output page milestone Mar 31, 2018
@stale
Copy link

stale bot commented Jan 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Status: stale Issue will be considered inactive soon label Jan 10, 2019
@stsewd stsewd added Accepted Accepted issue on our roadmap and removed Status: stale Issue will be considered inactive soon labels Jan 10, 2019
@humitos humitos added Needed: design decision A core team decision is required and removed Accepted Accepted issue on our roadmap labels Jan 10, 2019
@humitos
Copy link
Member

humitos commented Apr 5, 2022

Closing as duplicated of #4288

@humitos humitos closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants