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-57116] Fix empty yamls introduced on upgrade to 1.15.1 #462

Merged
merged 2 commits into from
May 9, 2019

Conversation

carlossg
Copy link
Contributor

Although I don't see were it could come from
Added logging to debug it

@carlossg carlossg requested a review from Vlatombe April 30, 2019 17:11
Although I don't see were it could come from
Added logging to debug it
Remove items with empty strings
Add tests
@carlossg carlossg changed the title [JENKINS-57116] Ensure we don't try to parse an empty yaml [JENKINS-57116] Fix empty yamls introduced on upgrade to 1.15.1 May 9, 2019
@carlossg
Copy link
Contributor Author

carlossg commented May 9, 2019

Ok, figured it out and fixed it. The config.xml may end having

<yamls>
<string></string>
</yamls>

@@ -47,7 +47,7 @@
<java.level>8</java.level>
<jenkins.version>2.138.4</jenkins.version>
<no-test-jar>false</no-test-jar>
<surefire.rerunFailingTestsCount>1</surefire.rerunFailingTestsCount>
<surefire.rerunFailingTestsCount>0</surefire.rerunFailingTestsCount>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@carlossg was there a flaky test we were using the rerun option for?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there have been some flaky tests in the past, but I'd rather avoid rerunning and fix them, and we have 2 different builds happening

@carlossg carlossg merged commit 46cdc75 into master May 9, 2019
@carlossg carlossg deleted the JENKINS-57116 branch May 9, 2019 13:15
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.

2 participants