-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Support for comment preservation is not actively being worked on
Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through features like the Pipeline Editor. Due to technical and time constraints, this is infeasible to do in the short term without a high level of engineering investment.
Problem
Would be nice to have support for comments in the ModelAST. TBD whether the comments are required to be fully round-trip aware, but for anyone using the ModelAST classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful.
- is related to
-
JENKINS-43005 Warn if there are comment strings in declarative pipeline when opened in editor
-
- Open
-
[JENKINS-38864] Add support for preserving comments and formatting for Jenkinsfile roundtrip
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Description | Original: Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
New:
{panel:title=Support for comment preservation is not actively being worked on|titleBGColor=lightgrey} Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through the editor. Due to technical constraints, this is infeasible to do in the short term without a high level of engineering time. {panel} *Problem* Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
Summary | Original: Add support for comments to the ModelAST | New: Add support for preserving comments and formatting for Jenkinsfile roundtrip |
Description |
Original:
{panel:title=Support for comment preservation is not actively being worked on|titleBGColor=lightgrey} Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through the editor. Due to technical constraints, this is infeasible to do in the short term without a high level of engineering time. {panel} *Problem* Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
New:
{panel:title=Support for comment preservation is not actively being worked on|titleBGColor=lightgrey} Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through features like the Pipeline Editor. Due to technical constraints, this is infeasible to do in the short term without a high level of engineering investment. {panel} *Problem* Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
Description |
Original:
{panel:title=Support for comment preservation is not actively being worked on|titleBGColor=lightgrey} Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through features like the Pipeline Editor. Due to technical constraints, this is infeasible to do in the short term without a high level of engineering investment. {panel} *Problem* Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
New:
{panel:title=Support for comment preservation is not actively being worked on|titleBGColor=lightgrey} Many users have asked for preservation of comments, formatting and "shebang"s when loading and saving a Jenkinsfile through features like the Pipeline Editor. Due to technical and time constraints, this is infeasible to do in the short term without a high level of engineering investment. {panel} *Problem* Would be nice to have support for comments in the {{ModelAST}}. TBD whether the comments are required to be fully round-trip aware, but for anyone using the {{ModelAST}} classes to generate a groovy pipeline definition the ability to inject comments into the generated groovy would be incredibly useful. |
Resolution | Original: Won't Fix [ 2 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
Link | New: This issue is related to JENKINS-43005 [ JENKINS-43005 ] |
Epic Link |
New:
|
Assignee | Original: Andrew Bayer [ abayer ] |