gt;
>>> In my never-ending quest to create a deployment script for Jenkins (why
>>> is this so difficult?), I would like to be able to configure the quiet
>>> period on startup, *without needing to configure it through the UI*.
>>>
>>> Is there a way of c
>>
>> In my never-ending quest to create a deployment script for Jenkins (why
>> is this so difficult?), I would like to be able to configure the quiet
>> period on startup, *without needing to configure it through the UI*.
>>
>> Is there a way of configuring this thr
8 February 2017 09:18:46 UTC, Barry Laffoy wrote:
>
> In my never-ending quest to create a deployment script for Jenkins (why is
> this so difficult?), I would like to be able to configure the quiet period
> on startup, *without needing to configure it through the UI*.
>
> Is the
In my never-ending quest to create a deployment script for Jenkins (why is
this so difficult?), I would like to be able to configure the quiet period
on startup, *without needing to configure it through the UI*.
Is there a way of configuring this through groovy? Ideally I would like to
place a
Is there a way to enable quiet periods via MB Pipeline and properties
command?
The option is not there in the pipeline syntax codegen and I am wondering
if there is a reason for that...
Thanks,
-M
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users"
Hi,
Check the plugin repository, there is
https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
for that.
Björn
Am Dienstag, 2. Februar 2016 03:49:01 UTC+1 schrieb Mark Bidewell:
>
> Is there a way to assign a quiet period in Jenkins such that it only
> affects
Is there a way to assign a quiet period in Jenkins such that it only
affects automatic builds and build triggers, but "Build Now" requests still
happen without delay?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To u
I am using Jenkins with a Git repository. I have configured the quiet
period to 5 minutes for my project. Pushing a change on a branch causes a
new build to be queued as expected and it does wait in the queue for 5min.
However, if I push another change to the same branch within the quiet
Is this via polling or by hitting "Build Now"? I *think* that Build Now
does not use quiet period as such. From the link provided:
"It is also possible for some of those to override the quiet period
configured in the project. For example, when you click "Build Now" but
Job get started immediately without the delay time. I have the quiet period
value as 600
On Tuesday, June 25, 2013 5:44:48 PM UTC+5:30, Geoff Cummings wrote:
>
> How is it behaving for you?
>
> http://jenkins-ci.org/content/quiet-period-feature
>
> avoid setting quiet peri
How is it behaving for you?
http://jenkins-ci.org/content/quiet-period-feature
avoid setting quiet period longer than the polling interval.
On 25 Jun 2013, at 10:57, Saju Joseph wrote:
*Details*:- We have a requirement to configure some kind of delayed job
execution in Jenkins, and came to
*Details*:- We have a requirement to configure some kind of delayed job
execution in Jenkins, and came to know that 'Quiet period' in 'Manage
Jenkins->Configure Systems' screen is basically designed for "a newly
scheduled build waits for this many seconds before actu
nother vm. I'm guessing I have enough RAM to have 3 executors doing this.
I have created separate jobs to start a vm, run the appropriate script on a
vm (after a quiet period to allow booting to finish), and stop a vm. The
jobs are chained: the Start VM job has a post-build action to star
Hi,
I want to change quiet period at run time by passing a parameters from
upstream to downstream field.
I have a dependency chain where upstream job triggers the downstream job.
On the other side, svn hooks notify jobs. I want to one logical change set
is delivered in several commit
Hi,
I would like to set up a job A such that it would be triggered after the
given period of time after the last successful build of another job B.
If B succeed, A waits for n minutes and If in that period of time when
Awas waiting,
B succeed once again, the schedule for A is delayed once again so
Aaron,
If I set the quiet period to 2 hours and another code change is submitted
then it will reset the quiet period and I might not get a build for several
hours. This is what I would like to avoid. I would like it to function
normally with a quiet period, but if, for some reason, the quiet
Lewis,
Can you just set your quiet period to 2 hours? Then no matter how often
commits happen, your code will be built every 2 hours instead of every 30
minutes.
Maybe I don't understand what you want to accomplish.
-Aaron
On Thu, Jun 14, 2012 at 11:25 AM, Lewis wrote:
> Does anyone
Does anyone know of a way to limit the number of times a project will wait
for it's quiet period?
My goal is to ensure that the project will build even it commits keep
happening.
For example:
Say my quiet period is 30 minutes, I want my project to build after 2 hours
even if new co
18 matches
Mail list logo
