Bug 417268 - Monitored tasks should not fail because there is no Hudson valid job name
Summary: Monitored tasks should not fail because there is no Hudson valid job name
Status: ASSIGNED
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-14 14:09 EDT by Albert Boulanger CLA
Modified: 2014-01-17 13:54 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Boulanger CLA 2013-09-14 14:09:06 EDT 
Hi I had accidentally wiped out Hudson and had to be re-install. Meanwhile my monitored external tasks were failing in the monitoring process itself. Monitoring should be robust (or at least a switch -- I can think there are uses cases for both) so that the task can complete even if the monitoring mechanism itself fails somewhere along the line.

Here is an exmaple task execution that failed.
C:\Rudin\Weather\python>java -jar C:\Rudin\hudson-monitor\hudson-core-*.jar "Weather Observation Update on Anderson" cmd
.exe /c C:\Python27\python.exe C:\Rudin\Weather\python\weather_history.py
Weather Observation Update on Anderson is not a valid job name on http://hudson:rnateammon@bucky.ldeo.columbia.edu:8080/
 (Not Found)
PS C:\Rudin\Weather\python> .\obs-mon.bat
Comment 1 Albert Boulanger CLA 2013-09-18 11:59:22 EDT 
Also it should not fail if the recieving Hudson instance for some reason is down or even missing