date:20121219















































SCM/JIRA link daemon
 commented on  JENKINS-15235


Trailing space in Git branch name causes build failures















Code changed in jenkins
User: Samuel Moritz
Path:
 src/main/java/hudson/plugins/git/BranchSpec.java
 src/test/java/hudson/plugins/git/TestBranchSpec.java
http://jenkins-ci.org/commit/git-plugin/7a1e61eb2f08b2ed4aebb31e3cee272cf8a54ee6
Log:
  FIXES JENKINS-15235

	Trim branch name before storing it, since a valid branch name does
not begin or end with whitespace.
	Use same code for setting name in constructor and in setName().
Previously, there were no check for valid values in setName().































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

[JIRA] (JENKINS-15235) Trailing space in Git branch name causes build failures

2012-12-19 Thread james.simp...@securetrading.com (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-15235


Trailing space in Git branch name causes build failures















Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/hudson/plugins/git/BranchSpec.java
 src/test/java/hudson/plugins/git/TestBranchSpec.java
http://jenkins-ci.org/commit/git-plugin/442eecdd44365a3d3420578db3c9e8325c7aec8e
Log:
  Merge pull request #115 from thesam/jenkins15235

FIXES JENKINS-15235 Add whitespace trimming of branch name.


Compare: https://github.com/jenkinsci/git-plugin/compare/707a99181369...442eecdd4436




























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

[JIRA] (JENKINS-16167) Timer triggers with comments do not work after copy

2012-12-19 Thread huttrae...@gmail.com (JIRA)















































Mathias Steinbach
 created  JENKINS-16167


Timer triggers with comments do not work after copy 















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


exception.txt



Components:


plugin



Created:


19/Dec/12 12:55 PM



Description:


We have Jobs with timer trigger and SCM timer trigger.
Every trigger has an comment like this:


	every 30 minutes
*/30 * * * *



If we copy jobs with these triggers by URL(Jenkins-URL/createItem?name=copyOfJob) and config.xml as post data, then the triggers are not activ. Jenkins handles


	every 30 minutes
*/30 * * * *



as a whole comment.

If the trigger configuration ist like:

*/30 * * * *

	every 30 minutes



then copy by URL ist not possible. Jenkins gives an Exception (see Attachment)





Environment:


Jenkins Version: 1.480




Project:


Jenkins



Labels:


jenkins
trigger




Priority:


Major



Reporter:


Mathias Steinbach

























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

[JIRA] (JENKINS-16167) Timer triggers with comments do not work after copy

2012-12-19 Thread huttrae...@gmail.com (JIRA)















































Mathias Steinbach
 updated  JENKINS-16167


Timer triggers with comments do not work after copy 
















Change By:


Mathias Steinbach
(19/Dec/12 12:57 PM)




Description:


WehaveJobswithtimertriggerandSCMtimertrigger.Everytriggerhasancommentlikethis:#
#
every30minutes*/30IfwecopyjobswiththesetriggersbyURL(Jenkins-URL/createItem?name=copyOfJob)andconfig.xmlaspostdata,thenthetriggersarenotactiv.Jenkinshandles#
#
every30minutes*/30asawholecomment.Ifthetriggerconfigurationistlike:*/30#
#
every30minutesthencopybyURListnotpossible.JenkinsgivesanException(seeAttachment)



























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

[JIRA] (JENKINS-16167) Timer triggers with comments do not work after copy

2012-12-19 Thread huttrae...@gmail.com (JIRA)















































Mathias Steinbach
 updated  JENKINS-16167


Timer triggers with comments do not work after copy 
















Change By:


Mathias Steinbach
(19/Dec/12 12:57 PM)




Description:


WehaveJobswithtimertriggerandSCMtimertrigger.Everytriggerhasancommentlikethis:
\
#
#
every30minutes*/30IfwecopyjobswiththesetriggersbyURL(Jenkins-URL/createItem?name=copyOfJob)andconfig.xmlaspostdata,thenthetriggersarenotactiv.Jenkinshandles
\
#
#
every30minutes*/30asawholecomment.Ifthetriggerconfigurationistlike:*/30
\
#
#
every30minutesthencopybyURListnotpossible.JenkinsgivesanException(seeAttachment)



























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

[JIRA] (JENKINS-16168) Cannot specify a build with parameters containing slash(/)

2012-12-19 Thread de...@ikedam.jp (JIRA)















































Yasuyuki IKEDA
 created  JENKINS-16168


Cannot specify a build with parameters containing slash(/)















Issue Type:


Bug



Assignee:


Unassigned


Components:


copyartifact



Created:


19/Dec/12 1:24 PM



Description:


In a following case, Copy Artifact fails to find the build to copy.


	In confituration: specify Project name filtering with a build parameters, using variables.
	In build: use variables containing slash("/").



For instance:

	Configure Project name to "SomeParameterizedJob/BRANCH=${value1}"
	Run build with setting value1 to "origin/develop"



Even if there is a build with BRANCH=origin/develop in SomeParameterizedJob, this results in a following failure:
Unable to find project for artifact copy: SomeParameterizedJob/BRANCH=origin/master

This seems caused for Copy Artifact uses the LAST slash to devide the Project name parameter to the job name and the filter parametes (In CopyArtifact.JobResolver, using lastIndexOf).
So "SomeParameterizedJob/BRANCH=origin/master" is devided into "SomeParameterizedJob/BRANCH=origin" and "master".

Job names never contain slashes, and how about replaces lastIndexOf to indexOf to use the FIRST slash to devide the project name?




Environment:


Windows XP

Jenkins 1.494

Copy Artifact 1.25




Project:


Jenkins



Priority:


Major



Reporter:


Yasuyuki IKEDA

























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

[JIRA] (JENKINS-16169) PROMOTED_* variables are not available when sending mail on a Promotion event

2012-12-19 Thread uri.mil...@gmail.com (JIRA)















































uri milman
 created  JENKINS-16169


PROMOTED_* variables are not available when sending mail on a Promotion event















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Slide-O-Mix



Components:


email-ext



Created:


19/Dec/12 1:35 PM



Description:


When using the Promoted Build plugin, some variables are exposed:
PROMOTED_NUMBER
PROMOTED_URL
PROMOTED_JOB_NAME
PROMOTED_ID

When sending mail while promoting, those vars do not exist, so one cannot refer to the original build which was promoted. Also, the ${Changes} token takes changes of the promoted build, which is empty, since the changes list itself is not copied to the promoted one. 

use case: send an email of the build being promoted to QA, with its number, and a link to the changes-list, so it's possible to see the changes between 2 promoted builds. 




Project:


Jenkins



Priority:


Major



Reporter:


uri milman

























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

[JIRA] (JENKINS-16170) Ability for the plugin to auto-install Unity3d

2012-12-19 Thread lacos...@java.net (JIRA)















































lacostej
 created  JENKINS-16170


Ability for the plugin to auto-install Unity3d















Issue Type:


New Feature



Assignee:


lacostej



Components:


unity3d-plugin



Created:


19/Dec/12 1:50 PM



Description:


From a CI server perspective, it would be useful to have the ability to install Unity automatically.

If you want this, vote for: http://feedback.unity3d.com/unity/all-categories/1/hot/active/ability-to-install-unity-from-th




Project:


Jenkins



Priority:


Major



Reporter:


lacostej

























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

[JIRA] (JENKINS-16169) PROMOTED_* variables are not available when sending mail on a Promotion event

2012-12-19 Thread slide.o....@gmail.com (JIRA)















































Slide-O-Mix
 commented on  JENKINS-16169


PROMOTED_* variables are not available when sending mail on a Promotion event















Did you try the ENV token? See the content token help when configuring the email-ext plugin for how to use 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

[JIRA] (JENKINS-16171) Not sending emails if pre-build fails















































JPSimpson
 created  JENKINS-16171


Not sending emails if pre-build fails















Issue Type:


Bug



Assignee:


Unassigned


Components:


ssh



Created:


19/Dec/12 2:30 PM



Description:


We have a ssh pre-build script set up that resets our test data on another box in our Jenkins instance before we then run our tests. However we noticed this morning that the job had failed during the pre-build section. However we did not get the email through from jenkins saying the build had failed. I'm guessing the whole thing crashed out so it never even attempted the email. Here is the traceback we received:

java.lang.NullPointerException
	at org.jvnet.hudson.plugins.SSHBuildWrapper.executePreBuildScript(SSHBuildWrapper.java:78)
	at org.jvnet.hudson.plugins.SSHBuildWrapper.setUp(SSHBuildWrapper.java:62)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
	at hudson.model.Run.execute(Run.java:1543)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)


Is there a reason why this shouldn't email that it failed? 




Project:


Jenkins



Priority:


Major



Reporter:


JPSimpson

























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

[JIRA] (JENKINS-11850) Issue with PMC Integrity Pug in

2012-12-19 Thread satyanarayana.srihariveeraven...@in.bosch.com (JIRA)















































satya b
 reopened  JENKINS-11850


Issue with PMC Integrity Pug in
















we are facing same issue for setup jenkins with MKS. we are getting the error as mentioned you. could you please update me what changes have you done in IntegrityClientSite.rc to resolve the same.





Change By:


satya b
(19/Dec/12 2:34 PM)




Resolution:


Fixed





Status:


Closed
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

[JIRA] (JENKINS-16149) Ability to match multiple Policies

2012-12-19 Thread james.simp...@securetrading.com (JIRA)
















































JPSimpson
 closed  JENKINS-16149 as Not A Defect


Ability to match multiple Policies
















Yes thanks, the two work combined 





Change By:


JPSimpson
(19/Dec/12 2:49 PM)




Status:


Open
Closed





Resolution:


NotADefect



























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

[JIRA] (JENKINS-16172) Issue with PTC Integrity Pug in

2012-12-19 Thread satyanarayana.srihariveeraven...@in.bosch.com (JIRA)















































satya b
 created  JENKINS-16172


Issue with PTC Integrity Pug in















Issue Type:


Bug



Assignee:


Cletus DSouza



Attachments:


MKS-Jenkins.doc



Components:


integrity-plugin



Created:


19/Dec/12 2:53 PM



Description:


I am trying to set up CI using jenkins for our projects. We use MKS Integrity as our source control . jenkins was not able to connect to our MKS server  to check out source code , Do you see any issue with my configuration set up. 




Environment:


MKS, jenkins, ant script




Project:


Jenkins



Priority:


Major



Reporter:


satya b

























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

[JIRA] (JENKINS-15235) Trailing space in Git branch name causes build failures

2012-12-19 Thread samuel.mor...@gmail.com (JIRA)















































Samuel Moritz
 commented on  JENKINS-15235


Trailing space in Git branch name causes build failures















D'oh! I entered "FIXES" instead of "FIXED", so this was not resolved automatically.



























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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

2012-12-19 Thread christian.koeb...@gmail.com (JIRA)















































Christian Köberl
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















This seems to happen only with master/slave (multiple nodes) setup.

We have a second Jenkins (both 1.489) with nearly the same configuration - the only difference is that this one has no slaves. There the problem does not occur.



























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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

2012-12-19 Thread nanzal...@achievementnetwork.org (JIRA)















































Nicolas Anzalone
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















I just started using Jenkins about a month ago, and it was happening with some frequency on stand-alone server (no master/slave setup). I haven't seen the problem in the last 2 weeks however. As per D C's comment, reloading from disk resolves the issue whenever I see 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

[JIRA] (JENKINS-12983) Redundat syncs when using matrix jobs

2012-12-19 Thread thomasmfie...@gmail.com (JIRA)















































Thomas Fields
 commented on  JENKINS-12983


Redundat syncs when using matrix jobs















Is this ever going to be fixed?

Tom



























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

[JIRA] (JENKINS-14128) Workspaces not getting cleaned upon build completion

2012-12-19 Thread thomasmfie...@gmail.com (JIRA)















































Thomas Fields
 commented on  JENKINS-14128


Workspaces not getting cleaned upon build completion















Has any progress been made on this issue?

Tom



























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

[JIRA] (JENKINS-12587) Avoid deprecated warnings during build of trac-plugin
















































SCM/JIRA link daemon
 resolved  JENKINS-12587 as Fixed


Avoid deprecated warnings during build of trac-plugin
















Change By:


SCM/JIRA link daemon
(19/Dec/12 5:22 PM)




Status:


InProgress
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

[JIRA] (JENKINS-12094) ruby-runtime plugin fails to initialize

2012-12-19 Thread m...@labzero.com (JIRA)















































Matthew Wilson
 commented on  JENKINS-12094


ruby-runtime plugin fails to initialize















Sebastien, JRuby isn't far from Java.  This is still broken for Windows Vista.  Here's the error seen when trying to install the plugin without a restart:

hudson.util.IOException2: Failed to dynamically deploy this plugin
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1259)
	at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1056)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Unable to delete C:\Program Files (x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\jruby-complete-1.6.5.jar
	at hudson.Util.deleteFile(Util.java:243)
	at hudson.Util.deleteRecursive(Util.java:293)
	at hudson.Util.deleteContentsRecursive(Util.java:204)
	at hudson.Util.deleteRecursive(Util.java:284)
	at hudson.Util.deleteContentsRecursive(Util.java:204)
	at hudson.Util.deleteRecursive(Util.java:284)
	at hudson.Util.deleteContentsRecursive(Util.java:204)
	at hudson.Util.deleteRecursive(Util.java:284)
	at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:411)
	at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:117)
	at hudson.PluginManager.dynamicLoad(PluginManager.java:391)
	at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1255)
	... 7 more

The file C:\Program Files (x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\jruby-complete-1.6.5.jar exists but Windows prevents the file from being deleted if a process is using it.  It seems that Jenkins tries to load it which is why it's unable to be deleted.



























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

[JIRA] (JENKINS-7032) Trac plugin creates wrong links















































Gerd Zanker
 started work on  JENKINS-7032


Trac plugin creates wrong links
















Change By:


Gerd Zanker
(19/Dec/12 5:32 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

[JIRA] (JENKINS-13366) Prefix or truncate the file path of a change set to build Trac source browser URL















































Gerd Zanker
 started work on  JENKINS-13366


Prefix or truncate the file path of a change set to build Trac source browser URL
















Change By:


Gerd Zanker
(19/Dec/12 5:32 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

[JIRA] (JENKINS-13366) Prefix or truncate the file path of a change set to build Trac source browser URL
















































Gerd Zanker
 assigned  JENKINS-13366 to Gerd Zanker



Prefix or truncate the file path of a change set to build Trac source browser URL
















Change By:


Gerd Zanker
(19/Dec/12 5:33 PM)




Assignee:


GerdZanker



























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

[JIRA] (JENKINS-7032) Trac plugin creates wrong links

2012-12-19 Thread nanzal...@achievementnetwork.org (JIRA)
















































Gerd Zanker
 assigned  JENKINS-7032 to Gerd Zanker



Trac plugin creates wrong links
















Change By:


Gerd Zanker
(19/Dec/12 5:33 PM)




Assignee:


GerdZanker



























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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

2012-12-19 Thread tylerohl...@gmail.com (JIRA)















































Tyler Ohlsen
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















This started happening for us after we upgraded to 1.494.  Reloading configuration from file fixes temporarily.  We have a Master/Slave setup.



























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

[JIRA] (JENKINS-16174) add documentation and help

2012-12-19 Thread d...@fortysix.ch (JIRA)















































domi
 created  JENKINS-16174


add documentation and help 















Issue Type:


Improvement



Assignee:


Honza Brázdil



Components:


ghprb



Created:


19/Dec/12 6:02 PM



Description:


It would be nice if there would be more information on how to use the "Github pull request builder plugin". 
None of the configuration options in Jenkins has a help page and the wiki is not clear on how to setup the environment. 
e.g.

	what do you mean by 'bot'? what kind of user is this?, which permissions does he need
	does it work over https, without ssh?
	what about an internal GH Enterprise installation?



maybe some pictures on the wiki would help too




Project:


Jenkins



Priority:


Major



Reporter:


domi

























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

[JIRA] (JENKINS-15344) ClassCastException when reports are created with maven-site-plugin

2012-12-19 Thread f.mod...@gmx.net (JIRA)















































Falko Modler
 commented on  JENKINS-15344


ClassCastException when reports are created with maven-site-plugin















Any updates? I just had to downgrade to maven-site-plugin 3.0.



























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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion













































 
Nicolas Anzalone
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















I just started using Jenkins about a month ago, and it was happening with some frequency on stand-alone server (no master/slave setup). I haven't seen the problem in the last 2 weeks however. As per D C's comment, reloading from disk resolves the issue whenever I see it.

edit: just happened again a few minutes ago. may have been caused by renaming. renamed the job in question to make way for a better implementation of the same job, but I've done the same thing to a few others without seeing 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

2012-12-19 Thread tylerohl...@gmail.com (JIRA)













































 
Tyler Ohlsen
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















This started happening for us after we upgraded to 1.494.  Reloading configuration from file fixes temporarily.  We have a Master/Slave setup.
Edit: This started happening, and continues to happen after every build, just after I renamed my project.



























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

[JIRA] (JENKINS-16175) Dashboard not showing job status

2012-12-19 Thread richard_merr...@yahoo.com (JIRA)















































Richard Merrill
 created  JENKINS-16175


Dashboard not showing job status















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


gui



Created:


19/Dec/12 9:24 PM



Description:


I am having intermittent issues with Jenkins where the dashboard will indicate that a job has never been run even though it has. The files and folders from the previous build(s) are all in place and if I run the build again, it usually updates the status correctly after the build completes. However, that status may go back to indicating that the job has never been built at a later time. Most of the time it is not the latest job/build which loses its status. The status may switch to the correct data after a different job is built, but not always. I have yet to determine any kind of pattern as to which builds are being ignored, much less why. This was happening regularly with version 1.493 and has now started happening with 1.494.




Environment:


Windows Server 2008 R2 Enterprise




Project:


Jenkins



Priority:


Major



Reporter:


Richard Merrill

























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

[JIRA] (JENKINS-14908) Enable Maven project support.















































SCM/JIRA link daemon
 commented on  JENKINS-14908


Enable Maven project support.















Code changed in jenkins
User: Gregory Boissinot
Path:
 src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java
http://jenkins-ci.org/commit/cppcheck-plugin/b5887d2f1618673373541e753c0b2470a895d65e
Log:
  Fix JENKINS-14908





























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

[JIRA] (JENKINS-14908) Enable Maven project support.















































SCM/JIRA link daemon
 commented on  JENKINS-14908


Enable Maven project support.















Code changed in jenkins
User: Gregory Boissinot
Path:
 pom.xml
http://jenkins-ci.org/commit/cppcheck-plugin/918a415a45525b2f9852bbf0572f6af93fa54945
Log:
  Fix JENKINS-14908


Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/b3f0e3e623a1...918a415a4552




























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

[JIRA] (JENKINS-14908) Enable Maven project support.

2012-12-19 Thread gregory.boissi...@gmail.com (JIRA)
















































Gregory Boissinot
 resolved  JENKINS-14908 as Fixed


Enable Maven project support.
















Change By:


Gregory Boissinot
(19/Dec/12 10:27 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

[JIRA] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows

2012-12-19 Thread dbac...@dustnetworks.com (JIRA)

Dave Bacher
created JENKINS-16176

ShiningPanda PATH update uses wrong separator on Windows

Issue Type:

Bug

Assignee:

Unassigned

Components:

shiningpanda

Created:

19/Dec/12 10:37 PM

Description:

When running ShiningPanda on a Windows slave, the plugin (or virtualenv?) updates the PATH to include the virtualenv directory.

0. Install ShiningPanda plugin (this result is for v1.15)
1. Create a build with a Virtualenv build step
2. Use the Shell or XShell command with a minimal script:

set
pip.exe install -r pkg_requirements.txt

The build fails because the pip command can not be found. The output shows the Path environment variable uses the : (colon) separator for the virtualenv Scripts directory. On Windows, the PATH separator should be ; (semicolon).

[1-SMSDK-apps-venv] $ cmd.exe /c call C:\DOCUME~1\builder\LOCALS~1\Temp\shiningpanda4030889806584404855.bat

c:\jenkins-dev\workspace\1-SMSDK-apps-venvset
... [edited for relevance] ...
Path=c:\jenkins-dev\workspace\1-SMSDK-apps-venv:c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts:C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\FLEXlm;C:\Program Files\CollabNet\Subversion Client;c:\cygwin\bin;c:\cygwin\usr\bin;C:\Program Files\Java\jre6\bin
PYTHON_EXE=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9\Scripts\python.exe
VIRTUAL_ENV=c:\jenkins-dev\shiningpanda\deb23754\virtualenvs\d41d8cd9
WORKSPACE=c:\jenkins-dev\workspace\1-SMSDK-apps-venv

c:\jenkins-dev\workspace\1-SMSDK-apps-venvpip.exe install -r pkg_requirements.pip
'pip.exe' is not recognized as an internal or external command,
operable program or batch file.

Environment:

Linux master, Windows XP slave with Python 2.7

Project:

Jenkins

Priority:

Major

Reporter:

Dave Bacher

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

[JIRA] (JENKINS-16177) Numeric build links should always go to the specific numeric build number they represent

2012-12-19 Thread trej...@java.net (JIRA)















































trejkaz
 created  JENKINS-16177


Numeric build links should always go to the specific numeric build number they represent















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


19/Dec/12 10:44 PM



Description:


When I go to the front page of Jenkins, it shows things like:

  commit-trigger   1 hr 2 min (#12159)   2 days 0 hr (#12151)

This #12151 link, however, doesn't go to build 12151, but rather it goes to build "lastFailedBuild".

This leads to subsequent confusion. For instance, I had a browser tab open on a specific failed test in "lastFailedBuild". I wanted to see which other tests failed in the same build, so I clicked on "Test Result". This took me to a page which said the test I was looking at passed and it was a couple of minutes until I realised how I had been tricked.

Ideally, I think that any link to lastFailedBuild/lastSuccessfulBuild/lastCompletedBuild should also immediately redirect to the actual build it represents, so that subsequent links followed will go to deterministic destinations.




Project:


Jenkins



Priority:


Minor



Reporter:


trejkaz

























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

[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2012-12-19 Thread slide.o....@gmail.com (JIRA)















































Slide-O-Mix
 commented on  JENKINS-16163


NullPointerException when sending post build emails - all triggers appear to be impacted















You could also enable debug mode in the global config and then post the output from the 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

[JIRA] (JENKINS-16178) Builds for username page Missing Some Entries

2012-12-19 Thread emre.bur...@wdc.com (JIRA)















































Emre Burhan
 created  JENKINS-16178


Builds for username page Missing Some Entries















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


gui



Created:


19/Dec/12 11:08 PM



Description:


Builds listed on "Builds for username" page is missing some of the entries. 

Steps to reproduce:
1. Make sure logged on with a valid user
2. Create a job that updates source from SVN
3. Build the job
4. Go to http://jenkins_server/user/user_name/builds

Expected:
All builds started by the user is shown

Actual:
Some of the builds are not listed

Additional Notes:


	The build page at http://jenkins_server/job/job_name/build_number/ for the build started on Step 3 above is displaying the user name correctly:
"Started by user user_name"




	Seems like only the builds that have "Changes" (SVN changes since last build) are listed on the "Builds for username" page.






Environment:


Fedora 15

2.6.43.8-1.fc15.x86_64




Project:


Jenkins



Priority:


Major



Reporter:


Emre Burhan

























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

[JIRA] (JENKINS-16178) Builds for username page Missing Some Entries

2012-12-19 Thread emre.bur...@wdc.com (JIRA)















































Emre Burhan
 commented on  JENKINS-16178


Builds for username page Missing Some Entries















Using Security Realm: Active Directory



























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

[JIRA] (JENKINS-16178) Builds for username page Missing Some Entries

2012-12-19 Thread emre.bur...@wdc.com (JIRA)















































Emre Burhan
 updated  JENKINS-16178


Builds for username page Missing Some Entries
















Change By:


Emre Burhan
(19/Dec/12 11:26 PM)




Component/s:


active-directory



























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

[JIRA] (JENKINS-15881) svn revision check failed when checking out older revision after HEAD build

2012-12-19 Thread j...@s171023571.onlinehome.us (JIRA)

J K
commented on JENKINS-15881

svn revision check failed when checking out older revision after HEAD build

One of our products is a mesh networking device comprised of three microprocessors, each of which maps to a different development team, each of which maintains their own SVN repo and such. Our team is using Jenkins to manage a CI process with build management and unit testing (all specific to our microprocessor), but also integration testing and release management. The integration testing involves pulling and building the code for all three processors and deploying it into a testbed environment that runs automated tests taking anywhere from a few minutes to a few days depending on needed scope. Generally we want to pull from the head of trunk for all three projects.

However, there have been times when the independent teams get into a state where there would be incompatibilities running the most recent code for all three. For instance, if the highest priority for teams A and B is to get a new interprocessor communication protocol working, but for team C is to get a mesh networking component ready, then trunk@HEAD processor C can no longer talk with trunk@HEAD A or B. When this happens we've used the ability to go back revisions on A and B to do integration testing and (internal) release management when our systems test (human-driven) resources were available.

I created a groovy script that monitors SVN commit comments for certain key word/value pairs, one of which specifies if a particular revision of processor A and/or B code is needed. This, plus the patch I submitted on github for issue #14116, took care of the problem. We're still quite new to Jenkins and CI in general, so there may be a more elegant solution. But so far this has been working for us.

[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang















































SCM/JIRA link daemon
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/hudson/remoting/Capability.java
 src/main/java/hudson/remoting/Channel.java
 src/main/java/hudson/remoting/Command.java
 src/main/java/hudson/remoting/MimicException.java
 src/main/java/hudson/remoting/ProxyOutputStream.java
 src/test/java/hudson/remoting/DeadRemoteOutputStreamTest.java
http://jenkins-ci.org/commit/remoting/d084f5095f11a8bcb80913266d664b9d1f17dc3b
Log:
  FIXED JENKINS-7114 fixed the layer confusion in the remoting

When ProxyOutputStream sends write(byte[]) to the other end and the actual write fails, "NotifyDeadWriter" object comes back and reports back that the write has failed. Without this mechanism, the writer side will keep on going.

Because the RemoteOutputStream service is a lower layer service that cannot rely on custom classloading service (doing so would create cyclic dependencies), when we send back this exception, the object graph of the exception needs to be deserializable on the receiver side. This is not the case when the exception class is defined by the user (as is the case of winstone.ClientSocketException.)

This fix addresses this problem by turning an exception class into another class that emulates the output of the original exception.

To make this change interopeable with earlier versions, we need to introduce a new capability flag. If we send MimicException to the other side and the other side doesn't have this class definition, then it'll cause automatic fail.


Compare: https://github.com/jenkinsci/remoting/compare/2b1ec8ab1528...d084f5095f11




























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

[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang















































SCM/JIRA link daemon
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 changelog.html
 pom.xml
http://jenkins-ci.org/commit/jenkins/3cfa3e55a1f57b6634576a0d6d7ac044714e1022
Log:
  FIXED JENKINS-7114

The actual change is in the remoting 1.20.


Compare: https://github.com/jenkinsci/jenkins/compare/75fc9308a9f2...3cfa3e55a1f5




























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

[JIRA] (JENKINS-7114) aborting download of workspace files makes slave agent hang

2012-12-19 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-7114


aborting download of workspace files makes slave agent hang















Integrated in  jenkins_main_trunk #2154
 FIXED JENKINS-7114 (Revision 3cfa3e55a1f57b6634576a0d6d7ac044714e1022)

 Result = SUCCESS
kohsuke : 3cfa3e55a1f57b6634576a0d6d7ac044714e1022
Files : 

	changelog.html
	pom.xml





























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

[JIRA] (JENKINS-14524) Slave agent authorization 401















































Craig Ringer
 updated  JENKINS-14524


Slave agent authorization 401
















Amended report to tag github-oauth, tweak formatting.





Change By:


Craig Ringer
(20/Dec/12 5:49 AM)




Description:


Icanconnectmyslaveagentusingthedownloadedjnlpfile,butWindowsserviceisnotworkingbecauseofauthorization.Myconfigurationlookslikethis:
{code}
-Xrs-jar%BASE%\slave.jar-authxxx:xxx-jnlpUrlhttp://xxx.dyndns.org/computer/windows/slave-agent.jnlp-cp%BASE%\lib\commons-codec-1.5.jar-jnlpCredentialsxxx:xxx
{code}


AndinlogsIsee:
{code}
Failingtoobtainhttp://homersoft-ci.dyndns.org/computer/windows/slave-agent.jnlpjava.io.IOException:Failedtoloadhttp://xxx.dyndns.org/computer/windows/slave-agent.jnlp:403Forbidden	athudson.remoting.Launcher.parseJnlpArguments(Launcher.java:230)	athudson.remoting.Launcher.run(Launcher.java:192)	athudson.remoting.Launcher.main(Launcher.java:168)
{code}ImusingtheGitHubOAuthplugin.





Component/s:


github-oauth



























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

[JIRA] (JENKINS-14524) Slave agent authorization 401















































Craig Ringer
 commented on  JENKINS-14524


Slave agent authorization 401















Yeah, the GitHub plugin needs to allow an exception for the JNLP file, or preferably generate a unique per-worker username/password that it displays in the JNLP launch commands and uses automatically in the service. Not trivial to do, though.



























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

[JIRA] (JENKINS-4071) jnlp slaves doesn't support HTTP Auth















































Craig Ringer
 commented on  JENKINS-4071


jnlp slaves doesnt support HTTP Auth















This doesn't change the example commands to show the authentication argument on the node info page, so you have to research how to get the slave to work once you hit this 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

[JIRA] (JENKINS-14524) Slave agent authorization 401















































Craig Ringer
 updated  JENKINS-14524


Slave agent authorization 401
















Change By:


Craig Ringer
(20/Dec/12 6:13 AM)




Priority:


Critical
Major



























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

[JIRA] (JENKINS-14524) Slave agent authorization 401















































Craig Ringer
 commented on  JENKINS-14524


Slave agent authorization 401















Related to JENKINS-11149



























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

[JIRA] (JENKINS-11149) JNLP slave fails to connect if Anonymous has not permission READ















































Craig Ringer
 updated  JENKINS-11149


JNLP slave fails to connect if Anonymous has not permission READ
















Change By:


Craig Ringer
(20/Dec/12 6:15 AM)




Component/s:


security





Component/s:


slave-setup



























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

[JIRA] (JENKINS-14524) Slave agent authorization 401