Skip to content

[JENKINS-12997] Version number variable empty when multiple concurrent builds are running #118

Description

@jenkins-infra-bot

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.


Originally reported by plillevold, imported from: Version number variable empty when multiple concurrent builds are running
  • status: Open
  • priority: Major
  • component(s): versionnumber-plugin
  • label(s): build, concurrent-build
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251216-225446
Raw content of original issue

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.

  • environment: Jenkins 1.452

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions