![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Joe Hansche
|
|
Components:
|
confluence-publisher |
|
Created:
|
08/Feb/13 3:19 PM
|
|
Description:
|
I've run into a situation a couple of times in my environment where if our confluence site goes down (for whatever reason) the publish action for numerous jobs causes the run to fail. This causes QA and dev to question whether they should proceed with upgrades etc, and overall a lot of churn.
Using the flexible publisher I could devise a method to conditionally run the confluence post build action only if certain criterion were met that guaranteed the confluence site was available. However since the plugin already has the ability to look ahead to see if it can connect to a page it would be an ideal way to provide this switch to the user who does not want or know how to work around cases like mine.
Something like:
[X] Do not publish if the page does not exist
|
|
Environment:
|
Ubuntu 12.04 Server, Jenkins LTS 1.480.2
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Trivial]() Trivial
|
|
Reporter:
|
sid nancy
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
