date:20120406

Piotr Czachur created JENKINS-13370:
---

 Summary: Logout when trying to set Show only n last builds on 
Filter trend data page
 Key: JENKINS-13370
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13370
 Project: Jenkins
  Issue Type: Bug
  Components: performance-plugin
Affects Versions: current
 Environment: Ubuntu 11.00 Oneiric 64bit
OpenJDK 1.7
Reporter: Piotr Czachur
Assignee: Manuel Carrasco
Priority: Critical


Hi!

Before I will run into details I just want to say this issue can be a blocker 
for using performance plugin. If you got hundreds of builds and you cannot make 
Jenkins to generate trend report for only last N builds you wait hours for 
images to appear.

OK, here are details: 

When I'm trying to set only n last builds value on Filter trend data page, 
I get immediately logged out.
I've looked into the cookie set by this action and it looks like this:
===
Name: hudson.plugins.performance
Content: BUILD
Path: /jenkins/job/mytestjob
===


There are two side effects here:

1) Setting limit for n last build simply doesn't work


2) After pressing Save button I'm getting immediately logged out and - later 
- when I try to access build page  (mytestjob) I'm also getting logged out. 
Other jobs' pages work fine. I suspect this has something to do with content of 
the cookie sent to the server:

# cookie sent after setting n last builds limit
Cookie: hudson.plugins.performance=BUILD; screenResolution=1920x1080; 
JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF

# cookie sent by Jenkins in normal conditions (no performance plugin cookie)
Cookie: screenResolution=1920x1080; JSESSIONID=C3EDF6F50798299F696D9387DFC6CBEF


Cheers!



--
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-13371) Wrong URL on WIKI for perfformance-plugin bug list.

Piotr Czachur created JENKINS-13371:
---

 Summary: Wrong URL on WIKI for perfformance-plugin bug list.
 Key: JENKINS-13371
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13371
 Project: Jenkins
  Issue Type: Bug
  Components: performance-plugin
Reporter: Piotr Czachur
Assignee: Manuel Carrasco


On Performance Plugin WIKI page 
(https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin) where is URL 
for Open Issues:
http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hidereset=truejqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance%27

but should be:
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hidereset=truejqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance-plugin%27

Please update WIKI page.


Cheers!

--
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-13372) Add process last N builds for trend in jenkins configuration.

Piotr Czachur created JENKINS-13372:
---

 Summary: Add process last N builds for trend  in jenkins 
configuration.
 Key: JENKINS-13372
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13372
 Project: Jenkins
  Issue Type: Bug
  Components: performance-plugin
Affects Versions: current
 Environment: Performance Plugin 1.7
Reporter: Piotr Czachur
Assignee: Manuel Carrasco


Generating trend graphs in case there are hundreds of builds is very resource 
intensive task. Currently there is an option for setting this limit in browser 
cookie (btw I have just filled issue - it doesn't work) but before user set it 
to explicit value, all available builds are taken into consideration. This can 
be very bad and block Jenkins from responding because it's crazy busy parsing 
gigs of data.
Cookie has also important disadventage: can expire, be cleared and is attached 
to one browser. If user logs in from another location limit setting is lost.

My proposition is to add this limit to Jenkins Configure System page just 
like it's done for many popular plugins.

Cheers!

--
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-13372) Add process last N builds for trend to Configure System Jenkns page.

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

Piotr Czachur updated JENKINS-13372:

Summary: Add process last N builds for trend to Configure System
Jenkns page. (was: Add process last N builds for trend in jenkins
configuration.)

Add process last N builds for trend to Configure System Jenkns page.
-

Key: JENKINS-13372
URL: https://issues.jenkins-ci.org/browse/JENKINS-13372
Project: Jenkins
Issue Type: Bug
Components: performance-plugin
Affects Versions: current
Environment: Performance Plugin 1.7
Reporter: Piotr Czachur
Assignee: Manuel Carrasco

Generating trend graphs in case there are hundreds of builds is very resource
intensive task. Currently there is an option for setting this limit in
browser cookie (btw I have just filled issue - it doesn't work) but before
user set it to explicit value, all available builds are taken into
consideration. This can be very bad and block Jenkins from responding because
it's crazy busy parsing gigs of data.
Cookie has also important disadventage: can expire, be cleared and is
attached to one browser. If user logs in from another location limit setting
is lost.
My proposition is to add this limit to Jenkins Configure System page just
like it's done for many popular plugins.
Cheers!

[JIRA] (JENKINS-13369) Lost 'Managed script file' section and all saved scripts after Jenkins upgrade

2012-04-06 Thread salm...@mail.com (JIRA)

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

Tetiana Tvardovska updated JENKINS-13369:
-

Description:
The section Managed script file - create a managed/reusable script) had
disappeared with all saved scripts after Jenkins upgrade to ver. 1.458.
See attached screenshot, right site 'ci:8080'
It happened after upgrading a headless system using option 'Upgrade
Automatically'.

Jenkins ver. 1.458.
[Managed
Scripts|https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin]
version 0.2.0

Bug is related to the [Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
version 2.0.

PS Other installation (localhost on the attached screenshot) on Ubuntu system
had not lost scripts and still shows all scripts and saved scripts. It has
[Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
older version 1.2.

was:
The section Managed script file - create a managed/reusable script) had
disappeared with all saved scripts after Jenkins upgrade to ver. 1.458.
See attached screenshot, right site 'ci:8080'
It happened after upgrading a headless system using option 'Upgrade
Automatically'.

Jenkins ver. 1.458.
Managed Scripts version 0.2.0

PS Other installation (localhost on the attached screenshot) on Ubuntu system
had not lost scripts and still shows all scripts and saved scripts. Used type
of installation - via 'Upgrade system'.

Component/s: config-file-provider

Bug looks related to the [Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]:

Failure 'ci' system has [Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
version 2.0
Good 'local' system has [Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
version 1.2

Lost 'Managed script file' section and all saved scripts after Jenkins upgrade
--

Key: JENKINS-13369
URL: https://issues.jenkins-ci.org/browse/JENKINS-13369
Project: Jenkins
Issue Type: Bug
Components: config-file-provider, managed-scripts
Affects Versions: current
Reporter: Tetiana Tvardovska
Assignee: domi
Priority: Critical
Attachments: configfiles_ci_localhost.JPG,
configfiles_ci_localhost_inspection.JPG

The section Managed script file - create a managed/reusable script) had
disappeared with all saved scripts after Jenkins upgrade to ver. 1.458.
See attached screenshot, right site 'ci:8080'
It happened after upgrading a headless system using option 'Upgrade
Automatically'.
Jenkins ver. 1.458.
[Managed
Scripts|https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin]
version 0.2.0
Bug is related to the [Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
version 2.0.
PS Other installation (localhost on the attached screenshot) on Ubuntu system
had not lost scripts and still shows all scripts and saved scripts. It has
[Config File Provider
Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
older version 1.2.

[JIRA] (JENKINS-13372) Add process last N builds for trend to Configure System Jenkns page.

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

Piotr Czachur updated JENKINS-13372:

Issue Type: Improvement (was: Bug)

Add process last N builds for trend to Configure System Jenkns page.
-

Key: JENKINS-13372
URL: https://issues.jenkins-ci.org/browse/JENKINS-13372
Project: Jenkins
Issue Type: Improvement
Components: performance-plugin
Affects Versions: current
Environment: Performance Plugin 1.7
Reporter: Piotr Czachur
Assignee: Manuel Carrasco

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

SCM/JIRA link daemon resolved JENKINS-12457.


Resolution: Fixed

 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-13214) Tests with the same name are no longer reported in the test results


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

SCM/JIRA link daemon commented on JENKINS-13214:


Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
 core/src/test/java/hudson/tasks/junit/TestResultTest.java
 core/src/test/resources/hudson/tasks/junit/JENKINS-13214/27449.xml
 core/src/test/resources/hudson/tasks/junit/JENKINS-13214/27540.xml
 core/src/test/resources/hudson/tasks/junit/JENKINS-13214/29734.xml
http://jenkins-ci.org/commit/jenkins/1d249b98fb2a70f31b27849898e5d50dd5b018a4
Log:
  Added testcase and changelog for JENKINS-13214. The actual fix is in 
7fba652710e64f6dce00e2e186e77ee2a39bd445


Compare: https://github.com/jenkinsci/jenkins/compare/2dd0398...1d249b9



 Tests with the same name are no longer reported in the test results
 ---

 Key: JENKINS-13214
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13214
 Project: Jenkins
  Issue Type: Bug
  Components: maven2
Affects Versions: current
Reporter: ajbanck
Assignee: kutzi
  Labels: regression
 Attachments: xml_result.zip


 After updating from 1.425 to 1.456 test results will only show one test for 
 tests having the same name.
 Test set having tests executed with parameters:
 ...
 ..Executing TestMyTest#testDefault(true)
 ..Executing TestMyTest#testDefault(false)
 .Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed 
 [132] tests.
 Resulting test results: xml
 ...
 testcase time=0.047 classname=TestMyTest name=testDefault/
   testcase time=0.043 classname=TestMyTest name=testDefault/
 /testsuite
 In version 1.425 the 132 test results where correctly displayed.
 In version 1.456 the test results page is only having one entry for these 
 tests, total amount of tests reported is no longer valid and is the count per 
 test method and not the count of tests actually executed.

--
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-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

SCM/JIRA link daemon commented on JENKINS-12457:


Code changed in jenkins
User: Christoph Kutzinski
Path:
 core/src/main/java/hudson/tasks/junit/CaseResult.java
 core/src/main/java/hudson/tasks/junit/SuiteResult.java
 core/src/main/java/hudson/tasks/junit/TestResult.java
 core/src/test/java/hudson/tasks/junit/TestResultTest.java
 core/src/test/resources/hudson/tasks/junit/eclipse-plugin-test-report.xml
http://jenkins-ci.org/commit/jenkins/7fba652710e64f6dce00e2e186e77ee2a39bd445
Log:
  Revert [FIXED JENKINS-12457] 'Age' column on 'Test Result' tab may show 
incorrect value when a test suite divided into multiple junit files

This reverts commit 05937f5343f844593ebd23ced2f62c4ca7308793.




 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-13038) HTML5 notifier plugin breaks Jenkins with CSRF protection


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

jieryn commented on JENKINS-13038:
--

Prototype 1.7 was included in the base Jenkins install. Is this now a problem 
on the default install? I don't think this is an html5-notifier-plugin issue 
anymore..

 HTML5 notifier plugin breaks Jenkins with CSRF protection
 -

 Key: JENKINS-13038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13038
 Project: Jenkins
  Issue Type: Bug
  Components: html5-notifier
 Environment: Jenkins 1.454
 HTML5 Notifier Plugin 1.1
Reporter: mdp
Assignee: jieryn
Priority: Critical

 The prototype-1.7.js version included in the plugin replaces code from the 
 patched Prototype included in core Jenkins.
 Result: with notifiers and CSRF protection enabled POSTs fail with 403.
 One easily visible example: trying to disable an installed plugin results in
 Status Code: 403
 Exception: No valid crumb was included in the request
 displayed where the restart button should appear.

--
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-13038) HTML5 notifier plugin breaks Jenkins with CSRF protection


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

jieryn updated JENKINS-13038:
-

   Assignee: (was: jieryn)
Component/s: core
 (was: html5-notifier)

 HTML5 notifier plugin breaks Jenkins with CSRF protection
 -

 Key: JENKINS-13038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13038
 Project: Jenkins
  Issue Type: Bug
  Components: core
 Environment: Jenkins 1.454
 HTML5 Notifier Plugin 1.1
Reporter: mdp
Priority: Critical

 The prototype-1.7.js version included in the plugin replaces code from the 
 patched Prototype included in core Jenkins.
 Result: with notifiers and CSRF protection enabled POSTs fail with 403.
 One easily visible example: trying to disable an installed plugin results in
 Status Code: 403
 Exception: No valid crumb was included in the request
 displayed where the restart button should appear.

--
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-12538) java.lang.String cannot be cast to net.sf.json.JSONArray


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

jieryn commented on JENKINS-12538:
--

This is an issue with bundled prototype 1.7.

 java.lang.String cannot be cast to net.sf.json.JSONArray
 

 Key: JENKINS-12538
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12538
 Project: Jenkins
  Issue Type: Bug
  Components: html5-notifier
Affects Versions: current
 Environment: Centos5.6 x86_64 installed from rpm on 
 http://pkg.jenkins-ci.org/redhat/
Reporter: Rob Coward

 Ever since updating to version 1.446 (and it is still a problem in the latest 
 1.449 rpm installation) after clicking save on the job configuration screen I 
 get this server error. The changes do appear to have been saved however, and 
 if I navigate back to the job configuration page it does show the saved 
 changes correctly.
 Status Code: 500
 Exception:
 Stacktrace:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 net.sf.json.JSONArray
   at 
 org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$ArtifactDeployerDescriptor.newInstance(ArtifactDeployerPublisher.java:265)
   at 
 org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$ArtifactDeployerDescriptor.newInstance(ArtifactDeployerPublisher.java:221)
   at hudson.util.DescribableList.rebuild(DescribableList.java:154)
   at hudson.model.Project.submit(Project.java:198)
   at hudson.model.Job.doConfigSubmit(Job.java:979)
   at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:643)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   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:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
   at 
 hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at

[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin


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

jieryn commented on JENKINS-13322:
--

Starting with Jenkins 1.455 prototype v1.7 is bundled, html5-notifier-plugin 
does not include its own prototype.js

 Configure tab freezes when using both the HTML5 notifier plugin and the 
 Android Emulator Plugin
 ---

 Key: JENKINS-13322
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322
 Project: Jenkins
  Issue Type: Bug
  Components: android-emulator, html5-notifier
 Environment: Mac OS X
Reporter: Johannes Pelto-Piri
Assignee: Christopher Orr

 When trying to configure a job with both the HTML5 notifier plugin and the 
 Android Emulator plugin the job configuration wont load. I tried again in a 
 fresh installation and installed the plugins separately and the issue 
 remained. 

--
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-13038) HTML5 notifier plugin breaks Jenkins with CSRF protection


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

jieryn resolved JENKINS-13038.
--

Resolution: Fixed

html5-notifier-plugin:1.2 was released: 
http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/html5-notifier-plugin/1.2/

 HTML5 notifier plugin breaks Jenkins with CSRF protection
 -

 Key: JENKINS-13038
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13038
 Project: Jenkins
  Issue Type: Bug
  Components: core
 Environment: Jenkins 1.454
 HTML5 Notifier Plugin 1.1
Reporter: mdp
Priority: Critical

 The prototype-1.7.js version included in the plugin replaces code from the 
 patched Prototype included in core Jenkins.
 Result: with notifiers and CSRF protection enabled POSTs fail with 403.
 One easily visible example: trying to disable an installed plugin results in
 Status Code: 403
 Exception: No valid crumb was included in the request
 displayed where the restart button should appear.

--
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-12538) java.lang.String cannot be cast to net.sf.json.JSONArray


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

jieryn closed JENKINS-12538.


Resolution: Fixed

html5-notifier-plugin:1.2 was released: 
http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/html5-notifier-plugin/1.2/

 java.lang.String cannot be cast to net.sf.json.JSONArray
 

 Key: JENKINS-12538
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12538
 Project: Jenkins
  Issue Type: Bug
  Components: html5-notifier
Affects Versions: current
 Environment: Centos5.6 x86_64 installed from rpm on 
 http://pkg.jenkins-ci.org/redhat/
Reporter: Rob Coward

 Ever since updating to version 1.446 (and it is still a problem in the latest 
 1.449 rpm installation) after clicking save on the job configuration screen I 
 get this server error. The changes do appear to have been saved however, and 
 if I navigate back to the job configuration page it does show the saved 
 changes correctly.
 Status Code: 500
 Exception:
 Stacktrace:
 java.lang.ClassCastException: java.lang.String cannot be cast to 
 net.sf.json.JSONArray
   at 
 org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$ArtifactDeployerDescriptor.newInstance(ArtifactDeployerPublisher.java:265)
   at 
 org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$ArtifactDeployerDescriptor.newInstance(ArtifactDeployerPublisher.java:221)
   at hudson.util.DescribableList.rebuild(DescribableList.java:154)
   at hudson.model.Project.submit(Project.java:198)
   at hudson.model.Job.doConfigSubmit(Job.java:979)
   at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:643)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   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:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   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.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
   at 
 hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
   at

[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin


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

jieryn closed JENKINS-13322.


Resolution: Fixed

html5-notifier-plugin:1.2 was released: 
http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/html5-notifier-plugin/1.2/

 Configure tab freezes when using both the HTML5 notifier plugin and the 
 Android Emulator Plugin
 ---

 Key: JENKINS-13322
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322
 Project: Jenkins
  Issue Type: Bug
  Components: android-emulator, html5-notifier
 Environment: Mac OS X
Reporter: Johannes Pelto-Piri
Assignee: Christopher Orr

 When trying to configure a job with both the HTML5 notifier plugin and the 
 Android Emulator plugin the job configuration wont load. I tried again in a 
 fresh installation and installed the plugins separately and the issue 
 remained. 

--
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-13138) Verify action doesn't work with CSRF option


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

jieryn closed JENKINS-13138.


Resolution: Fixed

html5-notifier-plugin:1.2 was released: 
http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/html5-notifier-plugin/1.2/

 Verify action doesn't work with CSRF option
 ---

 Key: JENKINS-13138
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13138
 Project: Jenkins
  Issue Type: Bug
  Components: html5-notifier
Affects Versions: current
 Environment: Debian x64
Reporter: Sébastien Heurtematte
Priority: Minor
  Labels: csrf, mantis
 Attachments: mantis.jpg


 Etat HTTP 403 - No valid crumb was included in the request

--
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-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

dogfood commented on JENKINS-12457:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! 
[jenkins_main_trunk #1642|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1642/]
 Revert [FIXED JENKINS-12457] 'Age' column on 'Test Result' tab may show 
incorrect value when a test suite divided into multiple junit files (Revision 
7fba652710e64f6dce00e2e186e77ee2a39bd445)

 Result = UNSTABLE
Christoph Kutzinski : 
[7fba652710e64f6dce00e2e186e77ee2a39bd445|https://github.com/jenkinsci/jenkins/commit/7fba652710e64f6dce00e2e186e77ee2a39bd445]
Files : 
* core/src/test/resources/hudson/tasks/junit/eclipse-plugin-test-report.xml
* core/src/test/java/hudson/tasks/junit/TestResultTest.java
* core/src/main/java/hudson/tasks/junit/CaseResult.java
* core/src/main/java/hudson/tasks/junit/SuiteResult.java
* core/src/main/java/hudson/tasks/junit/TestResult.java


 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-11146) Automatically redirect users to secure connection

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

jieryn commented on JENKINS-11146:
--

I think that forcing a redirect it outside the scope of this plugin. Rather, it
would be better and easier to enable this in the web.xml:

{code:xml} security-constraint
web-resource-collection
web-resource-name/web-resource-name
url-pattern/*/url-pattern
/web-resource-collection
user-data-constraint
transport-guaranteeCONFIDENTIAL/transport-guarantee
/user-data-constraint
/security-constraint
{code}

Automatically redirect users to secure connection
-

Key: JENKINS-11146
URL: https://issues.jenkins-ci.org/browse/JENKINS-11146
Project: Jenkins
Issue Type: Improvement
Components: hsts-filter
Reporter: Christopher Orr
Assignee: jieryn

Currently the plugin always sends the STS header, regardless of whether
Jenkins is being accessed via a secure connection.
The spec says:
bq. A HSTS Server MUST NOT include the Strict-Transport-Security HTTP
Response Header in HTTP responses conveyed over a non-secure transport.
Similarly, browsers will ignore any STS headers received over a non-secure
connection. So it's quite possible that users may end up never accessing
Jenkins securely, unless they manually visit the secure URL at least once.
The recommended practice when servers receive non-secure requests is to send
an HTTP redirect to the secure version of the content. Then that allows the
STS header to be sent, and accepted by the browser.
So it would be good if this was implemented, so that a redirect would be sent
whenever the STS header is enabled in the plugin config and a user accesses
Jenkins insecurely.
However I guess that may also need an optional config field for entering the
secure URL (e.g. if the hostnames differ between secure and non-secure).

[JIRA] (JENKINS-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'

2012-04-06 Thread dbarbi...@fusionio.com (JIRA)


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

Devin Barbieri commented on JENKINS-13295:
--

Here's an example of what we're seeing at the tail of the log:

18:59:42  Email was triggered for: Success
18:59:42  Sending email for trigger: Success
19:43:13  Sending email to: (removed for privacy)

 Jenkins hangs for ~1 hour after posting 'Sending Email'
 ---

 Key: JENKINS-13295
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13295
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Reporter: Devin Barbieri
Priority: Critical



--
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-13295) Jenkins hangs for ~1 hour after posting 'Sending Email'

2012-04-06 Thread dbarbi...@fusionio.com (JIRA)


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

Devin Barbieri commented on JENKINS-13295:
--

We had a job sit there for over 12 hours so we had to kill the jenkins process. 
We aren't able to kill the job with the [x]. I know from working on a different 
plugin that we have to throw the InterruptedException back up to the core 
somewhere, I handled it once in my own way and it made the [x] button useless, 
may be the same, may not, just thought i'd mention that.

 Jenkins hangs for ~1 hour after posting 'Sending Email'
 ---

 Key: JENKINS-13295
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13295
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Reporter: Devin Barbieri
Priority: Critical



--
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-11719) active-directory plugin only ships x86 com4j.dll

2012-04-06 Thread jacob.robertson.w...@gmail.com (JIRA)


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

jacob_robertson commented on JENKINS-11719:
---

Unfortunately, it turns out that running 32 bit java on a 64 bit machine 
restricts the amount of memory we can allocate to Jenkins, so we are back up 
against this problem.  Does anyone have any suggestions?  I've tried what 
Hemant mentioned, but can't get that to work.

 active-directory plugin only ships x86 com4j.dll
 

 Key: JENKINS-11719
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11719
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
Affects Versions: current
 Environment: 1.4.36
Reporter: Trevor Baker

 AD plugin reports following stack on windows with x64 jre.  Consider shipping 
 both x86 and x64 versions on com4j.dll and using correct one based on env.
 http://java.net/projects/com4j/downloads
 Nov 14, 2011 10:28:44 AM 
 hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DesciprotrImpl 
 canDoNativeAuth
 INFO: COM4J isn't working. Falling back to non-native authentication
 java.lang.UnsatisfiedLinkError: 
 C:\Users\build\.hudson\plugins\active-directory\WEB-INF\lib\com4j.dll: Can't 
 load IA 32-bit .dll on a AMD 64-bit platform
   at java.lang.ClassLoader$NativeLibrary.load(Native Method)
   at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1928)
   at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1825)
   at java.lang.Runtime.load0(Runtime.java:792)
   at java.lang.System.load(System.java:1059)
   at com4j.COM4J.loadNativeLibrary(COM4J.java:430)
   at com4j.COM4J.clinit(COM4J.java:386)
   at 
 com4j.typelibs.ado20.ClassFactory.createConnection(ClassFactory.java:13)
   at 
 hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DesciprotrImpl.canDoNativeAuth(ActiveDirectorySecurityRealm.java:227)
   at 
 hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DesciprotrImpl$canDoNativeAuth.call(Unknown
  Source)
   at 
 org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
   at 
 org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
   at 
 org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112)
   at Script1.run(Script1.groovy:12)
   at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:135)
   at 
 hudson.plugins.active_directory.ActiveDirectorySecurityRealm.createSecurityComponents(ActiveDirectorySecurityRealm.java:129)
   at 
 hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:398)
   at hudson.security.HudsonFilter.reset(HudsonFilter.java:134)
   at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:1916)
   at jenkins.model.Jenkins$15.run(Jenkins.java:2397)
   at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
   at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
   at jenkins.model.Jenkins$5.runTask(Jenkins.java:798)
   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.runWorker(ThreadPoolExecutor.java:1110)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
   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-13373) Job in quiet period blocks other jobs even if executors are available

johno created JENKINS-13373:
---

 Summary: Job in quiet period blocks other jobs even if executors 
are available
 Key: JENKINS-13373
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: johno
 Attachments: queue.png

If there is a job in quiet period other jobs which do not depend on its 
completion will block anyway even if executors are available.

--
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-12598) In 2.0 update you need to specify branch for every module

2012-04-06 Thread fred...@hotmail.com (JIRA)

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

Fred G commented on JENKINS-12598:
--

I agree, my mockup is definitely not the best.
Nevertheless I think there is a need for a text field that allows a large
number of modules to be pasted in.
That's also what Ulli requested in the issue's description.

As mentioned on IRC, when a large number of modules is checked out, it's pretty
save to assume that no custom local names are used. Therefore no local name
field is needed in that case.
If a user wants to use local names anyways he can still specify them as single
modules.

In 2.0 update you need to specify branch for every module
-

Key: JENKINS-12598
URL: https://issues.jenkins-ci.org/browse/JENKINS-12598
Project: Jenkins
Issue Type: Improvement
Components: cvs
Reporter: Ulli Hafner
Priority: Critical
Attachments: Jenkins_CvsPluginModules.png,
repositoryLocationProposal.png

After an upgrade to the new 2.0 version of the cvs plug-in we now need to
specify the Module location (trunk, branch) for each module. This is quite
cumbersome if you have a lot of modules. In the 1.x plug-in releases you are
able to select a given branch for all modules in one text field.
While I think the new feature has a lot of use cases (i.e., having trunk
and branches mixed), the usability could be improved here. My requirement is
to select/change the branch (or trunk) for all modules in a simple way.
A non-Ajax suggestion would be to have a default entry in the Selection,
i.e. Trunk, Branch, Tag, Default. And you can define the default behavior at
the top of the cvs configuration.

[JIRA] (JENKINS-10880) Git plugin fails on remote Poll


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

dogfood commented on JENKINS-10880:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! 
[plugins_git-plugin #314|http://ci.jenkins-ci.org/job/plugins_git-plugin/314/]
 
 Result = UNSTABLE

 Git plugin fails on remote Poll
 ---

 Key: JENKINS-10880
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10880
 Project: Jenkins
  Issue Type: Bug
  Components: git
Affects Versions: current
Reporter: robertdw
Assignee: Kohsuke Kawaguchi
Priority: Minor

 If you enable remote polling in the Git Plugin, the project will never poll 
 successfully, and stops other projects polling as well.
 In GitSCM, requiresWorkspaceForPolling() returns false if remotePoll is 
 enabled.
 https://github.com/jenkinsci/git-plugin/blob/git-1.1.12/src/main/java/hudson/plugins/git/GitSCM.java#L582
 This mean that in the jenkins-core AbstractProject (at least on the LTS 
 branch), a null value is passed in for the workspace parameter to SCM.poll()
 https://github.com/jenkinsci/jenkins/blob/jenkins-1.409.1/core/src/main/java/hudson/model/AbstractProject.java#L1305
 This ends up in 'compareRemoteRevisionWith' back in GitSCM. At line 651, the 
 call to 'workingDirectory(workspace)' returns null - because null was passed 
 in as a param from AbstractProject. This means that at line 657, the call to 
 !!workingDirectory.exists() results in a null pointer.
 Suggested fix: remove the remotePoll, or make it require a workspace to do 
 the polling. 
 Stacktrace:
 Sep 2, 2011 2:41:50 PM hudson.triggers.SCMTrigger$Runner runPolling
 SEVERE: Failed to record SCM polling
 java.lang.NullPointerException
   at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:657)
   at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:354)
   at hudson.scm.SCM.poll(SCM.java:371)
   at hudson.model.AbstractProject.poll(AbstractProject.java:1305)
   at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
   at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
   at hudson.triggers.SCMTrigger.run(SCMTrigger.java:103)
   at hudson.triggers.SCMTrigger.run(SCMTrigger.java:83)
   at hudson.triggers.Trigger$1.run(Trigger.java:229)
   at hudson.DependencyRunner.run(DependencyRunner.java:73)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)

--
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-13356) Git fast remote polling always triggers build when missing locale

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

dogfood commented on JENKINS-13356:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png!
[plugins_git-plugin #314|http://ci.jenkins-ci.org/job/plugins_git-plugin/314/]

Result = UNSTABLE

Git fast remote polling always triggers build when missing locale
-

Key: JENKINS-13356
URL: https://issues.jenkins-ci.org/browse/JENKINS-13356
Project: Jenkins
Issue Type: Bug
Components: git
Reporter: Marc Günther
Assignee: Nicolas De Loof
Priority: Minor

Symptom:
All jobs which had fast remote polling enabled triggered on every change in
their repository, even if it was on an unrelated branch.
Cause:
Fast remote polling issues a {{git ls-remote -h repo branch}} command.
The output of this command is supposed to be the sha hash of the last commit,
but in our case it was:
{{bash: warning: setlocale: LC_ALL: cannot}}
Explanation:
We have some slaves that use a german locale. This locale does not exist on
the Git repository server nor on the Jenkins server. Installing it on the
Jenkins server had no effect, as the above warning comes from the Git
repository server.
Quick fix:
Install the missing locale on the both servers.
Solution:
Installing locales on some server should not be required. Either ignore
stderr when issuing the {{git ls-remote}} command, or manipulate the passed
in environment to something that does not cause side effects like this.
Question:
Why is the environment from the slave used on the server when doing the
polling? {{LC_ALL}} is not set on our Jenkins server, so this definitely
comes from a slave. I also notice that variables like HOME, USER, DISPLAY are
set to values which make no sense on the server, and can lead to more
problems like this.

[JIRA] (JENKINS-12514) .hpi versus .jpi causes inability to upgrade Subversion Plugin

2012-04-06 Thread bhaza...@gmail.com (JIRA)


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

Bill Hazard commented on JENKINS-12514:
---

for those seeking a workaround: 

rm WEB-INF/plugins/subversion.hpi and re-install via Manage Plugins

ditto for cvs and translation

 .hpi versus .jpi causes inability to upgrade Subversion Plugin
 --

 Key: JENKINS-12514
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12514
 Project: Jenkins
  Issue Type: Bug
  Components: update-center
 Environment: Ubuntu 11.10, OpenJDK 1.6.0_23, Tomcat 7.0.21, Jenkins 
 1.448  1.449
 Jenkins 1.456 on Windows Server 2003 64-bit, Sun JDK 6.0.260.3
Reporter: Charlie Huggard
Assignee: Kohsuke Kawaguchi
Priority: Blocker

 Reproduction:
 $JENKINS_HOME/plugins: subversion (directory), subversion.hpi
 1) Open http://root/pluginManager. Update Subversion plugin from 1.34 - 
 1.37 using download now and install after restart button.
 $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), 
 subversion.hpi.pinned, subversion.jpi (1.37)
 2) Restart Tomcat/Jenkins
 $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), 
 subversion.hpi (1.34) subversion.hpi.pinned, subversion.jpi (1.37)
 3) PluginManager still reports old version 
 Should note that the logs report:
 INFO: Ignoring /ci/jenkins-home/plugins/subversion.jpi because 
 /ci/jenkins-home/plugins/subversion.hpi is already loaded
 Also the plugin is broken at this point with a NoClassDefFound on 
 org/tmatesoft/svn/core/SVNException 
 Clean State: 
 1) /etc/init.d/tomcat7 stop
 2) cd $JENKINS_HOME/plugins
 3) rm subversion*
 4) /etc/init.d/tomcat7 start
 Workaround:
 1) Restore clean state
 2) Update plugin
 3) Stop tomcat/jenkins
 4) cd $JENKINS_HOME/plugins
 5) mv subversion.jpi subversion.hpi
 6) Start tomcat/jenkins

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

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files

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


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

kutzi reopened JENKINS-12457:
-


 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-12619) Failed to test the validity of the user name on all security matrices since upgrade

2012-04-06 Thread jacob.robertson.w...@gmail.com (JIRA)


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

jacob_robertson commented on JENKINS-12619:
---

Reproduced exactly on windows server 2008.   Jenkins 1.447.1 and AD plugin 1.26.
Seems fixed after downgrading to 1.16 - why did we choose that version?

 Failed to test the validity of the user name on all security matrices since 
 upgrade
 -

 Key: JENKINS-12619
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12619
 Project: Jenkins
  Issue Type: Bug
  Components: active-directory
 Environment: Jenkins 1.450, plugin version 1.26
 Windows Server 2003, non-domain server
 Installed as local user
 Our Windows domain name specified in configuration as ourdomain.co.uk
Reporter: Tom Fanning
Priority: Minor
  Labels: jenkins, plugin, windows

 Upgraded plugin to version 1.26 just after upgrading Jenkins to 1.450
 Now get message Failed to test the validity of the user name x wherever 
 there is a security checkbox matrix.
 Everything seems to work alright still as far as I can tell.
 Stack trace:
 org.acegisecurity.BadCredentialsException: Failed to retrieve user 
 information for x; nested exception is javax.naming.NamingException: [LDAP: 
 error code 1 - 04DC: LdapErr: DSID-0C0906E8, comment: In order to perform 
 this operation a successful bind must be completed on the connection., data 
 0, v1db1]; remaining name 'DC=ourdomain,DC=co,DC=uk'
   at 
 hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231)
   at 
 hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:130)
   at 
 hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:95)
   at 
 hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:27)
   at 
 hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:551)
   at 
 hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:304)
   at 
 hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:288)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   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:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   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.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

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

SCM/JIRA link daemon resolved JENKINS-12457.


Resolution: Fixed

 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

SCM/JIRA link daemon commented on JENKINS-12457:


Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
 core/src/main/java/hudson/tasks/junit/CaseResult.java
 core/src/main/java/hudson/tasks/junit/TestResult.java
 core/src/test/java/hudson/tasks/junit/TestResultTest.java
 core/src/test/resources/hudson/tasks/junit/JENKINS-12457/TestSuite_a1.xml
 core/src/test/resources/hudson/tasks/junit/JENKINS-12457/TestSuite_a2.xml
 core/src/test/resources/hudson/tasks/junit/JENKINS-12457/TestSuite_b.xml
 
core/src/test/resources/hudson/tasks/junit/JENKINS-12457/TestSuite_b_duplicate.xml
http://jenkins-ci.org/commit/jenkins/d9e87705e8d693bc9d028e1da8c614c0fb736cd3
Log:
  [Re-FIXED JENKINS-12457] 'Age' column on 'Test Result' tab may show incorrect 
value when a test suite divided into multiple junit files






 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-13296) Changelists that include excluded files and files outside of the client view will trigger a build.

2012-04-06 Thread pmacc...@yahoo.com (JIRA)


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

Patrick McKeown commented on JENKINS-13296:
---

Any updates?

 Changelists that include excluded files and files outside of the client view 
 will trigger a build.
 --

 Key: JENKINS-13296
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13296
 Project: Jenkins
  Issue Type: Improvement
  Components: perforce
Reporter: Patrick McKeown
Assignee: Rob Petti
Priority: Minor

 If there is already a way to handle this I apologize, looked around but 
 didn't find anything.
 Given a client spec 
 //depot/test/... //client/test/...
 with an exclude list such as
 //depot/test/exclude/...
 and polling turned on-
 if someone submits a changelist with an excluded file and a file outside the 
 client spec such as 
 changelist 1234
 //depot/test/exclude/example.txt#1
 //depot/test2/example2.txt#1
 then //depot/test2/example2.txt#1 will trigger the build as it does not match 
 anything in the exclude list.
 I would like a way to consider any files outside of the client spec as 
 excluded files without actually having to specify them.  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-13373) Job in quiet period blocks other jobs even if executors are available


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

johno updated JENKINS-13373:


Description: If there is a job in quiet period other jobs which do not 
depend on its completion will block even if executors are available.  (was: If 
there is a job in quiet period other jobs which do not depend on its completion 
will block anyway even if executors are available.)

 Job in quiet period blocks other jobs even if executors are available
 -

 Key: JENKINS-13373
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: johno
 Attachments: queue.png


 If there is a job in quiet period other jobs which do not depend on its 
 completion will block even if executors are available.

--
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-13360) Envinject fails with UnsupportedMediaException

2012-04-06 Thread gb...@java.net (JIRA)


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

gbois closed JENKINS-13360.
---

Resolution: Cannot Reproduce

Can't reproduce.
Please reopen if you have any new inputs.

 Envinject fails with UnsupportedMediaException
 --

 Key: JENKINS-13360
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13360
 Project: Jenkins
  Issue Type: Bug
  Components: envinject
 Environment: JBOSS 7.1.1, FreeBSD 8.2, openjdk 6
Reporter: Radim Kolar
Assignee: gbois
Priority: Critical

 It does this in all cases, even if property file does not exists.
 [EnvInject] - Preparing an environment for the build.
 [EnvInject] - [ERROR] - SEVERE ERROR occurs: 
 com/sun/xml/internal/ws/server/UnsupportedMediaException
 Archiving artifacts
 EnvInject 1.44

--
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-13325) PYTHONPATH gets undefined with latest 1.44 version of EnvInject

2012-04-06 Thread gb...@java.net (JIRA)

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

gbois commented on JENKINS-13325:
-

Any update?
Are you sure it is the right file, your given file is filled with plain values.
Therefore it should never be unseted variables.

PYTHONPATH gets undefined with latest 1.44 version of EnvInject
---

Key: JENKINS-13325
URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
Project: Jenkins
Issue Type: Bug
Components: envinject
Environment: Jenkins 1.457, Windows master, Linux slave
Reporter: Marc Sanfacon
Assignee: gbois
Attachments: BuildFingerprint.txt, config.xml

We are using envinject on our Linux slave. With version 1.36, we get the
following behavior:
08:51:39 [EnvInject] - Injecting environment variables from a build step.
08:51:39 [EnvInject] - Injecting as environment variables the properties
file path 'BuildFingerprint.txt'
08:51:39 [EnvInject] - Variables injected successfully.
08:51:39 [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
08:51:39 [EnvInject] - Unset unresolved 'PATH' variable.
08:51:39 [EnvInject] - Unset unresolved 'NEWSCP' variable.
08:51:39 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
08:51:39 [EnvInject] - Unset unresolved 'TEMP' variable.
But somehow, the variable PYTHONPATH is still set afterwards since we call a
script found in the path and it works.
With version 1.44, we get this:
08:49:16 [EnvInject] - Injecting environment variables from a build step.
08:49:16 [EnvInject] - Injecting as environment variables the properties
file path 'BuildFingerprint.txt'
08:49:16 [EnvInject] - Variables injected successfully.
08:49:16 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
Only PYTHONPATH gets undefined, but it really is. The next build step fails
when calling the script because it is not found in the path.
I don't know what changed between the builds, but reverting the plugin fixed
it.
Also, why does EnvInject undefines other variables? All I want is for it to
inject the variables I asked. The ini files does not contain PYTHONPATH.

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


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

dogfood commented on JENKINS-12457:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! 
[jenkins_main_trunk #1645|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1645/]
 
 Result = UNSTABLE

 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
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-13375) Display window (for g-j for example) should use the offset from the top of the viewport, not top of the screen

2012-04-06 Thread ty...@monkeypox.org (JIRA)

R. Tyler Croy created JENKINS-13375:
---

 Summary: Display window (for g-j for example) should use the 
offset from the top of the viewport, not top of the screen
 Key: JENKINS-13375
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13375
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Reporter: R. Tyler Croy
Assignee: jieryn


If I'm scrolled down the page, all the display doesn't appear for me :(

--
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-13170) JellyTagException when clicking on CCM trend chart

2012-04-06 Thread brunodepau...@yahoo.com.br (JIRA)


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

Work on JENKINS-13170 stopped by Bruno P. Kinoshita.

 JellyTagException when clicking on CCM trend chart
 --

 Key: JENKINS-13170
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13170
 Project: Jenkins
  Issue Type: Bug
  Components: ccm
Affects Versions: current
 Environment: Ubuntu
Reporter: Samuele Gantner
Assignee: Bruno P. Kinoshita
 Attachments: screenshot.png, stacktrace.txt


 When trying to click on the CCM chart, the resulting page has 500 status code.
 org.apache.commons.jelly.JellyTagException: 
 file:/var/lib/jenkins/plugins/ccm/WEB-INF/classes/hudson/plugins/ccm/CCMProjectAction/nodata.jelly:5:64:
  st:include No page found 'sidepanel.jelly' for class 
 hudson.plugins.ccm.CCMProjectAction
 Exception and screenshots are attached.

--
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-13177) CCM result in build shows only top 15 methods even though CCM is configured for 100

2012-04-06 Thread brunodepau...@yahoo.com.br (JIRA)


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

Work on JENKINS-13177 stopped by Bruno P. Kinoshita.

 CCM result in build shows only top 15 methods even though CCM is configured 
 for 100
 ---

 Key: JENKINS-13177
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13177
 Project: Jenkins
  Issue Type: Bug
  Components: ccm
Affects Versions: current
 Environment: Ubuntu master / Windows 7 slave
Reporter: Samuele Gantner
Assignee: Bruno P. Kinoshita
Priority: Minor
 Attachments: result.png, settings.png


 I configured CCM to show 100 methods in Number of metrics. However in the 
 results I only see 15 methods. Screenshots are attached

--
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-13317) Mail not sent: NullPointerException in plugins.ContentBuilder.transformText(ContentBuilder.java:68)

2012-04-06 Thread harold.shins...@sap.com (JIRA)


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

shinsato updated JENKINS-13317:
---

Attachment: email-ext.hpi

A version of 2.20-SNAPSHOT with some debugging for the 
ContentBuilder.transformText code to make it easier to see where the null 
String is being introduced.

 Mail not sent: NullPointerException in 
 plugins.ContentBuilder.transformText(ContentBuilder.java:68)
 ---

 Key: JENKINS-13317
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13317
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Affects Versions: current
 Environment: jdk1.6.0_29  Linux
Reporter: Chris J
Priority: Blocker
  Labels: email-ext, exception, plugin
 Attachments: email-ext.hpi


 email-ext fails with a NullPointerException when sending some emails (not 
 all).
 I am not a java developer but if someone could send me a version of email-ext 
 having this line (ContentBuilder.java:68) devided in several lines, next time 
 it fails we could locate more precisely the error.
 Here is the stack I have:
 --
 Build step 'Execute shell' marked build as failure
 Email was triggered for: Failure
 Sending email for trigger: Failure
 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.transformText(ContentBuilder.java:68)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:463)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:311)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   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.cleanUp(Build.java:171)
   at hudson.model.Run.run(Run.java:1454)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Finished: FAILURE

--
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-13317) Mail not sent: NullPointerException in plugins.ContentBuilder.transformText(ContentBuilder.java:68)

2012-04-06 Thread harold.shins...@sap.com (JIRA)


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

shinsato reassigned JENKINS-13317:
--

Assignee: shinsato

 Mail not sent: NullPointerException in 
 plugins.ContentBuilder.transformText(ContentBuilder.java:68)
 ---

 Key: JENKINS-13317
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13317
 Project: Jenkins
  Issue Type: Bug
  Components: email-ext
Affects Versions: current
 Environment: jdk1.6.0_29  Linux
Reporter: Chris J
Assignee: shinsato
Priority: Blocker
  Labels: email-ext, exception, plugin
 Attachments: email-ext.hpi


 email-ext fails with a NullPointerException when sending some emails (not 
 all).
 I am not a java developer but if someone could send me a version of email-ext 
 having this line (ContentBuilder.java:68) devided in several lines, next time 
 it fails we could locate more precisely the error.
 Here is the stack I have:
 --
 Build step 'Execute shell' marked build as failure
 Email was triggered for: Failure
 Sending email for trigger: Failure
 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.transformText(ContentBuilder.java:68)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:463)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:311)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251)
   at 
 hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211)
   at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
   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.cleanUp(Build.java:171)
   at hudson.model.Run.run(Run.java:1454)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Finished: FAILURE

--
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-13170) JellyTagException when clicking on CCM trend chart

2012-04-06 Thread brunodepau...@yahoo.com.br (JIRA)


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

Bruno P. Kinoshita commented on JENKINS-13170:
--

Hi again Samuele!

I've refactored CCM Plug-in to be used like other static analysis plug-ins 
(https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins).

As a result of this change, the plug-in now is not a Builder anymore, but a 
Publisher. It means, basically, that the plug-in is not invoked during the 
build anymore, but after all the build steps have finished. So now you have to 
use MSBuild, or add a Windows batch command to invoke CCM, and output in XML. 
Then enable CCM.

However, the bright side of this is that the UI is the same as PMD, Tasks, 
FindBugs and other plug-ins configured using analysis-core (yup, you have to 
install this one first, I know it can be inconvenient, but it's worth :).

There are more graphics in the dashboard available now, as well as better 
organization of results. 

Could you give it a try again? 

Sorry for taking this decision without letting you know first. I created CCM 
plug-in before the analysis-core and other static analysis plug-ins were 
released, and it was my first plug-in. That's why I had to do such change.

Thank you!
Bruno


 JellyTagException when clicking on CCM trend chart
 --

 Key: JENKINS-13170
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13170
 Project: Jenkins
  Issue Type: Bug
  Components: ccm
Affects Versions: current
 Environment: Ubuntu
Reporter: Samuele Gantner
Assignee: Bruno P. Kinoshita
 Attachments: screenshot.png, stacktrace.txt


 When trying to click on the CCM chart, the resulting page has 500 status code.
 org.apache.commons.jelly.JellyTagException: 
 file:/var/lib/jenkins/plugins/ccm/WEB-INF/classes/hudson/plugins/ccm/CCMProjectAction/nodata.jelly:5:64:
  st:include No page found 'sidepanel.jelly' for class 
 hudson.plugins.ccm.CCMProjectAction
 Exception and screenshots are attached.

--
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-13170) JellyTagException when clicking on CCM trend chart

2012-04-06 Thread brunodepau...@yahoo.com.br (JIRA)


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

Bruno P. Kinoshita commented on JENKINS-13170:
--

CCM plug-in 3.0 should have this issue fixed.

 JellyTagException when clicking on CCM trend chart
 --

 Key: JENKINS-13170
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13170
 Project: Jenkins
  Issue Type: Bug
  Components: ccm
Affects Versions: current
 Environment: Ubuntu
Reporter: Samuele Gantner
Assignee: Bruno P. Kinoshita
 Attachments: screenshot.png, stacktrace.txt


 When trying to click on the CCM chart, the resulting page has 500 status code.
 org.apache.commons.jelly.JellyTagException: 
 file:/var/lib/jenkins/plugins/ccm/WEB-INF/classes/hudson/plugins/ccm/CCMProjectAction/nodata.jelly:5:64:
  st:include No page found 'sidepanel.jelly' for class 
 hudson.plugins.ccm.CCMProjectAction
 Exception and screenshots are attached.

--
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-13177) CCM result in build shows only top 15 methods even though CCM is configured for 100

2012-04-06 Thread brunodepau...@yahoo.com.br (JIRA)


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

Bruno P. Kinoshita commented on JENKINS-13177:
--

CCM plug-in 3.0 should have this issue fixed.

 CCM result in build shows only top 15 methods even though CCM is configured 
 for 100
 ---

 Key: JENKINS-13177
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13177
 Project: Jenkins
  Issue Type: Bug
  Components: ccm
Affects Versions: current
 Environment: Ubuntu master / Windows 7 slave
Reporter: Samuele Gantner
Assignee: Bruno P. Kinoshita
Priority: Minor
 Attachments: result.png, settings.png


 I configured CCM to show 100 methods in Number of metrics. However in the 
 results I only see 15 methods. Screenshots are attached

--
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-13376) Ability to add in new groups of test types

2012-04-06 Thread jason_m_...@yahoo.com (JIRA)

Jason May created JENKINS-13376:
---

 Summary: Ability to add in new groups of test types
 Key: JENKINS-13376
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13376
 Project: Jenkins
  Issue Type: New Feature
  Components: labeled-test-groups-publisher
Affects Versions: current
Reporter: Jason May


Currently the 'group label' has the values 
unit,smoke,regression,integration,special,misc.  Would be nice to (via Jenkins 
config?) be able to add in custom groups rather than have them hard-coded.

--
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-11538) Jenkins serves existing files regardless of security


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

johno commented on JENKINS-11538:
-

Please see https://github.com/stapler/stapler/pull/6/files for proposed patch.

 Jenkins serves existing files regardless of security
 

 Key: JENKINS-11538
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11538
 Project: Jenkins
  Issue Type: Bug
  Components: security, www
Affects Versions: current
 Environment: Jenkins 1.436, Windows 7 64-bit SP1, build-in Winstone 
 servlet engine 0.9.10
Reporter: Steve Betts
Priority: Critical

 an url of the form (note the dot): https:/server/WEB-INF./web.xml will 
 return the file, even with security turned on and the client unauthenticated. 
 As will any other url that references a valid filename with a '.' after the 
 first directory name, such as https://server/scripts./behavior.js.
 these behaviors are considered culnerabilites by our large corporation.
 http://xforce.iss.net/xforce/xfdb/9446
 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1858

--
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-11538) Jenkins serves existing files regardless of security