[JIRA] (JENKINS-39219) Pipeline from SCM options disappear

6 views
Skip to first unread message

cameron.spencer@caseware.com (JIRA)

unread,
Oct 24, 2016, 2:06:01 PM10/24/16
to jenkinsc...@googlegroups.com
Cam Spencer created an issue
 
Jenkins / Bug JENKINS-39219
Pipeline from SCM options disappear
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: Pipeline from SCM Bug.png, Pipeline from SCM Expected.png
Components: pipeline
Created: 2016/Oct/24 6:05 PM
Environment: Jenkins 2.19.1
Java 1.8.0_101
Pipeline 2.4
Priority: Major Major
Reporter: Cam Spencer

When I create a new Pipeline job, there are 5 options for the build step Pipeline script from SCM (None, CVS, CVS Projectset, Git, Subversion). After I save the new job, when I go to Configure, some of the options disappear.

Steps:

  1. Create a new Pipeline job
  2. Set Pipeline script from SCM to None
  3. Save the job
  4. Configure the job

EXPECTED: None is still selected
BUG: None and other options are removed from the list
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

cameron.spencer@caseware.com (JIRA)

unread,
Oct 24, 2016, 2:20:02 PM10/24/16
to jenkinsc...@googlegroups.com
Cam Spencer updated an issue
Change By: Cam Spencer
When I create a new Pipeline job, there are 5 options for the build step {{Pipeline script from SCM}} (None, CVS, CVS Projectset, Git, Subversion). After I save the new job, when I go to {{Configure}}, some of the options disappear.

Steps:
# Create a new Pipeline job
# Set {{Pipeline script from SCM}} to {{None}}
# Save the job
# Configure the job


EXPECTED: {{None}} is still selected
BUG: {{None}} and other options are removed from the list


Complete list of Pipeline plugins in use

{code:java}
Pipeline 2.4
Pipeline Graph Analysis Plugin 1.2   
Pipeline: API  2.5
Pipeline: Basic Steps 2.2
Pipeline: Build Step 2.3
Pipeline: Groovy 2.21
Pipeline: Input Step 2.3
Pipeline: Job 2.7
Pipeline: Milestone Step 1.1
Pipeline: Multibranch 2.9
Pipeline: Nodes and Processes 2.5
Pipeline: REST API Plugin 2.1
Pipeline: SCM Step 2.2
Pipeline: Shared Groovy Libraries 2.4
Pipeline: Stage Step 2.2
Pipeline: Stage View Plugin 2.1
Pipeline: Step API 2.4
{code}

cameron.spencer@caseware.com (JIRA)

unread,
Oct 24, 2016, 2:22:01 PM10/24/16
to jenkinsc...@googlegroups.com
Cam Spencer updated an issue
Change By: Cam Spencer
Component/s: workflow-scm-step-plugin

jglick@cloudbees.com (JIRA)

unread,
Nov 10, 2016, 12:22:02 PM11/10/16
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
Change By: Jesse Glick
Component/s: pipeline

jglick@cloudbees.com (JIRA)

unread,
Nov 10, 2016, 12:26:01 PM11/10/16
to jenkinsc...@googlegroups.com
Jesse Glick commented on Bug JENKINS-39219
 
Re: Pipeline from SCM options disappear

Actually the bug, if it is indeed reproducible, is that the inappropriate options (SCMs not yet compatible with Pipeline, and None) are offered the first time. StaplerReferer hack not working, perhaps.

stefan.drissen@gmail.com (JIRA)

unread,
Feb 9, 2017, 7:00:01 PM2/9/17
to jenkinsc...@googlegroups.com
Stefan Drissen edited a comment on Bug JENKINS-39219
Using 2.45 and all plug-ins updated to latest on Windows 10.

I have the same issue with Team Foundation Version Control (TFVC) - it is shown as SCM option (None / GIT / TFVC) with all the valid options for TFVC when creating the pipeline.

Building fails with:
{quote}     java.lang.AbstractMethodError: you must override the new overload of checkout
     at hudson.scm.SCM.checkout(SCM.java:489)
     at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
     at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
     at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57)
     at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215)
     at hudson.model.ResourceController.execute(ResourceController.java:98)
     at hudson.model.Executor.run(Executor.java:405)
    Finished: FAILURE {quote}

Reopening the pipeline shows Git as only valid SCM option.

stefan.drissen@gmail.com (JIRA)

unread,
Feb 9, 2017, 7:00:01 PM2/9/17
to jenkinsc...@googlegroups.com

Using 2.45 and all plug-ins updated to latest on Windows 10.

I have the same issue with Team Foundation Version Control (TFVC) - it is shown as SCM option (None / GIT / TFVC) with all the valid options for TFVC when creating the pipeline.

Building fails with:

java.lang.AbstractMethodError: you must override the new overload of checkout


at hudson.scm.SCM.checkout(SCM.java:489)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Finished: FAILURE

Reopening the pipeline shows Git as only valid SCM option.

stefan.drissen@gmail.com (JIRA)

unread,
Feb 9, 2017, 7:01:01 PM2/9/17
to jenkinsc...@googlegroups.com
Stefan Drissen edited a comment on Bug JENKINS-39219
Using 2.45 and all plug-ins updated to latest on Windows 10.

I have the same issue with Team Foundation Version Control (TFVC) - it is shown as SCM option (None / GIT / TFVC) with all the valid options for TFVC when creating the pipeline.

Building fails with:
{ quote} { java.lang.AbstractMethodError: you must override the new overload of checkout

at hudson.scm.SCM.checkout(SCM.java:489)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Finished: FAILURE {quote } }

Reopening the pipeline shows Git as only valid SCM option.

stefan.drissen@gmail.com (JIRA)

unread,
Feb 9, 2017, 7:02:01 PM2/9/17
to jenkinsc...@googlegroups.com
Stefan Drissen edited a comment on Bug JENKINS-39219
Using 2.45 and all plug-ins updated to latest on Windows 10.

I have the same issue with Team Foundation Version Control (TFVC) - it is shown as SCM option (None / GIT / TFVC) with all the valid options for TFVC when creating the pipeline.

Building fails with:
{ { noformat}
java.lang.AbstractMethodError: you must override the new overload of checkout
at hudson.scm.SCM.checkout(SCM.java:489)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:57)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:405)
Finished: FAILURE

{noformat } }

Reopening the pipeline shows Git as only valid SCM option.

jglick@cloudbees.com (JIRA)

unread,
Mar 3, 2017, 2:53:02 PM3/3/17
to jenkinsc...@googlegroups.com
Jesse Glick resolved as Duplicate
 
Change By: Jesse Glick
Status: Open Resolved
Resolution: Duplicate

yotu.tuy@gmail.com (JIRA)

unread,
Jul 5, 2019, 5:08:01 AM7/5/19
to jenkinsc...@googlegroups.com
Karolina Arancibia Valuskova commented on Bug JENKINS-39219
 
Re: Pipeline from SCM options disappear

was this actually solved? I run into the same issue in version 2.176.1
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

tal@cedato.com (JIRA)

unread,
Jul 16, 2019, 9:52:02 AM7/16/19
to jenkinsc...@googlegroups.com
tal z commented on Bug JENKINS-39219

same problem here....

tal@cedato.com (JIRA)

unread,
Jul 16, 2019, 9:56:02 AM7/16/19
to jenkinsc...@googlegroups.com
tal z edited a comment on Bug JENKINS-39219
same problem here....

version 2.176.1

tal@cedato.com (JIRA)

unread,
Jul 16, 2019, 2:02:03 PM7/16/19
to jenkinsc...@googlegroups.com
tal z commented on Bug JENKINS-39219

Karolina Arancibia Valuskova , did you solve it by downgrade to lower jenkins version?

Thanks

yotu.tuy@gmail.com (JIRA)

unread,
Jul 18, 2019, 5:34:02 AM7/18/19
to jenkinsc...@googlegroups.com

tal z no, as a work around I change the pipeline > definition to: **pipeline script. Save. Then change again to pipeline script from SCM, and then the SCM options are back. it is a bit of a pain, but since we are planning to use a repository in the future, it is not a big issue for us. Hope that helps until this is fixed.
Reply all
Reply to author
Forward
0 new messages