Make jenkins checkout using cvs over ssh with given port

Hi! trying to checkout a cvs-repository using transport over ssh with port 2022. If I give it on a command line (/bin/sh): { export CVSROOT=anoncvs@:/cvs export CVS_RSH=$HOME/bin/SSH cvs -q get -P src } with { $HOME/bin/SSH }: { ssh -p 2022 -o UserKnownHostsFile=/dev/null -o

How can I handle over an environment variable within a build flow?

Hi! I've set up a build flow using the Build Flow Plugin https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin: guard { build( job1 ) build( job2 ) build( job3 ) build( job4 ) } rescue { build( job_cleanup ) } Now I want two things: 1. All these jobs shall share one

Two jobs that never shall build if the other one builds

Hi! I'm having two jobs each one depends on the other and shall never build while the other one builds. Both are independend of each other except they are using the result of each: - cmake blocks building of llvm - llvm blocks building of cmake I've entered cmake as blocker in llvm, and llvm

Re: How can I handle over an environment variable within a build flow?

On Tuesday, May 19, 2015 at 4:26:40 PM UTC+2, rginga wrote: Let’s see,,, 1. What SCM are you using? I use Perforce and can tell the Perforce Plugin “not” to manage “client views” and create one in a fixed location AND set the Use custom workspace in Advanced Project Options to

Re: Two jobs that never shall build if the other one builds

On Tuesday, May 19, 2015 at 3:58:01 PM UTC+2, tps800 wrote: Hi! I'm having two jobs each one depends on the other and shall never build while the other one builds. Both are independend of each other except they are using the result of each: - cmake blocks building of llvm - llvm blocks

Re: Two jobs that never shall build if the other one builds

On Tuesday, May 19, 2015 at 5:58:12 PM UTC+2, Baptiste Mathus wrote: Better use the throttle concurrent build plugin IMO. Works fine for us: Define a central token. Then configure both job to acquire it when starting. Done. Both jobs won't run at the same time. This plugin isn't as easy

Multiple projects, same commands

Hi! I have to build and test some projects. All these use the same commands. I've made them each into a project: 1. checkout 2. build1 3. build2 4. install1 5. install2 6. build3 7. install3 8. test This has to be done multiple times on different hardware. At now I

Binding a workflow to a free build processor until the last build in the flow finishes

jenkins 1.616, Build-Flow-Plugin Hi! I've defined a build flow: *guard {* * build( VMstart, BHOST:test-sct-bsf8 )* * build( freebsd_8.01checkout,BHOST:test-sct-bsf8, BPORT:22 )* * build( freebsd_8.03setup, BHOST:test-sct-bsf8, BPORT:22 )* * build( freebsd_8.04buildworld,

Re: How can I handle over an environment variable within a build flow?

{ out.println $it.key - $it.value } *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *tps800 *Sent:* Thursday, May 21, 2015 4:22 AM *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: How can I handle over

Change date and time format in views

Hi! jenkins uses a really lengthy date and time format in views. It reads in german like (for column Last success: 2 Stunden 23 Minuten - #12 http://test-sct-jci-muc.bfs.de:8080/me/my-views/view/CJV/lastSuccessfulBuild/ I'd liked to have that much shorter and more compact: 2h23m-#12 With:

truttling build checkout, but not builds

Hi! I have six projects all checking out from the same svn server. Only two parallel checkouts are allowed by this server. How can I trottle jobs as long as they are checking out svn? After checking out these six jobs may run parallel only checkout is possible for only two of them at any time.