Re: make Buildflow show a passed parameter in the subjob box in the buildgraph visualisation

[frank stockmans]

Looks like it works when installing the latest versions of the plugins.

never mind :-)


On Friday, December 13, 2013 2:00:06 PM UTC-8, frank stockmans wrote:
>
> Hi,
>
> We are using the Jenkins Buildflow and loving it.
> One thing we do is launch the same subjob in parallel from the top job and 
> pass in different variables.
>
> e.g. 
>
> Joblauncher TESTSUITE="test1 test2 test3"
> --->smoketestjob #1
> --->smoketestjob #2
> --->smoketestjob #3 
>
> We would like the vizualization to show us which test is run by the 
> smoketestjob instance.
>
> We are able to update the jobid description in the subjob, e.g. like so 
> "smoketestjob test3 #154", but we would also have it show as such in the 
> visualisation.
>
> Like so:
> Joblauncher TESTSUITE="test1 test2 test3"
> --->smoketestjob test1 #1
> --->smoketestjob test3 #2
> --->smoketestjob test2 #3 
>
> This is what our DSL looks like:
>
> ==
>
> def aSuites = params['TESTSUITE'].tokenize();
> parallel (aSuites.collect { name -> return { build("smoketest", 
> TESTSUITE:name) } })
>
> ==
>
> br/Frank
>

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

make Buildflow show a passed parameter in the subjob box in the buildgraph visualisation

[frank stockmans]

Hi,

We are using the Jenkins Buildflow and loving it.
One thing we do is launch the same subjob in parallel from the top job and 
pass in different variables.

e.g. 

Joblauncher TESTSUITE="test1 test2 test3"
--->smoketestjob #1
--->smoketestjob #2
--->smoketestjob #3 

We would like the vizualization to show us which test is run by the 
smoketestjob instance.

We are able to update the jobid description in the subjob, e.g. like so 
"smoketestjob test3 #154", but we would also have it show as such in the 
visualisation.

Like so:
Joblauncher TESTSUITE="test1 test2 test3"
--->smoketestjob test1 #1
--->smoketestjob test3 #2
--->smoketestjob test2 #3 

This is what our DSL looks like:

==

def aSuites = params['TESTSUITE'].tokenize();
parallel (aSuites.collect { name -> return { build("smoketest", 
TESTSUITE:name) } })

==

br/Frank

-- 
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: Build-Flow graph disappeared after restart jenkins

[frank stockmans]

We had a similar problem upgrading to LTS 1.504.9. Part of it was upgrading 
the buildflow plugin. We reverted to version 0.9 for now, till they fix a 
bug. So waiting for that release to upgrade.

br/Frank


On Thursday, December 12, 2013 6:20:54 AM UTC-8, zacky az wrote:
>
> Hi,
>
> After restart Jenkins or Reload Configuration from Disk Build-Flow graph 
> disappeared
>
> Jenkins ver. 1.542 on SUSE Linux Enterprise Server 11 SP2 (x86_64) 
>
> buildgraph-view 1.1.1 
> CloudBees Build Flow plugin 0.10
>
> Can you please let me know what i am doing wrong
>
> Regards Zacky
>
>
>

-- 
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: Slave setup questions...

[frank stockmans]

I tend to run all my builds on slaves. 
- make sure the workspace on slaves is different from that on the master
- have a recent version of java on the slave
- be able to ssh to it and our .cshrc should throw any error's or messages 
to the terminal when you get there
Slaves need to be able to get to your git/SVN servers.

You don't need tomcat to run a jenkins master. You can run it natively.
>java --jar jenkins.war &
Backup $JENKINS_HOME on the master. It is all you need.

Have Fun
Frank


On Tuesday, December 11, 2012 3:33:09 PM UTC-8, Jeff Vincent wrote:
>
> I'm starting to setup a new master/slave configuration using Ubuntu 12.10 
> + Tomcat 7.  I couldn't find any real docs regarding slaves and could use 
> some clarification on best practices particularly with tools.
>
> My builds use:
>
> Git or SVN
> Maven
> SVN
> Java 6 and 7
>
> Additionally I have configured ANT for some legacy projects (that I may 
> not convert) and with maven I use SONAR and the maven release plugin.
>
> What is the best practice for getting a slave configured?
>
> So far, the issues I've had relate to configuring GIT, git ssh-key auth, 
> and Maven settings.  I'm sure the list will continue.
>
> Any help is appreciated to make this less painful...
>
> -- 
> Jeff Vincent
> preda...@gmail.com 
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox  !!  
>
>