Hello,
If you have some kind of pipeline approach then you could have a look at
the Job Generator plugin which is aimed to define job templates. We are
using it at work to generate 100+ jobs defined by 20 Job Generators. Maybe
it could help you.
Cheers,
syl20bnr
Le jeudi 31 janvier 2013 08:0
Hi All,
What url would I hit to make sure a build of a job is marked as "keep
forever"?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups "Jenkin
So you can just do something like
public Run getAssociatedBuild(AbstractBuild build){
String name = build.getProject().getName();
String maybeUpstreamName = name.replaceAll("foo","bar");
AbstractProject upstreamProject =
AbstractProject.findNearest(maybeUpstreamName);
I'm trying to write a plugin. My question is how I can get build
information about a completely different project than the project that will
notify the listener.
So as an example
ProjectA
Build1
Build2
ProjectB
Build4
Build5
When ProjectB reaches on completion for say Build6, I
It could well be because we also use the Join plugin. The direct
ancestor that triggered the build was not "BaselineGemStone", but the
original trigger was. So, perhaps my problem is related this.
On Thu, Jan 31, 2013 at 5:35 PM, Otto Behrens wrote:
> Hi,
>
> We've recently started using the Copy
Hi,
We've recently started using the Copy Artifact Plugin (in stead of the
"Copy files into the job's workspace before building" option). Have got
version 1.25 installed on jenkins 1.500.
Some jobs do work, but we've got the case where a job responds with "Unable
to find a build for artifact c
Hi,
I'm considering Jenkins as continuous integration tool in the company where
I work. I prefer Jenkins than Hudson because I believe it has a better
future and it's widely adopted.
However, I've seen a drawback in Jenkins which is solved in Hudson: job
inheritance. In other words, the funcio
Thanks Matthew for the info.
-Original Message-
From: Matthew.Webber
To: jenkinsci-users ; bap-jenkins
Sent: Thu, Jan 31, 2013 3:58 pm
Subject: RE: Run Condition plugin is invisible
I think you have misunderstood - The run condition plugin does not depend on
anything. Instead,
I think you have misunderstood - The run condition plugin does not depend on
anything. Instead, other things depend on it.
For example, we have Conditional Buildstep plugin (which depends on; i.e. use,
the Run Condition plugin). In our job configuration, we can “Add build step” of
type “Condit
