[JIRA] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor

2014-04-22 Thread vanpoppel.ke...@gmail.com (JIRA)














































Kevin Van Poppel
 commented on  JENKINS-22427


Parameterized Remote Trigger Plugin fails when remote job waits for available executor















'wait to trigger remote builds until no other builds are running' doesn't fix the issue for me.

Do you have any idea when this JSON update is getting released?



























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


[JIRA] [git] (JENKINS-22706) SSH

2014-04-22 Thread flavio.do...@gmx.ch (JIRA)














































Flavio Donzé
 created  JENKINS-22706


SSH















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git, git-client



Created:


22/Apr/14 7:02 AM



Description:


Trying to switch from HTTPS to SSH. Getting the following exception after switching (changed the link for this post):

Fetching upstream changes from git@server:username/repository.git
using GIT_SSH to set credentials server ssh
FATAL: Failed to fetch from git@server:username/repository.git
hudson.plugins.git.GitException: Failed to fetch from git@server:username/repository.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:623)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:855)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1251)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:605)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:514)
	at hudson.model.Run.execute(Run.java:1703)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress git@server:username/repository.git +refs/heads/master:refs/remotes/origin/master" returned status code 128:
stdout: 
stderr: 'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1276)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1146)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:254)
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:621)
	... 11 more




Environment:


git 2.2.1, git-client 1.8.0, windows server 2008 R2 64bit




Project:


Jenkins



Priority:


Major



Reporter:


Flavio Donzé

























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


[JIRA] [git] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH

2014-04-22 Thread flavio.do...@gmx.ch (JIRA)














































Flavio Donzé
 updated  JENKINS-22706


git fetching fails after switching from HTTPS to SSH
















Change By:


Flavio Donzé
(22/Apr/14 7:03 AM)




Summary:


gitfetchingfailsafterswitchingfromHTTPSto
SSH



























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


[JIRA] [slave-setup] (JENKINS-16418) Cannot start Windows Server 2012 slave.

2014-04-22 Thread rkmou...@yahoo.com (JIRA)














































Raghwendra Mourya
 commented on  JENKINS-16418


Cannot start Windows Server 2012 slave. 















To connect to Windows Server 2012, Change Permission for following registry key to Full Control:

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID{72C24DD5-D70A-438B-8A42-98424B88AFB8}

Launch 'regedit' (as Administrator)
Find (Ctrl+F) the following registry key: "{72C24DD5-D70A-438B-8A42-98424B88AFB8}" in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\
Right click and select 'Permissions'
Change owner to administrators group (Advanced...).
Change permissions for administrators group. Grant Full Control.
Change owner back to TrustedInstaller (user is "NT Service\TrustedInstaller" on local machine)
Restart Remote Registry Service (Administrative Tools / Services)



























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


[JIRA] [scm-api] (JENKINS-22707) xml api: first character of changeSet/item/affectedPath value is truncated

2014-04-22 Thread mistaf...@java.net (JIRA)














































mistafunk
 created  JENKINS-22707


xml api: first character of changeSet/item/affectedPath value is truncated















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


scm-api



Created:


22/Apr/14 7:59 AM



Environment:


Linux




Project:


Jenkins



Priority:


Minor



Reporter:


mistafunk

























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


[JIRA] [slave-setup] (JENKINS-16418) Cannot start Windows Server 2012 slave.

2014-04-22 Thread rkmou...@yahoo.com (JIRA)












































 
Raghwendra Mourya
 edited a comment on  JENKINS-16418


Cannot start Windows Server 2012 slave. 
















To connect to Windows Server 2012, Change Permission for following registry key to Full Control:


	HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID{72C24DD5-D70A-438B-8A42-98424B88AFB8}

- HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}

Launch 'regedit' (as Administrator)
Find (Ctrl+F) the following registry key: "{72C24DD5-D70A-438B-8A42-98424B88AFB8}" in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\
Right click and select 'Permissions'
Change owner to administrators group (Advanced...).
Change permissions for administrators group. Grant Full Control.
Change owner back to TrustedInstaller (user is "NT Service\TrustedInstaller" on local machine)
Repeat the steps above for HKEY_CLASSES_ROOT\CLSID{76A64158-CB41-11D1-8B02-00600806D9B6}
Restart Remote Registry Service (Administrative Tools / Services)





























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


[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-04-22 Thread daniel.kuff...@googlemail.com (JIRA)














































Daniel Kuffner
 created  JENKINS-22708


JobDSL Plugin can produce never ending jobs (resource leak)















Issue Type:


Bug



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


22/Apr/14 8:34 AM



Description:



It is possible to create a job which will never end by configuring a job like:


job {
	name "Test"
	configure { root -
	 // Please note I forgot to start with "root"
		properties / 'hudson.plugins.disk__usage.DiskUsageProperty').@plugin="disk-usage@0.23"
	}
}


I did obviously a mistake in the configuration block since I start with "properties" instead of "root". Neverless it would be good if in this case the job would just fail.


JobDSL Plugin Version 1.22





Project:


Jenkins



Priority:


Blocker



Reporter:


Daniel Kuffner

























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


[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-04-22 Thread daniel.kuff...@googlemail.com (JIRA)














































Daniel Kuffner
 updated  JENKINS-22708


JobDSL Plugin can produce never ending jobs (resource leak)
















Change By:


Daniel Kuffner
(22/Apr/14 8:37 AM)




Description:


Itispossibletocreateajobwhichwillneverendbyconfiguringajoblike:{code}job{	nameTest	configure{root-	//PleasenoteIforgottostartwithroot
		(
		properties/
(
hudson.plugins.disk__usage.DiskUsageProperty).@plugin=disk-usage@0.23	}}{code}IdidobviouslyamistakeintheconfigurationblocksinceIstartwithpropertiesinsteadofroot.Neverlessitwouldbegoodifinthiscasethejobwouldjustfail.JobDSLPluginVersion1.22



























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


[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-04-22 Thread daniel.kuff...@googlemail.com (JIRA)














































Daniel Kuffner
 updated  JENKINS-22708


JobDSL Plugin can produce never ending jobs (resource leak)
















Change By:


Daniel Kuffner
(22/Apr/14 8:36 AM)




Description:



Itispossibletocreateajobwhichwillneverendbyconfiguringajoblike:{code}job{	nameTest	configure{root-	//PleasenoteIforgottostartwithroot		properties/
(
hudson.plugins.disk__usage.DiskUsageProperty).@plugin=disk-usage@0.23	}}{code}IdidobviouslyamistakeintheconfigurationblocksinceIstartwithpropertiesinsteadofroot.Neverlessitwouldbegoodifinthiscasethejobwouldjustfail.JobDSLPluginVersion1.22



























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


[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-04-22 Thread daniel.kuff...@googlemail.com (JIRA)














































Daniel Kuffner
 commented on  JENKINS-22708


JobDSL Plugin can produce never ending jobs (resource leak)















Just for clearifiaction, the JobDSL Plugin job hangs forever



























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


[JIRA] [dependency-check-jenkins] (JENKINS-21990) DependencyCheck aborted due to exception

2014-04-22 Thread troe...@axway.com (JIRA)














































Thorsten Roemer
 commented on  JENKINS-21990


DependencyCheck aborted due to exception















Sorry, report and log are not available anymore from that date.



























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


[JIRA] [job-dsl-plugin] (JENKINS-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-04-22 Thread daniel.kuff...@googlemail.com (JIRA)












































 
Daniel Kuffner
 edited a comment on  JENKINS-22708


JobDSL Plugin can produce never ending jobs (resource leak)
















Just for clarification, the JobDSL Plugin job hangs forever



























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


[JIRA] [core] (JENKINS-22710) Broken Debian upgrades because postinst doesn't check for present group/user

2014-04-22 Thread jenkins-ci....@michael-prokop.at (JIRA)














































Michael Prokop
 commented on  JENKINS-22710


Broken Debian upgrades because postinst doesnt check for present group/user















See https://github.com/jenkinsci/jenkins/pull/1208 for my PR.



























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


[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves

2014-04-22 Thread svalch...@gmail.com (JIRA)














































Stoil Valchkov
 commented on  JENKINS-18781


Configurable channel timeout for slaves















Hi guys,

Are there any plans to fix that soon? It is crucial to have it in order to have stable environment.

Thanks



























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


[JIRA] [git-client] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate

2014-04-22 Thread j...@lucidity.ie (JIRA)














































jose porcel
 commented on  JENKINS-22675


Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate















Installed the plugin, same issue.

It works with a public GitHub repository, but not with my GitLab instance, and the issue is not related to credentials (tried keys and username and password).

The Jenkins version I use is Jenkins ver. 1.559 and it is under Windows (shamefully), I am running it for testing purposes with default basic configuration.



























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


[JIRA] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account

2014-04-22 Thread svalch...@gmail.com (JIRA)














































Stoil Valchkov
 commented on  JENKINS-14847


Apply button not taken into account















1.532.3 is having the same problem.



























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


[JIRA] [email-ext] (JENKINS-22656) Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.

2014-04-22 Thread godheart...@gmail.com (JIRA)














































Gabor Borbely
 commented on  JENKINS-22656


Email-ext plugin gets a NullPointerExeptions. Works every ~ 8 times / 10.















I could install the latest LTS version of Jenkins, and I updated the email-ext plugin too. I would like to test the application for a few days, then i will go back with my latest feedback! brb



























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


[JIRA] [perforce] (JENKINS-22711) Using streams in perforce doesn't use -s switch on workspace command

2014-04-22 Thread niknap...@hotmail.com (JIRA)














































Nik San
 created  JENKINS-22711


Using streams in perforce doesnt use -s switch on workspace command















Issue Type:


Bug



Affects Versions:


current



Assignee:


Rob Petti



Components:


perforce



Created:


22/Apr/14 10:54 AM



Description:


When using streams in the Perforce plugin the following command is issued.

jenkins_test $ "C:\Program Files\Perforce\p4.exe" workspace -o -S //Streamed_Depot/MyStream NikSanWS

But this doesn't perform a switch workspace view, so perforce is still working the stream selected in P4V etc rather than the one specified bu the plugin. A fix is to supply an extra -s parameter like so. (only when dealing with streams)

jenkins_test $ "C:\Program Files\Perforce\p4.exe" workspace -o -s -S //Streamed_Depot/MyStream NikSanWS




Project:


Jenkins



Priority:


Major



Reporter:


Nik San

























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 started work on  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:04 AM)




Status:


Open
InProgress



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 updated  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:04 AM)




Assignee:


rsandell
rin_ne



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 stopped work on  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:15 AM)




Status:


InProgress
Open



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)















































rin_ne
 resolved  JENKINS-22634 as Incomplete


Installing gerrit plugin somehow affects ability to display details of git changes
















PR: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/144





Change By:


rin_ne
(22/Apr/14 11:17 AM)




Status:


Open
Resolved





Resolution:


Incomplete



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 reopened  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:19 AM)




Resolution:


Incomplete





Status:


Resolved
Reopened



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 started work on  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:20 AM)




Status:


Reopened
InProgress



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 stopped work on  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 11:21 AM)




Status:


InProgress
Open



























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


[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0

2014-04-22 Thread svalch...@gmail.com (JIRA)














































Stoil Valchkov
 commented on  JENKINS-21640


scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0















Unfortunately we are with Subversion plugin 2.1 and would really like to use SCM plugin. Is there a workaround? It would be great if we can somehow fix it at least temporarily.

Thanks 



























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


[JIRA] [perforce] (JENKINS-2947) Perforce should factor out global configuration to the global page

2014-04-22 Thread shobha_dashot...@symantec.com (JIRA)














































Shobha Dashottar
 commented on  JENKINS-2947


Perforce should factor out global configuration to the global page















Has anyone found a solution to this? Recently our Perforce IT has mandated using AD accounts for Perforce authentication which expire every 90 days. This is causing us a lot of grief as we have 100 of build jobs across 4-5 Jenkins servers. It would be a great help if this enhancement could be implemented.
 On one defect trail I read we could even use global config, mask password and parameter substitution but note how that works. Any clue?



























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


[JIRA] [gerrit-trigger] (JENKINS-22595) REST is broken due to trailing slash in URL

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 started work on  JENKINS-22595


REST is broken due to trailing slash in URL
















Change By:


rin_ne
(22/Apr/14 11:40 AM)




Status:


Open
InProgress



























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


[JIRA] [gerrit-trigger] (JENKINS-22595) REST is broken due to trailing slash in URL

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 updated  JENKINS-22595


REST is broken due to trailing slash in URL
















Change By:


rin_ne
(22/Apr/14 11:40 AM)




Assignee:


rsandell
rin_ne



























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


[JIRA] [gerrit-trigger] (JENKINS-22595) REST is broken due to trailing slash in URL

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 stopped work on  JENKINS-22595


REST is broken due to trailing slash in URL
















Change By:


rin_ne
(22/Apr/14 11:45 AM)




Status:


InProgress
Open



























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


[JIRA] [gerrit-trigger] (JENKINS-22595) REST is broken due to trailing slash in URL

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 commented on  JENKINS-22595


REST is broken due to trailing slash in URL















PR: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/145



























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


[JIRA] [build-flow] (JENKINS-22596) Issue where all jobs get blocked in 'pending' state while using Build Flow plugin and build parameters

2014-04-22 Thread e...@exelerus.com (JIRA)














































Edin Mujkanovic
 commented on  JENKINS-22596


Issue where all jobs get blocked in pending state while using Build Flow plugin and build parameters 















We have the same problem and this is a pretty big issue for us since our jobs often have 30-40 parameters with default values, and we start them by setting 1-2 of those through the build-flow plugin.
Our env: Jenkins 1.559 and build-flow 0.11.1



























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


[JIRA] [git] (JENKINS-21914) Intermittent Git(hub) polling errors on Windows

2014-04-22 Thread ryanmalg...@gmail.com (JIRA)














































Ryan Malgren
 commented on  JENKINS-21914


Intermittent Git(hub) polling errors on Windows















I had this problem and just as the error message said there was a file called config.lock that needed to be deleted from .git folder.

The file was located in a path like this on my Jenkins server:
C:\GitRepo\master\RepoName\.git\config.lock

Once I deleted that file, my build was happy again.



























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


[JIRA] [tfs] (JENKINS-21460) TFS plugin throws NumberFormatException

2014-04-22 Thread niclas.lindqv...@bytbil.com (JIRA)














































Niclas Lindqvist
 commented on  JENKINS-21460


TFS plugin throws NumberFormatException 















I get the same result trying to checkout code from TFS 2013 using the TFS Plugin.
Any news on this issue?

I run Jenkins. 1.560 on a Windows 8.1 machine.
TFS runs on Windows 2012 server.
Login via domain account.



























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


[JIRA] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22673


Sites for nested Maven multi-module projects deeper than one level are archived flat















Code changed in jenkins
User: Marcel
Path:
 src/test/java/hudson/maven/MavenModuleTest.java
 src/test/java/hudson/maven/MavenProjectTest.java
 src/test/resources/hudson/maven/maven-nested-multimodule-site.zip
http://jenkins-ci.org/commit/maven-plugin/2e719ab36d416e47791b6b53c69195cfbe4b4b8f
Log:
  JENKINS-22673 added test for nested multi-module site building





























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


[JIRA] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22673


Sites for nested Maven multi-module projects deeper than one level are archived flat















Code changed in jenkins
User: Marcel
Path:
 src/main/java/hudson/maven/reporters/MavenSiteArchiver.java
http://jenkins-ci.org/commit/maven-plugin/1c42b1986a1069c80346296fda5b4085f2c30fe7
Log:
  FIXED JENKINS-22673 replicate maven project structure for site archiving





























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


[JIRA] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat

2014-04-22 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 resolved  JENKINS-22673 as Fixed


Sites for nested Maven multi-module projects deeper than one level are archived flat
















Change By:


SCM/JIRA link daemon
(22/Apr/14 12:21 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/d/optout.


[JIRA] [maven] (JENKINS-22673) Sites for nested Maven multi-module projects deeper than one level are archived flat

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22673


Sites for nested Maven multi-module projects deeper than one level are archived flat















Code changed in jenkins
User: Olivier Lamy
Path:
 src/main/java/hudson/maven/reporters/MavenSiteArchiver.java
 src/test/java/hudson/maven/MavenModuleTest.java
 src/test/java/hudson/maven/MavenProjectTest.java
 src/test/resources/hudson/maven/maven-nested-multimodule-site.zip
http://jenkins-ci.org/commit/maven-plugin/574406cfc25c8c668b8dcf638718c238757ede98
Log:
  Merge pull request #22 from marcelst/master

JENKINS-22673  Sites for nested Maven multi-module projects deeper than one level are archived flat


Compare: https://github.com/jenkinsci/maven-plugin/compare/a0ab96348cb0...574406cfc25c




























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


[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0

2014-04-22 Thread fcamb...@java.net (JIRA)














































Frédéric Camblor
 commented on  JENKINS-21640


scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0















Downgrade to subversion plugin  2.0

But I don't know if the downgrade will play well with your upgraded config.xml files, make tests before downgrading.



























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


[JIRA] [jdk_parameter_plugin] (JENKINS-22712) NPE when project build triggered remotely

2014-04-22 Thread r...@otit.fi (JIRA)














































Risto Oikarinen
 created  JENKINS-22712


NPE when project build triggered remotely















Issue Type:


Bug



Assignee:


Unassigned


Components:


jdk_parameter_plugin



Created:


22/Apr/14 12:35 PM



Description:


I have a job where build is automatically triggered by git commits.
(ie. Trigger builds remotely (e.g., from scripts) is enabled)
I'm using Jenkins 1.560 and JDK Parameter Plugin 1.0 and I have a default JDK set for the plugin (jdk1.8)

User-triggered builds work normally.
Whenever automatic build occurs, a NPE is thrown:

using GIT_SSH to set credentials 
Checking out Revision 1c33be19e2353a9f63d84a3749d657e728acd049 (origin/master)
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com
java.lang.NullPointerException
	at com.datalex.jdkparameter.JavaParameterValue.createBuildWrapper(JavaParameterValue.java:54)
	at hudson.model.ParametersAction.createBuildWrappers(ParametersAction.java:78)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:646)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:519)
	at hudson.model.Run.execute(Run.java:1703)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:525)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
project=hudson.maven.MavenModuleSet@677131a2DC2_autobuilder




Project:


Jenkins



Priority:


Major



Reporter:


Risto Oikarinen

























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


[JIRA] [email-ext] (JENKINS-22713) '+' char in content encoded as #43;

2014-04-22 Thread stephan.l...@gmail.com (JIRA)














































Stephan Lips
 created  JENKINS-22713


+ char in content encoded as #43;















Issue Type:


Bug



Affects Versions:


current



Assignee:


Alex Earl



Components:


email-ext



Created:


22/Apr/14 12:38 PM



Description:


'+' chars in the email content are encoded/received as as .  This is true regardless whether

	a '+' is included verbatim
	an email template is used
	any content containing a '+' is read in from file.



Use case: attempting to inline base64 as image source will cause image non-renderable, due to #43.  

Note that this also affects any data that is inlined by the email-ext plugin via the inline-data attribute on img tags (handled/processed by CssInliner).




Environment:


OS X, RHEL




Project:


Jenkins



Priority:


Minor



Reporter:


Stephan Lips

























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


[JIRA] [jdk_parameter_plugin] (JENKINS-22712) NPE when project build triggered remotely

2014-04-22 Thread r...@otit.fi (JIRA)














































Risto Oikarinen
 updated  JENKINS-22712


NPE when project build triggered remotely
















Change By:


Risto Oikarinen
(22/Apr/14 12:38 PM)




Description:


Ihaveajobwherebuildisautomaticallytriggeredbygitcommits.(ie.Triggerbuildsremotely(e.g.,fromscripts)isenabled)ImusingJenkins1.560andJDKParameterPlugin1.0andIhaveadefaultJDKsetfortheplugin(jdk1.8)User-triggeredbuildsworknormally.Wheneverautomaticbuildoccurs,aNPEisthrown:
{code}
usingGIT_SSHtosetcredentialsCheckingoutRevision1c33be19e2353a9f63d84a3749d657e728acd049(origin/master)ERROR:Processingfailedduetoabuginthecode.Pleasereportthistojenkinsci-us...@googlegroups.comjava.lang.NullPointerException	atcom.datalex.jdkparameter.JavaParameterValue.createBuildWrapper(JavaParameterValue.java:54)	athudson.model.ParametersAction.createBuildWrappers(ParametersAction.java:78)	athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:646)	athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:519)	athudson.model.Run.execute(Run.java:1703)	athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:525)	athudson.model.ResourceController.execute(ResourceController.java:88)	athudson.model.Executor.run(Executor.java:231)project=hudson.maven.MavenModuleSet@677131a2[DC2_autobuilder]
{code}



























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


[JIRA] [email-ext] (JENKINS-22713) '+' char in content encoded as #43;

2014-04-22 Thread stephan.l...@gmail.com (JIRA)














































Stephan Lips
 commented on  JENKINS-22713


+ char in content encoded as #43;















Adding email exchange on jenkins forum with Slide that preceded opening of this issue.

Slide slide.o@gmail.com
6:41 PM (12 hours ago)

to Jenkins 
File an issue and I'll get to it when I can.



On Mon, Apr 21, 2014 at 4:12 PM, Stephan Lips stephan.l...@gmail.com wrote:
Hmmm.  So I looked at the src for CssInliner.  Most interesting is that if the attribute data-inline="true" is set on an img node, the image is retrieved, base64-encoded, and included inline.  So I did a li'l test, where I referenced an image via URL, setting data-inline="true".  And lo and behold, the resulting base64-encoded string that arrived in my inbox had  the '+' characters replaced with  (prohibiting it from rendering)

Other than that, the only code that explicitly deals with the '+' for replacement is line 135:
String trimmedStylesheet = stylesheet.replaceAll("\n", "").replaceAll("/\\*.*?*/", "").replaceAll(" +", " ");
and would not apply, due to the leading space.

So looks like this issue manifests itself with use of the data-inline attribute, making that feature essentially unusable.  In general, base64-encoded strings (or '+' chars anywhere in the email content) do not work with ext-email.

So where/how do we go from here? 

Thx, S



On Mon, Apr 21, 2014 at 5:43 PM, Slide slide.o@gmail.com wrote:
Hmm, actually, it looks like the CssInliner could be doing something. It processes anything that is text/html. I had forgotten about that because I didn't write that part. There is currently not a way to turn it off.


On Mon, Apr 21, 2014 at 3:24 PM, Stephan Lips stephan.l...@gmail.com wrote:
Nope, does not make a difference.  I blank'd out all fields in the default email configuration, and configured the ext-email plug-in overrides.  '+' characters in email content still arrive as 

Is some jenkins/ext-email dependency doing this?

Thx, S


On Mon, Apr 21, 2014 at 3:59 PM, Slide slide.o@gmail.com wrote:
Email-ext DOES have it's own server configuration, you just have to check "override default settings" in the global config. That would be another thing to try, overriding the default settings so that the session is created completely in email-ext.


On Mon, Apr 21, 2014 at 12:37 PM, Stephan Lips stephan.l...@gmail.com wrote:
If I check 'save to workspace' the '+' chars are not being escaped with .

FWIW, I also tried a couple different email providers (my corporate smtp server, and google), in both cases the arriving email had the '+' substituted for #34.  Since ext-email does not have its own mail server configuration, I assume it is piggy-backing of the standard email configuration/server.  Is this substitution happening further downstream, e.g. in the regular email code?

Thx, S


On Mon, Apr 21, 2014 at 2:16 PM, Slide slide.o@gmail.com wrote:
I don't know of anything in the email-ext code that would escape anything like you are describing. Can you try checking the "save to workspace" checkbox in the project settings and see if the same escaping is shown in the saved off file?


On Mon, Apr 21, 2014 at 11:08 AM, Stephan Lips stephan.l...@gmail.com wrote:
Yes, the issue reproduces with a template.  Curiously, when testing the template (through the 'Email Template Testing' link in the workspace), the inserted base64 string renders correctly.  The received email, however, still sees the  escapes instead of the '+' char, causing the base64 img src to not render.

The template I'm using (saved to $JENKINS_HOME/email-templates) is

TABLE
  TRTD align="right"IMG SRC=""blue.gif" : build.result.toString() == 'FAILURE' ? 'red.gif' : 'yellow.gif' %" /
  /TDTD valign="center"B style="font-size: 200%;"BUILD ${build.result}/B/TD/TR
  TRTDBuild URL/TDTDA href=""${rooturl}${build.url}/A/TD/TR
  TRTDProject:/TDTD${project.name}/TD/TR
  TRTDDate of build:/TDTD${it.timestampString}/TD/TR
  TRTDBuild duration:/TDTD${build.durationString}/TD/TR
/TABLE
BR/


img src=""my-image.b64").readToString() %" width="700" height="400"


The file 'my-image.b64' is confirmed to exist in the workspace, and contain valid base64.  The contents of the file are inserted correctly, save for the html-escaped '+' char.

So, how do I turn off html escaping of content?

Thx, S


On Mon, Apr 21, 2014 at 9:59 AM, Slide slide.o@gmail.com wrote:
Yes, I'd like you to try and see if the issue occurs with a template.

On Apr 21, 2014 6:49 AM, "Stephan Lips" stephan.l...@gmail.com 

[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0

2014-04-22 Thread svalch...@gmail.com (JIRA)














































Stoil Valchkov
 commented on  JENKINS-21640


scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0















That will require much efforts for reconfiguration of the existing jobs. For time being we'll try https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin. Our main goal is to have a way to view changes in configurations.



























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


[JIRA] [plugin] (JENKINS-22604) WebSphere-deployer Plugin doesnot work with Security Emnabled WAS

2014-04-22 Thread pradeepkumar.devarapa...@gmail.com (JIRA)














































pradeep kumar
 commented on  JENKINS-22604


WebSphere-deployer Plugin doesnot work with Security Emnabled WAS















i have configure jenkin with websphere-deployer plugin, and trying to deploy one ear to websphere, build was success but i am getting below error while installing that ear to websphere please help on this

Deploying New 'LoyaltyAdminWebEAR' to IBM WebSphere Application Server
Starting New Application 'LoyaltyAdminWebEAR'...
Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not start artifact 'LoyaltyAdminWebEAR': 
	at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.startArtifact(WebSphereDeploymentService.java:186)
	at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.startArtifact(WebSphereDeployerPlugin.java:206)
	at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:172)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:779)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1541)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)

Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE



























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


[JIRA] [jenkins-tracker] (JENKINS-22714) all slaves are terminated when javaw is stopped on one slave

2014-04-22 Thread z...@innovid.com (JIRA)














































ziv  SHAPIRA
 created  JENKINS-22714


all slaves are terminated when javaw is stopped on one slave















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


jenkins-fail1.png



Components:


jenkins-tracker



Created:


22/Apr/14 1:31 PM



Description:


When I ran Java update on a slave, it requested that javaw is stopped.
when approving that ALL the slaves were terminated. 
I am adding the error in the server log for one of the slaves.

The slaves pages also display a "failed to abort" error (pic attached) and cannot be restarted using javaw, before the whole server is restarted.

--
WARNING: NioChannelHub keys=17 gen=201082: Computer.threadPoolForRemoting 2 for + HV1-VM-SLAVE-22 terminated
java.io.IOException: Failed to abort
at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:184)
at org.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:599)
at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:481)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
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:662)
Caused by: java.nio.channels.ClosedChannelException
at sun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:663)
at sun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:430)
at org.jenkinsci.remoting.nio.Closeables$1.close(Closeables.java:20)
at org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport.closeR(NioChannelHub.java:289)
at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:226)
at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:224)
at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:474)
... 7 more
Apr 22, 2014 8:56:08 AM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed




Environment:


ubuntu (Server) Windows7 (slaves)




Project:


Jenkins



Labels:


jenkins




Priority:


Major



Reporter:


ziv  SHAPIRA

























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


[JIRA] [perforce] (JENKINS-22711) Using streams in perforce doesn't use -s switch on workspace command

2014-04-22 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 assigned  JENKINS-22711 to Unassigned



Using streams in perforce doesnt use -s switch on workspace command
















Change By:


Rob Petti
(22/Apr/14 1:33 PM)




Assignee:


RobPetti



























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


[JIRA] [jenkins-tracker] (JENKINS-22714) all slaves are terminated when javaw is stopped on one slave

2014-04-22 Thread z...@innovid.com (JIRA)














































ziv  SHAPIRA
 updated  JENKINS-22714


all slaves are terminated when javaw is stopped on one slave
















Change By:


ziv  SHAPIRA
(22/Apr/14 1:33 PM)




Description:


WhenIranJavaupdateonaslave,itrequestedthatjavawisstopped.whenapprovingthatALLtheslaveswereterminated.Iamaddingtheerrorintheserverlogforoneoftheslaves.Theslavespagesalsodisplayafailedtoaborterror(picattached)andcannotberestartedusingjavaw,beforethewholeserverisrestarted.
version:1.560
--WARNING:NioChannelHubkeys=17gen=201082:Computer.threadPoolForRemoting[#2]for+HV1-VM-SLAVE-22terminatedjava.io.IOException:Failedtoabortatorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:184)atorg.jenkinsci.remoting.nio.NioChannelHub.abortAll(NioChannelHub.java:599)atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:481)atjenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)atjava.util.concurrent.FutureTask.run(FutureTask.java:138)atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)atjava.lang.Thread.run(Thread.java:662)Causedby:java.nio.channels.ClosedChannelExceptionatsun.nio.ch.SocketChannelImpl.shutdownInput(SocketChannelImpl.java:663)atsun.nio.ch.SocketAdaptor.shutdownInput(SocketAdaptor.java:430)atorg.jenkinsci.remoting.nio.Closeables$1.close(Closeables.java:20)atorg.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport.closeR(NioChannelHub.java:289)atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:226)atorg.jenkinsci.remoting.nio.NioChannelHub$NioTransport$1.call(NioChannelHub.java:224)atorg.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:474)...7moreApr22,20148:56:08AMjenkins.slaves.JnlpSlaveAgentProtocol$Handler$1onClosed



























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread eric.tuc...@bluespurs.com (JIRA)














































Eric Tucker
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















Is it possible this change broke something with polling?  I updated to the latest version of Jenkins today and now all of my polling jobs keep displaying errors like this:

Started on Apr 22, 2014 10:33:58 AM
We need to schedule a new build to get a workspace, but deferring 8,741ms in the hope that one will become available soon (all_suitable_nodes_are_offline)
Done. Took 0 ms
No changes


These jobs and polling all worked prior to the update.



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22634


Installing gerrit plugin somehow affects ability to display details of git changes















Code changed in jenkins
User: rinrinne
Path:
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/ChangeIdAnnotator.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/778d041e90165370970eec26a263892a0433dfe3
Log:
  Fix NPE for ChangeIdAnnotator

Check whether gerritCause.getEvent() returns null or not.

Fix for JENKINS-22634
https://issues.jenkins-ci.org/browse/JENKINS-22634





























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread jbrej...@praqma.net (JIRA)














































Jens  Brejner
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















@Eric, how long has the master been running ? You can get this message the first 10 minutes it runs, because we allow some time for slaves to come online - and I assume that your slaves are online ?



























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


[JIRA] [gerrit-trigger] (JENKINS-22595) REST is broken due to trailing slash in URL

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22595


REST is broken due to trailing slash in URL















Code changed in jenkins
User: rinrinne
Path:
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/3d340fa375fce2594c5b05bab84b4f0f7f775c0a
Log:
  Fix slash in URL handling in REST connection test.

Fix for JENKINS-22595
https://issues.jenkins-ci.org/browse/JENKINS-22595





























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread eric.tuc...@bluespurs.com (JIRA)














































Eric Tucker
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















I am not using slaves.  I have never used slaves.  I have one build server with Jenkins running as (I assume) the master.

It's been up all morning (hours) and the issue keeps happening on every polling attempt.



























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread eric.tuc...@bluespurs.com (JIRA)












































 
Eric Tucker
 edited a comment on  JENKINS-21394


Avoid queuing request for workspace while node is offline
















I am not using slaves.  I have never used slaves.  I have one build server with Jenkins running as (I assume) the master.

It's been up all morning (hours) and the issue keeps happening on every polling attempt.

Edit: reverting to Jenkins 1.559-1.1 through yum seems to address the issue as my builds immediately started polling successfully after reverting.



























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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)















































rin_ne
 resolved  JENKINS-22634 as Fixed


Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 2:06 PM)




Status:


Open
Resolved





Assignee:


rin_ne
rsandell





Fix Version/s:


current





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


[JIRA] [gerrit-trigger] (JENKINS-22634) Installing gerrit plugin somehow affects ability to display details of git changes

2014-04-22 Thread rin...@java.net (JIRA)















































rin_ne
 assigned  JENKINS-22634 to Robert Luberda



Installing gerrit plugin somehow affects ability to display details of git changes
















Change By:


rin_ne
(22/Apr/14 2:07 PM)




Assignee:


rsandell
RobertLuberda



























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


[JIRA] [jobconfighistory] (JENKINS-22644) Build history job config changed link does not respect Jenkins url

2014-04-22 Thread stefan.brau...@1und1.de (JIRA)















































Stefan Brausch
 assigned  JENKINS-22644 to Stefan Brausch



Build history job config changed link does not respect Jenkins url
















Change By:


Stefan Brausch
(22/Apr/14 2:14 PM)




Assignee:


MirkoFriedenhagen
StefanBrausch



























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


[JIRA] [debian-package-builder] (JENKINS-22715) Cannot upgrade to 1.560 on debian using deb package

2014-04-22 Thread kohei.yosh...@gehirn.co.jp (JIRA)














































Kohei YOSHIDA
 created  JENKINS-22715


Cannot upgrade to 1.560 on debian using deb package















Issue Type:


Bug



Assignee:


Unassigned


Components:


debian-package-builder



Created:


22/Apr/14 2:15 PM



Description:


There is a bug in debian/debian/jenkins.postinst.  If JENKINS_USER and/or JENKINS_GROUP are created before run it, jenkins.postinst will exits with status code 1.

The cause of this bug is that addgroup or adduser always run even if JENKINS_USER or JENKINS_GROUP exists on system.

This bug is mixed at this commit: https://github.com/jenkinsci/jenkins/commit/7216aab0d3f7215be7d71109936ad4b3aa0a583b#diff-9e43a327b861c17bacb4b0991828debd




Project:


Jenkins



Priority:


Blocker



Reporter:


Kohei YOSHIDA

























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


[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8

2014-04-22 Thread r...@otit.fi (JIRA)














































Risto Oikarinen
 created  JENKINS-22716


Jacoco: Zero coverage with java8















Issue Type:


Bug



Assignee:


Ognjen Bubalo



Components:


jacoco, maven



Created:


22/Apr/14 2:18 PM



Description:


I have a Java 7 project I am trying to port to Java 8. 
Everything else is working fine except maven tests, which result in zero coverage when project source/target is 1.8. Upon inspecting the resulting jacoco.exec it appears to be intact and showing executed classes properly.

I don't know if this is an issue with jacoco-maven-plugin or if it's actually a problem with maven-compiler-plugin or aspectj-maven-plugin.
The only differences between Java 7 and 8 in my pom.xml are related to maven-compiler-plugin and aspectj-maven-plugin:


properties
		jdk.version1.7/jdk.version
/properties



plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
	source${jdk.version}/source
	target${jdk.version}/target
	showDeprecationfalse/showDeprecation
/configuration
			/plugin



groupIdorg.codehaus.mojo/groupId
	artifactIdaspectj-maven-plugin/artifactId
	version1.6/version
	configuration
		showWeaveInfotrue/showWeaveInfo
		source${jdk.version}/source
		target${jdk.version}/target
		Xlintignore/Xlint
		complianceLevel${jdk.version}/complianceLevel





Project:


Jenkins



Priority:


Major



Reporter:


Risto Oikarinen

























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


[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8

2014-04-22 Thread r...@otit.fi (JIRA)














































Risto Oikarinen
 updated  JENKINS-22716


Jacoco: Zero coverage with java8
















Change By:


Risto Oikarinen
(22/Apr/14 2:22 PM)




Description:


IhaveaJava7projectIamtryingtoporttoJava8.Everythingelseisworkingfineexceptmaventests,whichresultinzerocoveragewhenprojectsource/targetis1.8.Uponinspectingtheresultingjacoco.execitappearstobeintactandshowingexecutedclassesproperly.Idontseeanyjacocorelatederrorsinthebuildlogandbuildissuccessfulwithbothjavaversions.Imusingjenkins1.560,jacoco-maven-plugin0.7.0.201403182114,jenkinsjacocoplugin1.0.14.Idontknowifthisisanissuewithjacoco-maven-pluginorifitsactuallyaproblemwithmaven-compiler-pluginoraspectj-maven-plugin.TheonlydifferencesbetweenJava7and8inmypom.xmlarerelatedtomaven-compiler-pluginandaspectj-maven-plugin:

{code}properties		jdk.version1.7/jdk.version/properties{code}{code}			plugingroupIdorg.apache.maven.plugins/groupIdartifactIdmaven-compiler-plugin/artifactIdconfiguration	source${jdk.version}/source	target${jdk.version}/target	showDeprecationfalse/showDeprecation/configuration			/plugin{code}{code}groupIdorg.codehaus.mojo/groupId	artifactIdaspectj-maven-plugin/artifactId	version1.6/version	configuration		showWeaveInfotrue/showWeaveInfo		source${jdk.version}/source		target${jdk.version}/target		Xlintignore/Xlint		complianceLevel${jdk.version}/complianceLevel{code}



























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


[JIRA] [jacoco] (JENKINS-22716) Jacoco: Zero coverage with java8

2014-04-22 Thread r...@otit.fi (JIRA)














































Risto Oikarinen
 updated  JENKINS-22716


Jacoco: Zero coverage with java8
















Change By:


Risto Oikarinen
(22/Apr/14 2:21 PM)




Description:


IhaveaJava7projectIamtryingtoporttoJava8.Everythingelseisworkingfineexceptmaventests,whichresultinzerocoveragewhenprojectsource/targetis1.8.Uponinspectingtheresultingjacoco.execitappearstobeintactandshowingexecutedclassesproperly.Idont
seeanyjacocorelatederrorsinthebuildlogandbuildissuccessfulwithbothjavaversions.Imusingjenkins1.560,jacoco-maven-plugin0.7.0.201403182114,jenkinsjacocoplugin1.0.14.Idont
knowifthisisanissuewithjacoco-maven-pluginorifitsactuallyaproblemwithmaven-compiler-pluginoraspectj-maven-plugin.TheonlydifferencesbetweenJava7and8inmypom.xmlarerelatedtomaven-compiler-pluginandaspectj-maven-plugin:{code}properties		jdk.version1.7/jdk.version/properties{code}{code}			plugingroupIdorg.apache.maven.plugins/groupIdartifactIdmaven-compiler-plugin/artifactIdconfiguration	source${jdk.version}/source	target${jdk.version}/target	showDeprecationfalse/showDeprecation/configuration			/plugin{code}{code}

groupIdorg.codehaus.mojo/groupId	artifactIdaspectj-maven-plugin/artifactId	version1.6/version	configuration		showWeaveInfotrue/showWeaveInfo		source${jdk.version}/source		target${jdk.version}/target		Xlintignore/Xlint		complianceLevel${jdk.version}/complianceLevel{code}



























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


[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration

2014-04-22 Thread kacynski.w...@aoins.com (JIRA)














































Walter Kacynski
 commented on  JENKINS-21496


Version .6.22 removes advanced options for AccuRev Servers in Global configuration















What is the status of this.  In the latest release I see that the Global / Server configuration options don't have an advanced section anymore.



























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread jbrej...@praqma.net (JIRA)














































Jens  Brejner
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















Thank you.
What are you polling ? ( I mean which kind of SCM ? Subversion, git, ?)
Would you mind to enable logging and log on AbstractProject ?



























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


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread eric.tuc...@bluespurs.com (JIRA)














































Eric Tucker
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















I am polling git at intervals between 2 and 5 minutes.

I cannot afford to move to the latest version at this time to facilitate logging.  If there's any further information I can provide without going to the latest version I would be happy to provide 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/d/optout.


[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0

2014-04-22 Thread fcamb...@java.net (JIRA)














































Frédéric Camblor
 commented on  JENKINS-21640


scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0















Yup, this plugin is a good alternative 



























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


[JIRA] [openid] (JENKINS-22717) multiple domains with OpenId plugin (google app login)

2014-04-22 Thread roberto.gonza...@blue-tc.com (JIRA)














































Roberto González
 created  JENKINS-22717


multiple domains with OpenId plugin (google app login)















Issue Type:


New Feature



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


openid



Created:


22/Apr/14 3:08 PM



Description:


The actual openId plugin only allows to set one custom domain in the Security Configuration.

Google Apps SSO (with OpenID) could allow multiple domains, like:
"domain.com,domain.es"




Project:


Jenkins



Labels:


openid




Priority:


Major



Reporter:


Roberto González

























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


[JIRA] [sbt] (JENKINS-22718) Getting a NullPointerException if sbt-launch.jar is not executable

2014-04-22 Thread hrleq...@gmail.com (JIRA)














































Richard Tarczaly
 created  JENKINS-22718


Getting a NullPointerException if sbt-launch.jar is not executable 















Issue Type:


Bug



Affects Versions:


current



Assignee:


uzilan



Components:


sbt



Created:


22/Apr/14 3:13 PM



Description:


See the stacktrace below if sbt-launch.jar is not executable. I upgraded to SBT 0.13.2 installing it RPM and it so happens that the jar is only "a+r".
Once I did a "chmod a+x sbt-launch.jar" the NPE did not happen anymore.

java.lang.NullPointerException
	at org.jvnet.hudson.plugins.SbtPluginBuilder.buildCmdLine(SbtPluginBuilder.java:159)
	at org.jvnet.hudson.plugins.SbtPluginBuilder.perform(SbtPluginBuilder.java:111)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:740)
	at hudson.model.Build$BuildExecution.build(Build.java:198)
	at hudson.model.Build$BuildExecution.doRun(Build.java:159)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:519)
	at hudson.model.Run.execute(Run.java:1703)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)




Environment:


CentOS 6.5

sbt 0.13.2 (installed as RPM)

Jenkins 1.560

sbt plugin 1.4




Project:


Jenkins



Priority:


Major



Reporter:


Richard Tarczaly

























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


[JIRA] [credentials] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.

2014-04-22 Thread smithgcov...@gmail.com (JIRA)














































Greg Smith
 commented on  JENKINS-22542


Subversion polling not work with externals or variables in URL -  E200015: No credential to try.















This is occurring for us too  Ubuntu master, Windows slaves.

The first build of a clean workspace works.  Any following builds fail on the revision check for any externs in the svn tree.  




























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


[JIRA] [xvfb] (JENKINS-22719) Xvfb plugin does not start for release plugin

2014-04-22 Thread dm...@java.net (JIRA)














































dma_k
 created  JENKINS-22719


Xvfb plugin does not start for release plugin















Issue Type:


Bug



Affects Versions:


current



Assignee:


zregvart



Components:


xvfb



Created:


22/Apr/14 4:20 PM



Description:


The release in my free-style project is performed using Release Plugin. Unfortunately Xvfb plugin is not started before Release plugin and there are no pre-release targets that can trigger it.

Expected:

	Either Xvfb is automatically stated before Release plugin.
	Or there is a "Add release step" - "Start Xvfb" target available to start Xvfb.






Project:


Jenkins



Priority:


Minor



Reporter:


dma_k

























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


[JIRA] [publish-over-ssh] (JENKINS-16240) Problem with NOT_BUILT build result

2014-04-22 Thread massdos...@java.net (JIRA)














































massdosage
 commented on  JENKINS-16240


Problem with NOT_BUILT build result















Having the same problem here. 

@ThiagoC, @Mahmoud AllamehAmiri - what environment variable did you set to work around 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/d/optout.


[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline

2014-04-22 Thread bjag...@teads.tv (JIRA)














































Brice Jaglin
 commented on  JENKINS-21394


Avoid queuing request for workspace while node is offline















I am seeing the same issue since the upgrade to 1.560, with git (plugin 2.2.1) polling every minute. How can I enable logs?



























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


[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder

2014-04-22 Thread leandro.lucare...@sociomantic.com (JIRA)














































Leandro Lucarella
 commented on  JENKINS-22537


Seemingly random failures of GitHub plugin PR builder















There is also a possibility to provide some funding to fix this, is the FreedomSponsors.org sponsoring really used?



























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


[JIRA] [core] (JENKINS-22720) Non-recursive ListViews unnecessarily call owner.getAllItems in getItems

2014-04-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 created  JENKINS-22720


Non-recursive ListViews unnecessarily call owner.getAllItems in getItems















Issue Type:


Bug



Assignee:


Daniel Beck



Components:


core



Created:


22/Apr/14 6:30 PM



Project:


Jenkins



Priority:


Major



Reporter:


Daniel Beck

























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


[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens

2014-04-22 Thread mixaltu...@users.sf.net (JIRA)














































Michal Turek
 started work on  JENKINS-22721


Project page has broken layout on smaller screens
















Change By:


Michal Turek
(22/Apr/14 6:46 PM)




Status:


Open
InProgress



























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


[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens

2014-04-22 Thread mixaltu...@users.sf.net (JIRA)














































Michal Turek
 created  JENKINS-22721


Project page has broken layout on smaller screens















Issue Type:


Bug



Affects Versions:


current



Assignee:


Michal Turek



Attachments:


projectaction_layout_after.png, projectaction_layout_before.png



Components:


disk-usage



Created:


22/Apr/14 6:46 PM



Description:


Floating box with the graph on the project page contains a long line which increases the box width and breaks the layout. The text can be moved to a new "disk usage" section with large icon and the same information. See the attached screenshots.




Environment:


Version 0.23




Project:


Jenkins



Priority:


Major



Reporter:


Michal Turek

























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


[JIRA] [disk-usage] (JENKINS-22721) Project page has broken layout on smaller screens

2014-04-22 Thread mixaltu...@users.sf.net (JIRA)














































Michal Turek
 commented on  JENKINS-22721


Project page has broken layout on smaller screens















Fixed in https://github.com/mixalturek/disk-usage-plugin/commit/f00e12df71070b87a09535488ed6b0800d9125d2, pull request sent.



























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


[JIRA] [core] (JENKINS-22720) Non-recursive ListViews unnecessarily call owner.getAllItems in getItems

2014-04-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-22720


Non-recursive ListViews unnecessarily call owner.getAllItems in getItems















https://github.com/jenkinsci/jenkins/pull/1210



























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


[JIRA] [core] (JENKINS-22720) Non-recursive ListViews unnecessarily call owner.getAllItems in getItems

2014-04-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 started work on  JENKINS-22720


Non-recursive ListViews unnecessarily call owner.getAllItems in getItems
















Change By:


Daniel Beck
(22/Apr/14 7:49 PM)




Status:


Open
InProgress



























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


[JIRA] [master-slave] (JENKINS-22722) Master doesn't show connected slave

2014-04-22 Thread lgri...@free.fr (JIRA)














































Gregory Fernandez
 created  JENKINS-22722


Master doesnt show connected slave















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


master-slave



Created:


22/Apr/14 7:51 PM



Description:


When updating slave.jar on slave with version shipped with Jenkins 1.560, slave show a message "connected" but master does not show the slave online.

Reverting to the slave.jar in 1.533 or 1.559 make it work as usual.

Tried with direct connection or via Apache reverse proxy.




Environment:


Master: debian wheezy (jenkins installed by apt)

Slave: Windows 7 (x64)




Project:


Jenkins



Priority:


Minor



Reporter:


Gregory Fernandez

























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


[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs

2014-04-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-18364


Optimize creation of relative links to jobs
















Issue is a performance regression introduced in 1.512, therefore reclassifying as bug to make this eligible for LTS inclusion.

Measured on a pristine instance with ~8000 freestyle jobs, no builds:


	1.511: All view opens in 1 second
	1.512: All view opens in 44 seconds, takes 100% CPU during that time.







Change By:


Daniel Beck
(22/Apr/14 8:03 PM)




Issue Type:


Improvement
Bug





Labels:


lts-candidateperformance
regression



























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


[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs

2014-04-22 Thread dan...@beckweb.net (JIRA)












































 
Daniel Beck
 edited a comment on  JENKINS-18364


Optimize creation of relative links to jobs
















Issue is a performance regression introduced in 1.512, therefore reclassifying as bug to make this eligible for LTS inclusion.

Measured on a pristine instance with ~8000 freestyle jobs (j0 to j8447), no builds:


	1.511: List view with simple regex (j1.*) opens in 1 second
	1.512: Same list view opens in 44 seconds, takes 100% CPU during that time.





























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


[JIRA] [ruby-runtime] (JENKINS-16284) Failing to launch SSH slave agents after upgrade to 1.498

2014-04-22 Thread mathe...@cisco.com (JIRA)














































Matt Herbert
 commented on  JENKINS-16284


Failing to launch SSH slave agents after upgrade to 1.498















Piling on, same here. Running Ubuntu 14.04 with Jenkins 1.532.3 LTS. Everything was working great for me, then I installed a plugin (can't remember which: either unreliable slave, OfflineOnFailure, or Buildtimout) 2 days ago which pulled in ruby-runtime as a pre-requisite. Today I tried disconnect/reconnect a slave and it would just sit there spinning with no output. I updated Jenkins and Ubuntu to latest (which I needed to do anyway), and still it didn't work. Fortunately after much googling I found this thread. I disabled ruby-runtime, and restarted tomcat, and voila, everything worked again.



























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


[JIRA] [hipchat] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job

2014-04-22 Thread gray...@gmail.com (JIRA)














































Alex Gray
 created  JENKINS-22723


Cannot pass hipchat room number as a parameter to a job















Issue Type:


Bug



Assignee:


Unassigned


Components:


hipchat



Created:


22/Apr/14 9:28 PM



Description:


We want to parameterize a job that takes in the hipchat room.

We have a general-purpose, parameterized test job, and upon failure, we want a notification to be sent to the correct room.

We define the hipchat room number in an upstream job, so when the upstream job kicks this test job, the test job will send a hipchat notification upon completion.

We are using 0.1.4 version of hipchat




Project:


Jenkins



Priority:


Major



Reporter:


Alex Gray

























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


[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder

2014-04-22 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-22537


Seemingly random failures of GitHub plugin PR builder















I don't think I've seen any bug that was fixed due to sponsoring.  I don't watch all the bugs, but I do watch all the git-plugin and git-client-plugin bugs, and I don't recall any bug which has been fixed as a result of sponsoring.

I'm not a Cloudbees employee, but there are Cloudbees employees who might be persuaded to work on this bug, though it would require that you have paid support from them.  Paid support from them probably requires that you purchase their Jenkins Enterprise product.



























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


[JIRA] [git] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH

2014-04-22 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-22706


git fetching fails after switching from HTTPS to SSH















I believe you will have better results if you define a credential with the user name and password (or with the ssh key if available), rather than embedding the user name and password in the ssh URL.

I'm perplexed why the warning appears about "C:\Program" not being a recognized command.  If that message continues even after you define a credential, you may want to check that Git\bin is in the PATH on the slave, or that the full path to the git executable is listed in the node configuration.



























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


[JIRA] [git] (JENKINS-22706) git fetching fails after switching from HTTPS to SSH

2014-04-22 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-22706


git fetching fails after switching from HTTPS to SSH















Mark: Possibly related to 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/d/optout.


[JIRA] [xvfb] (JENKINS-22719) Xvfb plugin does not start before release plugin

2014-04-22 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22719


Xvfb plugin does not start before release plugin















Code changed in jenkins
User: Zoran Regvart
Path:
 src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java
http://jenkins-ci.org/commit/xvfb-plugin/f6aa827efb5092c66263ea385dafa5661c453242
Log:
  JENKINS-22719 Xvfb plugin does not start before release plugin





























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


[JIRA] [parameterized-trigger] (JENKINS-22705) Parameterized Trigger Plugin setting is not retained: Use files in matrix child builds

2014-04-22 Thread de...@ikedam.jp (JIRA)















































ikedam
 assigned  JENKINS-22705 to ikedam



Parameterized Trigger Plugin setting is not retained: Use files in matrix child builds
















Change By:


ikedam
(22/Apr/14 10:05 PM)




Assignee:


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


[JIRA] [xvfb] (JENKINS-22719) Xvfb plugin does not start before release plugin

2014-04-22 Thread zregv...@java.net (JIRA)














































zregvart
 updated  JENKINS-22719


Xvfb plugin does not start before release plugin
















Hi,
thanks for reporting. If the build wrapper plugin does not explicitly specify order, order is determined by comparing plugin names. Starting with X xvfb build wrapper would be almost always the last plugin executed.

I've explicitly set the order to the maximal value, so xvfb plugin will be run before any other build wrapper plugin.

In order to have this order you'll need to re-save the job's configuration, because ordering is done when saving the job.





Change By:


zregvart
(22/Apr/14 10:05 PM)




Summary:


Xvfbplugindoesnotstart
for
before
releaseplugin



























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


[JIRA] [xvfb] (JENKINS-22719) Xvfb plugin does not start before release plugin

2014-04-22 Thread zregv...@java.net (JIRA)















































zregvart
 resolved  JENKINS-22719 as Fixed


Xvfb plugin does not start before release plugin
















Fixed in version 1.0.10





Change By:


zregvart
(22/Apr/14 10:10 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/d/optout.


[JIRA] [hipchat] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job

2014-04-22 Thread gposton1...@gmail.com (JIRA)














































Glenn Poston
 commented on  JENKINS-22723


Cannot pass hipchat room number as a parameter to a job















We're in the same boat.  We have a parameterized job that is shared with several upstream jobs, but we would like the hipchat notification to go to different rooms based on the triggering (upstream) job.  It would be great if we could pass the hipchat room in as a parameter.



























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


[JIRA] [weblogic-deployer] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer

2014-04-22 Thread r...@orange.fr (JIRA)














































Raphael CHAUMIER
 started work on  JENKINS-21244


Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
















Change By:


Raphael CHAUMIER
(22/Apr/14 10:22 PM)




Status:


Open
InProgress



























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


[JIRA] [weblogic-deployer] (JENKINS-13981) Adding configuration file validation for weblogic-deployer-plugin

2014-04-22 Thread r...@orange.fr (JIRA)















































Raphael CHAUMIER
 resolved  JENKINS-13981 as Wont Fix


Adding configuration file validation for weblogic-deployer-plugin 
















Change By:


Raphael CHAUMIER
(22/Apr/14 10:24 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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


[JIRA] [weblogic-deployer] (JENKINS-13981) Adding configuration file validation for weblogic-deployer-plugin

2014-04-22 Thread r...@orange.fr (JIRA)















































Raphael CHAUMIER
 closed  JENKINS-13981 as Wont Fix


Adding configuration file validation for weblogic-deployer-plugin 
















Change By:


Raphael CHAUMIER
(22/Apr/14 10:24 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/d/optout.


[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job

2014-04-22 Thread mishael...@yahoo.com (JIRA)














































Mishael Kim
 commented on  JENKINS-18678


Builds disappear some time after renaming job















Has anyone successfully tested this fix in the latest LTS build after migrating the older problem jobs/configs over?  I'm still seeing my builds disappear in LTS version 1.532.2 when using jobs carried over from my backup.  Does it possibly require the creation of a new job to get past this bug?

@amargono
BTW, I haven't run into any LDAP issues with this build.



























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


[JIRA] [parameterized-trigger] (JENKINS-22705) Parameterized Trigger Plugin setting is not retained: Use files in matrix child builds

2014-04-22 Thread de...@ikedam.jp (JIRA)














































ikedam
 commented on  JENKINS-22705


Parameterized Trigger Plugin setting is not retained: Use files in matrix child builds















Sorry for my so elementary error...
Made a pull request to fix: https://github.com/jenkinsci/parameterized-trigger-plugin/pull/65



























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


[JIRA] [git] (JENKINS-22724) Git merge before build does not work with bitbucket SCM trigger

2014-04-22 Thread michael.po...@elotouch.com (JIRA)














































Michael Power
 created  JENKINS-22724


Git merge before build does not work with bitbucket SCM trigger















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


23/Apr/14 12:30 AM



Description:


This could be a bug in the bitbucket plugin
bitbucket plugin version: 1.0
Git plugin version: 2.2.1
Jenkins version: 1.532.2.3

See stackoverflow question: 
http://stackoverflow.com/questions/23203806/cloudbees-prebuild-merge-no-longer-works

If I configure a job to do a merge before the build then let SCM trigger the job it does not do a merge before the build.  Since I have also turned on the git publisher the push fails because the target branch has diverged.  The build is supposed to merge the source branch and the target branch together and push it back to target.  If I kick off the build manually the the merge is done before the build and the git publisher runs without error.

Approximate steps to reproduce.

Create job named mergeAndBuild
Configure mergeAndBuild to use git
Configure mergeAndBuild to look for changes on sourceBranch and targetBranch
Add merge before build to git configuration
Name of repository: Origin
Branch to merge to: targetBranch
Merge strategy: default
Enable bitbucket build trigger.
Add git publisher to the build
Push Only If Build Succeeds: yes
Merge Results: yes

Make sure the bitbucket hook is configured with your jenkins server.

Then do something like the following
git clone giturl
git checkout -b sourceBranch
touch sourceBranch.txt
git add sourceBranch.txt
git commit -m "Add sourceBranch.txt"
git checkout master
git checkout -b targetBranch
touch targetBranch.txt
git add targetBranch.txt
git commit -m "Add targetBranch.txT"
git push origin targetBranch:targetBranch
git push origin sourceBranch:sourceBranch


At this point it will build and the log will say:
commit notification 6161e4adb567c8be106ee8fa70594d67a756e481
Building remotely on 5a988271 in workspace /scratch/jenkins/workspace/da/b2.potter
Fetching changes from the remote Git repository
Fetching upstream changes from g...@bitbucket.org:elosystemsteam/paypoint-potter.git
Checking out Revision 6161e4adb567c8be106ee8fa70594d67a756e481 (detached)

Then towards then end when the git publisher tries to push:
Pushing HEAD to branch B2-Bisque of origin repository
ERROR: Failed to push merge to origin repository
hudson.plugins.git.GitException: Command "git push g...@bitbucket.org:elosystemsteam/paypoint-potter.git HEAD:B2-Bisque" returned status code 1:
stdout: 
stderr: To g...@bitbucket.org:elosystemsteam/paypoint-potter.git
 ! rejectedHEAD - B2-Bisque (non-fast-forward)
error: failed to push some refs to 'g...@bitbucket.org:elosystemsteam/paypoint-potter.git'
hint: Updates were rejected because a pushed branch tip is behind its remote
hint: counterpart. Check out this branch and merge the remote changes
hint: (e.g. 'git pull') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1276)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1146)




Project:


Jenkins



Priority:


Major



Reporter:


Michael Power

























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 

[JIRA] [gerrit] (JENKINS-17452) a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger

2014-04-22 Thread rin...@java.net (JIRA)














































rin_ne
 updated  JENKINS-17452


a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger
















Change By:


rin_ne
(23/Apr/14 2:27 AM)




Component/s:


gerrit-trigger



























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


[JIRA] [scm-sync-configuration] (JENKINS-22573) SCM Sync Stops working

2014-04-22 Thread jkep...@timg.com (JIRA)














































James Keppel
 commented on  JENKINS-22573


SCM Sync Stops working















I tested the snapshot of the plugin that kutzi posted to fix the issue in JENKINS-22199, and the issue was not resolved.

For those attempting to reproduce the error, install the SCM Sync Plugin, and go to http://servername/scm/SubversionSCM/enterCredential

The error above occurs (for me at least) when entering any URL.

When entering the correct URL and the incorrect password. the additional line below is returned, which leads me to believe that Jenkins is connecting, authenticating, but unable to issue the OPTIONS command.

Failed to authenticate: svn: E170001: OPTIONS of '/svn/repo/trunk': 401 Authorization Required (https://svnserver)




























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


[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion

2014-04-22 Thread jkep...@timg.com (JIRA)














































James Keppel
 commented on  JENKINS-22199


Jenkins throwing errors in SCM Polling and Updates with Subversion















Hi kutzi, I tested the plugin snapshot in order to try and resolve the related issue JENKINS-22573, and I ma still receiving a stacktrace like Jay in issue JENKINS-22573.

I have also posted this in issue JENKINS-22573, and steps to reproduce the "org.tmatesoft.svn.core.SVNException: svn: E175002:" via the SCM Sync Plugin.

Happy to undertake any testing to assist in resolving this issue (if it is in in fact the SVN plugin and not the SCM Sync plugin) 



























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


  1   2   >