-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Hudson ver. 1.367
I've created a batch task foo for a project that did not have any batch tasks before. Then I've added my project name to "Post-build Actions"/"Invoke batch tasks". The dropt down list was empty. Then I've pressed "Save" and openeded the project configuration agian. Now "Post-build Actions"/"Invoke batch tasks" showed "foo" automatically. So things appear to be ok. But when I run the build, I get an error "ERROR: No such task exists: . Perhaps you meant foo". So I open the configuration again, just click on the "Post-build Actions"/"Invoke batch tasks" drow down list and save it. Then things work.
[JENKINS-7030] batch-task reference invalid
Axel Heider
added a comment - Consider it more a usability isse then. 
I would expect an error message or something if there is no batch task to the project. At the moment the error is silently ignored if I don't enter a batch task name ot there is none. Next time I open the configuration, the batch task name is magically set to the first 
batch taks - but this appears to be for the GUI only. And it becomes more confusing, with the build error ""ERROR: No such task exists: . Perhaps you meant foo". Becuase if I look at the configuration GUI, "foo" is written there.
Axel Heider
added a comment - Consider it more a usability isse then.
I would expect an error message or something if there is no batch task to the project. At the moment the error is silently ignored if I don't enter a batch task name ot there is none. Next time I open the configuration, the batch task name is magically set to the first batch taks - but this appears to be for the GUI only. And it becomes more confusing, with the build error ""ERROR: No such task exists: . Perhaps you meant foo". Becuase if I look at the configuration GUI, "foo" is written there. 
you have to save your new batch task, then configure the project again and select both the project name and the particular task to execute in the post-build step.. sounds like you had the project name, but not the particular task. so I'm not really seeing what the bug is here.. ?