[JIRA] (JENKINS-60550) Determine if heavyweight or lightweight checkout was used for multibranch pipelines

8 views
Skip to first unread message

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:23:02 PM1/2/20
to jenkinsc...@googlegroups.com
Carroll Chiou updated an issue
 
Jenkins / Improvement JENKINS-60550
Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Change By: Carroll Chiou
Summary: Let SCMBinder indicate Determine if heavyweight or lightweight checkout was used for multibranch pipelines
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:24:02 PM1/2/20
to jenkinsc...@googlegroups.com
Carroll Chiou updated an issue
Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails.  There is no public way to tell which type of checkout was use. Propose adding Maybe we can add an isLightweight() method like in CpsScmFlowDefinition . ?

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:25:02 PM1/2/20
to jenkinsc...@googlegroups.com
Carroll Chiou updated an issue
Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails.  There is no public way to tell which type of checkout was use. Maybe we can add an isLightweight() method like in CpsScmFlowDefinition?

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:25:02 PM1/2/20
to jenkinsc...@googlegroups.com

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:25:03 PM1/2/20
to jenkinsc...@googlegroups.com
Carroll Chiou edited a comment on Improvement JENKINS-60550

cchiou@cloudbees.com (JIRA)

unread,
Jan 2, 2020, 4:26:02 PM1/2/20
to jenkinsc...@googlegroups.com
Carroll Chiou updated an issue
Change By: Carroll Chiou
Currently, SCMBinder will attempt to perform a lightweight checkout, falling back to heavyweight when that fails.   There   However, there is no public way to tell which type of checkout was use.
Reply all
Reply to author
Forward
0 new messages