• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: batch-task-plugin
• Labels:

  None
• Environment:

  Platform: All, OS: All

[JENKINS-993] there is no way to schedule a batch-task

Collapse comment: Kohsuke Kawaguchi added a comment - 2007-11-18 18:37

Kohsuke Kawaguchi added a comment - 2007-11-18 18:37

Issue #992 would fix this.

• • • This issue has been marked as a duplicate of 992 ***

Expand comment: Kohsuke Kawaguchi added a comment - 2007-11-18 18:37

Kohsuke Kawaguchi added a comment - 2007-11-18 18:37 Issue #992 would fix this. This issue has been marked as a duplicate of 992 ***

Collapse comment: Laurent Denanot added a comment - 2013-09-13 00:00, Edited by Laurent Denanot - 2013-09-25 16:14

Laurent Denanot added a comment - 2013-09-13 00:00 - edited

IMHO this is not a duplicate of JENKINS-992 ('Make batch task a project').

This issue is specifically aimed at the possibility of scheduling a batch task...

Please also see my comment on JENKINS-346: my view is that ideally, batch tasks could be used to implement different goals and associated schedules to the same job, therefore allowing for sharing the same code base/workspace between different 'sub-jobs', which would greatly reduce the no. of jobs needed to cater for all tasks that may need to be scheduled for a same job (e.g. normal build, release build and Sonar build, each running on different schedules but on the same codebase/workspace)

Expand comment: Laurent Denanot added a comment - 2013-09-13 00:00, Edited by Laurent Denanot - 2013-09-25 16:14

Laurent Denanot added a comment - 2013-09-13 00:00 - edited IMHO this is not a duplicate of JENKINS-992 ('Make batch task a project'). This issue is specifically aimed at the possibility of scheduling a batch task... Please also see my comment on JENKINS-346 : my view is that ideally, batch tasks could be used to implement different goals and associated schedules to the same job, therefore allowing for sharing the same code base/workspace between different 'sub-jobs', which would greatly reduce the no. of jobs needed to cater for all tasks that may need to be scheduled for a same job (e.g. normal build, release build and Sonar build, each running on different schedules but on the same codebase/workspace)