Re: Current build artifact

I had followed your step 3 (ls -ltr | tail -1) but just wanted to know any other options. I will explore your suggestion mentioned in step 2, thanks for it. Regards, Seenu. On Monday, 8 July 2013 22:33:36 UTC+5:30, Eric Pyle wrote: > > Some thoughts: > > 1) If I understand correctly, in you

Re: matrix job axis with parameter

The best I could come up with: try { context.build.buildVariables.collect { k, v -> v } + [ 'fixed' ] } catch (Exception e) { return [ 'fixed' ] } Seems to trigger the correct axes (in my case, the ones named for the parameters' values + one named 'fixed'). Note that the UI seems wrong between

M2 Release Plugin (release:branch not working for me)

I'm trying to use the M2 Release Plugin in a Jenkins 1.517 job with github, but it doesn't seem to be working ... I only want to use it to release:branch at the moment and want to give the branchName as a parameter, I have tried it as a parameter and hard coded (with and w/o -e): -Dresume=fa

matrix job axis with parameter

Hi All, I am trying to create a matrix job. But while for one axis my values are predefined for the other axis my value depends on a parameter that the job that triggers my job pass. I have tried using groovy axis plugin and read this parameter by using: def build = Thread.currentThread().execu

Re: Half of the project configure screen is grayed out with Loading message!

Hi, I just tried the newer version 1.522, and the problem is fixed. Thanks, Sameh On Wednesday, July 3, 2013 9:26:45 AM UTC-7, Sameh Tawfik wrote: > > > Hi, > > We just installed Jenkins ver. 1.521, and now whenever we open any project > to update some configuration by clicking

Re: Half of the project configure screen is grayed out with Loading message!

Hi, I just tried the newer version 1.522 and the problem is fixed. Thanks, Sameh On Thursday, July 4, 2013 1:54:16 PM UTC-7, Schalk Cronjé wrote: > I also saw this today. I can confirm downgrading to 1.520 resolves the > problem. > > > On Wednesday, 3 July 2013 17:26:45 UTC+1, Sameh Tawf

Re: email notification in case of new warnings

You'd have to access the public api directly I believe, not the token or rest api. On Jul 8, 2013 10:14 AM, "Johannes Wienke" wrote: > On 08.07.13 17:34 schrieb Ulli Hafner: > > Actually the analysis plugs-in expose the number of new warnings as > token or via the REST API. Can't you just use tha

Re: email notification in case of new warnings

On 08.07.13 17:34 schrieb Ulli Hafner: > Actually the analysis plugs-in expose the number of new warnings as token or > via the REST API. Can't you just use that information to trigger the email? That sounds very interesting. Is there any hint on how to access this information in a trigger script

Re: email notification in case of new warnings

On 08.07.13 17:01 schrieb Kevin Fleming (BLOOMBERG/ 731 LEXIN): > I don't think the Warnings plugin exports that information in a way that > email-ext could extract it at this point, but it's certainly doable. > > I'd be quite careful about just using the number of warnings though; a commit > th

Re: Current build artifact

Some thoughts: 1) If I understand correctly, in your step 1 you run a Maven snapshot build, which creates some artifacts. Assuming you are using a Nexus repository, you can have step 2 download the required artifact from Nexus. You can find an example bash script to do that at [1]. 2) You co

Re: Unable to release project from a specific jenkins box using m2 release plugin and perforce SCM

Both the job failing and succeeding are running on OSX boxes. On Monday, July 8, 2013 9:21:30 AM UTC-7, Usman Ismail wrote: > > The password is simple its just the user name that has the slash. > Its running on an OSX box. > > On Monday, July 8, 2013 1:20:42 AM UTC-7, James Nord (jnord) wrote: >>

Re: Unable to release project from a specific jenkins box using m2 release plugin and perforce SCM

The password is simple its just the user name that has the slash. Its running on an OSX box. On Monday, July 8, 2013 1:20:42 AM UTC-7, James Nord (jnord) wrote: > > Passwords with any shell special characters aren’t handled properly > (there is an open JIRA). > > > > So ‘\’ on Unix like OSs wi

Re: email notification in case of new warnings

Actually the analysis plugs-in expose the number of new warnings as token or via the REST API. Can't you just use that information to trigger the email? Ulli Am 08.07.2013 um 17:13 schrieb Slide : > I don't have specific knowledge of the Warnings plugin, so I don't know what > is available. >

Re: java.io.IOException: Remote call failed

I'm also seeing a similar error but with an ssh slave. Ben On Wed, Jul 3, 2013 at 6:55 AM, Bharathi Ramalingam wrote: > I often get the following error when I try to launch a Job. Even though the > slave is up and connected to the master. Following error is thrown. > Restarting the slave and re-

Re: email notification in case of new warnings

I don't have specific knowledge of the Warnings plugin, so I don't know what is available. On Mon, Jul 8, 2013 at 7:57 AM, Johannes Wienke < jwie...@techfak.uni-bielefeld.de> wrote: > Hi, > > On 07/08/2013 03:23 PM, Slide wrote: > > If you used the email-ext plugin, you could add a script trigge

Re: email notification in case of new warnings

I don't think the Warnings plugin exports that information in a way that email-ext could extract it at this point, but it's certainly doable. I'd be quite careful about just using the number of warnings though; a commit that resolves an existing warning and introduces a new one would be missed,

Re: email notification in case of new warnings

Hi, On 07/08/2013 03:23 PM, Slide wrote: > If you used the email-ext plugin, you could add a script trigger that > checked for the number of warnings and then sent out an email only if there > were warnings for that job. Thanks, that's a solution I didn't know so far. I know that for something l

Re: email notification in case of new warnings

If you used the email-ext plugin, you could add a script trigger that checked for the number of warnings and then sent out an email only if there were warnings for that job. slide On Mon, Jul 8, 2013 at 4:05 AM, Johannes Wienke < jwie...@techfak.uni-bielefeld.de> wrote: > Hi, > > for our jobs w

How can I access SVN username and password in shell ( which is already stored in in jenkins)

I am trying to commit build to SVN repository using shell script, But how i can I access the SVN username and paasword which is stored in jenkins. If I directly give username and password in shell , it is working (I need it to be dynamic ie for each user it should be their SVN username and pas

Subversion plugin is not working.

I am using Jenkins and SVN Publisher plugin to generate build and then to upload build back to repository. It generates build but not uploading the build to repository. (I added post build action as to publish to subversion repository) This is the colsole after generating build. Started by

email notification in case of new warnings

Hi, for our jobs we have several analysis tasks running like PMD, checkstyle and so on. However, we are currently not in a position that we can achieve a 0-warnings rate for our projects. Hence failing or marking a build instable just because of the warnings is no options for use. However, it woul

RE: Disable fingerprinting? (1.509.1 LTS)

We have no need of fingerprints, but the CopyArtifact plugin "helpful" creates them anyhow (this is by design) - spending CPU and disk for no reason. I opened https://issues.jenkins-ci.org/browse/JENKINS-18653 to request that the CopyArtifact plugin make this optional. Of course, global disablin

RE: Disable fingerprinting? (1.509.1 LTS)

For Maven2/3 type jobs you don't have the ability to disable fingerprinting. For the other Freestyle job IIRC you have to enable fingerprinting of files. /James > -Original Message- > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci- > us...@googlegroups.com] On Behalf Of Steffen

Re: Disable fingerprinting? (1.509.1 LTS)

Hi Chris! On 05.07.2013 18:58, Chris Withers wrote: > > What problem are you experiencing that make you think you want to go out > of your way to disable fingerprinting? > > If you don't need it, don't actively use it, but it being there does you > no harm... Well, unfortunately, that isn't ent

Re: Current build artifact

Sorry for not being clear in articulating my requirement if my first mail: 1) In step 1 of my build plan, I have maven generate the following file: /var/lib/jenkins/jobs/myjob/modules/org.opendaylight.controller$distribution.opendaylight/builds/2013-07-05_19-01-16/archive/org.opendaylight.contr

Re: How does the SVN polling work (internally)?

Hi Dean! On 05.07.2013 20:41, Dean Yu wrote: Having you considered using a Subversion post-commit hook to trigger your jobs? That sounds like a brilliant idea, I'll look into this! Thanks! Regards Steffen -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Current build artifact

All tasks within same job execution start in same directory. In such case there should not be any problems with finding build artifacts. This case is not really Jenkins specific. If you want to use artifacts of job A in job B (triggered by job A) you should use Copy Artifact Plugin

RE: Unable to release project from a specific jenkins box using m2 release plugin and perforce SCM

Passwords with any shell special characters aren't handled properly (there is an open JIRA). So '\' on Unix like OSs will want some escaping - try your password with \\ instead of a single backslash - or put quotes around it. Is your other box which can perform releases a windows box? That's t