Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-56121] Add option to (not) show raw yaml in console #459

Merged
merged 4 commits into from
May 9, 2019
Merged

[JENKINS-56121] Add option to (not) show raw yaml in console #459

merged 4 commits into from
May 9, 2019

Conversation

joyarzun
Copy link
Contributor

https://issues.jenkins-ci.org/browse/JENKINS-56121

Based on #451 @fredg02

Since the raw yaml can add quite some noise to the console log, an
option was added to disable it. Default is ShowRawYaml=true, so the
default behavior does not change.

Since the raw yaml can add quite some noise to the console log, an
option was added to disable it. Default is ShowRawYaml=true, so the
default behavior does not change.
@carlossg
Copy link
Contributor

carlossg commented May 8, 2019

I can't push to the PR, can you add this commit ?
435e2fc

@joyarzun
Copy link
Contributor Author

joyarzun commented May 9, 2019

I can't push to the PR, can you add this commit ?
435e2fc

I did the change requested but why change boolean to Boolean?

@carlossg
Copy link
Contributor

carlossg commented May 9, 2019

It's a tricky thing with Jenkins. On upgrade only the readResolve method is called, not the initializers. We need to set the value to true, so using a boolean we can see that if it is null it means we are upgrading and then set it to true.

@carlossg carlossg merged commit f3c1c7f into jenkinsci:master May 9, 2019
@joyarzun
Copy link
Contributor Author

joyarzun commented May 9, 2019

It's a tricky thing with Jenkins. On upgrade only the readResolve method is called, not the initializers. We need to set the value to true, so using a boolean we can see that if it is null it means we are upgrading and then set it to true.

Thanks for the explanation

@fredg02
Copy link
Member

fredg02 commented May 12, 2019

Thanks @joyarzun & @carlossg for picking this up and completing my PR. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants