![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
urltrigger |
|
Created:
|
02/Jun/14 5:30 PM
|
|
Description:
|
0.37 version of the urltrigger plugin
Configuration: URLTrigger on machine #1 grabs the last successful build on machine #2 via url. cron schedule is every hour during business hours. The cron job does not run overnight.
Use Case:
1. URLTrigger on machine #1 starts up and stores the URL contents from machine #2 in-memory.
2. URLTrigger runs on cron schedule and compares URL in-memory contents and triggers build when the contents are different.
3. cron schedule stops polling hourly.
4. Build on machine #2 updates the last successful build.
5. Manual trigger of job on machine #1. The shell script grabs the last successful build from machine #2.
6. It's morning again and the URL trigger cron job starts up. It grabs the last successful build from step #4 because there was no way for step #5 to communicate to the filter that the in-memory URL value should be updated off-cycle.
It would be great if there was some way to prompt the plugin to update its in-memory cached information and/or provide a new value for the in-memory cached information. In that way, the manual build could communicate with the URLTrigger plugin and we could avoid our scenario.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
c reilly
|
|
|
|
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/d/optout.
