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

Parent Project can not be defined by variable

    XMLWordPrintable

Details

    Description

      Defining the parent project (publisher) to get the workspace from by a variable does not work. Variables entered don't get expanded. That is a big problem if the job is used in several builds with different configurations.

      Attachments

        Issue Links

          Activity

            compi Maik Richey added a comment -

            This one is related to JENKINS-9778 cause the fix for this issue also contains the fix for JENKINS-9778.

            compi Maik Richey added a comment - This one is related to JENKINS-9778 cause the fix for this issue also contains the fix for JENKINS-9778 .
            compi Maik Richey added a comment -

            Contains the fix for JENKINS-9778 and JENKINS-9779. Suggest to use it as version 0.4. Can someone please verify and release the new version.

            compi Maik Richey added a comment - Contains the fix for JENKINS-9778 and JENKINS-9779 . Suggest to use it as version 0.4. Can someone please verify and release the new version.

            I would like this fixes aswell, why are they not released in a 0.4 version?

            ki82 Christian Bremer added a comment - I would like this fixes aswell, why are they not released in a 0.4 version?

            Code changed in jenkins
            User: Andrew Bayer
            Path:
            src/main/java/hudson/plugins/cloneworkspace/CloneWorkspaceSCM.java
            http://jenkins-ci.org/commit/jenkins-clone-workspace-scm-plugin/703b61c1b5f7a32b28d8d8a9de34874ef483853c
            Log:
            [FIXED JENKINS-9779] Process parent job name for parameters.

            Compare: https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/compare/46807bc...703b61c

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrew Bayer Path: src/main/java/hudson/plugins/cloneworkspace/CloneWorkspaceSCM.java http://jenkins-ci.org/commit/jenkins-clone-workspace-scm-plugin/703b61c1b5f7a32b28d8d8a9de34874ef483853c Log: [FIXED JENKINS-9779] Process parent job name for parameters. Compare: https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/compare/46807bc...703b61c
            greghansen Greg Hansen added a comment - - edited

            I've just been trying out this plugin, and see that you've marked this resolved by allowing parameters in the parent project specification. Unfortunately, in the configuration UI, the parent project is specified by a drop-down that lists the available Publishers, without any way to use a variable. Can you either a) change that drop-down to allow us to type over what's there, or b) tell us which parameter it uses to obtain the workspace, so we can set that in the calling project?

            Jenkins ver 1.519, Jenkins clone workspace plugin ver 0.6

            greghansen Greg Hansen added a comment - - edited I've just been trying out this plugin, and see that you've marked this resolved by allowing parameters in the parent project specification. Unfortunately, in the configuration UI, the parent project is specified by a drop-down that lists the available Publishers, without any way to use a variable. Can you either a) change that drop-down to allow us to type over what's there, or b) tell us which parameter it uses to obtain the workspace, so we can set that in the calling project? Jenkins ver 1.519, Jenkins clone workspace plugin ver 0.6

            I am experiencing the same problem in both versions 0.5 and 0.6 with Jenkins 1.519. It would be great to have this fixed because without this functionality the plugin is much less useful

            davfuenmayor David Fuenmayor added a comment - I am experiencing the same problem in both versions 0.5 and 0.6 with Jenkins 1.519. It would be great to have this fixed because without this functionality the plugin is much less useful
            greghansen Greg Hansen added a comment -

            I've gone to a scheme of syncing the sources in one project, then passing the machine name and workspace path from that job as parameters to the child processes. These child processes can then reach out and copy the sources to their own workspace to do the actual build. I have one parent project per branch, but can use a common set of build jobs. Turns an N x M problem into an N + M one.

            greghansen Greg Hansen added a comment - I've gone to a scheme of syncing the sources in one project, then passing the machine name and workspace path from that job as parameters to the child processes. These child processes can then reach out and copy the sources to their own workspace to do the actual build. I have one parent project per branch, but can use a common set of build jobs. Turns an N x M problem into an N + M one.

            There are two proposed fixes on github - 1 and 2. Right now this is kind of a showstopper for me unless I write some hack to work around it.

            The plugin hasn't been touched in two years and is on many lists of "essential Jenkins plugins." Is it still being maintained?

            aarondmarasco_vsi Aaron D. Marasco added a comment - There are two proposed fixes on github - 1 and 2 . Right now this is kind of a showstopper for me unless I write some hack to work around it. The plugin hasn't been touched in two years and is on many lists of "essential Jenkins plugins." Is it still being maintained?

            People

              Unassigned Unassigned
              compi Maik Richey
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: