Hi ikedam,

The Downstream of seems a feasible solution for our problem.

Am I correct: This selector is not subject to the "plugin" property problem because:

  1. The iteration on the builds of SubJob will be handled internally and
  2. the "plugin" property will not be verified?
    (i.e. it is not a bare string comparison)

So, if I see it correct, the configuration would be as follows:

  • Job 1: DepJob
  • Job 2: SubJob
    • Build selector for Copy Artifact Parameter: SELECT_ME
      • Default selector : Specific build
      • Build number : 123
    • Build step: Copy artifacts from another project:
      • Project Name : DepJob
      • Which build : Specified by a build parameter
        • Parameter Name : SELECT_ME
  • Job 3: MainJob
    • Build selector for Copy Artifact Parameter: SELECT_DEPJOB
      • Default selector : Downstream of
      • Upstream project : DepJob
      • Build number : 123
    • Build step: Copy artifacts from another project:
      • Project Name : SubJob
      • Which build : Specified by a build parameter
        • Parameter Name : SELECT_DEPJOB
      • Parameter filters : none
Just one final remark

Shouldn't it be called Upstream of instead of Downstream of?

Rationale: In the MainJob configuration: You choose the upstream (i.e. DepJob) project selection of the SubJob.

P.S. Thank you very much for the quick responses! It is really appreciated!

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to