![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
04/Feb/15 4:25 AM
|
|
Description:
|
JENKINS-24380 changed the build id to be just the number. This makes the $BUILD_ID the same as $BUILD_NUMBER, but when I click on the "See the list of available environment variables" link under the "command" (in the "Execute Shell" build step) it loads a page called "/env-vars.html/", which still says $BUILD_ID is a date.
This should be fixed. And possibly either $BUILD_ID or $BUILD_NUMBER should be obsoleted, since they are identical now. Or the docs should let me know why I should use one or the other.
Also, is there a new env. variable for the date? (I only noticed all this after the new $BUILD_ID format caused bugs in my other scripts which were expecting a date).
|
|
Environment:
|
Jenkins ver. 1.598
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
David Caldwell
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
