Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
The current user experience in Jenkow plugin is such that.
- you create a new job, specifying a non-existent workflow name
- you run the build once, make it fail (this is when the plugin internally creates a skeleton workflow file)
- you checkout the newly created bpmn file, and edit it.
This idea of inducing a failure to have it created it is bit strange, and it also has an undesirable side-effect that if you have a typo in the workflow name, you end up creating one.
I think a better user experience is:
- you create a new job, specifying a non-existent workflow name
- form validation gives you a button/link that lets you create new template workflow files (or copy from existing one, which is likely useful, too) see Subversion plugin for how it does this, when the user types in a repository URL for which it doesn't yet have a credential.
Code changed in jenkins
User: Max Spring
Path:
jenkow-plugin/src/main/java/com/cisco/step/jenkins/plugins/jenkow/JenkowBuilder.java
http://jenkins-ci.org/commit/jenkow-plugin/ac27f4cd4ebc0f1e912dbdf717d42a30634ccb68
Log:
fixed
JENKINS-15341