Point of information for clarity: the 'H' in crontab hash syntax [0]
is conceptually different than SCM 'Quiet Periods' [1].
[0] https://issues.jenkins-ci.org/browse/JENKINS-17311
[1] https://jenkins.io/blog/2010/08/11/quiet-period-feature/
On Wed, Apr 27, 2016 at 7:38 AM, Maciej Jaros wrote:
>
myke (2016-04-13 10:20):
Looking for ideas...
I have build events which do not have a fixed time between events
I have downstream jobs running tests after each build.
Thereafter my environment is doing nothing until the next build event
(could be multiple days)
I want my test environment t
Looking for ideas...
I have build events which do not have a fixed time between events
I have downstream jobs running tests after each build.
Thereafter my environment is doing nothing until the next build event
(could be multiple days)
I want my test environment to make use of the quiet peri
