At least within a block step, it should be possible to set something like a ConsoleLogFilter to decorate the output written to TaskListener. Possible use cases:
- Replacement for decorateLogger in SimpleBuildWrapper.
- Ability to mask passwords from BindingStep in credentials-binding (unless there is an equivalent to getSensitiveBuildVariables moved up to Run).
- is blocking
-
JENKINS-27486 Workflow step to mask console output
-
- Resolved
-
-
JENKINS-27207 Add timestamps to workflow console output
-
- Resolved
-
-
JENKINS-24673 SimpleBuildWrapper
-
- Resolved
-
- is related to
-
JENKINS-30777 ConsoleLogFilter isn't truly global
-
- Open
-
-
JENKINS-26053 Handle ConsoleAnnotator
-
- Open
-
- relates to
-
JENKINS-43814 Password parameters should be hidden in pipeline logs by default
-
- Open
-
- links to
(1 relates to, 3 links to)
[JENKINS-27392] API to decorate console output
Link |
New:
This issue is blocking |
Link |
New:
This issue is blocking |
Link |
New:
This issue is blocking |
Link | New: This issue is related to JENKINS-26053 [ JENKINS-26053 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Suggested API: reuse ConsoleLogFilter (passing null for the AbstractBuild argument and requiring implementations to be Serializable), where you can pass this in to BodyInvoker.withContexts (first checking for an instance in your own context to delegate to).
OutputStream SimpleBuildWrapper.decorateLogger(AbstractBuild, OutputStream) could then be made to delegate to a new method ConsoleLogFilter SimpleBuildWrapper.createDecorator(Run<?,?> build) if the API were copied into core, and CoreWrapperStep (PR 37) needs to call that.