Hi all.
Been thinking on trying to migrate some of our stuff to Pipeline, *but*:
http://stackoverflow.com/questions/39905978/complex-and-long-single-job-jenkins-job-pipleine-builds-there-yet
# TL;DR
Does it make sense to have one *single* Jenking Job Pipeline job for a
full long-running deplo
Ver: LTS Jenkins ver. 1.625.2
We run our Windows Build nodes/slaves via the Windows Service
jenkins-slave.exe
Sometimes the Windows Service process "goes down", but its java.exe
child process that is actually running the jenkins slave continues to
work (fine).
What we noticed with this is
Hi all!
I was considering taking a look at the free Folders Plugin from
Cloudbees, but reading a piece back from 2013 I'm a bit scared:
full meassage see:
https://groups.google.com/forum/#!msg/jenkinsci-users/VcxGHiFvBAY/mDwr_hL-7JsJ
On 28.10.2013 22:55, Daniel Beck wrote to
jenkinsci-users
>> ... you can dynamically change the logic of a build job by inventing
your own job attributes. <<
Could you elaborate? I don't quite follow.
cheers,
Martin
On 05.10.2015 13:57, Walter Kacynski wrote:
I use the Enterprise Templates extensively. They are very powerful
but difficult to debug
Hello users.
I'm looking for independent opinions on the Jenkins Enterprise Templates
Plugin.
It would be one of the main reasons for us to adopt Jenkins Enterprise,
but I was quite shocked to learn (see
http://documentation.cloudbees.com/docs/cje-user-guide/temolate-sect-job-template-tutori
On 17.04.2015 18:05, Krishna Desiraju wrote:
Could anyone please help to see if there are any potential disadvantages
with this approach
In our scenario, where we have multiple projects which get added
frequently, we wanted to minimize the effort of creating jobs, so we
thought of reusing the jo
Hi everyone and esp. CloudBees!
What are the main benefits the Jenkins Enterprise [Role-based Access
Control Plugin][1] offers over the free [Role Strategy Plugin][2] ???
thanks for any insight,
Martin
[1] :
http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-role-based-access
On 24.06.2013 09:44, VinodKumar wrote:
I am looking for a plugin or way to notify people n minutes before the job
actually starts.
There was a plugin I saw a long time ago but I don't remember the name.
It used to send notification at scheduled time then start actual job "n
Minutes" after the sch
On 03.05.2013 03:36, Eric Blom wrote:
Hello Everyone,
We started using Jenkins about a year ago and have been very happy with it. We
keep finding more way to use it! Some of our jobs use hardware connected to the
slave and when that slave job is canceled we need to execute a clean up step,
ho
Is there anything to allow for executors (instead of whole nodes) to be
labeled?
I know there's the workaround to just have the same machine run a second
node, but that really does feel awkward.
I'd want to use labeled executors to include Jobs from other Jobs with
[Trigger/call builds on ot
I have a Job that is a) Parameterized and b) allowed to [Execute
concurrent builds if necessary].
I now have a second job that must not run when the first job is running
with a specific set of parameters.
As I can't cover this with the [Throttle Concurrent Builds Plugin] (nor
any other plugi
On 15.03.2013 11:45, Martin Ba wrote:
I'll start with my questions:
-
* Should I run Jenkins on Windows with the included JRE (currentl
1.6_26) or should I run it with a more recent Java version?
* Should I make sure slaves run within the same java version (
I'll start with my questions:
-
* Should I run Jenkins on Windows with the included JRE (currentl
1.6_26) or should I run it with a more recent Java version?
* Should I make sure slaves run within the same java version (or at
least bit-ness)? (Slaves don't have an "in
On 14.03.2013 21:50, Les Mikesell wrote:
On Thu, Mar 14, 2013 at 3:30 PM, Martin Ba <0xcdcdc...@gmx.at> wrote:
I'd say this is not intended:
I have a node that has "Leave this machine for tied jobs only" set.
It started to run a Job that certainly did not explicitly s
I'd say this is not intended:
I have a node that has "Leave this machine for tied jobs only" set.
It started to run a Job that certainly did not explicitly set this node.
However, this Job had "Restrict where this project can be run" set to:
!master
So, yes, this expression includes this
On 16.12.2012 09:50, Chris Withers wrote:
Hi All,
I've just upgraded my Jenkins install to 1.480.1 LTS is the hope of a
bit more stability, however, the 'Manage Jenkins' screen is now
offering 1.493 as an upgrade.
I thought one you moved to an LTS release, only future LTS releases
would be
16 matches
Mail list logo
