Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
-
jenkins 2.36 (deb), maven-plugin 2.14, java 1.7.0_65
Description
I can't make naginator work with a regex expression.
I have the following console output:
Build was aborted Aborted by xxxxxxxxx [htmlpublisher] Archiving HTML reports... [htmlpublisher] Archiving at BUILD level C:\xxxxxxxxx\workspace\testSuiteExecution\target\surefire-reports to /var/lib/jenkins/jobs/testSuiteExecution/builds/534/htmlreports/HTML_Report ERROR: Specified HTML directory 'C:\xxxxxx\workspace\testSuiteExecution\target\surefire-reports' does not exist. Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Notifying upstream projects of job completion Finished: ABORTED
I use the naginator plugin to rebuild previous build only if the it was aborted. Therefore I put
(please view attachement)
But this isn't working. I tried many regex variations (eg Build was aborted), but with no luck
Attachments
Activity
ikedam Where does this statement come from?
Naginator should not take in mind the reason why you want to rebuild. Moreover, the issue was quite specific. That could not use regex as means of parsing the log output.
ikedam
added a comment - Naginator doesn't retrigger aborted builds automatically as the feature is "Retry build after failure".
"ABORTED" and "FAILURE" are considered different in Jenkins.
And that's not a bug.
You should click "Retry" link of the build after clicking "x" button to abort the build.
ikedam
added a comment - Naginator doesn't retrigger aborted builds automatically as the feature is "Retry build after failure".
"ABORTED" and "FAILURE" are considered different in Jenkins.
And that's not a bug.
You should click "Retry" link of the build after clicking "x" button to abort the build. ikedam this is the plugin's page
https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin
Second bullet is:
Only rebuild the job if the build's log output contains a given regular expression
Please tell me where is the misconception here
ikedam
added a comment - "Only" means you can specify an additional filter condition for failed builds to retrigger.
So retriggered builds are: failed AND matching regexp
not: failed OR matching regexp
It's used to retrigger builds failed with specific situations.
ikedam
added a comment - "Only" means you can specify an additional filter condition for failed builds to retrigger.
So retriggered builds are: failed AND matching regexp
not: failed OR matching regexp
It's used to retrigger builds failed with specific situations. ikedam
added a comment - I can't get what you mean, but that's apparent from the implementation and unittests of the plugin.
I conclude it's not a bug as a maintainer and don't fix it.
ikedam
added a comment - I can't get what you mean, but that's apparent from the implementation and unittests of the plugin.
I conclude it's not a bug as a maintainer and don't fix it.
Naginator doesn't reschedule aborted builds.
It reschedules only failed or unstable builds.