-
New Feature
-
Resolution: Fixed
-
Major
-
None
Allow the workflow to (visually) configure an SCM, check it out into a workspace on the Jenkins master, and load a sandboxed Groovy script from a defined location in that workspace.
Perhaps allow the workspace to be treated as a sourcepath so libraries can be imported.
Optionally include the flow SCM in polling and/or changelog generation.
Abandoned ideas:
- Construct URL with an instance of URLStreamHandler we can create a URL space that can access files over FilePath, and somehow prevent the class loader from continuing to use the workspace after it goes out of scope.
- Similar but the URLStreamHandler uses SCMSource to access files without ever checking out anything.
- is related to
-
JENKINS-26129 Multibranch workflow projects
-
- Resolved
-
- links to
Code changed in jenkins
User: Jesse Glick
Path:
cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java
cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction.java
cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction2.java
cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java
cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly
http://jenkins-ci.org/commit/workflow-plugin/50be69d7db0fff857f044bf725bcb0f1d8d0e7a2
Log:
JENKINS-26101Proof of concept of flow definition loaded entirely from a local SCM checkout.Compare: https://github.com/jenkinsci/workflow-plugin/compare/0d2226288236^...50be69d7db0f