There is a [Parameterized Trigger Plugin][1], which enables &quot;Trigger/call builds on other projects&quot; in &quot;Add build step&quot; menu.


  [1]: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin

You can use the plugin at http://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin

Basically you create 3 jobs:

A = your prebuild ste

B = your main job

C = your trigger.

You &#39;build&#39; C. It calls A, and once A is successful, it calls B. The plugin page gives you more information. The good thing about this plugin is that you can have any number of pre-build jobs.

We actually have a set of 5 pre-build jobs before our main is run.


================================================

If you don&#39;t want to try that:

If you are using Linux, you can do the following from within your &quot;shell&quot; script:

    wget http://yourserver/hudson/job/MyJob/build?delay=0sec

This will trigger the job. The bad part about this is that it will not wait for the job to finish.




Actually I know how to answer to your question:
This is the plug-in that you need:

[PreBuild](https://wiki.jenkins-ci.org/display/JENKINS/PreBuild+Plugin)

It is not widely famous, but it does what you want.

It basically runs a Build before your chosen one. For example: You want A to run before B. 
You click on &quot;run B&quot; it will execute A before running B.

Pro: 
-&gt; Very versatile
-&gt; Easy to use

Cons:
-&gt; No support / Option in case the pre-build fails (e.g. do not build if pre-build fails)
-&gt; The development seems not being that active at all.

Here you can see how it looks like
![enter image description here][1]


  [1]: http://i.stack.imgur.com/C3SrS.jpg

**EDIT**


This answer is back from &#39;12, I know you are down-voting it, but back then this was a reliable solution, now I am sure there are other plug-ins that do the job.

I have the same issue and I found a way to do:

I am using jenkins version jenkins-1.452-1.1.

Say I have job A and B, and Job A is depending on job B. When building job B, I want A triggered automatically, and B is blocked until A build successfully.
  
When define build configuration in build section, I add &#39;trigger build on other projects&#39;. then fill the form.

I have the following code 

    public Object handlePermission(ProceedingJoinPoint joinPoint, RequirePermission permission) throws AccessException, Throwable {
        System.out.println(&quot;Permission = &quot; + permission.value());
        if (user.hasPermission(permission.value())) {
            System.out.println(&quot;Permission granted &quot;);
            return joinPoint.proceed();
        } else {
            System.out.println(&quot;No Permission&quot;);
            throw new AccessException(&quot;Current user does not have required permission&quot;);
        }

    }

When I use a user that does not have permissions, I get `java.lang.reflect.UndeclaredThrowableException` instead of `AccessException`. 

Getting UndeclaredThrowableException instead of my own exception

I have a table with a field of type bigint. This field store a timestamp.
I want to date format the field like this :

&lt;pre&gt;to_char( bigint_field,&#39;DD/MM/YYYY HH24:MI:SS&#39;)&lt;/pre&gt;

I get the following error :

&lt;pre&gt;
ERROR: multiple decimal points
&#201;tat SQL :42601
&lt;/pre&gt;



How to format bigint field into a date in Postgresql?

How do I trigger another job from hudson as a pre-build step?

<p>How do I trigger another job from hudson as a pre-build step?</p>


I&#39;ve been dealing with the problem of scaling CI at my company and at the same time trying to figure out which approach to take when it comes to CI and multiple branches. There is a similar question at stackoverflow, https://stackoverflow.com/questions/4943280/multiple-feature-branches-and-continous-integration. I&#39;ve started a new one because I&#39;d like to get more of discussion and provide some analysis in the question.

So far I&#39;ve found that there are 2 main approaches that I can take (or maybe some others???).

 * Multiple set of jobs (talking about Jenkins/Hudson here) per branch
 	* Write tooling to manage the extra jobs
 		* Create/modify/delete Jobs in bulk
 		* Custom settings for each job per branch (SCM url, dep management repos duplications)
 		* Some examples of people tackling this problem with shell tools, ant scripts and Jenkins CLI. See:
          1. http://jenkins.361315.n4.nabble.com/Multiple-branches-best-practice-td2306578.html
          1. http://jenkins.361315.n4.nabble.com/Is-it-possible-to-handle-multiple-branches-where-some-jobs-should-run-on-each-one-without-duplicatin-td954729.html 
          1. http://jenkins.361315.n4.nabble.com/Parallel-development-with-branches-td1013013.html
          1. https://stackoverflow.com/questions/3886892/configure-or-create-hudson-job-automatically
 	* Will cause more load on your CI cluster
 	* Feedback cycle for devs slows down (if the infrastructure cannot handle the new load)
 * Multiple set of jobs per 2 branches (dev &amp; stable)
 	* Manage the two sets manually (if you change the conf of a job then be sure to change in the other branch)
 		* PITA but at least so few to manage
 	* Other extra branches won&#39;t get a full test suite before they get pushed to dev
 	* Unsatisfied devs. Why should a dev care about CI scaling problems. He has a simple request, when I branch I would like to test my code. Simple.
 	
So it seems if I want to provide devs with CI for their own custom branches I need special tooling for Jenkins (API or shellscripts or something?) and handle scaling. Or I can tell them to merge more often to DEV and live without CI on custom branches. Which one would you take or are there other options? 

Handling multiple branches in continuous integration

I&#39;m currently using jenkins/hudson for continuous integration a large mostly C++ project.  We have separate projects for trunk and every branch.  Also, there are some related projects for the Java code, but the setup for those are fairly basic right now (we may do more later though).  The C++ projects do the following:

 * Builds everything with options for whether to reconfigure, do a clean build, or use a fresh checkout
 * Optionally builds and runs all tests
 * Optionally runs all tests using Valgrind&#39;s memcheck
 * Runs cppcheck
 * Generates doxygen documentation
 * Publishes reports: unit tests, valgrind, cppcheck, compiler warnings, SLOC, open tasks, and code coverage (using gcov, gcovr, and the cobertura plugin)
 * Deploys code nightly or on demand to a test environment and a package repository

Everything is configurable for automatic builds and optional for on demand builds.  Underneath, there&#39;s a bash script that controls much of this, which farther depends on our build system, which uses automake and autoconf along with custom bash scripts.

We started using Hudson (at the time) because that&#39;s what the Java guys were using and we just wanted nightly builds.  Since then, we&#39;ve added a lot more and continue to add more.  In some ways Hudson is great, but certainly isn&#39;t ideal.

I&#39;ve looked at other solutions and the only one that looks like it could be a replacement is buildbot.  Would buildbot be better for this situation?  Is the investment worth it since we&#39;re already using Hudson?  Why?

**EDIT**: Someone asked why I haven&#39;t found Hudson/Jenkins to be ideal.  The short answer is that everything can be improved.  I&#39;m simply wondering if Jenkins is the best current solution for my use case or whether there is something better (buildbot?) that would be easier to maintain in the long run even as new requirements come up.

buildbot vs hudson/jenkins for C++ continuous integration

I am running Jenkins from user `jenkins` thats has `$PATH` set to something and when I go into Jenkins web interface, in the *System Properties* window (`http://$host/systemInfo`) I see a different `$PATH`.

I have installed Jenkins on Centos with the native rpm from Jenkins website. I am using the startup script provided with the installation using `sudo /etc/init.d/jenkins start`

Can anyone please explain to me why that happens?

Jenkins / Hudson environment variables

Could someone please explain to me the idea of **artifacts** in the build process?

I have the workspace directory where I check out the code to compile and run my ant scripts etc. At the end, in my case, I get a jar file that&#39;s ready to install. Is that considered to be the artifact?

Where should I tell my build script to put the jar file? In the workspace directory? My jar file gets a unique filename depending on variables like `BUILD_ID` and such, how can I tell Jenkins which jar file to pick?


EDIT:
Okay, so i tried doing something like this:

![enter image description here][1]

The path does not exist yet in my workspace, because the build script is supposed to create it, and of course, the `.jar` and `.properties` files are not there because they haven&#39;t been generated yet. Why does it give me an error then? Seems like I&#39;m missing something.

  [1]: http://i.stack.imgur.com/rPNno.png

Also, does Jenkins delete the artifacts after each build (not the archived artifacts, I know I can tell it to delete those)? Otherwise it will clog the hard drive pretty quickly.

Archive the artifacts in Jenkins

I have a couple of jobs that use a shared resource (database), which sometimes can cause builds to fail in the (rare) event that the jobs happen to get triggered simultaneously. 

Given jobs A through E, for example, is there any way to specify that A and C **should never be run concurrently**?

Other than the aforementioned resource, the builds are independent of each other (not e.g. in a upstream/downstream relation).

A &quot;brute-force&quot; way would be limiting number of executors to one, but that obviously is less than ideal if most jobs could well be executed concurrently and there&#39;s no lack of computing resources on the build server.

How to prevent certain Jenkins jobs from running simultaneously?

I&#39;m trying to set up Jenkins-ci for a project using GitHub. I&#39;ve already set up Jenkins with the appropriate plugins. I want Jenkins to run build scripts only whenever someone on the project pushes to master. So far I&#39;ve been able to set it up so that a build will be triggered anytime anyone pushes to anywhere, but that is too broad. I&#39;ve done this with post-receive service hooks on Git.

I&#39;ve read the Jenkins wiki, and a couple of tutorials, but this particular detail is missing... is it something to do with polling maybe? Or should work be done on the Git side, so that Git only triggers Jenkins when `master` is changed?


Content Type	Original Author	Original Content on Stackoverflow
Question	sorin	View Question on Stackoverflow
Solution 1 - Hudson	Draco Ater	View Answer on Stackoverflow
Solution 2 - Hudson	Sagar	View Answer on Stackoverflow
Solution 3 - Hudson	7dr3am7	View Answer on Stackoverflow
Solution 4 - Hudson	Dustin	View Answer on Stackoverflow

How do I trigger another job from hudson as a pre-build step?

Hudson Problem Overview

Hudson Solutions

Solution 1 - Hudson

Solution 2 - Hudson

Solution 3 - Hudson

Solution 4 - Hudson

How to format bigint field into a date in Postgresql?

Getting UndeclaredThrowableException instead of my own exception

Attributions