Re: best approach to automate/manage jenkins jobs?

[Richard Bywater]

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 their configuration.
>
> From what I can tell, most people just manually config their jobs via the
> UI.  Unless there are only a few very simple jobs, this leads to an
> unmanageable mess.
>
> I think the jobs should be coded in a DRY fashion, version controlled, and
> deployed via a scripted system.
>
> Here are the approaches I am aware of:
>
> 1) scripting via command line (jenkins cli)
> 2) scripting via the rest web services
> 3) chef cookbook http://community.opscode.com/cookbooks/jenkins
>
> What are most people doing?
> Any recommendations?
>
> thanks
> phil
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to 
> jenkinsci-users+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins best practice for automated testing

[andres reynaldy]

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 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 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 core 
>> build job? do we put the integration testing source code in the same 
>> project as the core project (like unit testing) or make it a different 
>> project altogether? those are my questions for now, and if there's actually 
>> a forum for jenkins community like spring forum, please let me know. Thank 
>> you very much.
>>  
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins best practice for automated testing

[Russell Cecala]

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 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 core
> build job? do we put the integration testing source code in the same
> project as the core project (like unit testing) or make it a different
> project altogether? those are my questions for now, and if there's actually
> a forum for jenkins community like spring forum, please let me know. Thank
> you very much.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

jenkins best practice for automated testing

[andres reynaldy]

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 core 
build job? do we put the integration testing source code in the same 
project as the core project (like unit testing) or make it a different 
project altogether? those are my questions for now, and if there's actually 
a forum for jenkins community like spring forum, please let me know. Thank 
you very much.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: best approach to automate/manage jenkins jobs?

[phil swenson]

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-cloudbees-features-templates-plugin.cb
>
>
>
> *From:* James Nord (jnord)
> *Sent:* 21 February 2014 16:20
> *To:* jenkinsci-users
> *Subject:* RE: best approach to automate/manage jenkins jobs?
>
>
>
> Hi Phil,
>
>
>
> There is also the Job DSL plugin[1] and Cloudbees Templates[2].
>
> The DSL plugin (not used it) can store the DSL in source control - you can
> add the Cloudbees templates (done it) to an SCM like git and commit & push
> them after you make any changes.
>
>
>
> /James
>
>
>
> *From:* jenkinsci-users@googlegroups.com [
> mailto:jenkinsci-users@googlegroups.com ]
> *On Behalf Of *phil swenson
> *Sent:* 21 February 2014 15:15
> *To:* jenkinsci-users
> *Subject:* best approach to automate/manage jenkins jobs?
>
>
>
> Hi, we have a large number of jenkins jobs and would like to automate and
> version control their configuration.
>
>
>
> From what I can tell, most people just manually config their jobs via the
> UI.  Unless there are only a few very simple jobs, this leads to an
> unmanageable mess.
>
>
>
> I think the jobs should be coded in a DRY fashion, version controlled, and
> deployed via a scripted system.
>
>
>
> Here are the approaches I am aware of:
>
>
>
> 1) scripting via command line (jenkins cli)
>
> 2) scripting via the rest web services
>
> 3) chef cookbook http://community.opscode.com/cookbooks/jenkins
>
>
>
> What are most people doing?
>
> Any recommendations?
>
>
>
> thanks
>
> phil
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>--
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Major Problems after upgrading to 1.532.2 LTS Release

[Daniel Beck]

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 week for months when several 
important jobs have build times of 10+ hours isn't fun), and was able to 
resolve them by switching to LDAP. Given the AD specific stack trace, I 
suggested Andrew tries this as well.

On 22.02.2014, at 16:07, Baptiste Mathus  wrote:

> 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.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Major Problems after upgrading to 1.532.2 LTS Release

[Baptiste Mathus]

?
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 LDAP
> plugin[1] to do the same job.
>
> 1: https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin
>
> On 21.02.2014, at 00:47, Andrew Sumner 
> wrote:
>
> > Nearly everything I do gives this error - any assistance will be
> greatefully accepted!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Is a central/shared local Maven Repo still Not safe for Jenkins master and many slaves?

[Baptiste Mathus]

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 unless you delete it).

In your case, as you're likely to have many executors per slave (which btw
i wouldn't recommend) the probability to corrupt the cache is even bigger.
Then, on top of that, using NFS increases the risk even more, since (your
executors count) processes will access the cache concurrently.

Having a 'private' repository and cleaning it up on a regular basis is in
fact simple and quite straightforward. The only downside is the disk space,
but as having more disks is certainly cheaper than spending time to debug
corrupted  repository issues.

Hth
Le 21 févr. 2014 17:08, "Seena Kasmai"  a écrit :

> Greetings -
>
> It seems there is an outstanding maven issue "Concurrent-safe access to
> local Maven repository " which
> would advise against setting up all Jenkins servers to use a shared (e.g
> NFS mount) maven local repo - Can anyone confirm or share experience on how
> unsafe this would be?
>
> The issue with having different repo is managing the cleaning up for each
> and also not optimized when running same job in different slaves, all maven
> artifacts have to be republished etc...(this is for a setup of 1000s of
> jobs across 10 slaves)
>
> Any suggestions/advise would be helpful.
>
> Thanks,
> --Seena
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

For loop in the Jenkins build flow

[dev123]

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:

parallel (

 for (int i=1; 1<100; i++) {
  { build( "a", STEP: i) }
}
)

But that gives an error.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.