-
Notifications
You must be signed in to change notification settings - Fork 21
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
Upgrade POM (parent POM, minimum jenkins version, etc) #9
Conversation
Needed as we are scheduling the build twice. Unsure why the test was passing with a different value some years ago.
… skipped during serialization
1fff555
to
d7fa311
Compare
Could anyone please replay this PR build with the updated Jenkinsfile? |
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks a lot for the contribution. 👍
Windows build outputs [INFO] BUILD SUCCESS
but is marked as failed. 🤔
java.lang.AssertionError:
Expected 2-1:global-property:bar:anonymous in task output: [execute] $ cmd /c call C:\Jenkins\agent\workspace\Plugins_batch-task-plugin_PR-9\target\tmp\jenkins4380962449825284861.bat
C:\Jenkins\agent\workspace\Plugins_batch-task-plugin_PR-9\target\tmp\j h11703619928117714569\workspace\execute>echo "1-1:global-property:bar:anonymous"
"1-1:global-property:bar:anonymous"
C:\Jenkins\agent\workspace\Plugins_batch-task-plugin_PR-9\target\tmp\j h11703619928117714569\workspace\execute>exit 0
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.assertTrue(Assert.java:42)
at hudson.plugins.batch_task.BatchTaskTest.testExecute(BatchTaskTest.java:105)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:655)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.lang.Thread.run(Thread.java:833)
Well this is weird. I had to change the test expectations in 0749269 to that the expected $TASK_ID in the string would match the output (on Mac/Linux). This is because it appears that the tests scheduled 2 builds and then the build number is increased twice.
Is there anything obvious that would explain why on Windows the build number is only increased once? This test code is 15 years old. |
Remove the extra call to scheduleBuild2 and adjust expectations. Unsure why the test wasn't passing on Windows
Testing done
This is a work-in-progress, and an attempt to see if the CI builds are still triggered for this plugin.
The only testing done right now are the unit tests. One of them isn't passing anymore so it will have to be fixed in subsequent commit.
Submitter checklist