Skip to main content
aboutsummaryrefslogtreecommitdiffstats
blob: fbb06641b7c998669eff6b09bc9ae129c0c5e9c0 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
<!-- **************************************************************************
#
# Copyright (C) 2004-2011 Oracle Corporation
#
# All rights reserved. This program and the accompanying materials
# are made available under the terms of the Eclipse Public License v1.0
# which accompanies this distribution, and is available at
# http://www.eclipse.org/legal/epl-v10.html
#
# Contributors:
#         Kohsuke Kawaguchi, Anton Kozak, Duncan Mills
#
#************************************************************************** -->

<div>
  Provides a <a href="http://en.wikipedia.org/wiki/cron">cron</a>-like feature
  to periodically execute this job.

  <p>
  This feature is primarily for using Hudson as a cron replacement,
  and it is <b>not ideal for continuously building software jobs</b>.

  When people first start continuous integration, they are often so used to
  the idea of regularly scheduled builds like nightly/weekly that they use
  this feature. However, the point of continuous integration is to start
  a build as soon as a change is made, to provide a quick feedback to the change.
  To do that you need to
  <a href="https://wiki.eclipse.org/Building_a_software_project#Builds_by_changes_in_Subversion.2FCVS">hook up SCM change notification to Hudson.</a>.

  <p>
  So, before using this feature, stop and ask yourself if this is really what you want.
  <p>
  It's possible to use Job cascading feature for this property. Please review <a href="https://www.eclipse.org/hudson/the-hudson-book/book-hudson.chunked/ch06.html#section-common-job-configurations">
  this document</a>.
</div>

Back to the top