Skip to content

Conversation

@romanisb
Copy link
Contributor

In cases of using a log plugin to write build logs to a log storage such as Elasticsearch/OpenSearch, Logstash, etc., there is no need to also write the build logs to stdout. This will avoid redundant log entries if for example the JFR is executed on Kubernetes with an ELK setup which writes containers logs to the some log storage.

This change proposes a new PipelineRun options in which the log lines of the actual build are not written into stdout.
The build logs are then only written if a log plugin is installed and configured in the JFR image.

Testing done

### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

…f Jenkins

* Add --no-stdout option to disable logging to stdout of Jenkins

* Change option name to --no-build-logs
@romanisb romanisb requested a review from a team as a code owner June 14, 2023 12:27
@oleg-nenashev oleg-nenashev added the enhancement New feature or request label Jun 14, 2023
@oleg-nenashev oleg-nenashev merged commit e21031b into jenkinsci:main Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants