[JIRA] (JENKINS-23445) Can't use matrix-project with multiple-scms

9 views
Skip to first unread message

fabribait+jk20@gmail.com (JIRA)

unread,
Jan 20, 2020, 8:25:07 AM1/20/20
to jenkinsc...@googlegroups.com
fabri ba updated an issue
 
Jenkins / Bug JENKINS-23445
Can't use matrix-project with multiple-scms
Change By: fabri ba
On "master" task, no problem, jenkins checkout good repo and branch.

But on "slave" tasks, It checkout the same branch for all scm (git in my case).

How-to reproduce?
* create a multiconfiguration project
* Add 2 scm git
** 1 for
repo/ branch master (on / by default , or on dir "A", irrelevant )
** 2 for
repo/ branch debian B and put it on dir " debian B "
* add configuration matrix, with one axis that can take multiple values
/debian
On slave the folders structure gets created correctly, but the second one is empty.

When checking the console output, the "master" task clones and checks out the two repos correctly (different revision numbers (long string, probably a hash) for each of the 2 repos).

Each of the "slave" tasks defined by the configuration matrix,
will be try to fetch and checkout the same than / revision number for both repos, and therefore will fail :) on the second one.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

fabribait+jk20@gmail.com (JIRA)

unread,
Jan 20, 2020, 8:26:07 AM1/20/20
to jenkinsc...@googlegroups.com

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 20, 2020, 8:46:08 AM1/20/20
to jenkinsc...@googlegroups.com

fabri ba

The Jenkins Pipeline provides this facility in a more flexible, reliable, and supportable way. Rather than using a matrix configuration job, use:

If there is some critical reason that you cannot use Declarative Pipeline, then use:

Declarative Pipeline should be the first path because it intentionally limits the types of mistakes that a new user can make. It is the second generation of Jenkins Pipeline domain specific language. It uses what was learned from the first generation language (scripted) to intentionally reduce user mistakes.

Declarative Pipeline jobs can be defined graphically with Jenkins Blue Ocean. See the Jenkins Minute series for brief clips that illustrate Pipeline editing with Blue Ocean:

If you prefer a longer session, you could view:

mark.earl.waite@gmail.com (JIRA)

unread,
Jan 20, 2020, 8:46:12 AM1/20/20
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Bug JENKINS-23445
[~fbjkins]


The Jenkins Pipeline provides this facility in a more flexible, reliable, and supportable way.  Rather than using a matrix configuration job, use:


If there is some critical reason that you cannot use Declarative Pipeline, then use:

Declarative Pipeline should be the first path because it intentionally limits the types of mistakes that a new user can make.  It is the second generation of Jenkins Pipeline domain specific language.  It uses what was learned from the first generation language (scripted) to intentionally reduce user mistakes.

Declarative Pipeline jobs can be defined graphically with Jenkins Blue Ocean.  See the Jenkins Minute series for brief clips that illustrate Pipeline editing with Blue Ocean:


If you prefer a longer session, you could view:
* [Declarative Pipeline with Jenkins|https://youtu.be/79HfmjeOTEI]

fabribait+jk20@gmail.com (JIRA)

unread,
Jan 20, 2020, 10:06:07 AM1/20/20
to jenkinsc...@googlegroups.com
fabri ba commented on Bug JENKINS-23445

Thank you Mark Waite I'll have a look into that, appreciate your help!

Reply all
Reply to author
Forward
0 new messages