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

Interpret Nested Variables in Subversion URL

    XMLWordPrintable

Details

    Description

      See groups thread here:

      http://groups.google.com/group/jenkinsci-users/browse_frm/thread/5bb278d41fd97021/8a3f468c47b971f6?#8a3f468c47b971f6

      I'm trying to create a pipeline for my build process. The same steps will be executed, but against different subversion branches and/or data sources.

      For most areas I am using the "run script" build step, so I can do something like this:

      eval \$RELEASE_BRANCH_$STACK

      Where STACK=03 and RELEASE_BRANCH_03=http://server:port/repository/branches/03_BRANCH (the svn URL for the 03 release branch). The eval command won't work in that field. I'd like this sort of support, simular to the SSH plugins.

      Thanks!

      Attachments

        Issue Links

          Activity

            leojhartiv leojhartiv added a comment -

            Arno, also see this jira which tries to address the problem across Jenkins:
            https://issues.jenkins-ci.org/browse/JENKINS-12450

            leojhartiv leojhartiv added a comment - Arno, also see this jira which tries to address the problem across Jenkins: https://issues.jenkins-ci.org/browse/JENKINS-12450
            oleg_nenashev Oleg Nenashev added a comment -

            Such issue should be solved in the core (JENKINS-12450).
            It does not make sense to create additional "generic" logic in plugins.

            As a workaround, you can use a wrapper job, which will resolve variables using scripts

            oleg_nenashev Oleg Nenashev added a comment - Such issue should be solved in the core ( JENKINS-12450 ). It does not make sense to create additional "generic" logic in plugins. As a workaround, you can use a wrapper job, which will resolve variables using scripts

            People

              Unassigned Unassigned
              leojhartiv leojhartiv
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: