-
Bug
-
Resolution: Fixed
-
Major
When I create a simple project and add Execute shell task,
after save, the task contents are empty.
config.xml on the server is empty too:
<hudson.tasks.Shell><command/></hudson.tasks.Shell>
When editing the config a second time, the contents are saved properly.
Each consecutive add of shell task requires a second edit.
When using inheritance plugin, there is no way to workaround the bug, since each edit creates new revision, and all shell tasks are empty.
I tested it on 1.563 and 1.564
- is blocking
-
JENKINS-28769 Enable syntax highlighting on workflow DSL
-
- Resolved
-
- is related to
-
JENKINS-23148 Accessibility problem when editing shell script in the configuration of a job
-
- Open
-
-
JENKINS-15604 checkUrl and codemirror-mode do not mix
-
- Resolved
-
-
JENKINS-23632 LTS: JENKINS-23151 workaround
-
- Resolved
-
-
JENKINS-23026 Parameterized build can not save the "Parameter Description" in the first time
-
- Resolved
-
-
JENKINS-9130 Add a dynamic parser to colorize and indent groovy textareas
-
- Resolved
-
[JENKINS-23151] codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly)
Component/s | New: core [ 15593 ] | |
Component/s | Original: build-pipeline [ 15962 ] | |
Affects Version/s | Original: current [ 10162 ] | |
Description |
Original:
When I create a simple project and add Execute shell task, after save, the task contents are empty. config.xml on the server is empty too: {code} <hudson.tasks.Shell><command/></hudson.tasks.Shell> {code} When editing the config a second time, the contents are saved properly. Each consecutive add of shell task requires a second edit. When using inheritance plugin, there is no way to workaround the bug, since each edit creates new revision, and all shell tasks are empty. I tested it on 1.563 and 1564 |
New:
When I create a simple project and add Execute shell task, after save, the task contents are empty. config.xml on the server is empty too: {code} <hudson.tasks.Shell><command/></hudson.tasks.Shell> {code} When editing the config a second time, the contents are saved properly. Each consecutive add of shell task requires a second edit. When using inheritance plugin, there is no way to workaround the bug, since each edit creates new revision, and all shell tasks are empty. I tested it on 1.563 and 1.564 |
Summary | Original: Execute shell window not saved properly | New: Execute shell build step text not saved properly |
Assignee | New: Daniel Beck [ danielbeck ] |
Assignee | Original: Daniel Beck [ danielbeck ] |
Link |
New:
This issue is related to |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Labels | New: codemirror |
Assignee | Original: Jesse Glick [ jglick ] | |
Summary | Original: Execute shell build step text not saved properly | New: codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly) |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Link | New: This issue is related to JENKINS-23148 [ JENKINS-23148 ] |