[
https://issues.jenkins-ci.org/browse/JENKINS-12997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lillevold updated JENKINS-12997:
--------------------------------------
Summary: Version number variable empty when multiple concurrent builds are
running (was: Verson number variable empty when multiple concurrent builds are
running)
(minor edit: fixed spelling in Summary)
> Version number variable empty when multiple concurrent builds are running
> -------------------------------------------------------------------------
>
> Key: JENKINS-12997
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12997
> Project: Jenkins
> Issue Type: Bug
> Components: plugin, versionnumber
> Environment: Jenkins 1.452
> Reporter: Peter Lillevold
> Labels: build, concurrent-build
>
> I have configured a job to generate and use a version number like this:
> 0.0.${BUILD_NUMBER}.${SVN_REVISION}
> and place it in a variable called BUILD_VERSION.
> This works nicely when only one build is executing. But if a second build of
> the job is started while the first is running, the content of the
> BUILD_VERSION variable will be empty for the duration of that build.
> This is a major issue for us since it practically means we have to turn of
> "Execute concurrent builds if necessary" on all our CI builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
