Status: Closed (View Workflow)
- Core 2.78
- Experimental update center enabled
- Blue Ocean 1.3.0-beta-2, incl. editor
- Declarative 1.2-beta4
- GitHub Enterprise. Not a new pipeline, just a particular branch in an existing repo that I'd been testing with for a while.
- Fedora Workstation 26
- Google Chrome 61.0.3163.79Jenkins: - Core 2.78 - Experimental update center enabled - Blue Ocean 1.3.0-beta-2, incl. editor - Declarative 1.2-beta4 SCM: - GitHub Enterprise. Not a new pipeline, just a particular branch in an existing repo that I'd been testing with for a while. Client: - Fedora Workstation 26 - Google Chrome 61.0.3163.79
Sprint:Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2
In some cases you can make an invalid edit to a script block and it will show a warning, but it may be illegible (it is possbile that some cases slip through the validator and the user ends up with a non valid declarative file and the visual editor can be invoked).
Karl Shultz would be good if we could try this again (I build from master) to see if we can see any case where going from the editor gets to a non re-openable state (editing it by hand - well all bets are off in that case anyway).
- original from karl follows ---*
Given an existing, working Jenkinsfile which includes two parallel stages (supported by Declarative 1.2-beta4), saving changes to this Jenkinsfile from the Blue Ocean editor (1.3-beta2) is inop.
Not 100% reproducible, even with the same repos and branches.
1. A known-good Jenkinsfile in a remote repository, which includes at least one pair of parallel stages that are compliant with Declarative 1.2-beta4. I'm testing with a GitHub enterprise server.
3. A sample Jenkinsfile with which to recreate this problem is shown below:
4. Click Save. Provide a description of the change, then click "Save and Run." In this example I'm attempting to commit the changes straight to verify-parallel-lengths, but choosing a new branch name also demonstrates the problem:
5. You'll get an "Error - Bad request" message, and the change won't get saved.
6. I was not able to recreate this when editing master.
I will run back through this with the dev console open when I'm not multitasking taking screen shots, and grab a HAR file.