• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • batch-task-plugin
    • None
    • Platform: All, OS: All

      It would be nice if I could schedule a batch-task to run at certain times or
      afer a build completes for the given project.

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

          Jason Chaffee created issue -

          Issue #992 would fix this.

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

          Kohsuke Kawaguchi added a comment - Issue #992 would fix this. This issue has been marked as a duplicate of 992 ***
          Kohsuke Kawaguchi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Kohsuke Kawaguchi made changes -
          Link New: This issue duplicates JENKINS-992 [ JENKINS-992 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

          Laurent Denanot added a comment - - 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)

          Laurent Denanot added a comment - - 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)
          Laurent Denanot made changes -
          Resolution Original: Duplicate [ 3 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 131066 ] New: JNJira + In-Review [ 185873 ]

            kohsuke Kohsuke Kawaguchi
            jasonchaffee Jason Chaffee
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: