[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-39219 Re: Pipeline from SCM options disappear 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.15160.1563442440189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title tal z commented on JENKINS-39219 Re: Pipeline from SCM options disappear Karolina Arancibia Valuskova , did you solve it by downgrade to lower jenkins version? Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.12550.1563300120802%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title tal z edited a comment on JENKINS-39219 Re: Pipeline from SCM options disappear same problem here version 2.176.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.12198.1563285360658%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title tal z commented on JENKINS-39219 Re: Pipeline from SCM options disappear same problem here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.12190.1563285120337%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-39219 Re: Pipeline from SCM options disappear was this actually solved? I run into the same issue in version 2.176.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175646.1477332308000.2236.1562317680160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39219 Pipeline from SCM options disappear Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title
Stefan Drissen edited a comment on JENKINS-39219
Re: Pipeline from SCM options disappear
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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title
Stefan Drissen edited a comment on JENKINS-39219
Re: Pipeline from SCM options disappear
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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Stefan Drissen commented on JENKINS-39219 Re: Pipeline from SCM options disappear 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title
Stefan Drissen edited a comment on JENKINS-39219
Re: Pipeline from SCM options disappear
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.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Jesse Glick commented on 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. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39219 Pipeline from SCM options disappear Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Cam Spencer updated an issue Jenkins / JENKINS-39219 Pipeline from SCM options disappear Change By: Cam Spencer Component/s: workflow-scm-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title
Cam Spencer updated an issue
Jenkins / JENKINS-39219
Pipeline from SCM options disappear
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 jobEXPECTED: {{None}} is still selectedBUG: {{None}} and other options are removed from the list Complete list of Pipeline plugins in use{code:java}Pipeline 2.4Pipeline Graph Analysis Plugin 1.2 Pipeline: API 2.5Pipeline: Basic Steps 2.2 Pipeline: Build Step 2.3 Pipeline: Groovy 2.21Pipeline: 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}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Cam Spencer created an issue Jenkins / JENKINS-39219 Pipeline from SCM options disappear Issue Type: 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 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: 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
