-
New Feature
-
Resolution: Won't Do
-
Minor
-
None
-
Jenkins 2.24
Java 1.8.0_91
Pipeline 2.4
Pipeline Graph Analysis Plugin 1.2
Pipeline: API 2.4
Pipeline: Basic Steps 2.2
Pipeline: Build Step 2.3
Pipeline: Groovy 2.18
Pipeline: Input Step 2.1
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
Pipeline: Supporting APIs 2.8Jenkins 2.24 Java 1.8.0_91 Pipeline 2.4 Pipeline Graph Analysis Plugin 1.2 Pipeline: API 2.4 Pipeline: Basic Steps 2.2 Pipeline: Build Step 2.3 Pipeline: Groovy 2.18 Pipeline: Input Step 2.1 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 Pipeline: Supporting APIs 2.8
Currently, the only two options for a Pipeline definition are Pipeline script, and Pipeline script from SCM. Although our Jenkins file is included in our Git repository, we have slaves that do not have access to the repository. It would be nice if we could just pass in the script path (similar to the step in "Pipeline script from SCM) without forcing us to use SCM at the same time.
- is related to
-
JENKINS-39219 Pipeline from SCM options disappear
-
- Resolved
-
[JENKINS-39144] Add Pipeline definition option to build from specified script
Cam Spencer
added a comment - It would seem that I didn't realize this feature exists because the None option disappears after creating the job JENKINS-39219. If someone could close this and reference the version this was implemented that would be great.
Cam Spencer
added a comment - It would seem that I didn't realize this feature exists because the None option disappears after creating the job JENKINS-39219 . If someone could close this and reference the version this was implemented that would be great. You can always have an inline bootstrap script that load s the real Jenkinsfile after setting up a workspace somewhere.
I was updating the plugins on another Jenkins instance, and I noticed that there is an option for None when selecting the source control. I suppose this feature is already implemented then (though I'm not sure which version of what plugin is required)