-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows 10 Pro 64 bit
JRE 1.8.0_66
Jenkins 2.46.3
PlasticSCM plugin 2.9
Running Jenkins directly
Windows Installer
Google Chrome 59.0.3071.115
In the Pipeline section of a pipeline project I have "Pipeline script from SCM" selected.
Upon initial creation of the project my options for SCM are Git, Subversion, and Plastic SCM. I can make a project and save and apply and it works just fine. Whenever I try to enter the configure menu again for that same project the Plastic SCM option is taken away and the default option of Git is selected. I can then no longer make any changes to the configuration of the project because I can no longer select Plastic SCM to pull my pipeline file from.
This starting happening on my first pipeline project, the freestyle projects seem to work with the Plastic plugin just fine.
If I try to create a new project through reproducing one of these projects that no longer have the Plastic SCM option available, the option will also not be available in the new project.
In the jenkins.err.log I'm noticing this popping up on the builds for that project once this starts to happen.
INFO: {project} #{build number} completed: FAILURE
{timestamp} org.jenkinsci.plugins.workflow.flow.FlowExecutionList unregister
WARNING: Owner{project}/{build number}:{project}#{build number} was not in the list to begin with: []
{timestamp} org.jenkinsci.plugins.workflow.job.WorkflowRun finish
- is duplicated by
-
-
- Closed
-
[JENKINS-45321] Plastic-SCM plastic option disappears after initial creation of a pipeline project
Benjamin Buchfink
added a comment - There is a fix mentioned in the releasenotes of Plastic SCM version 7.0.16.1902:
[Quote]
Jenkins plugin: There was an issue configuring existing pipeline projects. The PlasticSCM entry didn't appear in the SCM dropdown list if the pipeline was set to get the script from SCM. Fixed.
[/Quote]
But this release is one of those experimental "lab release" ones... So, I haven't tried it jet.
Benjamin Buchfink
added a comment - There is a fix mentioned in the releasenotes of Plastic SCM version 7.0.16.1902:
see here
[Quote]
Jenkins plugin: There was an issue configuring existing pipeline projects. The PlasticSCM entry didn't appear in the SCM dropdown list if the pipeline was set to get the script from SCM. Fixed.
[/Quote]
But this release is one of those experimental "lab release" ones... So, I haven't tried it jet. Thanks swsbb. I have tried updating Plastic SCM to 7.0.16.1912 on the Jenkins master machine, but the problem remains. I should add that I am testing this under Ubuntu 16.04.3 LTS.
Confirmation from Codice Software that they have a bugfix, the bugfix is not in the Plastic SCM commandline software but in the Plastic SCM Jenkins plugin, and the bugfix is in the process of being published.
The fix is live in Plastic SCM plugin 2.10. Confirmed to work on my Jenkins instance. Thanks!
I see this as well. When I need to edit project settings for a pipeline project which has "Pipeline script from SCM" and uses Plastic, my current workaround is as follows:
(0. The first time you set up your project, note the SCM configuration somewhere outside of Jenkins, so it can be re-used.)
1. Open the project settings. Notice that the Plastic SCM option is gone and the SCM configuration is void.
2. Switch to "Pipeline Script". Make the desired changes to project settings, and click Save. (This will reconfigure the project to point to another SCM provider.)
3. Open the project settings again.
4. Switch to "Pipeline script from SCM", switch to Plastic SCM, paste in the appropriate SCM configuration, and click Save.
It's not great but it works for us for the time being.