Re: P4 Plugin throws Error occurred during the SSL handshake: invalid SSL session Error

2014-09-29 Thread Shobha Dashottar
I ran that test code and earlier it gave 128 . So, made a few more changes 
like reinstalling jdk, setting the java paths in a few more files for 
Jenkins to get the path during slave launch itself and then finally copying 
the UnlimitedJCEPolicy jar files even though they existed in the security 
folder.

Looks like something was messed up in my java environment as after I ran 
the test code it gave me the value 2147483647.  the SSL handshake error has 
gone away too.

Thanks Dan for your help on this. Much Appreciated.


On Friday, September 26, 2014 9:30:58 PM UTC+5:30, Dan Tran wrote:


 Also note, that p4jenkins uses the startup JRE to talk to perforce ( not 
 the one configure in the job)

 -D

 On Thursday, September 25, 2014 7:11:13 PM UTC-7, Dan Tran wrote:


  run a java test with your JRE?

 private boolean isUnlimitedCryptoSupported() throws 
 NoSuchAlgorithmException {
 int bits = Cipher.getMaxAllowedKeyLength(AES);
 this.getLog().info(Current encryption strength is:  + bits);
 return bits == 2147483647;

 }




 On Thursday, September 25, 2014 10:15:01 AM UTC-7, Shobha Dashottar wrote:

 I have now removed all the older jre versions from the systems leaving 
 jre only in one place. I even have the JRE  home in the PATH variable. 

 I have setup some Windows VMs now but those are too giving the same 
 error. They already have the JCE jars in their installation folders. 

 Is there some other requirement for this to work ?

 Thanks
 Shobha

 On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote:


 Very likely, you patch the wrong JRE

 -D

 On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar 
 wrote:

 I am setting up a  new Jenkins server. I have been using the Perforce 
 Plugin so far but this time I have switched to the P4 Plugin as has a 
 good 
 integration with the Credential Plugin to connect to the perforce server. 
  

 For most of the VMs that I am connecting to it goes ahead with P4 
 command execution without issue. So far one VM is giving issue and 
 throwing 
 exception while even trying to communicate with the perforce server.

 P4: Unable to connect: com.perforce.p4java.exception.ConnectionException: 
 Error occurred during the SSL handshake: invalid SSL session
 P4: Unable to use Workspace: java.lang.NullPointerException
 P4: Unable to close Perforce connection: java.lang.NullPointerException
 ERROR: Unable to update workspace: java.lang.NullPointerException

 After following some articles, I have added the jars from JCE for Java 7 
 inside the slave VMs jre/lib/security folder. 
 But still the error keeps popping up. 

 Does anyone know what is going on or is missing on that VM?

 Thanks
 Shobha




-- 
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/d/optout.


Re: How to set Environment variables in Global properties of global Jenkins configuration programmatically?

2014-09-29 Thread mr
Does anybody have an idea???


Am Dienstag, 23. September 2014 12:03:51 UTC+2 schrieb mr:

 Thanks for the answer!

 Where do you inject the username and password? I think you do it into the 
 current build.

 But I want to inject a new variable or change an existing variable (like 
 e.g. username or password) into the global configuration, thus next time 
 when I go into the Global Jenkins Configuration UI, I could see the 
 username or password in the section Global properties.

 Is this possible? Is there a package like hudson.configuration.global 
 within the API which would allow me to change the environment variable 
 within the global properties jenkins configuration section?


-- 
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/d/optout.


Re: Configuring Jenkins for production deployment

2014-09-29 Thread mr
It depends on how do you want deploy.
For example, if you deploy by means of ssh 
( https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin ) 
then you can choose the server to which you want to deploy.


Am Freitag, 26. September 2014 12:46:24 UTC+2 schrieb Harsh Saxena:

 Where do we configure the production servers while configuring a new job 
 in Jenkins.   In short how does Jenkins identify where to deploy the code ? 
 where do we configure the production/Destination servers where the code has 
 to be eventually deployed.


-- 
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/d/optout.


Re: NullPointerException using paramterized trigger plugin

2014-09-29 Thread Eddie Sholl
It turns out it was the Job DSL plugin causing the issue, although 
indirectly. The xml for the parameterized triggers was not valid, it was 
using UNSTABLE_OR_BETTER, which doesn't seem to be supported. I was also 
adding them as build actions instead of post build actions (steps instead 
of publishers).

This put me on to the solution:

https://issues.jenkins-ci.org/browse/JENKINS-23079

On Saturday, September 27, 2014 11:49:29 PM UTC+10, Eddie Sholl wrote:

 Hi all,


 I'm playing around with some fairly straight line jobs hooked up via the 
 paramterized trigger plugin. I'm building the jobs via the Job DSL plugin, 
 but I don't believe this will have an effect here. When I try to trigger my 
 sample root job in my pipeline, I'm getting the following exception:


 At revision 119303
 [workspace] $ powershell.exe  
 'C:\Users\EDDIES~1\AppData\Local\Temp\3\hudson7036549510980740414.ps1'
 hello
 FATAL: nulljava.lang.NullPointerException 
 http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException
   at 
 hudson.plugins.parameterizedtrigger.ResultCondition$3.isMet(ResultCondition.java:19)
  
 http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.ResultCondition$3.isMetentity=method
   at 
 hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:330)
  
 http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2entity=method
   at 
 hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:57)
  
 http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2entity=method
   at 
 hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:85)
  
 http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.parameterizedtrigger.TriggerBuilder.performentity=method
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.performentity=method
   at 
 hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
  
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.performentity=method
   at hudson.model.Build$BuildExecution.build(Build.java:199) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.buildentity=method
   at hudson.model.Build$BuildExecution.doRun(Build.java:160) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.doRunentity=method
   at 
 hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.runentity=method
   at hudson.model.Run.execute(Run.java:1745) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.executeentity=method
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.runentity=method
   at hudson.model.ResourceController.execute(ResourceController.java:89) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.executeentity=method
   at hudson.model.Executor.run(Executor.java:240) 
 http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.runentity=method


 The job I'm testing out here does a simple subversion checkout, then runs a 
 'hello' powershell script. It then triggers a bunch of downstream jobs, the 
 exact list is:


 trunk/full_build_trunk,trunk/unit_tests_trunk,trunk/DB_migration_tests_trunk,trunk/DB_integration_tests_trunk


 I've stepped through the plugin code on github, and it seems that the build 
 object being passed most of the way through this stack trace is null.


 Any ideas on what I can do to try to address this? Would this be better off 
 in the dev google group? The parameterized trigger plugin is version 2.25, 
 and jenkins itself is 1.579


 Cheers,


 Eddie



-- 
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/d/optout.


Jenkins dependencies and setup.py

2014-09-29 Thread Andrew Smith
Hi

I'm looking to set up jenkins to build a bunch of different python modules 
that are dependent upon each other.

Let's say I have a module app (Web App) that is dependent upon another 
module (Library).  I would like Web App
to be re-built whenever Library is rebuilt. 

In Jenkins I can achieve this with the Build after other projects are 
built build trigger.

However - I've already defined that dependency in my setup.py for my Web 
App module. What I'd really like to do is have Jenkins
understand the setup.py and set up the build triggers that way. This way 
if a developer changes a dependency they only need to
change it once.

Has anyone come across as similar problem? 

Thanks
Andy

-- 
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/d/optout.


Re: Build Failure Analyzer - Email Ext

2014-09-29 Thread Mike Bayliss
This came up some time ago when this code sample was posted:


j:jelly xmlns:j=jelly:core xmlns:st=jelly:stapler
 xmlns:d=jelly:define 
 BODY
 j:set var=failureCauses
 value=${it.getAction('com.sonyericsson.jenkins.plugins.bfa
 .model.FailureCauseBuildAction').getFoundFailureCauses()}/
 j:if test=${failureCauses.size() gt 0}
 j:forEach var=cause items=${failureCauses}
 ${cause.name}
 br/
 ${cause.description}
 br/
 /j:forEach
 /j:if
 /BODY
 /j:jelly


At the time it didn't work because the BFA ran after the email was sent.
After the recent upgrade to the BFA (to 1.10.0) this partially works.

If I use the macro $BUILD_FAILURE_ANALYZER} in the message body (not in a
jelly script) the macro is expanded to the failures.

If I use a jelly script with the above code, there are no failures reported.

If I make the message body the macro and the jelly script, the token is
expanded and the script also reports the same failures.

There's a start scan routine somewhere is called when the token is
evaluated and the routine (I presume) needs to be called before the code
fragment above.

Unfortunately I've no time to investigate further since a higher priority
task has landed in my in-tray.

Mike

On Mon, Sep 22, 2014 at 3:35 PM, Lukasz Wasylow lwasy...@gmail.com wrote:

 Hi
 I've been trying to use a Build Failure Analyzer to issue some emails
 using ext-Email.
 I ve been trying to use a Jelly Templates but it looks like BFA scanning
 for issues after ext-Email is being sent.

 I have tried to use a token macro ${BUILD_FAILURE_ANALYZER,
 includeTitle=true, includeIndications=true, useHtmlFormat=true} but either
 I'm not undestandt how to use it or its not working.

 Is anyone had a luck with that email macro?

 Regards
 Lukasz

 --
 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/d/optout.


-- 
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/d/optout.


Jenkins 1.480.0.3 compatible with Chrome 37.x

2014-09-29 Thread prakash . atlassian
Hi Team,
 
We are going to upgrade Chrome to latest version 37.X, I just want to know 
whether jenkins 1.480.0.3 works fine using Chrome 37.X.

-- 
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/d/optout.


Re: Jenkins 1.480.0.3 compatible with Chrome 37.x

2014-09-29 Thread Stephen Connolly
https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix

Those levels only apply to actively maintained branches (i.e. current LTS
and current HEAD)... if you are running a 2-3 year old version of Jenkins
then you are responsible for that version

On 29 September 2014 15:05, prakash.atlass...@gmail.com wrote:

 Hi Team,

 We are going to upgrade Chrome to latest version 37.X, I just want to know
 whether jenkins 1.480.0.3 works fine using Chrome 37.X.

 --
 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/d/optout.


-- 
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/d/optout.


Re: Project structure with git and Jenkins

2014-09-29 Thread Mark Waite
Can you explain further what you hope to gain by using a shared drive for
development?

Git works best with local drives.  It is a fast version control system in
large measure because the vast majority of its operations work on the local
file system.  If you make git operate on a shared file system, you've now
inserted a slowdown (network access) into all the operations performed by
developers, all day long.  That seems like a serious penalty for the most
active portion of a developer's working day.

Git users have the notion of a feature branch which allows a developer to
submit something to be evaluated by Jenkins, without making that change
available on the authoritative branch.  You could investigate a feature
branch based workflow, and use Jenkins to automate the merge from feature
branches to the authoritative branch.

Alternately, you could consider using Gerrit, which provides a code read
facility and related workflow as a layer over a git repository.

Mark Waite

On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com wrote:

 Hi All,

 Right now, in our project, developers develop code on shared drive,
 compile on common server, but deploy on local PC.
 But, we want continuous integration in future with git and Jenkins.
 Our main requirement is that developers should not have anything on their
 PC, they develop on shared drive, once they save, they can ask Jenkins to
 compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 --
 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/d/optout.




-- 
Thanks!
Mark Waite

-- 
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/d/optout.


Re: P4 Plugin throws Error occurred during the SSL handshake: invalid SSL session Error

2014-09-29 Thread Dan Tran
BTW, I am looking for maven users to try p4maven with maven release plugin 
as well.  Let me know if you need help on that area



On Sunday, September 28, 2014 11:23:08 PM UTC-7, Shobha Dashottar wrote:

 I ran that test code and earlier it gave 128 . So, made a few more changes 
 like reinstalling jdk, setting the java paths in a few more files for 
 Jenkins to get the path during slave launch itself and then finally copying 
 the UnlimitedJCEPolicy jar files even though they existed in the security 
 folder.

 Looks like something was messed up in my java environment as after I ran 
 the test code it gave me the value 2147483647.  the SSL handshake error has 
 gone away too.

 Thanks Dan for your help on this. Much Appreciated.


 On Friday, September 26, 2014 9:30:58 PM UTC+5:30, Dan Tran wrote:


 Also note, that p4jenkins uses the startup JRE to talk to perforce ( not 
 the one configure in the job)

 -D

 On Thursday, September 25, 2014 7:11:13 PM UTC-7, Dan Tran wrote:


  run a java test with your JRE?

 private boolean isUnlimitedCryptoSupported() throws 
 NoSuchAlgorithmException {
 int bits = Cipher.getMaxAllowedKeyLength(AES);
 this.getLog().info(Current encryption strength is:  + bits);
 return bits == 2147483647;

 }




 On Thursday, September 25, 2014 10:15:01 AM UTC-7, Shobha Dashottar 
 wrote:

 I have now removed all the older jre versions from the systems leaving 
 jre only in one place. I even have the JRE  home in the PATH variable. 

 I have setup some Windows VMs now but those are too giving the same 
 error. They already have the JCE jars in their installation folders. 

 Is there some other requirement for this to work ?

 Thanks
 Shobha

 On Thursday, September 25, 2014 9:32:35 PM UTC+5:30, Dan Tran wrote:


 Very likely, you patch the wrong JRE

 -D

 On Thursday, September 25, 2014 8:46:01 AM UTC-7, Shobha Dashottar 
 wrote:

 I am setting up a  new Jenkins server. I have been using the Perforce 
 Plugin so far but this time I have switched to the P4 Plugin as has a 
 good 
 integration with the Credential Plugin to connect to the perforce 
 server.  

 For most of the VMs that I am connecting to it goes ahead with P4 
 command execution without issue. So far one VM is giving issue and 
 throwing 
 exception while even trying to communicate with the perforce server.

 P4: Unable to connect: 
 com.perforce.p4java.exception.ConnectionException: Error occurred during 
 the SSL handshake: invalid SSL session
 P4: Unable to use Workspace: java.lang.NullPointerException
 P4: Unable to close Perforce connection: java.lang.NullPointerException
 ERROR: Unable to update workspace: java.lang.NullPointerException

 After following some articles, I have added the jars from JCE for Java 7 
 inside the slave VMs jre/lib/security folder. 
 But still the error keeps popping up. 

 Does anyone know what is going on or is missing on that VM?

 Thanks
 Shobha




-- 
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/d/optout.


Query which jobs are tied to a particular node

2014-09-29 Thread Karl Ostmo
Clicking on a Node displays the list of *labels* applied to that Node. 
 Configuring a Job can display the list of labels/nodes that job is tied 
to.  But is there a way to directly query which Jobs are tied to a 
particular Node?

-- 
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/d/optout.


Re: Query which jobs are tied to a particular node

2014-09-29 Thread Daniel Beck
It's on the node page, below the list of labels (Projects tied to 
(nodename)). The jobs ' label must exactly match the node's name.

https://wiki.jenkins-ci.org/display/JENKINS/Label+Linked+Jobs+Plugin may help 
if that is not the case.

On 29.09.2014, at 20:15, Karl Ostmo kos...@gmail.com wrote:

 Clicking on a Node displays the list of *labels* applied to that Node.  
 Configuring a Job can display the list of labels/nodes that job is tied to.  
 But is there a way to directly query which Jobs are tied to a particular Node?
 
 -- 
 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/d/optout.

-- 
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/d/optout.


Re: Query which jobs are tied to a particular node

2014-09-29 Thread Karl Ostmo
Thanks, the Label Linked Jobs Plugin does exactly what I need, although
it's a bit of a chore to have to click Configure on each of our existing
labels and select the Activate plugin to list projects linked to this
label box.

On Mon, Sep 29, 2014 at 11:23 AM, Daniel Beck m...@beckweb.net wrote:

 It's on the node page, below the list of labels (Projects tied to
 (nodename)). The jobs ' label must exactly match the node's name.

 https://wiki.jenkins-ci.org/display/JENKINS/Label+Linked+Jobs+Plugin may
 help if that is not the case.

 On 29.09.2014, at 20:15, Karl Ostmo kos...@gmail.com wrote:

  Clicking on a Node displays the list of *labels* applied to that Node.
 Configuring a Job can display the list of labels/nodes that job is tied
 to.  But is there a way to directly query which Jobs are tied to a
 particular Node?
 
  --
  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/d/optout.

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Users group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-users/fPJXeZfIyrs/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
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/d/optout.


Cannot use mvn -pl !module-to-be-skipped in Jenkins

2014-09-29 Thread Andrew Yan
Hi all,

I'm pretty new to Jenkins and I'm trying to skip modules by maven reactor 
within Jenkins. 

In my Jenkins job, the Build Goals and options looks like this:

*clean install -U -X -pl !module-to-be-skipped*


It gives me error like below:

[ERROR] Could not find the selected project in the reactor: 
!module-to-be-skipped - [Help 1]
org.apache.maven.MavenExecutionException: Could not find the selected project 
in the reactor: !module-to-be-skipped
at 
org.apache.maven.DefaultMaven.trimSelectedProjects(DefaultMaven.java:877)
at 
org.apache.maven.DefaultMaven.createProjectDependencyGraph(DefaultMaven.java:811)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at 
org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)


The exact same options work fine on command line. Please help!

Thanks!

- Andrew

-- 
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/d/optout.


Jenkins builds out of sync after server rebuild

2014-09-29 Thread m...@shiphawk.com
We moved our Jenkins installation as a result of launching a new server. 
Ever since, we get build failure emails for past builds that are no longer
relevant.  I went through the process of cleaning out the builds directory
and resetting the build number to 1 for our projects.  After the clean, and
having a build fail, once again we received a build failure email with an
incorrect build number.

Any ideas how to completely reset Jenkins last failure email build numbers?

Thanks in advance...



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Jenkins-builds-out-of-sync-after-server-rebuild-tp4721843.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
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/d/optout.


jenkins: perforce sync in to workspace keep extra . for each file?

2014-09-29 Thread Suresh Vuyyuru
you can see the attached pic for reference.

why jenkins keeps extra . after each file, it's really irritates me.


bellow is the p4 sync log.

Started by user anonymous http://137.69.81.46:8080/user/null
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/jobs/guiautomation/workspace
Using master perforce client: jenkins-automation-selenium2
[workspace] $ /auto/tools/bin/p4 workspace -o jenkins-automation-selenium2
Last build changeset: 452218
[workspace] $ /auto/tools/bin/p4 changes -s submitted -m 1 
//jenkins-automation-selenium2/...
Failed to get last submitted changeset in the view, falling back to change 
counter. Error was: Failed to get change numbers.
Response from perforce was:
do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused
do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused
Change 452141 on 2014/09/29 by hulims@hulims_linux-gui 'new locator '

[workspace] $ /auto/tools/bin/p4 counter change
[workspace] $ /auto/tools/bin/p4 -s changes -s submitted 
//jenkins-automation-selenium2/...@452219,@452219
Sync'ing workspace to changelist 452219.
[workspace] $ /auto/tools/bin/p4 -s sync 
//jenkins-automation-selenium2/...@452219
Sync complete, took 228 ms
[selenium2] $ ant -file build.xml -Denv.DDSM_HOME=/home/selenium 
-Denv.DDEM_HOME=/home/selenium -Denv.DDMS_HOME=/home/selenium clean_all all
Buildfile: /var/lib/jenkins/jobs/guiautomation/workspace/selenium2/build.xml



-- 
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/d/optout.