[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline

1 view
Skip to first unread message

andrew.bayer@gmail.com (JIRA)

unread,
Dec 6, 2018, 10:20:02 AM12/6/18
to jenkinsc...@googlegroups.com
Andrew Bayer updated an issue
 
Jenkins / Improvement JENKINS-49142
Be able to customize checkout as "options" in declarative pipeline
Change By: Andrew Bayer
Sprint: Declarative backlog
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jtaboada@cloudbees.com (JIRA)

unread,
Dec 11, 2018, 4:15:01 AM12/11/18
to jenkinsc...@googlegroups.com
Change By: Jose Blas Camacho Taboada
Assignee: Jose Blas Camacho Taboada

jtaboada@cloudbees.com (JIRA)

unread,
Dec 11, 2018, 10:08:03 AM12/11/18
to jenkinsc...@googlegroups.com
Status: Open In Progress

vivek.pandey@gmail.com (JIRA)

unread,
Dec 11, 2018, 1:02:01 PM12/11/18
to jenkinsc...@googlegroups.com
Vivek Pandey updated an issue
Change By: Vivek Pandey
Labels: triaged-2018-11

jtaboada@cloudbees.com (JIRA)

unread,
Dec 14, 2018, 3:19:01 AM12/14/18
to jenkinsc...@googlegroups.com
Change By: Jose Blas Camacho Taboada
Status: In Progress Review

jtaboada@cloudbees.com (JIRA)

unread,
Dec 17, 2018, 7:33:02 AM12/17/18
to jenkinsc...@googlegroups.com
Status: In Review Progress

jtaboada@cloudbees.com (JIRA)

unread,
Dec 18, 2018, 4:15:02 AM12/18/18
to jenkinsc...@googlegroups.com

jtaboada@cloudbees.com (JIRA)

unread,
Dec 19, 2018, 4:17:02 AM12/19/18
to jenkinsc...@googlegroups.com
Status: In Progress Review

jtaboada@cloudbees.com (JIRA)

unread,
Jan 11, 2019, 10:05:03 AM1/11/19
to jenkinsc...@googlegroups.com
Status: In Review Progress

jtaboada@cloudbees.com (JIRA)

unread,
Jan 11, 2019, 10:05:04 AM1/11/19
to jenkinsc...@googlegroups.com
Status: In Progress Open

brian.murrell@intel.com (JIRA)

unread,
Feb 10, 2020, 12:13:51 PM2/10/20
to jenkinsc...@googlegroups.com
Brian J Murrell commented on Improvement JENKINS-49142
 
Re: Be able to customize checkout as "options" in declarative pipeline

This is sorely needed.  It's a pity to see that the PR for it died on the vine. It seems the perfect became the enemy of the good perhaps.

In any case, all of the zillions of work-arounds (git command in sh step, scm command in stage steps, etc.) for updating submodules once the per-stage default scm checkout is done don't work if the Dockerfile that the stage is supposed to use for it's agent is in the submodule that needs to be checked-out/updated.
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages