date:20140205
















































Mark Waite
 closed  JENKINS-21116 as Fixed


Git Publisher does not use Credentials
















Confirmed closed in git-client-plugin 1.6.2





Change By:


Mark Waite
(05/Feb/14 2:03 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20286) JGit incorrectly reports changes detected when polling
















































Mark Waite
 closed  JENKINS-20286 as Fixed


JGit incorrectly reports changes detected when polling
















Confirmed fixed in git-client-plugin 1.6.2





Change By:


Mark Waite
(05/Feb/14 2:04 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
















































Mark Waite
 resolved  JENKINS-21016 as Fixed


Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
















Confirmed resolved in git-client-plugin 1.6.2





Change By:


Mark Waite
(05/Feb/14 2:03 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
















































Mark Waite
 closed  JENKINS-21016 as Fixed


Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
















Fix released in git-client-plugin 1.6.2





Change By:


Mark Waite
(05/Feb/14 2:03 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-20387) Timeout (10min) on git clone command













































  
Mark Waite
 edited a comment on  JENKINS-20387


Timeout (10min) on git clone command
















Pull requests have been accepted to both git-client-plugin and git-plugin.  This fix is available in git-client-plugin 1.6.2.  It will also need the next release of the git-plugin after 2.0.2



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error













































  
Mark Waite
 edited a comment on  JENKINS-20750


Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
















Pull requests have been accepted to both git-client-plugin and git-plugin.  This fix is available in git-client-plugin 1.6.2.  It will also need the next release of the git-plugin after 2.0.2



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [parameterized-trigger] (JENKINS-21586) Triggered project is not built with the same svn revision as the project which triggered it

2014-02-05 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-21586


Triggered project is not built with the same svn revision as the project which triggered it















Instead of using "Subversion revision", you can do as following:

	Use "Predefined parameters" and write like this:

UPSTREAM_SVN_REVISION=${SVN_REVISION}

	Configure following two Subversion in Project D:
	
		.../trunk/product@${UPSTREAM_SVN_REVISION}
		.../trunk/product/release@${UPSTREAM_SVN_REVISION}
	
	



You can specify revision to check out with repositoryurl@${revision}.
But I don't know well how it works, so you should test it carefully.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small













































  
Mark Waite
 edited a comment on  JENKINS-20445


Git plugin timeout is too small
















Pull request has been accepted.  This fix is available in git-client-plugin 1.6.2.  It will also need the next release of the git-plugin after 2.0.2



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small













































  
Mark Waite
 edited a comment on  JENKINS-20445


Git plugin timeout is too small
















Pull requests have been accepted to both git-client-plugin and git-plugin.  This fix is available in git-client-plugin 1.6.2.  It will also need the next release of the git-plugin after 2.0.2



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [multiple-scms] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building















































Mark Waite
 commented on  JENKINS-14019


Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building















If you were using wildcards in the branch names, then a bug in git-client-plugin versions prior to 1.6.2 might be affecting you.  The bug is exposed only if the branch name contains wildcards, so if your branch name was not using wildcards, then that bug is not the problem.

The bug was discovered while creating automated tests.  I don't think there is any bug report which describes it.  If you want to read the details of the bug, refer to https://github.com/jenkinsci/git-client-plugin/commit/e5e75d5a100905c0d5b332bbde3642e96ffe10a9 .



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [multiple-scms] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building













































  
Mark Waite
 edited a comment on  JENKINS-14019


Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
















If you were using wildcards in the branch names and were using Git remote polling, then a bug in git-client-plugin versions prior to 1.6.2 might be affecting you.  The bug is exposed only if the branch name contains wildcards, so if your branch name was not using wildcards, then that bug is not the problem.

The bug was discovered while creating automated tests.  I don't think there is any bug report which describes it.  If you want to read the details of the bug, refer to https://github.com/jenkinsci/git-client-plugin/commit/e5e75d5a100905c0d5b332bbde3642e96ffe10a9 .



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes















































Mark Waite
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















While writing tests for the git-client-plugin, I found a bug in the command line git implementation used for remote polling.  The bug is fixed in git-client-plugin 1.6.2 which was just released.

It is worth trying git-client-plugin 1.6.2 to see if it resolves the problem.  Refer to https://github.com/jenkinsci/git-client-plugin/commit/e5e75d5a100905c0d5b332bbde3642e96ffe10a9 for more details on the remote polling bug.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [postbuildscript] (JENKINS-11285) Ability to run postbuild script on a given node

2014-02-05 Thread tsara...@gmail.com (JIRA)















































Tony Sarajärvi
 commented on  JENKINS-11285


Ability to run postbuild script on a given node















Needing this as well.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-21664) Plugins with optional dependencies and compiled with Java6 cause Exception in loading

2014-02-05 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-21664


Plugins with optional dependencies and compiled with Java6 cause Exception in loading















Issue Type:


Bug



Assignee:


ikedam



Attachments:


stacktrace.log



Components:


core



Created:


05/Feb/14 2:23 PM



Description:


Steps to produce the problem:

	Install Copy Artifact
	Disable Maven plugin
	Restart Jenkins
	Fails to load Copy Artifact with: (full stacktrace is attached)

1) Error injecting constructor, java.lang.NoClassDefFoundError: hudson/maven/MavenBuild
  at hudson.plugins.copyartifact.CopyArtifact$DescriptorImpl.(Unknown Source)




I found followings:

	This can be reproduced when I package Copy Artifact with jdk 1.6.
	This cannot be reproduced when I package Copy Artifact with jdk 1.7.



It seems that something strange happens in Jenkins plugin loading system.
It may be a problem with guice 4.0 introduced in aea10298 (may be guice does not work with Java1.6).

What I will do are:

	Create a minimum plugin to reproduce the problem.
	Test what happens if reverted aea10298.
	Test what happens if downgrade guice to guice 3.0 (fails to compile?)






Environment:


Jenkins 1.532, 1.549

Copy Artifact 1.28




Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-10131) Git polling shouldn't need a workspace on a slave.















































Mark Waite
 commented on  JENKINS-10131


Git polling shouldn't need a workspace on a slave.















The 1.6.2 release of git-client-plugin fixed a bug in ls-remote polling for the command line git implementation.  The bug would have manifest itself as having ls-remote based polling show that there were changes when there were no changes.

Refer to https://github.com/jenkinsci/git-client-plugin/commit/e5e75d5a100905c0d5b332bbde3642e96ffe10a9 for more details on the bug.

That fix does not change the behavior described by Owen Jacobson.  Remote polling does not apply commit filtering, so if you're using inclusion or exclusion filters in your job definition, you can't use remote polling.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option "Branches to build" on Git Plugin for Jenkins















































Mark Waite
 commented on  JENKINS-20512


Git Plugin 2.0: Failure on Git Polling Log when using option "Branches to build" on Git Plugin for Jenkins















I agree with Charles' observation.  If the plugin cannot find Git, then it cannot perform its work.  You can either configure the location of Git for the slave as needed, or configure the slave, or consider adding "jgit" as a Git implementation on your master configuration, then define the job to use jgit rather than command line git.

The JGit implementation is not as full featured as the command line git implementation, so there are use cases which it does not meet.  You could attempt it and see if it meets your needs.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.

2014-02-05 Thread benjamin.de...@gmail.com (JIRA)















































Benjamin Dewez
 commented on  JENKINS-20682


Starting Jenkins with defined --webroot or JETTY_HOME not working.















This issue still opened for me and my teamworkers. It's the same behavior since https://issues.jenkins-ci.org/browse/JENKINS-18366.

Could you fix this one as soon as possible. Is it possible to up priority ? "Critical seems to be a good level" 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-02-05 Thread hvam...@gmail.com (JIRA)

Vamsi Hari
commented on JENKINS-21641

The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

Greg, thanks a lot for your quick response,
Let me explain what process we followed,
Say our build server as B and deployment server as D, which are on different hosts.
1)had copied the required jars(com.ibm.ws.admin.client_8.0.0.jar, com.ibm.ws.orb_8.0.0.jar) from D server to B server into the location specified as in the plugin doc.
2)had copied the DummyClientKeyFile.jks, DummyClientTrustFile.jks from D server to B server to certain location and given that path in the Job config.
3)had imported DummyClientTrustFile.jks to Java_home/jre/lib/security/cacerts.jks
4)had imported the websphere admin console url certificate of D server to Java_home/jre/lib/security/cacerts.jks in B server(suggested by you).

But Still the problem persists,
appreciate your help,

thanks,
Vamsi

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-21652) Building at each git-client polling interval even when no changes present















































Mark Waite
 commented on  JENKINS-21652


Building at each git-client polling interval even when no changes present















Would you be willing to install a more verbose logging unreleased version of git-client-plugin to help isolate the problem?  I think the polling may be hiding an exception (possibly hinted by the "could not remove the credential section", but there are several places  in that polling code which might throw the exception and a more verbose logging plugin would help isolate which case you're seeing.

That more verbose git-client-plugin doesn't exist yet.  I'll only create it if you're willing to use it to diagnose the problem further.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0















































Mark Waite
 commented on  JENKINS-20231


Wipe out repository & force clone option is broken since GIT plugin version 2.0















This problem is resolved for non-windows machines in git-client-plugin 1.6.2, available from the update center.  I was able to create a job which uses JGit or command line git and wipes the workspace successfully.

The command line git implementation also works to wipe the workspace on Windows.

The JGit implementation does not wipe the workspace on Windows due to JENKINS-19994 .



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin















































Greg Peters
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















Vamsi,

Open up your browser and point to your WebSphere Administration Console via https. Export the certificate using Google Chrome or some other browser. Import this certificate into the /jre/lib/security/cacerts file as well. Let me know if this works. You must also make sure the "cacerts" file is the correct JRE that Jenkins is using. Also, you're comments say your using "cacerts.jks" which is not the same as "cacerts". You can also try the InstallCert.java option which is defined in the "WebSphere Liberty" documentation. Let me know if this works.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
















































Mark Waite
 resolved  JENKINS-20231 as Fixed


Wipe out repository & force clone option is broken since GIT plugin version 2.0
















Fixed in git-client-plugin 1.6.2





Change By:


Mark Waite
(05/Feb/14 2:47 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin













































  
Greg Peters
 edited a comment on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 
















Vamsi,

Open up your browser and point to your WebSphere Administration Console via https. Export the certificate using Google Chrome or some other browser. Import this certificate into the /jre/lib/security/cacerts file as well. You must also make sure the "cacerts" file is in the correct JRE that Jenkins is using. Also, you're comments say your using "cacerts.jks" which is not the same as "cacerts". You can also try the InstallCert.java option which is defined in the "WebSphere Liberty" documentation. Let me know if this works.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20179) Jgit doesnt appear to work on Windows Slave
















































Mark Waite
 closed  JENKINS-20179 as Fixed


Jgit doesnt appear to work on Windows Slave
















Fixed in git-client-plugin





Change By:


Mark Waite
(05/Feb/14 2:52 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20231) Wipe out repository & force clone option is broken since GIT plugin version 2.0
















































Mark Waite
 closed  JENKINS-20231 as Fixed


Wipe out repository & force clone option is broken since GIT plugin version 2.0
















Change By:


Mark Waite
(05/Feb/14 2:53 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-21342) CliGitAPIImpl is hard-coded to use LocalLauncher
















































Mark Waite
 closed  JENKINS-21342 as Won't Fix


CliGitAPIImpl is hard-coded to use LocalLauncher
















Change By:


Mark Waite
(05/Feb/14 2:53 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-21298) Git polling not ignoring excluded users















































Mark Waite
 commented on  JENKINS-21298


Git polling not ignoring excluded users















The changes between 1.0.7 and 1.6.0 included a change to the default setting of "fast remote polling".  Previous, "slow" was the default, and "slow" allows user exclusions and commit content exclusions.  The new default is "fast", but does not allow user exclusions and commit content exclusions.

You can upgrade to the latest git client plugin and the latest git plugin if you change your job definitions to "Force polling using workspace".  That is the git-plugin 2.0 way of describing what was formerly called "fast remote polling".  The new description better describes what is really happening, since the reason "slow" is slow is because it required a workspace in order to perform polling.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-21638) PTC integrity plugin: version 1.22, download from MKS only folder without any file

2014-02-05 Thread cletusdso...@hotmail.com (JIRA)















































Cletus D'Souza
 commented on  JENKINS-21638


PTC integrity plugin: version 1.22, download from MKS only folder without any file















What is the version of JAVA/JRE running your Jenkins?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-19248) regression: Upgrading to 1.528 ("Upgrade Automatically") breaks "configure"
















































Jesse Glick
 resolved  JENKINS-19248 as Duplicate


regression: Upgrading to 1.528 ("Upgrade Automatically") breaks "configure"
















Believed to have been resolved with the fix in JENKINS-19457.





Change By:


Jesse Glick
(05/Feb/14 3:21 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-19511) Cannot use configure on any job after upgrade
















































Jesse Glick
 resolved  JENKINS-19511 as Duplicate


Cannot use configure on any job after upgrade
















Believed to have been resolved with the fix in JENKINS-19457.





Change By:


Jesse Glick
(05/Feb/14 3:21 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [gui] (JENKINS-19323) RegExp related Javascript exception on job configuration page
















































Jesse Glick
 resolved  JENKINS-19323 as Duplicate


RegExp related _javascript_ exception on job configuration page
















Believed to have been resolved with the fix in JENKINS-19457.





Change By:


Jesse Glick
(05/Feb/14 3:22 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [infrastructure] (JENKINS-9494) Configure System hangs with "LOADING" gray div covering top half of settings
















































Jesse Glick
 resolved  JENKINS-9494 as Duplicate


Configure System hangs with "LOADING" gray div covering top half of settings
















Believed to have been resolved with the fix in JENKINS-19457.





Change By:


Jesse Glick
(05/Feb/14 3:21 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads

2014-02-05 Thread cletusdso...@hotmail.com (JIRA)















































Cletus D'Souza
 commented on  JENKINS-21587


memory leak in Plugin 1.22 -orphaned Logger Threads















I highly doubt that this wasn't the problem in v1.18.  Nothing has changed in terms of the interaction with the API since v.18 (except for the sessions bug fix).

Seems like this is an API issue, so connecting to the Server directly will just move the problem from the Client Integration Point to the Server Integration Point.

My suggestion is you should monitor the threads (in the Integrity Client) like you've done in 1.22 and compare those results with 1.18 and see if there is a difference.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.

2014-02-05 Thread oldel...@java.net (JIRA)















































Richard Mortimer
 updated  JENKINS-20682


Starting Jenkins with defined --webroot or JETTY_HOME not working.
















Change By:


Richard Mortimer
(05/Feb/14 3:37 PM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [campfire] (JENKINS-19590) Campfire Plugin failing SSL check after upgrading Jenkins to latest 1.530

2014-02-05 Thread ke...@vanzonneveld.net (JIRA)













































  
Kevin van Zonneveld
 edited a comment on  JENKINS-19590


Campfire Plugin failing SSL check after upgrading Jenkins to latest 1.530
















To those running Ubuntu 12.04, after we installed the newer JRE (7 vs 6):

sudo aptitude install  openjdk-7-jre
sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java
sudo service jenkins stop
sudo service jenkins start

The error is gone and we're now seeing notifications in Campfire



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-02-05 Thread yves.schum...@ti8m.ch (JIRA)















































Yves Schumann
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















Any news on this? 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-02-05 Thread hvam...@gmail.com (JIRA)















































Vamsi Hari
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















Greg,
 Sorry haven't mentioned, still it is not working



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin

2014-02-05 Thread hvam...@gmail.com (JIRA)















































Vamsi Hari
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















Greg,
 What you said is correct, i had imported to cacerts.jks(custom one created). 
Now, 
1)i had correctly imported DummyClientTrustFile.jks to Java_home/jre/lib/security/cacerts
2)downloaded the installcert compiled it and run, and copied the generated jssecacerts file to cacerts location
java InstallCert :9043

But here, let me clarify you that i am using IBM WebSphere Application Server config, It may be out of context but could you please rectify once on what basis should we choose between liberty profile or Application Server  



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin















































Greg Peters
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















Another user suggested using JCE inside of WebSphere Application Server. It's definitely an SSL permissions issue from your error log. If WebSphere's cert was changed to use another one other than the Dummy* cert, you'll need to import that one instead. Keep me updated.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin













































  
Greg Peters
 edited a comment on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 
















Vamsi,

I understand you're using IBM WebSphere Application Server. I just wanted to see if the InstallCert helped you. WebSphere Liberty Profile is a different EE container from WAS. You'll know you're using WLP because it's totally different.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [websphere-deployer] (JENKINS-21641) The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin















































Greg Peters
 commented on  JENKINS-21641


The system cannot create a SOAP connector to connect to remote host using websphere deployer plugin 















Vamsi,

I understand you're using IBM WebSphere Application Server. I just wanted to see if the InstallCert helped you. WebSphere Liberty Profile is a different EE container from WAS. You'll now you're using WLP because it's totally different.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

2014-02-05 Thread vob...@gmail.com (JIRA)















































David Merrill
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















Thanks Mark, I just tried the new git-client plugin and it seems to fix the issue for me.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-05 Thread r...@owl.me.uk (JIRA)















































Rich Daley
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















Same issue here - exactly the same symptoms as described in this thread:


https://groups.google.com/forum/#!msg/jenkinsci-users/Q2jS5-6Zd9c/OS2rmeriJSwJ

Mine were also resolved by downgrading to 1.546.

~ R



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work

2014-02-05 Thread dirkh...@hotmail.com (JIRA)















































Dirk Hain
 commented on  JENKINS-20804


showDependencies for ${CHANGES} doesn't seem to work















Thanks for your comment, Alex. I checked the dependency graph and it is populated correctly. However, in the job that has the test failures I am copying test artifacts around. Not sure if that is the problem, I enabled fingerprinting of the copied artifacts to no avail. The fact that the dependent changes are shown correctly IF the job does not complete (no tests run) but does not show dependent changes IF the job completes unstable (tests are run with some failing) indicates that the root cause could be the copying of files. I will try to investigate further and see if I can get it working.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [performance-plugin] (JENKINS-21665) Add Parser/Support For Output From wrk

2014-02-05 Thread m...@johnmurray.io (JIRA)

John Murray
created JENKINS-21665

Add Parser/Support For Output From wrk

Issue Type:

New Feature

Assignee:

John Murray

Components:

performance-plugin

Created:

05/Feb/14 5:18 PM

Description:

wrk is a very useful utility for running basic or complex (via scripting interface). However it does not provide request-level data, but rather overall stats (mean, avg, etc.) that has been previously calculated within the performance plugin. wrk is a very useful utility for simulating higher levels of load on a single machine, which makes a great fit with many Jenkins setup(s)/build(s).

This will require some refactoring of the code, but overall I think it a good refactor should result in a more generalized codebase that can accept both request-level and aggregated results as input to parse.

The main concern is, wrk's output is not very standardized. So there may be concern of the format changing going forward. Not sure if the concern is much more than any other tool changing it's format, but it is a concern nonetheless.

Project:

Jenkins

Priority:

Major

Reporter:

John Murray

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes

2014-02-05 Thread zach....@metago.net (JIRA)















































Zachariah Day
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















Tried the new git-client-plugin (1.6.2) and am still seeing this issue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [github-api] (JENKINS-21667) Organization members list is a random selection of actual members

2014-02-05 Thread jjruss...@gmail.com (JIRA)















































John Russell
 created  JENKINS-21667


Organization members list is a random selection of actual members















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


github-api



Created:


05/Feb/14 5:29 PM



Description:


The code at the bottom of the description when run in the jenkins script console returns 30 members of the 82 members in my organization. I have found no pattern to which members it returns. Some are public, some are private. All are in github groups but many others in those same groups are missing. 

I discovered this because while using the github pullrequest builder plugin some users would be whitelisted and have their PRs run and some would not even though my organization was whitelisted. This appears to be the reason. 

The jenkins github user we use is an organization owner so should be able to see all users, but as I said, the list returned is both public and private already. 


import org.kohsuke.github.*;

serverAPIUrl = "https://api.github.com";
accessToken = "blahblah";
organisation = "myorg"

gh = GitHub.connectUsingOAuth(serverAPIUrl, accessToken);
org = gh.getOrganization(organisation)
members = org.getMembers();
members




Environment:


Jenkins 1.533 Github-api 1.43 ubuntu Amazon EC/2




Project:


Jenkins



Priority:


Major



Reporter:


John Russell

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git-client] (JENKINS-21652) Building at each git-client polling interval even when no changes present

2014-02-05 Thread robinson.ja...@gmail.com (JIRA)















































jason robinson
 commented on  JENKINS-21652


Building at each git-client polling interval even when no changes present















Absolutely!

Just point me to where to get it, or alternately, give me the repo URL and the maven build command and I'll build it.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [kpp-management] (JENKINS-21666) Provisioning profiles and keychains cannot be delivered when the master is not a Mac

2014-02-05 Thread tyr...@frontier.com (JIRA)















































Jonathan Zimmerman
 created  JENKINS-21666


Provisioning profiles and keychains cannot be delivered when the master is not a Mac















Issue Type:


Bug



Assignee:


Unassigned


Components:


kpp-management



Created:


05/Feb/14 5:28 PM



Description:


Our master is running on Windows Server 2012 and we have two Mac slaves.  I have successfully imported a keychain and several provisioning profiles, but when I attempt to use them in a job I get this error:

FATAL: Failed to copy C:\Jenkins\kpp_upload\iOS_Team_Provisioning_Profile_.mobileprovision to /User/jenkinssvc/Library/MobileDevice/Provisioning Profiles\0BD9DA02-3568-4EE7-94B9-766513F23728.mobileprovision
hudson.util.IOException2: Failed to copy C:\Jenkins\kpp_upload\0BD9DA02-3568-4EE7-94B9-766513F23728.mobileprovision to /User/*/Library/MobileDevice/Provisioning Profiles\0BD9DA02-3568-4EE7-94B9-766513F23728.mobileprovision
	at hudson.FilePath.copyTo(FilePath.java:1771)
	at com.sic.plugins.kpp.KPPProvisioningProfilesBuildWrapper.copyProvisioningProfiles(KPPProvisioningProfilesBuildWrapper.java:161)
	at com.sic.plugins.kpp.KPPProvisioningProfilesBuildWrapper.setUp(KPPProvisioningProfilesBuildWrapper.java:99)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:246)
Caused by: java.io.FileNotFoundException: /User/jenkinssvc/Library/MobileDevice/Provisioning Profiles\0BD9DA02-3568-4EE7-94B9-766513F23728.mobileprovision (No such file or directory)
	at java.io.FileOutputStream.open(Native Method)
	at java.io.FileOutputStream.(FileOutputStream.java:194)
	at java.io.FileOutputStream.(FileOutputStream.java:145)
	at hudson.FilePath$29.call(FilePath.java:1674)
	at hudson.FilePath$29.call(FilePath.java:1669)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:695)




Environment:


Master: Windows Server 2012

Slave: Mac OS X Mavericks




Project:


Jenkins



Priority:


Major



Reporter:


Jonathan Zimmerman

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [kpp-management] (JENKINS-21666) Provisioning profiles and keychains cannot be delivered when the master is not a Mac

2014-02-05 Thread tyr...@frontier.com (JIRA)
















































Jonathan Zimmerman
 resolved  JENKINS-21666 as Not A Defect


Provisioning profiles and keychains cannot be delivered when the master is not a Mac
















Ha.  My bad.  After looking at the error I noticed I entered the path in the node configuration wrong.





Change By:


Jonathan Zimmerman
(05/Feb/14 5:30 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings

2014-02-05 Thread jhans...@meetme.com (JIRA)















































Joe Hansche
 commented on  JENKINS-21104


Confluence Publisher Plugin ignores Jenkins proxy settings















I'm just trying to find a way to get the axis2 SOAP client to take a proxy configuration, and haven't had any luck yet.

the JIRA plugin also does not do anything with proxies – does that plugin work for you?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [jdepend] (JENKINS-17172) JDepend - handle multi project builds and wildcards paths

2014-02-05 Thread kaufman.b...@gmail.com (JIRA)















































Adam Kaufman
 commented on  JENKINS-17172


JDepend - handle multi project builds and wildcards paths















Another use case for this feature: when running a gradle build with multiple source sets, the gradle pmd plugin generates one file for each.  Even with a single source set and some tests, it will generate a main.xml and a test.xml.  It would be good to support this conventional functionality here.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [jdepend] (JENKINS-17172) JDepend - handle multi project builds and wildcards paths

2014-02-05 Thread kaufman.b...@gmail.com (JIRA)













































  
Adam Kaufman
 edited a comment on  JENKINS-17172


JDepend - handle multi project builds and wildcards paths
















Another use case for this feature: when running a gradle build with multiple source sets, the gradle jdepend plugin generates one file for each.  Even with a single source set and some tests, it will generate a main.xml and a test.xml.  It would be good to support this conventional functionality here.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes















































Mark Waite
 commented on  JENKINS-20767


Git plugin 2.0: Git polling causes builds even if no changes















Zachariah, can you include the output of one of your jobs that detected changes when there were none?  

Even better might be to include the output from a build and from the next build which follows it so that they can be compared.  If the change in git-client-plugin 1.6.2 fixed the problem for David Merrill and did not fix it for you, then I suspect the problem you're seeing is slightly different than the problem seen by David.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [performance-plugin] (JENKINS-21665) Add Parser/Support For Output From wrk

2014-02-05 Thread m...@johnmurray.io (JIRA)















































John Murray
 updated  JENKINS-21665


Add Parser/Support For Output From wrk 
















Change By:


John Murray
(05/Feb/14 5:21 PM)




Description:


{{wrk}} is a very useful utility for running basic or complex (via scripting interface). However it does not provide request-level data, but rather overall stats (mean, avg, etc.) that has been previously calculated within the {{performance}} plugin. {{wrk}} is a very useful utility for simulating higher levels of load on a single machine, which makes a great fit with many Jenkins setup(s)/build(s).This will require some refactoring of the code, but overall I think it a good refactor should result in a more generalized codebase that can accept both request-level and aggregated results as input to parse.The main concern is, wrk's output is not very _standardized_. So there may be concern of the format changing going forward. Not sure if the concern is much more than any other tool changing it's format, but it is a concern nonetheless.
 
 *Update*{{wrk}} website: https://github.com/wg/wrk



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [findbugs] (JENKINS-21155) swarm 1.10 incompatibility with findbugs 4.51















































Mark Waite
 commented on  JENKINS-21155


swarm 1.10 incompatibility with findbugs 4.51















There is no 1.12 on the distribution site, nor are there any commits for 1.12 on GitHub.

Maybe you meant 1.11, which is the current version and is showing the problem on the test machine which I was using?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [maven] (JENKINS-21554) NPE after "Waiting for Jenkins to finish collecting data"

2014-02-05 Thread tehran...@gmail.com (JIRA)















































Daniel Tehranian
 commented on  JENKINS-21554


NPE after "Waiting for Jenkins to finish collecting data"















Some more info:

This seems to be happening on Maven job type builds when the build state goes from Green (all unit tests pass) to Yellow (1 or more unit tests fail).  As long as tests are passing we have not seen this issue.  As soon as test fail or start to "flap", the job gets into this weird state where builds fail with the NPE.


We're considering moving away from the Maven job type after reading: http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [testng] (JENKINS-20438) Make it an option to show failed builds in trend graph

2014-02-05 Thread dstew...@afconnect.com (JIRA)















































Doug Stewart
 commented on  JENKINS-20438


Make it an option to show failed builds in trend graph















In my test environment I set up the Jenkins jobs to run my tests using a windows batch file.  Any test failures results in a failed build and the test results are not then included in the graph. I can work around this by using EXIT /B 0 in my batch file but this then does not indicate whether there were any failures for this particular test run.  I was relying on a failed test run/build to send me notification which no longer happens. I feel it would be better if including the results in the graph or not was set up as an available option.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-21163) Git Plugin causes Jenkins to stop working

2014-02-05 Thread caroe...@yahoo.com (JIRA)















































C. Alex Reober
 commented on  JENKINS-21163


Git Plugin causes Jenkins to stop working















Yes that was my initial solution.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [gerrit-trigger] (JENKINS-21036) NullPointerException in StreamWatchdog when trying to stop/restart

2014-02-05 Thread vladi...@gmail.com (JIRA)















































Vlad Dovlekaev
 commented on  JENKINS-21036


NullPointerException in StreamWatchdog when trying to stop/restart















Which release of Gerrit-Trigger your fix will be available in ?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [core] (JENKINS-17265) Builds disappearing from history

2014-02-05 Thread alex.ouzou...@me.com (JIRA)















































Alex Ouzounis
 commented on  JENKINS-17265


Builds disappearing from history















Hi all,

I am seeing the same problem occasionally and either restarting or reloading from disk fixes the problem.

I have a feeling that its related with:

"WARNING: Multiple builds have the same number: "

because every time I delete conflicting builds it goes away.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [perforce] (JENKINS-21498) Use Upstream Project revision does not seem to be working correctly

2014-02-05 Thread barn...@hotmail.com (JIRA)















































Andrew Barnish
 commented on  JENKINS-21498


Use Upstream Project revision does not seem to be working correctly















When I start the downstream job by hand it works correctly.
How can I inspect the "tag actions" for a job?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [performance-plugin] (JENKINS-21665) Add Parser/Support For Output From wrk

2014-02-05 Thread m...@johnmurray.io (JIRA)















































John Murray
 started work on  JENKINS-21665


Add Parser/Support For Output From wrk 
















Change By:


John Murray
(05/Feb/14 7:53 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [junit-attachments] (JENKINS-20737) Attached files appear in list, but throw a "404 Not Found" when attempting to view them

2014-02-05 Thread jrog...@socialserve.com (JIRA)















































Jonathan Rogers
 commented on  JENKINS-20737


Attached files appear in list, but throw a "404 Not Found" when attempting to view them















I just encountered very similar behavior. I determined that my problem was that my attachment file names contained percent-encoded slashes (%2F) and Jenkins was leaving them unmodified when generating links. The files existed but the links to them were wrong. My attachment file names had been deliberately percent-encoded since they had been generated from URL paths so I worked around the problem by simply using the last path segment instead of encoding slashes. I suspect that generating file names from URLs is a common need so Jenkins should deal with URL encoding in file names.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [support-core] (JENKINS-21669) Show ulimit -a















































Jesse Glick
 created  JENKINS-21669


Show ulimit -a















Issue Type:


New Feature



Assignee:


Unassigned


Components:


support-core



Created:


05/Feb/14 8:34 PM



Description:


ulimit -a (on Linux machines at least) can display information about process limits that may affect Jenkins. In particular, -n (open files) is usually too low.




Environment:


originally RM-2130




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [support-core] (JENKINS-21668) Show root certificates















































Jesse Glick
 created  JENKINS-21668


Show root certificates















Issue Type:


New Feature



Assignee:


Unassigned


Components:


support-core



Created:


05/Feb/14 8:33 PM



Description:


On occasion it would be useful to know what root certificate authorities are installed on the master JRE, all slave JREs, and also any JDK installations that can be found (tricky because of per-slave locations).




Environment:


originally RM-1886




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [support-core] (JENKINS-21671) Summarize Stapler bound objects















































Jesse Glick
 created  JENKINS-21671


Summarize Stapler bound objects















Issue Type:


New Feature



Assignee:


Unassigned


Components:


support-core



Created:


05/Feb/14 8:39 PM



Description:


Find some way to obtain all the BoundObjectTable.Table instances held in session attributes, and produce a histogram of the implementation classes of the targets (referents). This can help diagnose potential memory leaks (JENKINS-16341).




Environment:


originally RM-1866




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[JIRA] [support-core] (JENKINS-21670) Option to anonymize customer labels