-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 2.19.1
Java 1.8.0_101
Pipeline 2.4
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
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
- blocks
-
-
- Resolved
-
- duplicates
-
-
- Open
-
- is related to
-
JENKINS-39144 Add Pipeline definition option to build from specified script
-
- Resolved
-
[JENKINS-39219] Pipeline from SCM options disappear
Cam Spencer
created issue -
Cam Spencer
made changes -
| Link |
New:
This issue is related to |
Cam Spencer
made changes -
| Description |
Original:
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 |
New:
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} |
Cam Spencer
made changes -
| Component/s | New: workflow-scm-step-plugin [ 21717 ] |
| Component/s | Original: pipeline [ 21692 ] |
| Link |
New:
This issue blocks |
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.
| Link | New: This issue duplicates JENKINS-42216 [ JENKINS-42216 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
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.