Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21964

Build definition and workspace name should accept parameters and/or environment variables.

XMLWordPrintable

      We are looking to use the same build project for multiple streams in rtc (parallel supported versioning). Currently if you try to add a parameter or variable to the build definition name or repository workspace name, the team concert plugin will not parse the variable and error out, not finding the correct definition/workspace. for example

      parameter choice list :
      stream = ver2.5, ver3.2, ver6.0

      build definition = jenkins.$stream

      adding this functionality would allow us to greatly expand our use of jenkins for production builds as well as testing processes for individual developer workspaces. Currently we are considering this a blocker for set up of developer testing.

      the only know method around this is to set up a template project using another plugin.

            Unassigned Unassigned
            griffman99h James Griffin
            Votes:
            7 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: