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

Interpret Nested Variables in Subversion URL

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • subversion-plugin
    • None

      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!

          [JENKINS-12287] Interpret Nested Variables in Subversion URL

          leojhartiv created issue -

          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 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 made changes -
          Link New: This issue is related to JENKINS-12450 [ JENKINS-12450 ]

          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 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 made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 142609 ] New: JNJira + In-Review [ 190196 ]

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

              Created:
              Updated:
              Resolved: