[
https://issues.jboss.org/browse/JBIDE-18067?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-18067:
-------------------------------
Description:
The Naginator plugin [1] is now available in the JBoss Jenkins.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin
How should we use it? Hourly retries? Progressive retries? Regex-based retries (eg., for
github or nexus failures) ?
Here's one option: up to 3 hourly retries:
!naginator-retry-failed-builds.png!
was:
The Naginator plugin [1] is now available in the JBoss Jenkins.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin
How should we use it? Hourly retries? Progressive retries? Regex-based retries (eg., for
github or nexus failures) ?
!naginator-retry-failed-builds.png!
Consider using Naginator Jenkins plugin to retry builds that fail due
to transient issues
-----------------------------------------------------------------------------------------
Key: JBIDE-18067
URL:
https://issues.jboss.org/browse/JBIDE-18067
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Nick Boldt
Priority: Minor
Attachments: naginator-retry-failed-builds.png
The Naginator plugin [1] is now available in the JBoss Jenkins.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin
How should we use it? Hourly retries? Progressive retries? Regex-based retries (eg., for
github or nexus failures) ?
Here's one option: up to 3 hourly retries:
!naginator-retry-failed-builds.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)