RE: Run Condition plugin is invisible

2013-01-31 Thread Matthew.Webber
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 “Conditional step (single)” or “Conditional Steps (multiple)”. But I don’t 
think the run condition plugin itself exposes anything to the UI.

Matthew Webber

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of jhoomshar...@netscape.net
Sent: 31 January 2013 05:00
To: jenkinsci-users@googlegroups.com; bap-jenk...@bapit.co.uk
Subject: Run Condition plugin is invisible


Hi,
I installed “Run Condition plugin” with all dependencies it requires but unable 
to find it in project config section, anyone faced the similar kind of 
situation? Can someone help me in getting this plugin configured.
Will be thankful to you.

Thanks,
Jhoom





-- 

This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

 







-- 
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: Run Condition plugin is invisible

2013-01-31 Thread jhoomsharabi

Thanks Matthew for the info.




-Original Message-
From: Matthew.Webber matthew.web...@diamond.ac.uk
To: jenkinsci-users jenkinsci-users@googlegroups.com; bap-jenkins 
bap-jenk...@bapit.co.uk
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, 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 “Conditional step (single)” or “Conditional Steps (multiple)”. But I don’t 
think the run condition plugin itself exposes anything to the UI.
 
Matthew Webber 
 


From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of jhoomshar...@netscape.net
Sent: 31 January 2013 05:00
To: jenkinsci-users@googlegroups.com; bap-jenk...@bapit.co.uk
Subject: Run Condition plugin is invisible

 

 

Hi,

I installed “Run Condition plugin” with all dependencies it requires but unable 
to find it in project config section, anyone faced the similar kind of 
situation? Can someone help me in getting this plugin configured.

Will be thankful to you.

 

Thanks,

Jhoom 
 






 
--  
This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 


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

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




Job Inheritance

2013-01-31 Thread jck . kln
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 funcionality of defining common 
configuration in a parent job and apply to its children. In our case this 
is a necesarry feature, because we need to manage 300 projects at least.

I've seen a presentation of cloudbees about Jenkins and, if I'm not wrong, 
they announced that funcionality would be included in the future. Do you 
know when? If not, how does the people manage the common data of a huge 
amount of projects?

Thanks in advance.




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




copy artifact plugin - Unable to find a build

2013-01-31 Thread Otto Behrens
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 copy from: BaselineGemStone. In the config of 
the job, we've got Upstream build that triggered this job selected, with 
the project name BaselineGemStone.

I don't get this, because just prior to this message, it clearly says 
Started by upstream project BaselineGemStone build number 217.

Am I missing something? Can you please help?

Is there more debug info I can get?

Thanks for a great project. Using jenkins every day.

Otto

-- 
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: copy artifact plugin - Unable to find a build

2013-01-31 Thread Otto Behrens
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 o...@finworks.biz wrote:
 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 copy from: BaselineGemStone. In the config of
 the job, we've got Upstream build that triggered this job selected, with
 the project name BaselineGemStone.

 I don't get this, because just prior to this message, it clearly says
 Started by upstream project BaselineGemStone build number 217.

 Am I missing something? Can you please help?

 Is there more debug info I can get?

 Thanks for a great project. Using jenkins every day.

 Otto

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



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




Get Abstract Build Information

2013-01-31 Thread bearrito
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 will want the 
notifier to get information about the most recent build for ProjectA. In 
particular I will want to be able to get the environment variable 
information along with the person starting the job.

Looking at http://javadoc.jenkins-ci.org/hudson/model/AbstractBuild.html I 
feel that one of the getUpstream*() methods is what I want to use. 

Am I on the right track?

-b

-- 
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: Get Abstract Build Information

2013-01-31 Thread bearrito
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);
Run mostRecentUpstreamBuild = upstreamProject.getLastBuild();
return mostRecentUpstreamBuild;
}


I'm able to do the string replace because my job names are by convention.

-b

On Thursday, January 31, 2013 11:30:47 AM UTC-5, bearrito wrote:

 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 will want the 
 notifier to get information about the most recent build for ProjectA. In 
 particular I will want to be able to get the environment variable 
 information along with the person starting the job.

 Looking at http://javadoc.jenkins-ci.org/hudson/model/AbstractBuild.htmlI 
 feel that one of the getUpstream*() methods is what I want to use. 

 Am I on the right track?

 -b



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




keep this build forever via rest api?

2013-01-31 Thread Chris Withers

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 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: Job Inheritance

2013-01-31 Thread syl20bnr
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:09:17 UTC-5, jck...@gmail.com a écrit :

 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 funcionality of defining common 
 configuration in a parent job and apply to its children. In our case this 
 is a necesarry feature, because we need to manage 300 projects at least.

 I've seen a presentation of cloudbees about Jenkins and, if I'm not wrong, 
 they announced that funcionality would be included in the future. Do you 
 know when? If not, how does the people manage the common data of a huge 
 amount of projects?

 Thanks in advance.






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