date:20120507


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162486#comment-162486
 ] 

SCM/JIRA link daemon commented on JENKINS-12829:


Code changed in jenkins
User: David Santiago Turiño
Path:
 src/main/java/hudson/plugins/mercurial/MercurialSCM.java
 src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
 src/test/java/hudson/plugins/mercurial/SharingSCMTest.java
http://jenkins-ci.org/commit/mercurial-plugin/b1a2f8465fced379a54b6116d0fa059fc40deff7
Log:
  JENKINS-12829: A failed update sets revision of build to 00+

The mercurial plugin ensures that a failed clone operation throws the
corresponding exception, but that's not the case if the subsequent
update fails: no check is done of the return code of the hg update
command.

The effect is that the revision of the build is set to 00+, which
causes a huge change log calculation in the next build, as basically
the calculated log includes all thechange setss in the history of the
repo.




 A failed update sets revision of build to 00+
 -

 Key: JENKINS-12829
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12829
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Affects Versions: current
Reporter: David Santiago
Assignee: David Santiago
 Attachments: 00.png


 The mercurial plugin ensures that a failed clone operation throws the 
 corresponding exception, but that's not the case if the subsequent update 
 fails: no check is done of the return code of the hg update command.
 The effect is that the revision of the build is set to 00+, which causes 
 a huge changelog calculation in the next build, as basically the calculated 
 log includes all the changesets in the history of the repo.
 I've even seen a worse corner case, where a build is assigned up to three 
 different revisions if, for example, two update attempts fail and the third 
 one works when using the cache+share extension.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12829) A failed update sets revision of build to 000000+


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162487#comment-162487
 ] 

SCM/JIRA link daemon commented on JENKINS-12829:


Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/hudson/plugins/mercurial/MercurialSCM.java
 src/test/java/hudson/plugins/mercurial/MercurialSCMTest.java
http://jenkins-ci.org/commit/mercurial-plugin/a7483f9809464854c6af2d01db7ab6aab1c98461
Log:
  Merge pull request #22 from nimeacuerdo/fix-multiple-revisions-per-build-issue

[FIXED JENKINS-12829] A failed update sets revision of build to 00+


Compare: https://github.com/jenkinsci/mercurial-plugin/compare/99d221c...a7483f9



 A failed update sets revision of build to 00+
 -

 Key: JENKINS-12829
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12829
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Affects Versions: current
Reporter: David Santiago
Assignee: David Santiago
 Attachments: 00.png


 The mercurial plugin ensures that a failed clone operation throws the 
 corresponding exception, but that's not the case if the subsequent update 
 fails: no check is done of the return code of the hg update command.
 The effect is that the revision of the build is set to 00+, which causes 
 a huge changelog calculation in the next build, as basically the calculated 
 log includes all the changesets in the history of the repo.
 I've even seen a worse corner case, where a build is assigned up to three 
 different revisions if, for example, two update attempts fail and the third 
 one works when using the cache+share extension.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12829) A failed update sets revision of build to 000000+


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SCM/JIRA link daemon resolved JENKINS-12829.


Resolution: Fixed

 A failed update sets revision of build to 00+
 -

 Key: JENKINS-12829
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12829
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Affects Versions: current
Reporter: David Santiago
Assignee: David Santiago
 Attachments: 00.png


 The mercurial plugin ensures that a failed clone operation throws the 
 corresponding exception, but that's not the case if the subsequent update 
 fails: no check is done of the return code of the hg update command.
 The effect is that the revision of the build is set to 00+, which causes 
 a huge changelog calculation in the next build, as basically the calculated 
 log includes all the changesets in the history of the repo.
 I've even seen a worse corner case, where a build is assigned up to three 
 different revisions if, for example, two update attempts fail and the third 
 one works when using the cache+share extension.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162488#comment-162488
 ] 

SCM/JIRA link daemon commented on JENKINS-13656:


Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/analysis/core/BuildResult.java
http://jenkins-ci.org/commit/analysis-core-plugin/6a01bb768e88b9697652e8e006cb39d00967ebfc
Log:
  [FIXED JENKINS-13656] Make build history creation overridable.






 Trend graph shows values of wrong parser
 

 Key: JENKINS-13656
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13656
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: Jenkins ver. 1.458, warnings v4.4
Reporter: Johann Werner
Assignee: Ulli Hafner
Priority: Minor
 Attachments: build.xml, build54.png, enlarged_graph.png, 
 wrong_graph.png


 If there are several parsers activated, then the trend graph picks always the 
 results of the first parser instead of the selected one. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162489#comment-162489
 ] 

SCM/JIRA link daemon commented on JENKINS-13656:


Code changed in jenkins
User: Ulli Hafner
Path:
 pom.xml
 src/main/java/hudson/plugins/warnings/WarningsResult.java
http://jenkins-ci.org/commit/warnings-plugin/7db20dda08df20c7ba829a4c1b0f3d462e307140
Log:
  [FIXED JENKINS-13656] Use warnings history when restoring an instance of
WarningsResult.






 Trend graph shows values of wrong parser
 

 Key: JENKINS-13656
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13656
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: Jenkins ver. 1.458, warnings v4.4
Reporter: Johann Werner
Assignee: Ulli Hafner
Priority: Minor
 Attachments: build.xml, build54.png, enlarged_graph.png, 
 wrong_graph.png


 If there are several parsers activated, then the trend graph picks always the 
 results of the first parser instead of the selected one. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser

2012-05-07 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162490#comment-162490
 ] 

dogfood commented on JENKINS-13656:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_analysis-core 
#10446|http://ci.jenkins-ci.org/job/plugins_analysis-core/10446/]
 [FIXED JENKINS-13656] Make build history creation overridable. (Revision 
6a01bb768e88b9697652e8e006cb39d00967ebfc)

 Result = SUCCESS
Ulli Hafner : 
Files : 
* src/main/java/hudson/plugins/analysis/core/BuildResult.java


 Trend graph shows values of wrong parser
 

 Key: JENKINS-13656
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13656
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: Jenkins ver. 1.458, warnings v4.4
Reporter: Johann Werner
Assignee: Ulli Hafner
Priority: Minor
 Attachments: build.xml, build54.png, enlarged_graph.png, 
 wrong_graph.png


 If there are several parsers activated, then the trend graph picks always the 
 results of the first parser instead of the selected one. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser

2012-05-07 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162491#comment-162491
 ] 

dogfood commented on JENKINS-13656:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! 
[plugins_warnings #404|http://ci.jenkins-ci.org/job/plugins_warnings/404/]
 [FIXED JENKINS-13656] Use warnings history when restoring an instance of 
(Revision 7db20dda08df20c7ba829a4c1b0f3d462e307140)

 Result = UNSTABLE
Ulli Hafner : 
Files : 
* pom.xml
* src/main/java/hudson/plugins/warnings/WarningsResult.java


 Trend graph shows values of wrong parser
 

 Key: JENKINS-13656
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13656
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: Jenkins ver. 1.458, warnings v4.4
Reporter: Johann Werner
Assignee: Ulli Hafner
Priority: Minor
 Attachments: build.xml, build54.png, enlarged_graph.png, 
 wrong_graph.png


 If there are several parsers activated, then the trend graph picks always the 
 results of the first parser instead of the selected one. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-9093) Deploy: Allow specification of Context Path

2012-05-07 Thread t.lehm...@strato-rz.de (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162492#comment-162492
 ] 

Thomas Lehmann commented on JENKINS-9093:
-

I just built a snapshot of this plugin (at 37ae083) an tried the context path 
feature. It unfortunately does not work.

Trying to deploy to a GlassFish 3.1.2 with ContextRoot /A deployed the 
application with ContextRoot / (examined with GlassFish admin website).

 Deploy: Allow specification of Context Path
 ---

 Key: JENKINS-9093
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9093
 Project: Jenkins
  Issue Type: Improvement
  Components: deploy
Affects Versions: current
Reporter: Daniel Jones
Assignee: Willem Verstraeten
Priority: Minor

 It would be great if we could specify the context-path that the .war gets 
 deployed with.
 I'm trying to deploy a .war called ROOT.war, but when it's deployed via 
 Tomcat Manager it's context path is /ROOT instead of /. After restarting 
 Tomcat, the normal Tomcat behaviour of treating a .war called ROOT.war as the 
 default context takes over, but then we have two contexts instead of one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes

2012-05-07 Thread ah...@hotmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162493#comment-162493
 ] 

Amir Isfy commented on JENKINS-13227:
-

Any luck Michael?

 CVS plugin 2.1 does not detect changes
 --

 Key: JENKINS-13227
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227
 Project: Jenkins
  Issue Type: Bug
  Components: cvs
Reporter: Guillaume Bilodeau
Assignee: Michael Clarke
Priority: Critical
  Labels: cvs
 Attachments: rlog.txt


 As presented in the user group: 
 https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4
 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS 
 repository for a few weeks now, without any problems. The CVS plugin (v1.6) 
 was using the local cvsnt install.
 We've since upgraded the CVS plugin to version 2.1 (by manually pinning the 
 plugin) and since then, CVS changes are not detected. The CVS polling log is 
 triggered properly, tons of cvs rlog instructions are sent, but at the end 
 No changes is displayed.
 Using CVS plugin 1.6 the cvs polling command looked like this (executed at 
 5:26:21 PM EDT):
 cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 
 Thursday, March 22, 2012 9:26:21 PM UTC
 Using CVS plugin 2.1, the last cvs checkout command looked like this 
 (executed at 11:56:16 AM EDT):
 cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 
 11:56:16 EDT -d portailInt portailInt
 We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13650) Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins admin rights

2012-05-07 Thread lalm...@dgit.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162494#comment-162494
 ] 

Landis Almand commented on JENKINS-13650:
-

No user rights are granted, not just loss of Admin.  Only anonymous rights are 
granted.
Jenkins ver. 1.447.1

 Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins 
 admin rights
 ---

 Key: JENKINS-13650
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13650
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Windows Server 2003 x86, non-domain, connecting to 
 Windows Server 2008 Active Directory. Domain Name set to 
 ourcompanyname.com, Domain controller left blank. Jenkins version=1.450, AD 
 plugin version=1.26
Reporter: Tom Fanning
Assignee: Kohsuke Kawaguchi
  Labels: plugin, security

 I just updated the AD plugin with install without restarting turned on to 
 attempt to fix bug 12619 which I originally reported.
 It failed:
 INFO: Starting the installation of Active Directory plugin on behalf of 
 tfanning
 01-May-2012 11:23:40 hudson.model.UpdateCenter$UpdateCenterConfiguration 
 download
 INFO: Downloading Active Directory plugin
 01-May-2012 11:23:41 hudson.PluginManager dynamicLoad
 INFO: Attempting to dynamic load C:\Program 
 Files\Jenkins\plugins\active-directory.jpi
 01-May-2012 11:23:41 hudson.model.UpdateCenter$DownloadJob run
 SEVERE: Failed to install Active Directory plugin
 hudson.util.IOException2: Failed to dynamically deploy this plugin
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
   at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
   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\Jenkins\plugins\active-directory\WEB-INF\lib\active-directory-1.0.jar
   at hudson.Util.deleteFile(Util.java:237)
   at hudson.Util.deleteRecursive(Util.java:287)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:389)
   at 
 hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
   at hudson.PluginManager.dynamicLoad(PluginManager.java:340)
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
   ... 7 more
 I then restarted the Jenkins service, waited, logged in with my AD 
 credentials, so this appeared to work.
 However in Jenkins my AD account has now lost all of its admin privileges, 
 i.e. I nor any other person configured to have admin rights can now configure 
 Jenkins.
 I noticed active-directory.bak left over in the Jenkins plugin folder. 
 Stopped the service, deleted active-directory.jpi, renamed 
 active-directory.bak to .jpi, restarted, all working (albeit with bug 12619 
 still present)
 How should I upgrade to 1.27 safely?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13059) Backup userContent folder too


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Fürer resolved JENKINS-13059.


Resolution: Fixed

 Backup userContent folder too
 -

 Key: JENKINS-13059
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13059
 Project: Jenkins
  Issue Type: Improvement
  Components: thinBackup
 Environment: Jenkins 1.454
Reporter: Thomas Fields
Assignee: Thomas Fürer

 Hi there,
 First off, thinBackup is a super plugin. Just what I need. 
 I'd like to request that you add support for backing up the userContent 
 folder as well. If you don't want to hard code this path then could you at 
 least give me a new option such as Additional files included in backup 
 (regular expression) where I can specify the folder myself?
 Regards,
 Tom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13059) Backup userContent folder too


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162495#comment-162495
 ] 

Thomas Fürer commented on JENKINS-13059:


the work is almost done, but I need some time to test it. and I would also 
finish some other changes to release it. so please hold on...

 Backup userContent folder too
 -

 Key: JENKINS-13059
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13059
 Project: Jenkins
  Issue Type: Improvement
  Components: thinBackup
 Environment: Jenkins 1.454
Reporter: Thomas Fields
Assignee: Thomas Fürer

 Hi there,
 First off, thinBackup is a super plugin. Just what I need. 
 I'd like to request that you add support for backing up the userContent 
 folder as well. If you don't want to hard code this path then could you at 
 least give me a new option such as Additional files included in backup 
 (regular expression) where I can specify the folder myself?
 Regards,
 Tom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13427) Configuration view displays ERROR/Not Found under the edit boxes

[
https://issues.jenkins-ci.org/browse/JENKINS-13427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162497#comment-162497
]

Thomas Fürer commented on JENKINS-13427:

Integrated in !http://server:8080/jenkins/images/16x16/blue.png! [thinBackup
#33|http://server:8080/jenkins/job/thinBackup/33/]
fix for Jenkins-13427: Configuration view displays ERROR/Not Found under
the edit boxes (Revision 40549)

Result = SUCCESS

Configuration view displays ERROR/Not Found under the edit boxes

Key: JENKINS-13427
URL: https://issues.jenkins-ci.org/browse/JENKINS-13427
Project: Jenkins
Issue Type: Bug
Components: thinBackup
Reporter: Alexander Shusherov
Assignee: Thomas Fürer
Priority: Minor
Attachments: thinBackup-config.jpg

Hello, thinBackup developers! Thanks for a great plugin - we've been using it
for several months and it's very helpful!
2 cents though.
We've recently started to observe the attached picture. I.e. messages
ERROR, Not Found. Sorry!The page requested was not found. under the edit
boxes.
We are behind the proxy. The global jenkins proxy config (as well as the
config for the container) is correct - jenkins receives updates for plugins
successfully.

[JIRA] (JENKINS-13059) Backup userContent folder too


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162496#comment-162496
 ] 

Thomas Fürer commented on JENKINS-13059:


Integrated in !http://server:8080/jenkins/images/16x16/blue.png! [thinBackup 
#33|http://server:8080/jenkins/job/thinBackup/33/]
 fix for JENKINS-13059: Backup userContent folder too (Revision 40550)

 Result = SUCCESS
tofuatjava : [40550|http://fisheye4.atlassian.com/changelog/hudson/?cs=40550]
Files : 
* /trunk/hudson/plugins/thinBackup/pom.xml
* 
/trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java
* 
/trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPeriodicWork.java
* 
/trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java
* 
/trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java
* 
/trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/utils/Utils.java


 Backup userContent folder too
 -

 Key: JENKINS-13059
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13059
 Project: Jenkins
  Issue Type: Improvement
  Components: thinBackup
 Environment: Jenkins 1.454
Reporter: Thomas Fields
Assignee: Thomas Fürer

 Hi there,
 First off, thinBackup is a super plugin. Just what I need. 
 I'd like to request that you add support for backing up the userContent 
 folder as well. If you don't want to hard code this path then could you at 
 least give me a new option such as Additional files included in backup 
 (regular expression) where I can specify the folder myself?
 Regards,
 Tom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13656) Trend graph shows values of wrong parser

2012-05-07 Thread ullrich.haf...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162500#comment-162500
 ] 

Ulli Hafner commented on JENKINS-13656:
---

Integrated in !http://faktorzehn.org:8081/images/16x16/blue.png! [Jenkins 
Analysis Plug-ins (Compile) 
#492|http://faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20(Compile)/492/]
 [FIXED JENKINS-13656] Make build history creation overridable. (Revision 
6a01bb768e88b9697652e8e006cb39d00967ebfc)

 Result = SUCCESS

 Trend graph shows values of wrong parser
 

 Key: JENKINS-13656
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13656
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: Jenkins ver. 1.458, warnings v4.4
Reporter: Johann Werner
Assignee: Ulli Hafner
Priority: Minor
 Attachments: build.xml, build54.png, enlarged_graph.png, 
 wrong_graph.png


 If there are several parsers activated, then the trend graph picks always the 
 results of the first parser instead of the selected one. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12295) Jenkins apt-get repository does not allow to install specific version of Jenkins

2012-05-07 Thread gbringhu...@fusionio.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162501#comment-162501
 ] 

Gerald  Bringhurst commented on JENKINS-12295:
--

Are there any bad side affects if I use 'dpkg --install jenkins_1.459_all.deb' 
rather than 
not being able to use apt-get install jenkins=1.459


 Jenkins apt-get repository does not allow to install specific version of 
 Jenkins
 

 Key: JENKINS-12295
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12295
 Project: Jenkins
  Issue Type: Bug
  Components: release
Affects Versions: current
 Environment: Ubuntu 10.04
Reporter: Ian Formanek
Assignee: Peter Hayes

 I am trying to install specific version of Jenkins (1.427) via 'apt get 
 jenkins=1.427' which fails with E: Version '1.427' for 'jenkins' was not 
 found
 Here are details:
 Performing (as root):
 {code}
 wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo 
 apt-key add -
 sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/  
 /etc/apt/sources.list.d/jenkins.list'
 apt-get update
 apt-get install jenkins=1.427
 {code}
 Here is the output:
 {code}
 root@test2:~# wget -q -O - 
 http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
 OK
 root@test2:~# sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/  
 /etc/apt/sources.list.d/jenkins.list'
 root@test2:~# apt-get update
 Get:1 http://pkg.jenkins-ci.org binary/ Release.gpg [198B]
 Get:2 http://pkg.jenkins-ci.org binary/ Release [2126B]   
   
 Get:3 http://pkg.jenkins-ci.org binary/ Packages [564B]   

 Get:4 http://security.ubuntu.com lucid-security Release.gpg [198B]
   
 Hit http://archive.ubuntu.com lucid Release.gpg   

 Get:5 http://archive.ubuntu.com lucid-updates Release.gpg [198B]
 Get:6 http://security.ubuntu.com lucid-security Release [57.3kB]
 Hit http://archive.ubuntu.com lucid Release  
 Get:7 http://archive.ubuntu.com lucid-updates Release [57.3kB]
 Hit http://archive.ubuntu.com lucid/main Packages  
 Hit http://archive.ubuntu.com lucid/restricted Packages
 Hit http://archive.ubuntu.com lucid/universe Packages
 Hit http://archive.ubuntu.com lucid/main Sources
 Hit http://archive.ubuntu.com lucid/restricted Sources
 Hit http://archive.ubuntu.com lucid/universe Sources
 Get:8 http://security.ubuntu.com lucid-security/main Packages [251kB]
 Get:9 http://archive.ubuntu.com lucid-updates/main Packages [541kB]
 Get:10 http://security.ubuntu.com lucid-security/restricted Packages [14B]
 Get:11 http://security.ubuntu.com lucid-security/universe Packages [113kB]
   
 Get:12 http://security.ubuntu.com lucid-security/main Sources [73.1kB]

 Get:13 http://archive.ubuntu.com lucid-updates/restricted Packages [4011B]

 Get:14 http://archive.ubuntu.com lucid-updates/universe Packages [251kB]  

 Get:15 http://archive.ubuntu.com lucid-updates/main Sources [208kB]  
 Get:16 http://security.ubuntu.com lucid-security/restricted Sources [14B] 

 Get:17 http://security.ubuntu.com lucid-security/universe Sources [28.3kB]

 Get:18 http://archive.ubuntu.com lucid-updates/restricted Sources [1850B] 

 Get:19 http://archive.ubuntu.com lucid-updates/universe Sources [85.4kB]
 Fetched 1675kB in 2s (702kB/s) 
 Reading package lists... Done
 root@test2:~# apt-get install jenkins=1.427
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 E: Version '1.427' for 'jenkins' was not found
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kohsuke Kawaguchi updated JENKINS-11381:


Attachment: subversion.hpi

Uploaded 1.40 RC that supports Subversion 1.7

 Subversion Plugin does not support Subversion 1.7
 -

 Key: JENKINS-11381
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
Reporter: soundworker
Priority: Blocker
 Attachments: subversion.hpi




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162502#comment-162502
 ] 

Kohsuke Kawaguchi edited comment on JENKINS-11381 at 5/7/12 8:38 PM:
-

[Uploaded 1.40 
RC|https://issues.jenkins-ci.org/secure/attachment/21796/subversion.hpi] that 
supports Subversion 1.7. I'm running this on http://ci.jenkins-ci.org/ now, but 
any additional beta testing appreciated.

It does pass all the tests we have, but there are major changes in SVNKit, so 
I'm being bit cautious.

  was (Author: kohsuke):
Uploaded 1.40 RC that supports Subversion 1.7
  
 Subversion Plugin does not support Subversion 1.7
 -

 Key: JENKINS-11381
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
Reporter: soundworker
Priority: Blocker
 Attachments: subversion.hpi




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13698) Error 500 on static assets with 1.463-1.1 rpm

2012-05-07 Thread m...@kingant.net (JIRA)

Mark Doliner created JENKINS-13698:
--

 Summary: Error 500 on static assets with 1.463-1.1 rpm
 Key: JENKINS-13698
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13698
 Project: Jenkins
  Issue Type: Bug
  Components: greenballs
Reporter: Mark Doliner
Assignee: asgeirn


I yum updated to the jenkins-1.463-1.1 rpm from 
http://pkg.jenkins-ci.org/redhat/ repository today at noon PDT.  I'm running on 
CentOS 5.8 with java 1.6.0.

Since then, logged out users get the following error response for various 
static files (https://server:8443/static/5d0888f6/images/title.png, for 
example):
{noformat}
May 7, 2012 1:39:38 PM winstone.Logger logInternal
WARNING: Untrapped Error in Servlet
java.lang.NullPointerException
at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:50)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
at 
winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}

Interestingly, the error stops happening and the files are served successfully 
when the user logs in.  We *are* using the green balls plugin.  I don't know 
whether this is specific to the green balls plugin.

We're using project-based matrix auth strategy, where anonymous has fairly 
limited permissions: overall read and job read.

--
This message is

[JIRA] (JENKINS-13202) Artifact archiving from an ssh slave fails if symlinks are present

2012-05-07 Thread dre...@fb.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162503#comment-162503
 ] 

David Reiss commented on JENKINS-13202:
---

I created a pull request for this, including a trivial change to the original 
JENKINS-9118 test to expose the bug.

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

 Artifact archiving from an ssh slave fails if symlinks are present
 --

 Key: JENKINS-13202
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13202
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Slave must be a Unix via SSH slave.  I suspect the 
 master must be Unix-based also.  I tested with both the master and slave on 
 Linux.
Reporter: David Reiss
  Labels: artifact

 When archiving artifacts from a job executed on a Unix via SSH slave, if a 
 symlink is present and archived before its target, the archiving will fail.  
 It looks like the master is trying to chmod the local symlink (because it has 
 executable permissions stored in the tar used to do the remote copy), but 
 that fails because the target doesn't exist yet, and the exception aborts the 
 archiving.  I think the solution is to just not chmod symlinks, since they 
 don't have modes of their own.  This was a regression from 1.455 to 1.456.  I 
 suspect the fixes for JENKINS-9118 are the cause.
 To reproduce this problem, install the Jenkins master on a Linux machine and 
 add a Unix via SSH slave that is also a Linux machine.  Create a job with 
 the following build script:
 {noformat}
 rm -rf stuff
 mkdir stuff
 cd stuff
 touch zzfile
 ln -s zzfile aafile
 ln -s zzfile bbfile
 {noformat}
 Restrict this project to build on the slave.  Set up archiving for stuff/*. 
  Run the job.  The job will complete successfully, but archiving will abort 
 partway though with a stack trace in the console.
 {noformat}
 Archiving artifacts
 ERROR: Failed to archive artifacts: stuff/*
 hudson.util.IOException2: Failed to extract 
 /tmp/jenkins-slave-home/workspace/create_symlinks/stuff/*
   at hudson.FilePath.readFromTar(FilePath.java:1817)
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1729)
   at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
   at hudson.model.Build$RunnerImpl.post2(Build.java:162)
   at 
 hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625)
   at hudson.model.Run.run(Run.java:1435)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Caused by: java.io.IOException: Failed to chmod 
 /tmp/jenkins-home/jobs/create_symlinks/builds/2012-03-21_16-53-15/archive/stuff/aafile
  : No such file or directory
   at hudson.FilePath._chmod(FilePath.java:1248)
   at hudson.FilePath.readFromTar(FilePath.java:1813)
   ... 12 more
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13398) support for starteam cache agents

2012-05-07 Thread paulyphon...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162504#comment-162504
 ] 

Paul Coste commented on JENKINS-13398:
--

I would be very interested in participating in development and testing, and do 
have some cache agents to test on.  I am very interested in using this feature.

 support for starteam cache agents
 -

 Key: JENKINS-13398
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13398
 Project: Jenkins
  Issue Type: Improvement
  Components: starteam
Affects Versions: current
Reporter: mistafunk
Assignee: jan_ruzicka
Priority: Minor

 it would be nice to have support for starteam cache agents, this would 
 accelerate checkouts quite a bit.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7

2012-05-07 Thread ukrain...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162505#comment-162505
 ] 

Alexei Turchanikov commented on JENKINS-11381:
--

I just tried the 1.40 RC, it throws an exception when attempting to check out 
to a directory that isn't a working copy (such as when Always check out a 
fresh copy is selected or if this is the first build):


ERROR: Failed to check out https://domain/svn/repo
org.tmatesoft.svn.core.SVNException: svn: E155007: 
'C:\Data\Jenkins\workspace\job\src' is not a working copy
at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:170)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:379)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:283)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:276)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.openAnchor(SVNWCAccess.java:171)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:514)
at 
org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doCheckout(SVNUpdateClient16.java:965)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:19)
at 
org.tmatesoft.svn.core.internal.wc2.old.SvnOldCheckout.run(SvnOldCheckout.java:8)
at 
org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at 
org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at 
org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:781)
at 
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:86)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath.act(FilePath.java:832)
at hudson.FilePath.act(FilePath.java:814)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: svn: E155007: 'C:\Data\Jenkins\workspace\job\src' is not a working 
copy
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171)
at 
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126)
at 
org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:165)
... 28 more
FATAL: null
java.lang.NullPointerException
at java.util.ArrayList.addAll(Unknown Source)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1434)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)


 Subversion Plugin does not support Subversion 1.7
 -

 Key: JENKINS-11381
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381
 Project: Jenkins
  Issue Type: Improvement
  Components: subversion
Reporter: soundworker
Priority: Blocker
 Attachments: subversion.hpi




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-8398) Faster access to Console output

2012-05-07 Thread jgbai...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162506#comment-162506
 ] 

Justin Bailey commented on JENKINS-8398:


This feature seems to have disappeared from the latest builds of Jenkins. It's 
been gone since at least 1.461. Intentional change?

 Faster access to Console output
 ---

 Key: JENKINS-8398
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8398
 Project: Jenkins
  Issue Type: Improvement
  Components: core
Reporter: jonnycattt

 Requesting an enhancement for faster access to console output. Here are some 
 ideas:
 1) on the dashboard, have a new console icon that, when clicked, would 
 either show a) the current console output of a running build or b) the 
 console output of the last build
 2) On the Project page, under the Latest Test Result link, show a Latest 
 Console OUtput link
 3) On the Project page, in the Build History pod, show a link to the 
 console output. Again, if the build were running, it'd show that build's 
 current output, and if it were a completed build, it'd show that build's 
 completed output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13700) Build hangs during while Sending email

2012-05-07 Thread crw...@java.net (JIRA)

crwong created JENKINS-13700:


 Summary: Build hangs during while Sending email
 Key: JENKINS-13700
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13700
 Project: Jenkins
  Issue Type: Bug
  Components: core, email-ext
 Environment: OS: 
   Master: Ubuntu 10.04
   Slaves: OSX 1.7.3, Win2K8 Server, Win XP, Win2K3 Server
Jenkins: 1.424.1
Plugins:
   Email-ext plugin: 2.14.1
   Configuration Slicing plugin: 1.28.1
   Jenkins GIT plugin: 1.1.18
   Perforce Plugin: 1.3.9
Reporter: crwong


When building on the OSX slave, the build will get to the point where the 
console says that it is sending email, and it stays there.  If you look at the 
list of executors, the progress bar shows that the build is still on progress.  
If you look at the job's status page, it looks like the job has completed, and 
it is no longer running.  Clicking on the Stop build button next to the job 
in the Build Executors Status section, does nothing.  The only way to clear 
the executor is to restart Jenkins.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13699) Jenkins plugin does not identify itself as a ClientApplication

2012-05-07 Thread jan_ruzi...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162507#comment-162507
 ] 

jan_ruzicka commented on JENKINS-13699:
---

Changes were in commit d1e3cf743b382f49f0984aadce2a2cee9fd60321 and commit 
8489692fcfb05f5e0a0da9b150078fe1680cd390.

 Jenkins plugin does not identify itself as a ClientApplication
 --

 Key: JENKINS-13699
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13699
 Project: Jenkins
  Issue Type: New Feature
  Components: starteam
Reporter: pauldawg
Assignee: jan_ruzicka
Priority: Minor

 This fix has already been submitted and pulled into mainline.  I am 
 submitting the issue as a formality, but would like this pulled into a new 
 release of the plugin as soon as possible.  Without this feature, it blocks 
 StarTeam administrators from taking advantage of the AppControl feature in 
 2009 to block unauthorized clients and utilities.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12295) Jenkins apt-get repository does not allow to install specific version of Jenkins

2012-05-07 Thread peteha...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Hayes updated JENKINS-12295:
--

Component/s: core

This is not related to the release plugin.

 Jenkins apt-get repository does not allow to install specific version of 
 Jenkins
 

 Key: JENKINS-12295
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12295
 Project: Jenkins
  Issue Type: Bug
  Components: core, release
Affects Versions: current
 Environment: Ubuntu 10.04
Reporter: Ian Formanek
Assignee: Peter Hayes

 I am trying to install specific version of Jenkins (1.427) via 'apt get 
 jenkins=1.427' which fails with E: Version '1.427' for 'jenkins' was not 
 found
 Here are details:
 Performing (as root):
 {code}
 wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo 
 apt-key add -
 sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/  
 /etc/apt/sources.list.d/jenkins.list'
 apt-get update
 apt-get install jenkins=1.427
 {code}
 Here is the output:
 {code}
 root@test2:~# wget -q -O - 
 http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
 OK
 root@test2:~# sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/  
 /etc/apt/sources.list.d/jenkins.list'
 root@test2:~# apt-get update
 Get:1 http://pkg.jenkins-ci.org binary/ Release.gpg [198B]
 Get:2 http://pkg.jenkins-ci.org binary/ Release [2126B]   
   
 Get:3 http://pkg.jenkins-ci.org binary/ Packages [564B]   

 Get:4 http://security.ubuntu.com lucid-security Release.gpg [198B]
   
 Hit http://archive.ubuntu.com lucid Release.gpg   

 Get:5 http://archive.ubuntu.com lucid-updates Release.gpg [198B]
 Get:6 http://security.ubuntu.com lucid-security Release [57.3kB]
 Hit http://archive.ubuntu.com lucid Release  
 Get:7 http://archive.ubuntu.com lucid-updates Release [57.3kB]
 Hit http://archive.ubuntu.com lucid/main Packages  
 Hit http://archive.ubuntu.com lucid/restricted Packages
 Hit http://archive.ubuntu.com lucid/universe Packages
 Hit http://archive.ubuntu.com lucid/main Sources
 Hit http://archive.ubuntu.com lucid/restricted Sources
 Hit http://archive.ubuntu.com lucid/universe Sources
 Get:8 http://security.ubuntu.com lucid-security/main Packages [251kB]
 Get:9 http://archive.ubuntu.com lucid-updates/main Packages [541kB]
 Get:10 http://security.ubuntu.com lucid-security/restricted Packages [14B]
 Get:11 http://security.ubuntu.com lucid-security/universe Packages [113kB]
   
 Get:12 http://security.ubuntu.com lucid-security/main Sources [73.1kB]

 Get:13 http://archive.ubuntu.com lucid-updates/restricted Packages [4011B]

 Get:14 http://archive.ubuntu.com lucid-updates/universe Packages [251kB]  

 Get:15 http://archive.ubuntu.com lucid-updates/main Sources [208kB]  
 Get:16 http://security.ubuntu.com lucid-security/restricted Sources [14B] 

 Get:17 http://security.ubuntu.com lucid-security/universe Sources [28.3kB]

 Get:18 http://archive.ubuntu.com lucid-updates/restricted Sources [1850B] 

 Get:19 http://archive.ubuntu.com lucid-updates/universe Sources [85.4kB]
 Fetched 1675kB in 2s (702kB/s) 
 Reading package lists... Done
 root@test2:~# apt-get install jenkins=1.427
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 E: Version '1.427' for 'jenkins' was not found
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13702) extra columns plugin - would like to see tests run,failed,error,skipped numbers

2012-05-07 Thread aslo...@gmail.com (JIRA)

Adam Sloan created JENKINS-13702:


 Summary: extra columns plugin - would like to see tests 
run,failed,error,skipped numbers
 Key: JENKINS-13702
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13702
 Project: Jenkins
  Issue Type: New Feature
  Components: extra-columns, plugin
Affects Versions: current
 Environment: any
Reporter: Adam Sloan
Assignee: Fred G
Priority: Minor


It would be useful for me to be able to use the extra columns plugin to display 
on the View the columns: #tests run, # failed, # errored, and # skipped - or a 
sum to total/passed/failed


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13703) AJP support does not respect the specs. breaks with SSL

2012-05-07 Thread simp...@gmail.com (JIRA)

Simon Poirier created JENKINS-13703:
---

 Summary: AJP support does not respect the specs. breaks with SSL
 Key: JENKINS-13703
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13703
 Project: Jenkins
  Issue Type: Bug
  Components: www
Affects Versions: current
Reporter: Simon Poirier


According to this bug https://issues.apache.org/bugzilla/show_bug.cgi?id=39658 
an the mod_jk documentation, ssl_key_size attribute is passed as an integer.
Winstone parses it as a string and generates a stack trace.

Steps to reproduce:
1. Start jenkins in standalone mode with AJP activated on some port
2. Setup a reverse proxy on apache on a virtualhost which has ssl configured
3. navigate to https://rproxy.address/jenkins

Results
- Apache returns an Internal error
- /var/log/jenkins/jenkins.log is filled with EOFException stack such as this 
one
java.io.EOFException
at java.io.DataInputStream.readFully(DataInputStream.java:197)
at java.io.DataInputStream.readFully(DataInputStream.java:169)
at 
winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:244)
at 
winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:231)
at 
winstone.ajp13.Ajp13IncomingPacket.parsePacket(Ajp13IncomingPacket.java:168)
at 
winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:184)
at winstone.RequestHandlerThread.run(RequestHandlerThread.java:67)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)


Expected behaviour:
A jenkins page, like when using http


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13703) AJP support does not respect the specs. breaks with SSL

2012-05-07 Thread simp...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Poirier updated JENKINS-13703:


Attachment: ajp_ssl.patch

here is a patch based on the specs on the mod_proxy_ajp page 
https://httpd.apache.org/docs/2.2/mod/mod_proxy_ajp.html

 AJP support does not respect the specs. breaks with SSL
 ---

 Key: JENKINS-13703
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13703
 Project: Jenkins
  Issue Type: Bug
  Components: www
Affects Versions: current
Reporter: Simon Poirier
 Attachments: ajp_ssl.patch


 According to this bug 
 https://issues.apache.org/bugzilla/show_bug.cgi?id=39658 an the mod_jk 
 documentation, ssl_key_size attribute is passed as an integer.
 Winstone parses it as a string and generates a stack trace.
 Steps to reproduce:
 1. Start jenkins in standalone mode with AJP activated on some port
 2. Setup a reverse proxy on apache on a virtualhost which has ssl configured
 3. navigate to https://rproxy.address/jenkins
 Results
 - Apache returns an Internal error
 - /var/log/jenkins/jenkins.log is filled with EOFException stack such as this 
 one
 java.io.EOFException
 at java.io.DataInputStream.readFully(DataInputStream.java:197)
 at java.io.DataInputStream.readFully(DataInputStream.java:169)
 at 
 winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:244)
 at 
 winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:231)
 at 
 winstone.ajp13.Ajp13IncomingPacket.parsePacket(Ajp13IncomingPacket.java:168)
 at 
 winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:184)
 at winstone.RequestHandlerThread.run(RequestHandlerThread.java:67)
 at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
 at java.util.concurrent.FutureTask.run(FutureTask.java:166)
 at 
 winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 at java.lang.Thread.run(Thread.java:636)
 Expected behaviour:
 A jenkins page, like when using http

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13650) Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins admin rights


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162512#comment-162512
 ] 

Kohsuke Kawaguchi commented on JENKINS-13650:
-

Argh. My 8b4c00a79201b605908d5d8983a7c719b0d645ff must have caused this. Fixing 
this now.

 Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins 
 admin rights
 ---

 Key: JENKINS-13650
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13650
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Windows Server 2003 x86, non-domain, connecting to 
 Windows Server 2008 Active Directory. Domain Name set to 
 ourcompanyname.com, Domain controller left blank. Jenkins version=1.450, AD 
 plugin version=1.26
Reporter: Tom Fanning
Assignee: Kohsuke Kawaguchi
  Labels: plugin, security

 I just updated the AD plugin with install without restarting turned on to 
 attempt to fix bug 12619 which I originally reported.
 It failed:
 INFO: Starting the installation of Active Directory plugin on behalf of 
 tfanning
 01-May-2012 11:23:40 hudson.model.UpdateCenter$UpdateCenterConfiguration 
 download
 INFO: Downloading Active Directory plugin
 01-May-2012 11:23:41 hudson.PluginManager dynamicLoad
 INFO: Attempting to dynamic load C:\Program 
 Files\Jenkins\plugins\active-directory.jpi
 01-May-2012 11:23:41 hudson.model.UpdateCenter$DownloadJob run
 SEVERE: Failed to install Active Directory plugin
 hudson.util.IOException2: Failed to dynamically deploy this plugin
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
   at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
   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\Jenkins\plugins\active-directory\WEB-INF\lib\active-directory-1.0.jar
   at hudson.Util.deleteFile(Util.java:237)
   at hudson.Util.deleteRecursive(Util.java:287)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:389)
   at 
 hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
   at hudson.PluginManager.dynamicLoad(PluginManager.java:340)
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
   ... 7 more
 I then restarted the Jenkins service, waited, logged in with my AD 
 credentials, so this appeared to work.
 However in Jenkins my AD account has now lost all of its admin privileges, 
 i.e. I nor any other person configured to have admin rights can now configure 
 Jenkins.
 I noticed active-directory.bak left over in the Jenkins plugin folder. 
 Stopped the service, deleted active-directory.jpi, renamed 
 active-directory.bak to .jpi, restarted, all working (albeit with bug 12619 
 still present)
 How should I upgrade to 1.27 safely?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12607) Active directory user names should not be case sensitive.


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162513#comment-162513
 ] 

Kohsuke Kawaguchi commented on JENKINS-12607:
-

Sorry, this isn't fixed yet. It caused a serious regression JENKINS-13650 and 
needed to be backed out.

 Active directory user names should not be case sensitive. 
 --

 Key: JENKINS-12607
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12607
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
Affects Versions: current
 Environment: Windows Server 2008.
Reporter: Paul M
Priority: Minor

 Active directory user names should not be case sensitive. For example if I 
 add the user paul then I would expect to be able to also login as Paul, 
 pAul or any other case combination.
 At the moment this won't match any user name and fail to login the user in, 
 or worse match none and apply authenticated user permissions. This seems to 
 confuse a lot of users.
 If there is a use case where case sensitivity is required then I think there 
 should be a toggle option to enable or disable it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13650) Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins admin rights


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162514#comment-162514
 ] 

Kohsuke Kawaguchi commented on JENKINS-13650:
-

Rolled back. Fixed for 1.28.

 Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins 
 admin rights
 ---

 Key: JENKINS-13650
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13650
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Windows Server 2003 x86, non-domain, connecting to 
 Windows Server 2008 Active Directory. Domain Name set to 
 ourcompanyname.com, Domain controller left blank. Jenkins version=1.450, AD 
 plugin version=1.26
Reporter: Tom Fanning
Assignee: Kohsuke Kawaguchi
  Labels: plugin, security

 I just updated the AD plugin with install without restarting turned on to 
 attempt to fix bug 12619 which I originally reported.
 It failed:
 INFO: Starting the installation of Active Directory plugin on behalf of 
 tfanning
 01-May-2012 11:23:40 hudson.model.UpdateCenter$UpdateCenterConfiguration 
 download
 INFO: Downloading Active Directory plugin
 01-May-2012 11:23:41 hudson.PluginManager dynamicLoad
 INFO: Attempting to dynamic load C:\Program 
 Files\Jenkins\plugins\active-directory.jpi
 01-May-2012 11:23:41 hudson.model.UpdateCenter$DownloadJob run
 SEVERE: Failed to install Active Directory plugin
 hudson.util.IOException2: Failed to dynamically deploy this plugin
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
   at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
   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\Jenkins\plugins\active-directory\WEB-INF\lib\active-directory-1.0.jar
   at hudson.Util.deleteFile(Util.java:237)
   at hudson.Util.deleteRecursive(Util.java:287)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:389)
   at 
 hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
   at hudson.PluginManager.dynamicLoad(PluginManager.java:340)
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
   ... 7 more
 I then restarted the Jenkins service, waited, logged in with my AD 
 credentials, so this appeared to work.
 However in Jenkins my AD account has now lost all of its admin privileges, 
 i.e. I nor any other person configured to have admin rights can now configure 
 Jenkins.
 I noticed active-directory.bak left over in the Jenkins plugin folder. 
 Stopped the service, deleted active-directory.jpi, renamed 
 active-directory.bak to .jpi, restarted, all working (albeit with bug 12619 
 still present)
 How should I upgrade to 1.27 safely?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12607) Active directory user names should not be case sensitive.

[
https://issues.jenkins-ci.org/browse/JENKINS-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162515#comment-162515
]

Kohsuke Kawaguchi commented on JENKINS-12607:
-

The regression was that various code in Jenkins actually persists the user name
(such as the matrix security.) So any kind of automatic canonicalization
results in name mismatch, resulting in a loss of permissions.

The proper fix needs to be in the core where SecurityRealm would decide whether
the username/groupname is case sensitive.

Active directory user names should not be case sensitive.
--

Key: JENKINS-12607
URL: https://issues.jenkins-ci.org/browse/JENKINS-12607
Project: Jenkins
Issue Type: Bug
Components: active-directory
Affects Versions: current
Environment: Windows Server 2008.
Reporter: Paul M
Priority: Minor

Active directory user names should not be case sensitive. For example if I
add the user paul then I would expect to be able to also login as Paul,
pAul or any other case combination.
At the moment this won't match any user name and fail to login the user in,
or worse match none and apply authenticated user permissions. This seems to
confuse a lot of users.
If there is a use case where case sensitivity is required then I think there
should be a toggle option to enable or disable it.

[JIRA] (JENKINS-13650) Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins admin rights


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162517#comment-162517
 ] 

SCM/JIRA link daemon commented on JENKINS-13650:


Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 
src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java
http://jenkins-ci.org/commit/active-directory-plugin/15a8a87bc333a12ead447425075df3bdafd7625c
Log:
  [FIXED JENKINS-13650] Revert [JENKINS-12607] canonicalize the name.

This reverts commit 8b4c00a79201b605908d5d8983a7c719b0d645ff.


Compare: 
https://github.com/jenkinsci/active-directory-plugin/compare/e8943e7...15a8a87



 Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins 
 admin rights
 ---

 Key: JENKINS-13650
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13650
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Windows Server 2003 x86, non-domain, connecting to 
 Windows Server 2008 Active Directory. Domain Name set to 
 ourcompanyname.com, Domain controller left blank. Jenkins version=1.450, AD 
 plugin version=1.26
Reporter: Tom Fanning
Assignee: Kohsuke Kawaguchi
  Labels: plugin, security

 I just updated the AD plugin with install without restarting turned on to 
 attempt to fix bug 12619 which I originally reported.
 It failed:
 INFO: Starting the installation of Active Directory plugin on behalf of 
 tfanning
 01-May-2012 11:23:40 hudson.model.UpdateCenter$UpdateCenterConfiguration 
 download
 INFO: Downloading Active Directory plugin
 01-May-2012 11:23:41 hudson.PluginManager dynamicLoad
 INFO: Attempting to dynamic load C:\Program 
 Files\Jenkins\plugins\active-directory.jpi
 01-May-2012 11:23:41 hudson.model.UpdateCenter$DownloadJob run
 SEVERE: Failed to install Active Directory plugin
 hudson.util.IOException2: Failed to dynamically deploy this plugin
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
   at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
   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\Jenkins\plugins\active-directory\WEB-INF\lib\active-directory-1.0.jar
   at hudson.Util.deleteFile(Util.java:237)
   at hudson.Util.deleteRecursive(Util.java:287)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:389)
   at 
 hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
   at hudson.PluginManager.dynamicLoad(PluginManager.java:340)
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
   ... 7 more
 I then restarted the Jenkins service, waited, logged in with my AD 
 credentials, so this appeared to work.
 However in Jenkins my AD account has now lost all of its admin privileges, 
 i.e. I nor any other person configured to have admin rights can now configure 
 Jenkins.
 I noticed active-directory.bak left over in the Jenkins plugin folder. 
 Stopped the service, deleted active-directory.jpi, renamed 
 active-directory.bak to .jpi, restarted, all working (albeit with bug 12619 
 still present)
 How should I upgrade to 1.27 safely?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13674) AD Auth with Matrix authentication now requires LDAP name rather than username


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kohsuke Kawaguchi resolved JENKINS-13674.
-

Resolution: Duplicate

 AD Auth with Matrix authentication now requires LDAP name rather than username
 --

 Key: JENKINS-13674
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13674
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
Affects Versions: current
Reporter: Keith Starling

 As of active-directory 1.27, the system resolves the full LDAP name for the 
 user, and apparently attempts to use this rather than the username for 
 comparison in matrix based authentication.  This is a pain, since it's much 
 easier and more consistent to use usernames for rights management (plus 
 that's how it used to work).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13650) Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins admin rights


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162519#comment-162519
 ] 

Kohsuke Kawaguchi commented on JENKINS-13650:
-

In 1.27, because of the 8b4c00a7 change mentioned above, Jenkins was logging 
users into their canonical names, like Kohsuke Kawaguchi, instead of their 
user names, like kkawaguchi. Most authorization strategies record users by 
their user names, so of course such change results in the permission losses.

1.28 restores the previous behaviour. This unfortunately means for those who 
modified config.xml for 1.27 would have to redo that one more time. My 
apologies.

 Upgrading Active Directory plugin from 1.26 to 1.27 causes loss of Jenkins 
 admin rights
 ---

 Key: JENKINS-13650
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13650
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Windows Server 2003 x86, non-domain, connecting to 
 Windows Server 2008 Active Directory. Domain Name set to 
 ourcompanyname.com, Domain controller left blank. Jenkins version=1.450, AD 
 plugin version=1.26
Reporter: Tom Fanning
Assignee: Kohsuke Kawaguchi
  Labels: plugin, security

 I just updated the AD plugin with install without restarting turned on to 
 attempt to fix bug 12619 which I originally reported.
 It failed:
 INFO: Starting the installation of Active Directory plugin on behalf of 
 tfanning
 01-May-2012 11:23:40 hudson.model.UpdateCenter$UpdateCenterConfiguration 
 download
 INFO: Downloading Active Directory plugin
 01-May-2012 11:23:41 hudson.PluginManager dynamicLoad
 INFO: Attempting to dynamic load C:\Program 
 Files\Jenkins\plugins\active-directory.jpi
 01-May-2012 11:23:41 hudson.model.UpdateCenter$DownloadJob run
 SEVERE: Failed to install Active Directory plugin
 hudson.util.IOException2: Failed to dynamically deploy this plugin
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1137)
   at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:955)
   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\Jenkins\plugins\active-directory\WEB-INF\lib\active-directory-1.0.jar
   at hudson.Util.deleteFile(Util.java:237)
   at hudson.Util.deleteRecursive(Util.java:287)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.Util.deleteRecursive(Util.java:278)
   at hudson.Util.deleteContentsRecursive(Util.java:198)
   at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:389)
   at 
 hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
   at hudson.PluginManager.dynamicLoad(PluginManager.java:340)
   at 
 hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1133)
   ... 7 more
 I then restarted the Jenkins service, waited, logged in with my AD 
 credentials, so this appeared to work.
 However in Jenkins my AD account has now lost all of its admin privileges, 
 i.e. I nor any other person configured to have admin rights can now configure 
 Jenkins.
 I noticed active-directory.bak left over in the Jenkins plugin folder. 
 Stopped the service, deleted active-directory.jpi, renamed 
 active-directory.bak to .jpi, restarted, all working (albeit with bug 12619 
 still present)
 How should I upgrade to 1.27 safely?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7