[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

[dbeck@cloudbees.com (JIRA)]

Daniel Beck created an issue

Jenkins / JENKINS-42216 Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2017/Feb/21 2:12 PM Environment: Jenkins 2.32.2 Pipeline Groovy 2.27 TFS Plugin 5.3.1 Labels: stapler Priority: Minor Reporter: Daniel Beck Possibly bug in CpsScmFlowDefinition, or a Stapler issue. Install Pipeline and TFS Plugin. Create a Pipeline job. TFVC is offered in the 'Pipeline from SCM' when it shouldn't be, as it's missing the checkout(Job) override (and doesn't override isApplicable(Job)). Configure 'Pipeline from SCM: None", Apply, and reload. It will select Git, as it's the only applicable one now (NullSCM isn't either). Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-42216

Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config CpsScmFlowDefinition.DescriptorImpl.getApplicableDescriptors needs to use StaplerReferer.findItemFromRequest.

Add Comment

[andrew.bayer@gmail.com (JIRA)]

Andrew Bayer assigned an issue to Andrew Bayer

Jenkins / JENKINS-42216

Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

Change By: Andrew Bayer Assignee: Andrew Bayer

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[andrew.bayer@gmail.com (JIRA)]

Andrew Bayer commented on JENKINS-42216

Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Throwing this on my to-do list - the actual change is trivial, but I need to take the time to write a WebClient test to actually verify it works. And I'm not in the mood at the moment, so I'll do it later. =)

Add Comment

[vivek.pandey@gmail.com (JIRA)]

Vivek Pandey updated an issue

Jenkins / JENKINS-42216

Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

Change By: Vivek Pandey Labels: stapler triaged-2018-11

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[yotu.tuy@gmail.com (JIRA)]

Karolina Arancibia Valuskova commented on JENKINS-42216

Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue.

Add Comment

[yotu.tuy@gmail.com (JIRA)]

Karolina Arancibia Valuskova edited a comment on JENKINS-42216

Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue.

This is blocking the build of the job, since it throws a NP when it tries to find the scm

Add Comment

[yotu.tuy@gmail.com (JIRA)]

Karolina Arancibia Valuskova edited a comment on JENKINS-42216

Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config

Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue.

This is blocking the build of the job, since it throws a NP Null Pointer when it tries to find the scm even though I specified it as 'None'

Add Comment