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

Is there a way to have the build number/id as an env variable? #496

Closed
jfromaniello opened this issue Jul 30, 2014 · 4 comments
Closed

Is there a way to have the build number/id as an env variable? #496

jfromaniello opened this issue Jul 30, 2014 · 4 comments

Comments

@jfromaniello
Copy link

I'm using the Custom Scripts plugin.

Thanks a lot

kfatehi added a commit to Strider-CD/strider-env that referenced this issue Jul 30, 2014
@kfatehi
Copy link
Member

kfatehi commented Jul 30, 2014

@jfromaniello in this commit Strider-CD/strider-env@52e1d87 the strider-env plugin, when enabled, will always set STRIDER_JOB_ID to the job._id -- this becomes accessible to you in any of your custom scripts. to use this version just remove strider-env from your npm modules and clone that branch directly with git clone --branch job_id_envvar https://github.com/Strider-CD/strider-env.git remember to restart strider.

@kfatehi
Copy link
Member

kfatehi commented Jul 30, 2014

closing issue because the question has been answered

@kfatehi kfatehi closed this as completed Jul 30, 2014
@jfromaniello
Copy link
Author

Thanks a lot @keyvanfatehi!

@kfatehi
Copy link
Member

kfatehi commented Jul 30, 2014

np

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

No branches or pull requests

2 participants