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

svn-tag should resolve parameters in the tag name

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • svn-tag-plugin
    • None
    • Platform: All, OS: All

      Currently, via a BuildWrapper, I can add additional env variables to a running
      build. However, those variables do not persist past the execution of the actual
      core build steps. This means that they are not available to post build steps
      (e.g. Publishers).

      In my context, I want to be able to set a custom version string that is used
      both by the ant builder when generating my build artifact(i.e. version string in
      the jar manifest) and refer to that same version string in the svn tag publisher
      so it is used as the svn tag for the build.

      I'd very much like to have support for setting custom env variables that are
      visible throughout the build execution.

          [JENKINS-2267] svn-tag should resolve parameters in the tag name

          Alan Harder added a comment -

          I think you can use $env

          {'ABC'}

          syntax in svn-tag settings to reference the var, once Hudson core makes it available.. so closing this issue against svn-tag plugin in favor of one recently filed against core.

          Alan Harder added a comment - I think you can use $env {'ABC'} syntax in svn-tag settings to reference the var, once Hudson core makes it available.. so closing this issue against svn-tag plugin in favor of one recently filed against core.

            Unassigned Unassigned
            chudak chudak
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: