[JIRA] (JENKINS-14035) Responsive design

2012-06-07 Thread ohtake_tomoh...@java.net (JIRA)
OHTAKE Tomohiro created JENKINS-14035:
-

 Summary: Responsive design
 Key: JENKINS-14035
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14035
 Project: Jenkins
  Issue Type: New Feature
  Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro


Make Web UI responsive for better experience with smartphones.

{noformat:title=Desktops (current design)}
+---+
|Top Bar|
+---+
|Breadcrumbs|
+-+-+
|side-| main-panel  |
|panel| |
| | |
+-+-+
|Footer |
+---+
{noformat}

{noformat:title=Smartphones}
+---+
|Top bar|
+---+
|Breadcrumbs|
+---+
|side-panel |
|(togglable)|
+---+
|main-panel |
|   |
|   |
+---+
|Footer |
+---+
{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-14003) Starteam plugin takes a very long time for code check out

2012-06-07 Thread cool_a2...@yahoo.com (JIRA)

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

K Ningthouj commented on JENKINS-14003:
---

Yes, projects with huge files are more slower. Our project is quite huge and 
consists of around 3000 files.

ST set up is a dedicated one and Jenkins is on a separate machine from ST.

Started by user anonymous
No emails were triggered.
[workspace] $ cmd /c call C:\Windows\TEMP\hudson7170137422339611690.bat

C:\Program Files\Jenkins\jobs\BUILD1\workspacestcmd co -p 
test:testpwd@*:/sourceproject/viewname -is -F NCO -rp  
C:\Jenkins\Codebase\Project * 
StarTeam 11.0 Command Line Interface, Build 11.0.0.54
Copyright (c) 2003-2009 Borland Software Corporation. All rights reserved.
Using ini file: C:\ProgramData\Borland\StarTeam\ConnectionManager.ini
Folder: Code  (working dir: C:\Jenkins\Codebase\Project)
Folder: prototype  (working dir: C:\Jenkins\Codebase\Project\prototype)
readme.txt: checked out

Using command line, it takes around 10 minutes to do a clean checkout (after 
removing the local directory). Subsequent checkouts are pretty fast  1 min.






 Starteam plugin takes a very long time for code check out
 -

 Key: JENKINS-14003
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14003
 Project: Jenkins
  Issue Type: Improvement
  Components: starteam
Reporter: K Ningthouj
Assignee: jan_ruzicka

 We are using Starteam plugin with Jenkins for our project. When we perform 
 check-outs, it takes a very long time unlike when we run the starteam command 
 line using stcmd which is pretty fast. Is there any possibility in the 
 current plug-in that provides a way that we can pass a parameter just like 
 the starteam command line to speed up the checkout process?

--
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-13970) Build variable CC_BASELINE not populated with used baseline

2012-06-07 Thread c...@praqma.net (JIRA)

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

Christian Wolfgang commented on JENKINS-13970:
--

No problem. Thank you for reporting!

 Build variable CC_BASELINE not populated with used baseline
 ---

 Key: JENKINS-13970
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13970
 Project: Jenkins
  Issue Type: Bug
  Components: clearcase-ucm
Affects Versions: current
 Environment: Microsoft Windows Server 2003, Standard x64 Edition, 
 Service Pack 2
Reporter: Tim Pillsbury
Assignee: Christian Wolfgang
  Labels: clearcase, clearcase-ucm

 CCUCM says it is using the latest baseline, but the CC_BASELINE build 
 variable is not always set to it.
 The problem seems to occur after Updating view using all modules if CCUCM 
 finds activities and versions involved.
 {panel:title=Console Output|titleBGColor=#E7D6C1|bgColor=#CE}
 [CCUCM] Retrieved 28 baselines:
 [CCUCM] + WRKB_RLS_2012_06_00_ECM_5_18_12.1(Fri May 18 11:26:15 EDT 2012)
 [CCUCM] + WRKB_CL_WRKB_RLS_2012_06_00_ECM_5_18_12.1(Fri May 18 15:18:01 EDT 
 2012)
 [CCUCM] + WRKB_CL_WRKB_RLS_2012_06_00_ECM_5_19_12_CLR(Sat May 19 17:14:54 EDT 
 2012)
 [CCUCM]   ...
 [CCUCM] + _*WRKB_RLS_2012_06_00_ECM_jenkins_0529_0925(Tue May 29 09:25:52 EDT 
 2012)*_(n)
 [CCUCM] + WRKB_CL_WRKB_RLS_2012_06_00_ECM_5_29_12_CLR(Tue May 29 14:22:09 EDT 
 2012)
 [CCUCM] + WRKB_RLS_2012_06_00_ECM_5_29_12.1(Tue May 29 15:12:08 EDT 2012)
 [CCUCM] *Using* *baseline:WRKB_RLS_2012_06_00_ECM_5_29_12.1@\WRKB_PVOB*(y)
 [CCUCM] View root: E:\Jenkins\jobs\Workbench Build 2012 June All except 
 CPF\workspace\view
 [CCUCM] View tag : CCUCM_Workbench_Build_2012_June_All_except_CPF_XB57KDC
 [CCUCM] Reusing view root
 [CCUCM] Determine if view tag exists
 [CCUCM] Reusing view tag
 [CCUCM] UUID resulted in 
 CCUCM_Workbench_Build_2012_June_All_except_CPF_XB57KDC
 [CCUCM] Getting snapshotview
 [CCUCM] Rebasing development stream 
 (CCUCM_Workbench_Build_2012_June_All_except_CPF_XB57KDC) against parent 
 stream (WRKB_RLS_2012_06_00_ECM) Done
 [CCUCM] Updating view using all modules
 [CCUCM] _*Found 3 activities. 20 versions involved*_(i)
 {panel}
 But then Injected environment variable CC_BASELINE is incorrect
 {panel:title=Injected environment 
 variables|titleBGColor=#E7D6C1|bgColor=#CE}
 |CC_BASELINE|_*baseline:WRKB_RLS_2012_06_00_ECM_jenkins_0529_0925@\WRKB_PVOB*_|(n)|
 {panel}

--
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-14035) Responsive design

2012-06-07 Thread scm_issue_l...@java.net (JIRA)

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

SCM/JIRA link daemon commented on JENKINS-14035:


Code changed in jenkins
User: OHTAKE Tomohiro
Path:
 core/src/main/resources/lib/layout/layout.jelly
 war/src/main/webapp/less/jenkins.less
 war/src/main/webapp/scripts/bootstrap-collapse.js
 war/src/main/webapp/scripts/bootstrap-transition.js
http://jenkins-ci.org/commit/jenkins/62f266caaba66e437bb651e662b7361f9b124cb3
Log:
  [JENKINS-14035] Enable responsive design




 Responsive design
 -

 Key: JENKINS-14035
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14035
 Project: Jenkins
  Issue Type: New Feature
  Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro

 Make Web UI responsive for better experience with smartphones.
 {noformat:title=Desktops (current design)}
 +---+
 |Top Bar|
 +---+
 |Breadcrumbs|
 +-+-+
 |side-| main-panel  |
 |panel| |
 | | |
 +-+-+
 |Footer |
 +---+
 {noformat}
 {noformat:title=Smartphones}
 +---+
 |Top bar|
 +---+
 |Breadcrumbs|
 +---+
 |side-panel |
 |(togglable)|
 +---+
 |main-panel |
 |   |
 |   |
 +---+
 |Footer |
 +---+
 {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-14035) Responsive design

2012-06-07 Thread scm_issue_l...@java.net (JIRA)

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

SCM/JIRA link daemon commented on JENKINS-14035:


Code changed in jenkins
User: OHTAKE Tomohiro
Path:
 core/src/main/resources/lib/layout/layout.jelly
 war/src/main/webapp/scripts/bootstrap-button.js
http://jenkins-ci.org/commit/jenkins/a00b16611d205c922ae2c04b4213db9c2be16ce2
Log:
  [JENKINS-14035] Hide side-panel if width of device/window is small




 Responsive design
 -

 Key: JENKINS-14035
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14035
 Project: Jenkins
  Issue Type: New Feature
  Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro

 Make Web UI responsive for better experience with smartphones.
 {noformat:title=Desktops (current design)}
 +---+
 |Top Bar|
 +---+
 |Breadcrumbs|
 +-+-+
 |side-| main-panel  |
 |panel| |
 | | |
 +-+-+
 |Footer |
 +---+
 {noformat}
 {noformat:title=Smartphones}
 +---+
 |Top bar|
 +---+
 |Breadcrumbs|
 +---+
 |side-panel |
 |(togglable)|
 +---+
 |main-panel |
 |   |
 |   |
 +---+
 |Footer |
 +---+
 {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-13819) email notification can not send out whether the build is success or failed

2012-06-07 Thread chenjingjing...@163.com (JIRA)

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

pangpang wanzi commented on JENKINS-13819:
--

hi, it there any difference between triggered by jenkins to triggered manually? 
Now, the email can send out every time when I triggered manually, but failed to 
sent when triggered by upstream job.

 email notification can not send out whether the build is success  or failed
 ---

 Key: JENKINS-13819
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13819
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
 Environment: Jenkins version:1.428
Reporter: pangpang wanzi
Assignee: Slide-O-Mix
  Labels: email-ext, jenkins, plugin
 Attachments: config.xml, screenshot-1.jpg


 Email can not send out, error info as follows:
 Email was triggered for: Success
 Sending email for trigger: Success
 ERROR: Could not send email as a part of the post-build publishers.
 java.lang.NullPointerException
 or
 Email was triggered for: Success
 Sending email for trigger: Success
 ERROR: Could not send email as a part of the post-build publishers.
 java.lang.NullPointerException
   at java.util.regex.Matcher.quoteReplacement(Matcher.java:598)
   at 
 hudson.plugins.emailext.plugins.ContentBuilder$Tokenizer.appendReplacement(ContentBuilder.java:195)
   at 
 hudson.plugins.emailext.plugins.ContentBuilder.replaceTokensWithContent(ContentBuilder.java:96)
   at 
 hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:67)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.setContent(ExtendedEmailPublisher.java:369)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:274)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:220)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:212)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:174)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635)
   at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171)
   at hudson.model.Run.run(Run.java:1420)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:230)
 Finished: SUCCESS

--
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-14036) Sonar jobs not appering after upgrade

2012-06-07 Thread mixe...@gmail.com (JIRA)
Michel Drenthe created JENKINS-14036:


 Summary: Sonar jobs not appering after upgrade
 Key: JENKINS-14036
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14036
 Project: Jenkins
  Issue Type: Bug
  Components: sonar
Affects Versions: current
 Environment: Jenkins: 1.467
Sonar: 3.0.1 (Sonar Jenkins plugin-1.8)
openSUSE 12.1 (Asparagus) (x86_64)
Reporter: Michel Drenthe
Assignee: sonarteam


After updating Jenkins 1.466 - 1.467
All Jobs where Sonar is included are removed from the job list.
Log shows:

INFO   | jvm 1| 2012/06/07 09:44:51 | Jun 07, 2012 9:44:51 AM 
jenkins.InitReactorRunner$1 onTaskFailed
INFO   | jvm 1| 2012/06/07 09:44:51 | SEVERE: Failed Loading job Name SONAR
INFO   | jvm 1| 2012/06/07 09:44:51 | java.lang.NoSuchMethodError: 
hudson.maven.MavenModuleSet.getRootPOM()Ljava/lang/String;
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.plugins.sonar.SonarPublisher.getPomName(SonarPublisher.java:278)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.plugins.sonar.SonarPublisher.getSonarUrl(SonarPublisher.java:340)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.plugins.sonar.SonarPublisher.getProjectAction(SonarPublisher.java:358)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.tasks.BuildStepCompatibilityLayer.getProjectActions(BuildStepCompatibilityLayer.java:73)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:376)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:624)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:363)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.model.AbstractProject.onLoad(AbstractProject.java:279)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
hudson.model.Items.load(Items.java:115)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
jenkins.model.Jenkins$15.run(Jenkins.java:2472)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
jenkins.model.Jenkins$6.runTask(Jenkins.java:865)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
java.lang.Thread.run(Thread.java:722)



--
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-14036) Sonar jobs not appering after upgrade

2012-06-07 Thread roland.ew...@gmail.com (JIRA)

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

Roland Ewald commented on JENKINS-14036:


I guess this is caused by this problem: 
http://jira.codehaus.org/browse/SONARPLUGINS-1935

 Sonar jobs not appering after upgrade
 -

 Key: JENKINS-14036
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14036
 Project: Jenkins
  Issue Type: Bug
  Components: sonar
Affects Versions: current
 Environment: Jenkins: 1.467
 Sonar: 3.0.1 (Sonar Jenkins plugin-1.8)
 openSUSE 12.1 (Asparagus) (x86_64)
Reporter: Michel Drenthe
Assignee: sonarteam
  Labels: jenkins, job, plugin, sonar, update

 After updating Jenkins 1.466 - 1.467
 All Jobs where Sonar is included are removed from the job list.
 Log shows:
 INFO   | jvm 1| 2012/06/07 09:44:51 | Jun 07, 2012 9:44:51 AM 
 jenkins.InitReactorRunner$1 onTaskFailed
 INFO   | jvm 1| 2012/06/07 09:44:51 | SEVERE: Failed Loading job Name 
 SONAR
 INFO   | jvm 1| 2012/06/07 09:44:51 | java.lang.NoSuchMethodError: 
 hudson.maven.MavenModuleSet.getRootPOM()Ljava/lang/String;
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getPomName(SonarPublisher.java:278)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getSonarUrl(SonarPublisher.java:340)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getProjectAction(SonarPublisher.java:358)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.tasks.BuildStepCompatibilityLayer.getProjectActions(BuildStepCompatibilityLayer.java:73)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:376)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:624)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:363)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.AbstractProject.onLoad(AbstractProject.java:279)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.Items.load(Items.java:115)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 jenkins.model.Jenkins$15.run(Jenkins.java:2472)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 jenkins.model.Jenkins$6.runTask(Jenkins.java:865)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.lang.Thread.run(Thread.java:722)

--
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




Error while initializing Findbug Plugin

2012-06-07 Thread siddharth.shah
Hi All,

I am currently facing the problem with loading findbug plugin on Hudson
2.2.1

The details of the environment are
OS - Windows 32 bit
Hudson - 2.2.1
Tomcat 6.0
Ant 1.8.1
maven 2

I am able to install Static Code Analysis and Findbug plugin. However after
installing when I restart Tomcat I get the following error. The reason it
quotes is that it is not able to initialize analysis-core. Can someone
provide some help on the issue.

Error Log

SEVERE: Failed Initializing plugin findbugs
java.lang.NullPointerException
at hudson.PluginManager$2$1$2.run(PluginManager.java:313)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at hudson.model.Hudson$4.runTask(Hudson.java:698)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
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)

Jun 7, 2012 1:06:03 PM hudson.model.Hudson$5 onTaskFailed
SEVERE: Failed Initializing plugin analysis-core
java.lang.NullPointerException
at hudson.PluginManager$2$1$2.run(PluginManager.java:313)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at hudson.model.Hudson$4.runTask(Hudson.java:698)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
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)

Jun 7, 2012 1:06:03 PM hudson.model.Hudson$5 onAttained
INFO: Prepared all plugins

Jun 7, 2012 1:06:02 PM hudson.model.Hudson$5 onTaskFailed
SEVERE: Failed Loading plugin findbugs
java.io.IOException: Dependency analysis-core (1.39) doesn't exist
at 
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:443)
at hudson.PluginManager$2$1$1.run(PluginManager.java:296)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at hudson.model.Hudson$4.runTask(Hudson.java:698)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
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)

Jun 7, 2012 1:06:02 PM hudson.model.Hudson$5 onTaskFailed
SEVERE: Failed Loading plugin analysis-core
hudson.util.IOException2: Failed to load plugin instance for: analysis-core
at
org.hudsonci.inject.internal.plugin.SmoothiePluginStrategy.load(SmoothiePluginStrategy.java:193)
at
org.hudsonci.inject.internal.plugin.DelegatingPluginStrategy.load(DelegatingPluginStrategy.java:72)
at hudson.PluginManager$2$1$1.run(PluginManager.java:297)
at
org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at hudson.model.Hudson$4.runTask(Hudson.java:698)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
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.lang.LinkageError: loader (instance of 
org/hudsonci/inject/internal/plugin/PluginClassLoader): attempted  duplicate
class definition for name: org/apache/xerces/parsers/SAXParser
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at
org.aspectj.weaver.bcel.ExtensibleURLClassLoader.defineClass(ExtensibleURLClassLoader.java:63)
at
org.aspectj.weaver.loadtime.WeavingURLClassLoader.defineClass(WeavingURLClassLoader.java:151)
at
org.aspectj.weaver.bcel.ExtensibleURLClassLoader.defineClass(ExtensibleURLClassLoader.java:97)
at
org.aspectj.weaver.bcel.ExtensibleURLClassLoader.findClass(ExtensibleURLClassLoader.java:52)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at

[JIRA] (JENKINS-14036) Sonar jobs not appering after upgrade

2012-06-07 Thread mixe...@gmail.com (JIRA)

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

Michel Drenthe commented on JENKINS-14036:
--

Thats indeed the same problem. (From the comments they expect from Jenkins side 
that it will be fixed)

 Sonar jobs not appering after upgrade
 -

 Key: JENKINS-14036
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14036
 Project: Jenkins
  Issue Type: Bug
  Components: sonar
Affects Versions: current
 Environment: Jenkins: 1.467
 Sonar: 3.0.1 (Sonar Jenkins plugin-1.8)
 openSUSE 12.1 (Asparagus) (x86_64)
Reporter: Michel Drenthe
Assignee: sonarteam
  Labels: jenkins, job, plugin, sonar, update

 After updating Jenkins 1.466 - 1.467
 All Jobs where Sonar is included are removed from the job list.
 Log shows:
 INFO   | jvm 1| 2012/06/07 09:44:51 | Jun 07, 2012 9:44:51 AM 
 jenkins.InitReactorRunner$1 onTaskFailed
 INFO   | jvm 1| 2012/06/07 09:44:51 | SEVERE: Failed Loading job Name 
 SONAR
 INFO   | jvm 1| 2012/06/07 09:44:51 | java.lang.NoSuchMethodError: 
 hudson.maven.MavenModuleSet.getRootPOM()Ljava/lang/String;
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getPomName(SonarPublisher.java:278)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getSonarUrl(SonarPublisher.java:340)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.plugins.sonar.SonarPublisher.getProjectAction(SonarPublisher.java:358)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.tasks.BuildStepCompatibilityLayer.getProjectActions(BuildStepCompatibilityLayer.java:73)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:376)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:624)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:363)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.AbstractProject.onLoad(AbstractProject.java:279)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 hudson.model.Items.load(Items.java:115)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 jenkins.model.Jenkins$15.run(Jenkins.java:2472)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 jenkins.model.Jenkins$6.runTask(Jenkins.java:865)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
 INFO   | jvm 1| 2012/06/07 09:44:51 |   at 
 java.lang.Thread.run(Thread.java:722)

--
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-14037) Apply Label before resynchronize workspace

2012-06-07 Thread cyril.j...@gemalto.com (JIRA)
Cyril Jean created JENKINS-14037:


 Summary: Apply Label before resynchronize workspace
 Key: JENKINS-14037
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14037
 Project: Jenkins
  Issue Type: New Feature
  Components: integrity-plugin
Reporter: Cyril Jean
Assignee: Cletus D'Souza


Hello Cletus,

Here is the thing, today there is this great feature to be able to checkpoint 
before build, to be sure project is not altered between start and end of build.
MKS provides a keyword, $name$, that will be replaced with actual label applied 
to the checkpoint.
The problem now, is I cannot have this keyword replaced in the Jenkins build, 
because the label will only be applied at the end of the build.

So here is the request:
Can you add an option to apply label at the beginning of the build, same time 
you do the checkpoint.

Tks
cyril

--
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-14020) Exception during workspace synchronize

2012-06-07 Thread cyril.j...@gemalto.com (JIRA)

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

Cyril Jean commented on JENKINS-14020:
--

Hmm this build is missing now. not sure how it happens since I change a lot of 
thing. Maybe it's the reason, so I close the issue.

 Exception during workspace synchronize
 --

 Key: JENKINS-14020
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14020
 Project: Jenkins
  Issue Type: Bug
  Components: integrity-plugin
Affects Versions: current
 Environment: jenkins 1.465, PTC 1.13, WinXP 32bit SP3, no proxy, very 
 low bandwidth
Reporter: Cyril Jean
Assignee: Cletus D'Souza

 Have following exception during workspace resynchronize:
 SEVERE: An error occurred while reading stream from 
 'file:/D:/tools/.jenkins/jobs/SPS4Pack/builds/2012-06-05_15-40-14/changelog.xml',
  see nested exceptions
 com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: 
 Invalid byte 1 of 1-byte UTF-8 sequence.
   at 
 com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown 
 Source)
   at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(Unknown Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(Unknown
  Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown
  Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
  Source)
   at 
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown 
 Source)
   at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
  Source)
   at org.apache.commons.digester3.Digester.parse(Digester.java:1588)
   at org.apache.commons.digester3.Digester.parse(Digester.java:1557)
   at 
 hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:65)
   at 
 hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:20)
   at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:825)
   at hudson.model.AbstractBuild.access$600(AbstractBuild.java:103)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:591)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
   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)
 hudson.util.IOException2: Failed to parse 
 D:\tools\.jenkins\jobs\SPS4Pack\builds\2012-06-05_15-40-14\changelog.xml
   at 
 hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:69)
   at 
 hudson.scm.IntegrityChangeLogParser.parse(IntegrityChangeLogParser.java:20)
   at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:825)
   at hudson.model.AbstractBuild.access$600(AbstractBuild.java:103)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:591)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
   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: 
 com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: 
 Invalid byte 1 of 1-byte UTF-8 sequence.
   at 
 com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown 
 Source)
   at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.load(Unknown Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(Unknown
  Source)
   at 
 

[JIRA] (JENKINS-14038) Action tasks on build sidepannel don't use permalinks

2012-06-07 Thread nicolas.del...@gmail.com (JIRA)
Nicolas De Loof created JENKINS-14038:
-

 Summary: Action tasks on build sidepannel don't use permalinks
 Key: JENKINS-14038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14038
 Project: Jenkins
  Issue Type: Bug
  Components: core
Reporter: Nicolas De Loof
Assignee: Nicolas De Loof
Priority: Minor


When accessing a build using permalink (/lastSuccessful for sample), on 
sidepannel console or changes links have the expected /lastSuccessful/console 
URL, but other actions to contribute tasks use the actual build number.



--
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-14037) Apply Label before resynchronize workspace

2012-06-07 Thread cyril.j...@gemalto.com (JIRA)

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

Cyril Jean updated JENKINS-14037:
-

Description: 
Hello Cletus,

Here is the thing, today there is this great feature to be able to checkpoint 
before build, to be sure project is not altered between start and end of build.
MKS provides a keyword, $name$, that will be replaced with actual label applied 
to the checkpoint.
The problem now, is I cannot have this keyword replaced in the Jenkins build, 
because the label will only be applied at the end of the build.

So here is the request:
Can you add an option to apply label at the beginning of the build, same time 
you do the checkpoint.

Tks
cyril

Edit: If I may add, there is another point that could come handy, it's to be 
able to use the new checkpoint number you got when applying the checkpoint at 
beginning at the build.

Successfully executed pre-build checkpoint for project 
#/Perso_Infra#Workshop/Supervisions/SPS, new revision is 1.10

= the keyword would contain 1.10, and could be use in the tag for label 
application.
There may be a limitation if applying the label at same moment as the 
checkpoin...

  was:
Hello Cletus,

Here is the thing, today there is this great feature to be able to checkpoint 
before build, to be sure project is not altered between start and end of build.
MKS provides a keyword, $name$, that will be replaced with actual label applied 
to the checkpoint.
The problem now, is I cannot have this keyword replaced in the Jenkins build, 
because the label will only be applied at the end of the build.

So here is the request:
Can you add an option to apply label at the beginning of the build, same time 
you do the checkpoint.

Tks
cyril


 Apply Label before resynchronize workspace
 --

 Key: JENKINS-14037
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14037
 Project: Jenkins
  Issue Type: New Feature
  Components: integrity-plugin
Reporter: Cyril Jean
Assignee: Cletus D'Souza

 Hello Cletus,
 Here is the thing, today there is this great feature to be able to checkpoint 
 before build, to be sure project is not altered between start and end of 
 build.
 MKS provides a keyword, $name$, that will be replaced with actual label 
 applied to the checkpoint.
 The problem now, is I cannot have this keyword replaced in the Jenkins build, 
 because the label will only be applied at the end of the build.
 So here is the request:
 Can you add an option to apply label at the beginning of the build, same time 
 you do the checkpoint.
 Tks
 cyril
 Edit: If I may add, there is another point that could come handy, it's to be 
 able to use the new checkpoint number you got when applying the checkpoint at 
 beginning at the build.
 Successfully executed pre-build checkpoint for project 
 #/Perso_Infra#Workshop/Supervisions/SPS, new revision is 1.10
 = the keyword would contain 1.10, and could be use in the tag for label 
 application.
 There may be a limitation if applying the label at same moment as the 
 checkpoin...

--
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-14039) Scan-build can be used without xcode

2012-06-07 Thread sylves...@debian.org (JIRA)
Sylvestre Ledru created JENKINS-14039:
-

 Summary: Scan-build can be used without xcode
 Key: JENKINS-14039
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14039
 Project: Jenkins
  Issue Type: Improvement
  Components: clang-scanbuild
Reporter: Sylvestre Ledru
Assignee: Josh Kennedy
Priority: Minor


It would be nice if the clang-scanbuild plugin could be used outside of the 
XCode context. Indeed, scan-build can be used the following way:

scan-build ./configure
scan-build make

thanks


--
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-14038) Action tasks on build sidepannel don't use permalinks

2012-06-07 Thread scm_issue_l...@java.net (JIRA)

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

SCM/JIRA link daemon commented on JENKINS-14038:


Code changed in jenkins
User: Nicolas De Loof
Path:
 core/src/main/java/hudson/model/Run.java
http://jenkins-ci.org/commit/jenkins/a06acd9096ccab8e802389138fa52a9472359d1b
Log:
  [FIXED JENKINS-14038] consider requested context when building Run.url




 Action tasks on build sidepannel don't use permalinks
 -

 Key: JENKINS-14038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14038
 Project: Jenkins
  Issue Type: Bug
  Components: core
Reporter: Nicolas De Loof
Assignee: Nicolas De Loof
Priority: Minor

 When accessing a build using permalink (/lastSuccessful for sample), on 
 sidepannel console or changes links have the expected /lastSuccessful/console 
 URL, but other actions to contribute tasks use the actual build number.

--
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-14040) After the build I want to trigger two e-mails

2012-06-07 Thread artyukho...@gmail.com (JIRA)
vyacheslav artyukhov created JENKINS-14040:
--

 Summary: After the build I want to trigger two e-mails
 Key: JENKINS-14040
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14040
 Project: Jenkins
  Issue Type: Improvement
  Components: email-ext
Reporter: vyacheslav artyukhov
Assignee: Slide-O-Mix


After the build I want to trigger two e-mails. The first one is a mail to 
sharepoint server. Sharepoint uploads its attachements. The subject of this 
mail must matches sharepoint folder for uploading.

The second one is a mail for team. So, it should have nice subject rather than 
folder name :)

But now I can configure one Success trigger only. It would be nice if I can 
configure two or more Success triggers.

Is it possible to implement?


--
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-13835) upgrading Subversion Plugin to 1.40 totally ruined our CI server

2012-06-07 Thread panc...@java.net (JIRA)

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

pancake commented on JENKINS-13835:
---

*stephenconnolly*, E175002 doesn't seem to be related to server encoding issue. 
The bug occurred totally sporadically, i.e. didn't always reproduce for the 
same job (hence the same repo URL). In case that was caused by something wrong 
with repository, it should have been always reproducible for the same URL, 
right?

*Luca*, there is a workaround for not a working copy issue: go to Jenkins 
configuration and change WC format to 1.6. And E175002 never reproduced for me 
after downgrading 1.40 - 1.39.

 upgrading Subversion Plugin to 1.40 totally ruined our CI server
 

 Key: JENKINS-13835
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13835
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
 Environment: Jenkins ver. 1.460; Subversion Plugin ver. 1.40, 1.39; 
 Windows Server 2003 R2 x64 SP2; Subversion server ver. 1.6.16.
Reporter: pancake
  Labels: linux, plugin, subversion, windows

 Updating Subversion Plugin to 1.40 caused multiple bugs. Rolling back to 1.39 
 resulted to {color:red}complete inability to perform a checkout. CI server is 
 totally unusable now.{color}
 *Issue #1*
 After updating to Subversion Plugin to 1.40 (from 1.39) this exception 
 started occurring _sometimes_ (various salves, various jobs):
 {quote}
 Checking out a fresh workspace because there's no workspace at 
 C:\_JenkinsCI\workspace\XXX
 Cleaning local Directory .
 Checking out http://oursvnserver/svn/svnLatest/.../XXX
 A ...
 ERROR: Failed to check out http://oursvnserver/svn/svnLatest/.../XXX
 org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT 
 /svn/svnLatest/!svn/vcc/default failed
   at 
 org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304)
   at 
 org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289)
   at 
 org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277)
   at 
 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696)
   at 
 org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:328)
   at 
 org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289)
   at 
 org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:216)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:100)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:756)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)
   at 
 org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
   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:85)
   at 
 hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
   at 
 hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:152)
   at 
 hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
   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$FileCallableWrapper.call(FilePath.java:2154)
   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
   at hudson.remoting.Request$2.run(Request.java:287)
   at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 

[JIRA] (JENKINS-2792) Support for HTTP basic authentication on Jira server

2012-06-07 Thread pess...@seznam.cz (JIRA)

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

Peter Kolínek commented on JENKINS-2792:


I work in environment with multiple Jenkins servers and multiple JIRA systems 
with forced HTTP authentication. Support for HTTP authentication would help to 
use features of this plugin for many users. Thanks.

 Support for HTTP basic authentication on Jira server
 

 Key: JENKINS-2792
 URL: https://issues.jenkins-ci.org/browse/JENKINS-2792
 Project: Jenkins
  Issue Type: Improvement
  Components: jira
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: brandony

 Our Jira server is only accessible via https, and the webserver requires a
 username and a password to access the page.  When I enter the URL in the
 configuration path, I see Server returned HTTP response code: 401 for URL:.
 Could you please add support for HTTP authentication?

--
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-14041) Hide admin password

2012-06-07 Thread r...@orange.fr (JIRA)
Raphael CHAUMIER created JENKINS-14041:
--

 Summary: Hide admin password
 Key: JENKINS-14041
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14041
 Project: Jenkins
  Issue Type: Improvement
  Components: weblogic-deployer
Reporter: Raphael CHAUMIER
Assignee: Raphael CHAUMIER


The weblogic.Deployer API show the clear password on undeploy/deploy task.

--
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-14031) Anonymouse triggers 500 error

2012-06-07 Thread lshat...@java.net (JIRA)

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

Larry Shatzer, Jr. commented on JENKINS-14031:
--

In the stacktrace I see hudson.plugins.greenballs.GreenBallFilter.doFilter

Try removing the Green Balls plugin, and see if that fixes the problem. If so, 
then probably best to move this ticket to that plugin.

 Anonymouse triggers 500 error
 -

 Key: JENKINS-14031
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14031
 Project: Jenkins
  Issue Type: Bug
  Components: favorite
Reporter: Christian Höltje
Assignee: Larry Shatzer, Jr.

 I have the Role Strategy Plugin and Anonymous is configured with view 
 permissions. But it causes a 500 error when visiting the default page for 
 Jenkins (which I've configured to be Favorites)...
 Status Code: 500
 Exception: org.apache.commons.jelly.JellyTagException: 
 jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43:
  st:include Cannot invoke method isEmpty() on null object
 Stacktrace:
 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
 jar:file:/opt/local/stow/apache-tomcat-7.0.6/share/apache-tomcat-7.0.6/webapps/automan/WEB-INF/lib/jenkins-core-1.467.jar!/hudson/model/View/index.jelly:44:43:
  st:include Cannot invoke method isEmpty() on null object
   at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
   at 
 org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
   at 
 hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
   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 
 

[JIRA] (JENKINS-11814) Maven artifact fingerprints are computed and recorded twice

2012-06-07 Thread ku...@gmx.de (JIRA)

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

kutzi reassigned JENKINS-11814:
---

Assignee: kutzi

 Maven artifact fingerprints are computed and recorded twice
 ---

 Key: JENKINS-11814
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11814
 Project: Jenkins
  Issue Type: Improvement
  Components: maven2
Reporter: kutzi
Assignee: kutzi
Priority: Minor

 The artifacts which are produced by a maven job have their artifacts 
 fingerprinted twice. Once in MavenFingerprinter and once in 
 MavenArtifactArchiver (*). This adds unnecessary overhead to maven jobs.
 Proposal: as fingerprints are needed in the MavenArtifact records generated 
 in the MavenArtifactArchiver, it probably doesn't make much sense to remove 
 the fingerprinting from there. Instead, I'd propose to fingerprint all 'used' 
 artifacts in the MavenFingerprinter and all 'produced' artifacts in the 
 MavenArtifactArchiver
 *) Note that fingerprints are even generated in MavenArtifactArchiver if 
 automatic artifact archiving is disabled

--
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-14035) Responsive design

2012-06-07 Thread scm_issue_l...@java.net (JIRA)

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

SCM/JIRA link daemon commented on JENKINS-14035:


Code changed in jenkins
User: OHTAKE Tomohiro
Path:
 core/src/main/resources/lib/layout/layout.jelly
 war/src/main/webapp/less/jenkins.less
http://jenkins-ci.org/commit/jenkins/1c0f91af280adab783d7e5e39ae999ada9fa6b1d
Log:
  [JENKINS-14035] Adjust responsive layout






 Responsive design
 -

 Key: JENKINS-14035
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14035
 Project: Jenkins
  Issue Type: New Feature
  Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro

 Make Web UI responsive for better experience with smartphones.
 {noformat:title=Desktops (current design)}
 +---+
 |Top Bar|
 +---+
 |Breadcrumbs|
 +-+-+
 |side-| main-panel  |
 |panel| |
 | | |
 +-+-+
 |Footer |
 +---+
 {noformat}
 {noformat:title=Smartphones}
 +---+
 |Top bar|
 +---+
 |Breadcrumbs|
 +---+
 |side-panel |
 |(togglable)|
 +---+
 |main-panel |
 |   |
 |   |
 +---+
 |Footer |
 +---+
 {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-14044) System Groovy - Unable to cast to AbstractBuild

2012-06-07 Thread aferr...@paychex.com (JIRA)
Anthony Ferrari created JENKINS-14044:
-

 Summary: System Groovy - Unable to cast to AbstractBuild
 Key: JENKINS-14044
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14044
 Project: Jenkins
  Issue Type: Bug
  Components: groovy, plugin
Affects Versions: current
 Environment: Windows, 
Jenkins ver. 1.447.1, 
Groovy Plugin 1.8 OR Groovy Plugin 1.12
Reporter: Anthony Ferrari
Assignee: vjuranek


We just upgraded our Jenkins version from 1.424.6 1.447.1.

After the upgrade, all system groovy scripts that contained the following line 
stopped working:
AbstractBuild g_currentBuild = (AbstractBuild)Thread.currentThread().executable;

When this line in the script is executed, the following stacktrace was 
generated:
FATAL: null
java.lang.StackOverflowError
at org.codehaus.groovy.ast.ClassNode.redirect(ClassNode.java:178)
at org.codehaus.groovy.ast.ClassNode.equals(ClassNode.java:677)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1149)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
at 
org.codehaus.groovy.ast.ClassNode.genericTypeAsString(ClassNode.java:1152)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1127)
at org.codehaus.groovy.ast.ClassNode.toString(ClassNode.java:1132)
[...repeats until stack overflow.]

We upgraded our Groovy plugin to the latest version (1.12) with the same result.

We rolled back to Jenkins 1.424.6 and we do not see the error there.

--
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-14043) Javac warnings false positive from unit test log

2012-06-07 Thread sylvain.vey...@keyconsulting.fr (JIRA)
Sylvain Veyrié created JENKINS-14043:


 Summary: Javac warnings false positive from unit test log
 Key: JENKINS-14043
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14043
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
Reporter: Sylvain Veyrié
Assignee: Ulli Hafner
Priority: Minor


Some logs from unit test execution are wrongly taken by the Warnings Plugin as 
javac compiler warnings. Those (French) logs are from the app itself.

Two examples from Details tab

{noformat}
10:53:05,516 [INFO] - 
info.XXX.YYY.persistence.entity.scenario.RemplaceAffectation : 
_doProjette(this: RemplaceAffectation {id: 1, ligne:Ligne {nom: 
Ligne 2}, entite:Concept {id:2, nom:p2, generalisation:, specialisations:[], 
prototypes:[], constituants:[], caracteristiques:[], affectations:[]}, 
quantite:4}, pivot: Concept {id:2, nom:p2, generalisation:, specialisations:[], 
prototypes:[], constituants:[], caracteristiques:[], affectations, Java 
Compiler (javac), Priority: Normale 

}, projection: ConceptDto {id:2, nom:p2, caracteristiques: {}, affectations: 
{}}, date: 05/01/2012)


10:53:07,084 [ERROR] - info.XXX.YYY.service.entite.EntiteService : On trouve 
plusieurs resultats pour findByField(fieldName:nom, value:aa, klass:class 
info.stif.mr1.persistence.entity.entite.Entite): results=[Modele {id:101, nom: 
aa, generalisation:, specialisations:[], archetype:1, prototypes:[201], 
constituants:[], caracteristiques:[]}, Modele {id:102, nom: aa, 
generalisation:, specialisations:[], archetype:2, prototypes:[], 
constituants:[], caracteristiques:[]}, Concept {id:1, nom:aa, generalisation:, 
specialisations:[], prototypes:[101], constituants:[], caracteristiques:[], 
affectations:[]}, Concept {id:2, nom:aa, generalisation:, specialisations:[], 
prototypes:[102], constituants:[], caracteristiques:[], affectations, Java 
Compiler (javac), Priority: Normale

}, info.stif.mr1.persistence.entity.entite.ObjetConcret@2a6cd712]
{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-13863) MSBuild is unable to build projects in a different directory

2012-06-07 Thread dartm...@gmail.com (JIRA)

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

Aaron Laws commented on JENKINS-13863:
--

There we go! Just change the documentation to make the implementation correct!  
Although the documentation is still probably lacking a bit.  Perhaps 

{panel:title=| borderStyle = dashed}This is the absolute path to the project 
file MSBuild will use.  Alternatively, if the project file is in the root 
directory of the project's workspace, simply the name of the project file will 
suffice.{panel}

Can someone give me directions on compiling the {{MSBuild Plugin}} and testing 
it locally?  I would be happy to give this a whack.  It seems like it should be 
simple.  Most frameworks can resolve relative paths.

 MSBuild is unable to build projects in a different directory
 

 Key: JENKINS-13863
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13863
 Project: Jenkins
  Issue Type: Bug
  Components: msbuild
Affects Versions: current
 Environment: MS Windows Server 2008
Reporter: Aaron Laws
Assignee: kdsweeney
Priority: Minor
  Labels: path, plugin
 Attachments: badbuild.txt, badconfig.PNG, betterbuild.txt, 
 goodbuild.txt, goodconfig.PNG


 I use SVN to checkout a project to {{.\proj\}}  and a dependency to 
 {{.\dep\}}.  The {{.sln}} file is at {{.\proj\proj.sln}}.  I us the MsBuild 
 plugin with the setting MsBuild Build File = {{proj\proj.sln}} (or a 
 number of variants such as {{.\proj\proj.sln}}). Msbuild fails with 
 {{MSB1009: Project file does not exist.}} However, running a similar command 
 manually succeeds.

--
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-06-07 Thread ah...@hotmail.com (JIRA)

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

Amir Isfy commented on JENKINS-13227:
-

Michael,

I am using the snapshot from build 21. The 'Use Head If Not Found' seems to be 
broken. Even though it is checked, it tried to get that branch of the module 
which does not exist, therefore that module does not get checkout at all and I 
end up with an empty folder.

 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-14040) After the build I want to trigger two e-mails

2012-06-07 Thread slide.o....@gmail.com (JIRA)

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

Slide-O-Mix commented on JENKINS-14040:
---

This is currently not possible. It would take a bit of rework to be able to do 
this.

 After the build I want to trigger two e-mails
 -

 Key: JENKINS-14040
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14040
 Project: Jenkins
  Issue Type: Improvement
  Components: email-ext
Reporter: vyacheslav artyukhov
Assignee: Slide-O-Mix
  Labels: email-ext, plugin, trigger

 After the build I want to trigger two e-mails. The first one is a mail to 
 sharepoint server. Sharepoint uploads its attachements. The subject of this 
 mail must matches sharepoint folder for uploading.
 The second one is a mail for team. So, it should have nice subject rather 
 than folder name :)
 But now I can configure one Success trigger only. It would be nice if I can 
 configure two or more Success triggers.
 Is it possible to implement?

--
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-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations

2012-06-07 Thread jos...@azariah.com (JIRA)

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

Joshua Kugler commented on JENKINS-13554:
-

After disabling the promoted builds plugin, and cleaning up all the abandoned 
builds, it *seems* we no longer have this issue.

 Re: Matrix jobs does not automatically remove old artifacts for configurations
 --

 Key: JENKINS-13554
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13554
 Project: Jenkins
  Issue Type: Bug
  Components: matrix
Affects Versions: current
Reporter: stibbons
Assignee: vjuranek
Priority: Critical

 Hello
 I'm reporting an important issue on Jenkins with matrix build. The 'Discard 
 Old Builds' setting doesn't remove builds in configuration, leading to 
 increase disk usage without limit.
 Here is the behavior :
 - the master job is correctly cleaned, for instance, after a month if 
 configured so, the artifacts are dropped and the build are correctly deleted
 - however this is not the case for the configuration builds, if i go into the 
 page of one I can see a very long list of builds not having been deleted (so 
 this is not synchronized with the 'master'). 
 The files in
   ~/jenkins/jobs/MyJobName/configurations/axis-FOO/foo/axis-BAR/bar/builds
 are no deleted while
   ~/jenkins/jobs/MyJobName/builds/
 are correctly deleted.
 Also, disk usage is not correctly computed in the disk usage space : the size 
 of the configuration are not taken in account.
 This leads on my build machine a complete saturation of the disks after 1 
 week of work. I think this is a very critical issue.
 Thanks,
 Gaetan

--
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-14050) Unreadable HTML response

2012-06-07 Thread jhans...@myyearbook.com (JIRA)

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

Joe Hansche commented on JENKINS-14050:
---

Update:  In Firefox, if I go to about:config, and look for 
network.http.accept-encoding, and remove gzip from that field (so it says 
only deflate), it works okay in Firefox.  But can't seem to figure out how to 
disable gzip compression in Chrome.  Keeping this open anyway, because I think 
there's still a bug here.  I've been able to receive gzip encoding in the past, 
and it occurs in multiple browsers, so I do not believe this is a bug in my 
desktop.

 Unreadable HTML response
 

 Key: JENKINS-14050
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14050
 Project: Jenkins
  Issue Type: Bug
  Components: monitoring
 Environment: Jenkins v1.467
 CentOS 5.3 master, 16GB RAM, 8 cores
 2 CentOS 5.3 slaves
 2 Mac Mini slaves
Reporter: Joe Hansche
 Attachments: Screen Shot 2012-06-07 at 1.08.17 PM.png


 After installing the Monitoring plugin (choosing the Install without 
 Restart button), then navigating to http://jenkins/monitoring/, the response 
 I get is binary gibberish.  The page is served with Content-type: 
 text/html, but what it is outputting is clearly not HTML.  The same also 
 happens at http://jenkins/monitoring/nodes/
 Here is a sample request to /monitoring:
 {noformat}
 GET /monitoring HTTP/1.1
 Host: jenkins.company.com
 Connection: keep-alive
 Cache-Control: max-age=0
 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 
 (KHTML, like Gecko) Chrome/19.0.1084.54 Safari/536.5
 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
 Accept-Encoding: gzip,deflate,sdch
 Accept-Language: en-US,en;q=0.8
 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
 Cookie: JSESSIONID.xx=xx; screenResolution=2560x1440
 {noformat}
 {noformat}
 HTTP/1.1 200 OK
 Transfer-Encoding: chunked
 Server: Winstone Servlet Engine v0.9.10
 Cache-Control: no-cache
 Pragma: no-cache
 Expires: -1
 Content-Type: text/html;charset=UTF-8
 Content-Encoding: gzip
 Vary: Accept-Encoding
 Date: Thu, 07 Jun 2012 17:13:45 GMT
 X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
 ...
 {noformat}
 Based on the response headers, I see Content-encoding: gzip, which leads me 
 to believe that it is compressing the output, but my browser is not decoding 
 the response.  The same problem occurs in both Chrome 19.0, and Firefox 13.0.

--
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-13202) Artifact archiving from an ssh slave fails if symlinks are present

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

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

dogfood commented on JENKINS-13202:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-13202] Don't set mtime or mode on symlinks (Revision 
e15b2e19e394f5d63183f01a2e72a14115a0c370)
[FIXED JENKINS-13202] fixed a regression in untar on exotic platforms. 
(Revision 95c1728c05b11a55e72c8ed8240d2852528ea1db)

 Result = SUCCESS
Kohsuke Kawaguchi : 
[e15b2e19e394f5d63183f01a2e72a14115a0c370|https://github.com/jenkinsci/jenkins/commit/e15b2e19e394f5d63183f01a2e72a14115a0c370]
Files : 
* core/src/main/java/hudson/FilePath.java
* changelog.html
* core/src/test/java/hudson/FilePathTest.java

Kohsuke Kawaguchi : 
[95c1728c05b11a55e72c8ed8240d2852528ea1db|https://github.com/jenkinsci/jenkins/commit/95c1728c05b11a55e72c8ed8240d2852528ea1db]
Files : 
* core/src/main/java/hudson/util/DirScanner.java
* core/src/main/java/hudson/os/PosixAPI.java
* changelog.html


 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-13822) Maven plugin: expand variables in Room POM field

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

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

dogfood commented on JENKINS-13822:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 Fixes JENKINS-13822: expand variables in Root POM field of Maven plugin 
(Revision 4e8775fc2c53a4fe4409a8b79c3bdd7eaa0274c0)
changelog entry for [JENKINS-13822] (Revision 
25b694351f68076129734604dd270ae48f31b020)

 Result = SUCCESS
ian.kemp : 
[4e8775fc2c53a4fe4409a8b79c3bdd7eaa0274c0|https://github.com/jenkinsci/jenkins/commit/4e8775fc2c53a4fe4409a8b79c3bdd7eaa0274c0]
Files : 
* maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
* maven-plugin/src/main/java/hudson/maven/MavenModuleSet.java

Olivier Lamy : 
[25b694351f68076129734604dd270ae48f31b020|https://github.com/jenkinsci/jenkins/commit/25b694351f68076129734604dd270ae48f31b020]
Files : 
* changelog.html


 Maven plugin: expand variables in Room POM field
 --

 Key: JENKINS-13822
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13822
 Project: Jenkins
  Issue Type: Improvement
  Components: maven
Reporter: Ian Kemp
Assignee: Kohsuke Kawaguchi
Priority: Trivial

 The Root POM field in the maven-plugin does not expand build/environment 
 variables. I have made a code change to allow this and will commit + push+ 
 send a pull request as soon as it's checked in.
 I have a question about the maven-plugin though - why is it integrated into 
 the Jenkins core and not in its own separate repository?

--
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-12854) Large Artifacts can not be downloaded over WebInterface

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

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

dogfood commented on JENKINS-12854:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-13496 JENKINS-12854] Integrated the newer version of 
Winstone. (Revision e6a8d5e6449161a954dfe9998763906923555650)

 Result = SUCCESS
Kohsuke Kawaguchi : 
[e6a8d5e6449161a954dfe9998763906923555650|https://github.com/jenkinsci/jenkins/commit/e6a8d5e6449161a954dfe9998763906923555650]
Files : 
* war/pom.xml
* changelog.html


 Large Artifacts can not be downloaded over WebInterface
 ---

 Key: JENKINS-12854
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12854
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Server: Win XP SP3 32-Bit
Jenkins 1.451
 Client: Win XP SP3 32- Bit
   Browser: Firefox 10.0.2
Reporter: Andre Gross
Assignee: Andre Gross
 Fix For: current

 Attachments: jenkins.err.log


 I create an ISO which is around 3GB. When I try to access it through the web 
 interface I get the following error in FireFox:
 Die Dateien unter 
 http://wxde423hc4jw:8080/job/600_CreateSoMachineISO/lastSuccessfulBuild/artifact/SoMachine-3.1.1-12.02.22.03.iso
  konnten nicht gefunden werden.
 It says something like File not found. 
 I also attached the jenkins error log which shows an exception.

--
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-13429) Nested views not showing up with just read perms for View

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

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

dogfood commented on JENKINS-13429:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-13429] (Revision d1b2ba7e4988d26fbb815b8912efb16273c407d4)

 Result = SUCCESS
Kohsuke Kawaguchi : 
[d1b2ba7e4988d26fbb815b8912efb16273c407d4|https://github.com/jenkinsci/jenkins/commit/d1b2ba7e4988d26fbb815b8912efb16273c407d4]
Files : 
* core/src/main/java/hudson/security/AuthorizationStrategy.java
* changelog.html


 Nested views not showing up with just read perms for View
 -

 Key: JENKINS-13429
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13429
 Project: Jenkins
  Issue Type: Bug
  Components: nested-view
Affects Versions: current
Reporter: M S
Assignee: Kohsuke Kawaguchi
  Labels: jenkins, plugin, views

 Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy 
 1.1.2
 User has read permissions for View but Jenkins main page is missing Nested 
 views (even if they have sub views with jobs).
 Adding configure perms for View results in Nested views showing up 
 correctly.
 It looks like it's connected with:
 Added the View.READ permission to control visibility of views, and updated 
 the default implementation to hide empty views. (issue 3681)

--
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-13625) ERR_CONTENT_DECODING_FAILED returned on testResults and console output after Jenkins reload

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

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

dogfood commented on JENKINS-13625:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-13625] (Revision 18963ee9af2b98ce94eda799069d9135f6031a0e)

 Result = SUCCESS
Kohsuke Kawaguchi : 
[18963ee9af2b98ce94eda799069d9135f6031a0e|https://github.com/jenkinsci/jenkins/commit/18963ee9af2b98ce94eda799069d9135f6031a0e]
Files : 
* core/src/main/java/hudson/security/HudsonAuthenticationEntryPoint.java
* war/src/main/webapp/WEB-INF/web.xml
* core/src/main/java/jenkins/model/Jenkins.java
* core/pom.xml


 ERR_CONTENT_DECODING_FAILED returned on testResults and console output after 
 Jenkins reload
 ---

 Key: JENKINS-13625
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13625
 Project: Jenkins
  Issue Type: Bug
  Components: core, matrix, swarm
Affects Versions: current
Reporter: Anders Nickelsen
Assignee: Kohsuke Kawaguchi
Priority: Critical

 We have matrix configuration job that has a 'slave' axis to distribute tests 
 on Jenkins swarm slaves.
 When we 'reload configuration from disk' Jenkins all builds in the history of 
 the matrix job return ERR_CONTENT_DECODING_FAILED (HTTP error 330) when we 
 request console output for any slave on the axis. This also occurs when 
 requesting testresults (we record jUnit test results as a part of the build).
 We had issues with Jenkins losing references to slave after reload, which 
 were solved by https://issues.jenkins-ci.org/browse/JENKINS-8043, and I think 
 this bug is related.
 When the error occurs the following stack trace is observed in Jenkins' log:
 27-Apr-2012 08:26:50 winstone.Logger logInternal
 WARNING: Untrapped Error in Servlet
 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.461.jar!/hudson/tasks/test/MatrixTestResult/index.jelly:42:60:
  j:forEach java.lang.NullPointerException
   at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112)
   at 
 org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:162)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
   at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
   at 
 hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
   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 
 

[JIRA] (JENKINS-13378) XML API Logs Too Much Information When Invalid Char is Present

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

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

dogfood commented on JENKINS-13378:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-13378] Remove XML string writer from IOException2 when 
XPath error occurs. (Revision 668a0cc4dc786dc1b6a726b17db74e9974afa82a)
[JENKINS-13378] Add FINER logging of XML when XPath handling fails. (Revision 
e1a1d3f098d938fb9c4690cd283653a91a496ae6)
[JENKINS-13378] Update changelog.html with fix. (Revision 
752a7c7b8bd357f2962c0b361eef465b1fd1c83f)

 Result = SUCCESS
thomas.vandoren : 
[668a0cc4dc786dc1b6a726b17db74e9974afa82a|https://github.com/jenkinsci/jenkins/commit/668a0cc4dc786dc1b6a726b17db74e9974afa82a]
Files : 
* core/src/main/java/hudson/model/Api.java

thomas.vandoren : 
[e1a1d3f098d938fb9c4690cd283653a91a496ae6|https://github.com/jenkinsci/jenkins/commit/e1a1d3f098d938fb9c4690cd283653a91a496ae6]
Files : 
* core/src/main/java/hudson/model/Api.java

thomas.vandoren : 
[752a7c7b8bd357f2962c0b361eef465b1fd1c83f|https://github.com/jenkinsci/jenkins/commit/752a7c7b8bd357f2962c0b361eef465b1fd1c83f]
Files : 
* changelog.html


 XML API Logs Too Much Information When Invalid Char is Present
 --

 Key: JENKINS-13378
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13378
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: Thomas Van Doren
Assignee: Thomas Van Doren
  Labels: api, exception, jenkins

 When an XPath error occurs when calling the /api/xml API, the entire xml 
 string writer object is included as part of the exception. While this could 
 be useful in some circumstances, it poses a problem when there is a 
 significant amount of xml (i.e. tens or hundreds of megabytes).
 Recently I saw this in my jenkins installation. One of the chrome extensions 
 calls /api/xml?depth=2xpath=/*/job/lastBuildwrapper=hudson to get 
 information every minute or two. I was seeing 150MB of log data every time 
 that call was made because there was a stack trace followed by:
 Caused by: hudson.util.IOException2: Failed to do XPath/wrapper handling. XML 
 is as 
 follows:hudsonassignedLabelbusyExecutors0/busyExecutorsdescription...
  [150MB of xml]/hudson
 at hudson.model.Api.doXml(Api.java:142)
 ... 63 more
 Caused by: org.dom4j.DocumentException: Error on line 2170 of document  : An 
 invalid XML character (Unicode: 0x10) was found in the element content of the 
 document. Nested exception: An invalid XML character (Unicode: 0x10) was 
 found in the element content of the document.
 at org.dom4j.io.SAXReader.read(SAXReader.java:482)
 at org.dom4j.io.SAXReader.read(SAXReader.java:365)
 at hudson.model.Api.doXml(Api.java:100)
 ... 63 more
 Caused by: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 
 0x10) was found in the element content of the document.
 at 
 com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
 at 
 com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2894)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
 at 
 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
 at 
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
 at 
 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
 at 
 com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
 at 
 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
 at 
 com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
 at org.dom4j.io.SAXReader.read(SAXReader.java:465)
 ... 65 more
 It didn't take very long for the log file to consume all of the available 
 disk space on the 

[JIRA] (JENKINS-14038) Action tasks on build sidepannel don't use permalinks

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

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

dogfood commented on JENKINS-14038:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[jenkins_ui-changes_branch 
#30|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/30/]
 [FIXED JENKINS-14038] consider requested context when building Run.url 
(Revision a06acd9096ccab8e802389138fa52a9472359d1b)

 Result = SUCCESS
Nicolas De Loof : 
[a06acd9096ccab8e802389138fa52a9472359d1b|https://github.com/jenkinsci/jenkins/commit/a06acd9096ccab8e802389138fa52a9472359d1b]
Files : 
* core/src/main/java/hudson/model/Run.java


 Action tasks on build sidepannel don't use permalinks
 -

 Key: JENKINS-14038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14038
 Project: Jenkins
  Issue Type: Bug
  Components: core
Reporter: Nicolas De Loof
Assignee: Nicolas De Loof
Priority: Minor

 When accessing a build using permalink (/lastSuccessful for sample), on 
 sidepannel console or changes links have the expected /lastSuccessful/console 
 URL, but other actions to contribute tasks use the actual build number.

--
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-10835) Add support for JaCoCo coverage results

2012-06-07 Thread jhespin...@gmail.com (JIRA)

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

Jose Espinosa commented on JENKINS-10835:
-

Have anybody run the jacoco_to_emma.xslt file on maven?

When I run it I get the following error:
{code}
[INFO] --- xml-maven-plugin:1.0:transform (default) @ my-app ---
ERROR:  'Error checking type of the expression 'funcall(replace, 
[step(attribute, 22), literal-expr(/), literal-expr(.)])'.'
FATAL ERROR:  'Could not compile stylesheet'
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 19.400s
[INFO] Finished at: Thu Jun 07 17:04:31 PDT 2012
[INFO] Final Memory: 20M/81M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:xml-maven-plugin:1.0:transform 
(default) on project my-app: Failed to parse stylesheet 
javax.xml.transform.sax.SAXSource@233aa44: Could not compile stylesheet - 
[Help 1]
{code}

Any pointers? Thanks!

 Add support for JaCoCo coverage results
 ---

 Key: JENKINS-10835
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10835
 Project: Jenkins
  Issue Type: New Feature
  Components: emma
Reporter: Daniel Hirscher
Assignee: Kohsuke Kawaguchi
 Attachments: jacoco_to_emma.xslt


 JaCoCo is the successor of emma.
 Maybe it is possible to support the new coverage file format.

--
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-6256) Builds are listed under the wrong job

2012-06-07 Thread patrick.lemm...@thalesgroup.com.au (JIRA)

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

Patrick Lemmens commented on JENKINS-6256:
--

We have experienced the same issue and this has been corrupting our build 
history for quite some time... :-(

We also have experienced very strange symptoms because of this when the build 
number in a wrongly filed build folder was higher than the highest build number 
of the job; the workspace would either appear empty or it would show the 
workspace of the other job... Then CVS polling would go haywire and decide the 
job needed rebuilding as the workspace would be empty or contain the wrong 
code...

Only just found this bug report. Can it please be assigned to someone and fixed 
with high priority?

We are still on Hudson 1.395 and hope to move to Jenkins 1.447.1 LTS soon.

 Builds are listed under the wrong job
 -

 Key: JENKINS-6256
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6256
 Project: Jenkins
  Issue Type: Bug
  Components: downstream-buildview
 Environment: Hudson 1.354 (?)
Reporter: torbent
Priority: Critical

 This started over in JENKINS-6254, but I think it's not limited to Perforce, 
 so I'm submitting this in Core.
 Today, after upgrading to 1.354, I'm seeing cases where builds move from 
 their job into other jobs instead. In JENKINS-6254 I note one case where two 
 builds (412+413) from one job move to another job, and possibly cause the 
 Perforce plugin to get very confused about where to build.
 Earlier I had two jobs where 3 builds from each had switched sides and now 
 were listed as belonging to the other job.
 The switching was complete in the sense that the build directories on the 
 Hudson server were in the wrong places. I stopped the service and moved the 
 directories around, and they looked fine again.
 One of the those jobs consistently failed like this:
 {noformat}
 FATAL: null
 java.lang.NullPointerException
   at hudson.tasks.ArtifactArchiver.prebuild(ArtifactArchiver.java:147)
   at 
 hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:595)
   at 
 hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:590)
   at 
 hudson.model.AbstractBuild$AbstractRunner.preBuild(AbstractBuild.java:586)
   at hudson.model.Build$RunnerImpl.doRun(Build.java:114)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
   at hudson.model.Run.run(Run.java:1244)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:122)
 {noformat}
 I'm not really keen on going through all our jobs to scan for switched 
 builds, so I'll likely have to downgrade to 1.353.
 A curious thing, though, is that all of the switched jobs (so far) took place 
 April 7th (a week ago). We were not running 1.354 then, but I didn't see the 
 problems that I do now, so I'm mostly inclined to believe that it's something 
 to do with 1.354.
 After downgrading, I cannot really be of much help as we don't have a 
 testing server (but I'm beginning to think we should).

--
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-9091) NUnit plugin chokes on report xml

2012-06-07 Thread rahul_shela...@yahoo.com (JIRA)

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

Rahul Shelar updated JENKINS-9091:
--


This was caused because I was not deploying the files correctly. It is resolved 
now. Thanks.

 NUnit plugin chokes on report xml
 -

 Key: JENKINS-9091
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9091
 Project: Jenkins
  Issue Type: Bug
  Components: nunit
Affects Versions: current
 Environment: NUnit 2.5.7.10213
 Jenkins 1.401
 NUnit Plugin version 0.13
Reporter: Glenn Goodrich
Assignee: Rahul Shelar
 Attachments: TestResult.xml


 NUnit plugin chokes on the report xml with the following error:
 ERROR: Publisher hudson.plugins.nunit.NUnitPublisher aborted due to exception
 hudson.util.IOException2: Could not transform the NUnit report. Please report 
 this issue to the plugin author
   at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:60)
   at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26)
   at hudson.FilePath.act(FilePath.java:757)
   at hudson.FilePath.act(FilePath.java:739)
   at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:644)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:623)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:601)
   at hudson.model.Build$RunnerImpl.post2(Build.java:159)
   at 
 hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:570)
   at hudson.model.Run.run(Run.java:1386)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:145)
 Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
   at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown 
 Source)
   at 
 com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown 
 Source)
   at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
   at 
 hudson.plugins.nunit.NUnitReportTransformer.splitJUnitFile(NUnitReportTransformer.java:100)
   at 
 hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:71)
   at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55)
   ... 14 more

--
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-14055) Nunit plugin misses some test cases

2012-06-07 Thread rahul_shela...@yahoo.com (JIRA)
Rahul Shelar created JENKINS-14055:
--

 Summary: Nunit plugin misses some test cases
 Key: JENKINS-14055
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14055
 Project: Jenkins
  Issue Type: Bug
  Components: nunit
Affects Versions: current
Reporter: Rahul Shelar
Assignee: Rahul Shelar


I noticed that Nunit plugin (that generates test report from results files) 
misses some test cases. I see the test cases in results.xml file but it is not 
logged in the report. This happens with only passed test cases.

Is this a known issue? Could it be because the structure of test-case node of 
these skipped test cases is missing some attribute?

Thanks,
Rahul.

--
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