To add another (that I didn't see listed but apologies if it was), we use
Jenkins Job Builder - http://ci.openstack.org/jenkins-job-builder/
Richard.
On Saturday, February 22, 2014, phil swenson wrote:
> Hi, we have a large number of jenkins jobs and would like to automate and
> version control
My question is about design strategy, so I want to hear the pros and cons
from those more familiar with Jenkins. Thanks.
On Sunday, February 23, 2014 10:11:39 AM UTC+10, Red wrote:
>
> Hi. I am also new to jenknis. I searched
> http://serverfault.com/search?q=jenkins and found 414 jenkins relat
Hi. I am also new to jenknis. I searched
http://serverfault.com/search?q=jenkins and found 414 jenkins related post.
On Sat, Feb 22, 2014 at 3:45 PM, andres reynaldy
wrote:
> Hi,
>
> I'm new to Jenkins and I'm wondering is this the user forum for jenkins? I
> was expecting a forum, not a gmail
Hi,
I'm new to Jenkins and I'm wondering is this the user forum for jenkins? I
was expecting a forum, not a gmail mailing group. But anyway, I'm here to
ask about the best practice about how to set up integration testing in
Jenkins. Do we deploy that as separate build job thats run after the co
thanks for the replies!
No chef stories? interesting...
On Fri, Feb 21, 2014 at 9:20 AM, James Nord (jnord) wrote:
> Finger slipped - this time with some links.
>
>
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin
>
> [2]
> http://www.cloudbees.com/jenkins-enterprise-by-clo
I don't think there's a need to do so. It still works without any configuration
in a lot of cases. And configuration of the LDAP plugin can be annoying if you
know nothing about LDAP.
I've experienced a severe issue with AD a while back (essentially
JENKINS-16429; restarting Jenkins twice a wee
?
Curious, would that plugin somehow be deprecated? We've been using it for
many years (since the time when Jenkins had another name that extinguished
today) without any issue.
Le 21 févr. 2014 18:54, "Daniel Beck" a écrit :
> Don't use the Active Directory plugin. You likely can configure the LD
This is actually unsafe. You take the risk to corrupt the "maven local
repository" (badly named, think more about it like a cache). And there's
also potential issues of having a stale dependency installed in the local
cache/repository (and if it's not a snapshot, it will never be downloaded
again u
Is it possible to create a for loop in the jenkins build flow plugin DSL?
Currently I have:
parallel (
{ build( "a", STEP: 1) },
{ build( "a", STEP: 2 ) },
{ build( "a", STEP: 3 ) }
)
Which I need to scale to e.g. 100 parallel executions. Therefore I need to
be able to do something like
