Create Multijob in Jenkins using Tikal Multijob Plugin

Posted Thu, 15/09/2011 - 17:00 by roni
, , , , , , , , ,

A new multijob plugin was created by Tikal ALM team.

Using this job you can add full hierarchy of Jenkins jobs that will be executed in sequence or in parallel.

When creating new Jenkins job you have an option to create MultiJob project. This job can define in the Build section phases that contains one job or more. All jobs belong to one phase will be executed in parallel (if there are enough executors on the node), and all jobs in phase 2 will be executed only after jobs in phase 1 are completed etc.

For example we create MultiJob project called jenkins-multijob-inherent that contains 3 multijob phases:

This job manages the building and deployment of the Tikal multijob plugin at phase 1. Afterwards it downloads the snapshot version of jenkins and packs it again with Tikal multijob plugin that was created at phase 1. Finally at phase 3 it deploys the jenkins with the multijob plugin to a deployment machine, runs automatically Selenium tests to check the product and shutdown jenkins. Here is a snapshot of the phases section:

You can also see an hierarchical view of the multijob poject:

‹ Nexus adds an additional "-beta" to jar name. Port Forwarding to Broadcast Requests using Iptables ›

Comments

by swathikumar - 20/09/2011 - 09:12

Hi

Multi job plugin is a very good plugin.

For using this plugin from where i can download this plugin.

by itai - 20/09/2011 - 10:17

Hi ,

 

We are planning to add it to jenkins repository.

 

Currently is still in beta.

 

Attached the beta hpi.

 

 

Thanks ,

 

Itai

 

 

by swathikumar - 20/09/2011 - 15:08

 Hi 

Thanks for attaching the plugin.

 

 

Thanks

SwathiKumar

by ukrc03 - 13/11/2011 - 21:00

Hi, this is a good plugin, but we have an issue with it:

FATAL: hudson.maven.MavenModuleSetBuild cannot be cast to hudson.model.Build

java.lang.ClassCastException: hudson.maven.MavenModuleSetBuild cannot be cast to hudson.model.Build
	at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:96)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693)
	at hudson.model.Build$RunnerImpl.build(Build.java:178)
	at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459)
	at hudson.model.Run.run(Run.java:1403)
	at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:44)
	at hudson.model.ResourceController.execute(ResourceController.java:88) 

 

This happens if downstream Job is maven2/3 type.

 

Would you please let me know when do you think you will have a release of this plugin?

by itai - 13/11/2011 - 21:56

Hi

Attached link to download the plug in.

http://dev.tikalk.com/jenkins/view/tikal-hudson-jenkins/job/jenkins-mult...

This release include fix for maven 2/3 jobs.

We planning to release it soon.

Thanks ,

Itai

by ukrc03 - 14/11/2011 - 05:01

Thank you very much for quick response! I tested this build and in general it works for our cases.

But I only mentioned one another issue. And probably you have a fix for it already:

1. Let's assume you have two jobs A and B. Job A has parameter Param1 with default value "111".

2. Create multi-job M with parameter Param1 with default value "111".

3. Configure M to execute job A (in phase p1) and job B (in phase p2). In Parameters for job A specify: Param1=$Param1

4. Clicked Save.

5. Open job M configuration again and check Parameters value for job A. It should be Param1=$Param1.

6. Do not Save configuration. Just click on the link "Configuration" again (so the page just will be re-loaded).

7. Check Parameters value for job A. It will be Param1=111. So $Param1 is substituted by default value... Looks like it loads somehow default value of parameter from sub-job.

 

Please let me know if you have a fix for it.

 

Thank You and Best Regards!

 

by roni - 29/12/2011 - 12:38

Indeed there was a bug in the scenario you described.

We have deployed another Beta release with the fix.

You can download it from:

dev.tikalk.com/jenkins/job/jenkins-multijob-plugin/lastSuccessfulBuild/artifact/target/jenkins-multijob-plugin.hpi

We are planning to release an official release soon.

Thanks & Best Regards !