date:20120223


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

SCM/JIRA link daemon commented on JENKINS-12865:


Code changed in jenkins
User: Gregory Boissinot
Path:
 
src/main/java/org/jenkinsci/plugins/fstrigger/service/FSTriggerComputeFileService.java
 
src/main/java/org/jenkinsci/plugins/fstrigger/service/FSTriggerFileNameRetriever.java
http://jenkins-ci.org/commit/fstrigger-plugin/1032c41949a35c7c2a9eab4e46776d2520918fb7
Log:
  Fix JENKINS-12865






 [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger
 ---

 Key: JENKINS-12865
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12865
 Project: Jenkins
  Issue Type: Bug
  Components: fstrigger
Affects Versions: current
 Environment: Linux master (console only no jobs process on it) and a 
 Windows slave
Reporter: Brad Huggins
Assignee: gbois
Priority: Blocker
 Attachments: Output-IUS.xml


 I receive the following error when FSTrigger attempts to poll:
 [FSTrigger] - Monitor files
 Polling for the job Output-ICA
 Polling remotely on *
 Polling started on Feb 22, 2012 5:58:09 PM
 [ERROR] - SEVERE - Polling error Current Project is null
 I have attached the configuration file though I scrubbed the server name from 
 it.  I have tried using \ or / even no path with the same error.  

--
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-12858) With Maven3 when build fails does not show exceptions

2012-02-23 Thread marco.tizz...@gmail.com (JIRA)


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

Marco Tizzoni commented on JENKINS-12858:
-

Works using maven2 and compiler plugin 2.3.2 (not 2.0.2)

Probably this issue can be closed.

 With Maven3 when build fails does not show exceptions
 -

 Key: JENKINS-12858
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12858
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Affects Versions: current
 Environment: - Linux  2.6.18-238.1.1.el5xen #1 SMP Tue Jan 4 13:52:39 
 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
 - java version 1.6.0_24
 Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
 Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
Reporter: Marco Tizzoni
Priority: Minor
  Labels: console, maven

 Console does not display the full stack trace when building using maven3 if 
 the build fails. 
 {code:title=MAVEN 3 BUILD CONSOLE ON JENKINS|borderStyle=solid}
 [INFO] 
 
 [INFO] Building ConnectionPool-sportello-jar 1.0.0
 [INFO] 
 
 [INFO] 
 [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
 ConnectionPool-sportello-jar ---
 [INFO] 
 [INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
 ConnectionPool-sportello-jar ---
 [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
 resources, i.e. build is platform dependent!
 [INFO] Copying 1 resource
 [INFO] 
 [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ 
 ConnectionPool-sportello-jar ---
 [INFO] Compiling 5 source files to 
 /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/target/classes
 [INFO] 
 
 [INFO] BUILD FAILURE
 [INFO] 
 
 [INFO] Total time: 9.376s
 [INFO] Finished at: Wed Feb 22 19:05:08 CET 2012
 [INFO] Final Memory: 7M/81M
 [INFO] 
 
 mavenExecutionResult exceptions not empty
 message : Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 
 (default-compile) on project ConnectionPool-sportello-jar: Compilation failure
 cause : Compilation failure
 Stack trace : 
 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
 goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 
 (default-compile) on project ConnectionPool-sportello-jar: Compilation failure
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 [..]
   at java.lang.Thread.run(Thread.java:662)
 Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation 
 failure
   at 
 org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
   at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
   at 
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
   ... 27 more
 channel stopped
 Finished: FAILURE
 *** END MAVEN 3 BUILD CONSOLE ON JENKINS ***
 {code}
 Real console output
 {code:title=MAVEN 3 REAL OUTPUT|borderStyle=solid}
 [INFO] Finished at: Wed Feb 22 19:21:51 CET 2012
 [INFO] Final Memory: 5M/88M
 [INFO] 
 
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile 
 (default-compile) on project ConnectionPool-sportello-jar: Compilation 
 failure: Compilation failure:
 [ERROR] 
 /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[62,17]
  unmappable character for encoding UTF8
 [ERROR] 
 [ERROR] 
 /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[68,56]
  unmappable character for encoding UTF8
 [ERROR] 
 [ERROR] 
 /var/lib/jenkins/workspace/sisi.dsvai.sportello.ConnectionPool-sportello/ConnectionPool-sportello-jar/src/main/java/it/bankit/sportello/connectionPool/SockIOPool.java:[125,13]
  unmappable character for encoding UTF8
 [ERROR]

[JIRA] (JENKINS-11749) Included regions feature for GitSCM plugin


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

SCM/JIRA link daemon commented on JENKINS-11749:


Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
 src/main/resources/hudson/plugins/git/GitSCM/config.jelly
 src/main/webapp/help-includedRegions.html
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/57f504fc7a687108b24a9684cc704a8c8d7a3932
Log:
  Merge pull request #49 from juergh/add-included-regions

[FIXED JENKINS-11749] Included regions feature for GitSCM plugin






 Included regions feature for GitSCM plugin
 --

 Key: JENKINS-11749
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11749
 Project: Jenkins
  Issue Type: New Feature
  Components: git
Affects Versions: current
Reporter: Juerg Haefliger
Assignee: Juerg Haefliger
Priority: Minor

 For having several regions to be excluded from build its better to filter the 
 building process only for some included regions.
 [Description copied from http://issues.hudson-ci.org/browse/HUDSON-7294]

--
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-850) search box should match non-casesensitively


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

SCM/JIRA link daemon resolved JENKINS-850.
--

Resolution: Fixed

 search box should match non-casesensitively
 ---

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

 The search box would be even more useful if it would match text 
 non-casesensitively.

--
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-12865) [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger

2012-02-23 Thread gb...@java.net (JIRA)


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

gbois commented on JENKINS-12865:
-

There was a NullPointerException when the path doesn't exist.
It seems it was your use case.
Please upgrade to fstrigger 0.27. The issue should be fixed.

Do not hesitate to reopen the issue if the problem persists

 [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger
 ---

 Key: JENKINS-12865
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12865
 Project: Jenkins
  Issue Type: Bug
  Components: fstrigger
Affects Versions: current
 Environment: Linux master (console only no jobs process on it) and a 
 Windows slave
Reporter: Brad Huggins
Assignee: gbois
Priority: Blocker
 Attachments: Output-IUS.xml


 I receive the following error when FSTrigger attempts to poll:
 [FSTrigger] - Monitor files
 Polling for the job Output-ICA
 Polling remotely on *
 Polling started on Feb 22, 2012 5:58:09 PM
 [ERROR] - SEVERE - Polling error Current Project is null
 I have attached the configuration file though I scrubbed the server name from 
 it.  I have tried using \ or / even no path with the same error.  

--
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-12852) Automating the management of iOS provisioning profiles

2012-02-23 Thread lacos...@java.net (JIRA)


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

lacostej commented on JENKINS-12852:


Valerio, got it. I pushed a few changes to detect this problem and the error 
message will be cleaner. The documentation also.

It should be possible to set a value, even if none was set before hand. I've 
thus opened a detailed issue containing of the roadblocks toward that feature: 
https://github.com/lacostej/iOSprovisioningprofiles/issues/1

One first step is to add support to the apple_dev_center.rb script for 
certificate download, and it should be easy to do. You may want to look at it :)

 Automating the management of iOS provisioning profiles
 --

 Key: JENKINS-12852
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12852
 Project: Jenkins
  Issue Type: New Feature
  Components: xcode
Reporter: Valerio Mazzeo
Priority: Minor

 I was wondering if this is possible, and yesterday I bumped into this article:
 http://lacostej.blogspot.com/2012/02/automating-management-of-ios.html
 I have spent one day to make it work, but now is perfect!
 So, now could be really good to have this feature implemented into the plugin.
 Basically there are two steps:
 1) download all the profile you need from the apple developer center
 2) installing the new certificate into xcode and update the project file with 
 the new one
 if just the second point is integrated into the plugin should be sufficient 
 but if you can integrate all this process would be really amazing.
 I have already dealt with it, so I'm happy to answer your questions and doubt 
 about it.
 What do you think guys? I think would be a very great feature!

--
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-3681) Hide Empty Tabs (Views) in the GUI

2012-02-23 Thread saheba (JIRA)


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

saheba commented on JENKINS-3681:
-

thanks for the pull request. I am scheduling an update session as soon as it is 
merged to jenkins:master.

 Hide Empty Tabs (Views) in the GUI
 --

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

 I'd like the ability to hide tabs that have no visible jobs.  We use Project
 Based Security to limit development access to only their projects.  I don't 
 like
 that developers can still see all tabs used by the other groups, even though
 they are empty due to the security settings.

--
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-12674) Too many files open causes Jenkins to stop responding

2012-02-23 Thread te...@java.net (JIRA)


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

teilo commented on JENKINS-12674:
-

See also JENKINS-9882

 Too many files open  causes Jenkins to stop responding
 

 Key: JENKINS-12674
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12674
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: CentOS 6.0 x64
Reporter: Sagar Khushalani

 Seeing this issue recently. This causes Jenkins to stop responding. Have to 
 stop and restart the service to get any response - doing so breaks other 
 builds that are running.
 {noformat}
 Exception: 
 Stacktrace: 
 java.io.FileNotFoundException: 
 /var/lib/jenkins/jobs/MYPROJECTS_NAME/builds/2012-02-07_15-32-25/log (Too 
 many open files)
   at java.io.RandomAccessFile.open(Native Method)
   at java.io.RandomAccessFile.init(RandomAccessFile.java:233)
   at 
 org.kohsuke.stapler.framework.io.LargeText$FileSession.init(LargeText.java:349)
   at org.kohsuke.stapler.framework.io.LargeText$1.open(LargeText.java:75)
   at 
 org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:164)
   at 
 hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:158)
   at 
 hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:145)
   at 
 org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:214)
   at 
 hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:91)
   at sun.reflect.GeneratedMethodAccessor511.invoke(Unknown Source)
   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$4.doDispatch(MetaClass.java:203)
   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$12.dispatch(MetaClass.java:384)
   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:249)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
   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:195)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
   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

[JIRA] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1

2012-02-23 Thread ne...@solbox.com (JIRA)


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

hyunsoo lee updated JENKINS-11933:
--

Assignee: (was: hyunsoo lee)

my mistake :(

 Subversion plugin doesn't probably work correctly with svn server version 
 1.7.1
 ---

 Key: JENKINS-11933
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11933
 Project: Jenkins
  Issue Type: Bug
  Components: subversion
Affects Versions: current
 Environment: svn server 1.7.1
 ubuntu
Reporter: Nikita Aznauryan
Priority: Blocker
  Labels: plugin
 Attachments: 0001-imported-1.3.7.patch, 
 0002-Adjust-version-number-in-pom.patch, 
 0003-update-version-and-add-second-maven-repository-to-ge.patch, 
 0005_subversion_plugin_svnkit_1_3_7.patch


 I use usernames in my svn path like:
 svn+ssh://jenkins@somepath
 but I get a warning ... doesn't exist in the repository
 I think it started after svn server has been updated to 1.7.1 version
 It worked fine before.
 Subversion pooling log :
 Started on Nov 30, 2011 8:11:31 PM
 Location 'svn+ssh://jenkins@path' does not exist
 One or more repository locations do not exist anymore for 
 hudson.model.FreeStyleProject@3937bf4[], project will be disabled.
 Done. Took 1.3 sec
 No changes

--
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-777) The need for Subversion command line options.

2012-02-23 Thread dharmsh...@gmail.com (JIRA)


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

Dharmesh Sheta commented on JENKINS-777:


created a pull request for review for the patched feature
https://github.com/jenkinsci/subversion-plugin/pull/7 

 The need for Subversion command line options.
 -

 Key: JENKINS-777
 URL: https://issues.jenkins-ci.org/browse/JENKINS-777
 Project: Jenkins
  Issue Type: New Feature
  Components: subversion
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: nickleeye

 There is value in being able to specify command line args/options for the
 subversion update/checkout commands.
 In particular it would be very useful to override svn:externals prop.
 --ignore-externals

--
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-12871) Save buttons hides search result in install plugin page

2012-02-23 Thread alexl...@gmail.com (JIRA)

Alex Lehmann created JENKINS-12871:
--

 Summary: Save buttons hides search result in install plugin page
 Key: JENKINS-12871
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12871
 Project: Jenkins
  Issue Type: Improvement
  Components: core
 Environment: Firefox 10.0.2, Windows 7, Jenkins 1.451
Reporter: Alex Lehmann
Priority: Minor


When searching with ctrl-f in the plugin list on the manage pluings install 
page, the save button always hides the search result, if it is displayed at the 
bottom of the page.

E.g. start at the top of the page and search for git, the highlighted text is 
not visible, however if you scroll down 3 or 4 lines, the highlight becomes 
visible. I assume that the highlight text scrolls the page to the bottom line 
of the screen so that the hidden section covers the line.

Maybe it would be possible to realign the page so that the highlighted section 
is visible above the save button.



--
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-12874) Deploy a versioned SNAPSHOT to Artifactory fails with message Archived artifact is missing

2012-02-23 Thread dmlam...@gmail.com (JIRA)

Daniel M. Lambea created JENKINS-12874:
--

 Summary: Deploy a versioned SNAPSHOT to Artifactory fails with 
message Archived artifact is missing
 Key: JENKINS-12874
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12874
 Project: Jenkins
  Issue Type: Bug
  Components: artifactory
 Environment: Red Hat Enterprise Linux Server, release 5.3, kernel 
version 2.6.18.
JDK 1.6.0_23
Deployed into JBoss v4.2.3-GA-jdk6
Reporter: Daniel M. Lambea
Assignee: yossis
 Attachments: jenkins-console-output.txt

After a successful build, Jenkins attempts to deploy a versioned SNAPSHOT 
artifact to Artifactory 2.3.4.1 (rev. 13021).

Deployment fails because versioned JAR filename contains a non-unique version 
number instead of the word SNAPSHOT. Pom file has no finalName tag defined.

Jenkins Artifactory plugin version is 1.4.2

--
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-12875) No valid crumb was included in the request errors all around

2012-02-23 Thread nuq...@gmail.com (JIRA)

Núria Aloy created JENKINS-12875:


 Summary: No valid crumb was included in the request errors all 
around
 Key: JENKINS-12875
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12875
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: CentOS release 5.5 (Final) 64b
Reporter: Núria Aloy
Priority: Blocker
 Attachments: add_build_step.png, configuration.png, console_log.png, 
console_side.png, plugins.png

After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) 
several parts of Jenkins have become unusable with error No valid crumb was 
included in the request:

h4. Console output

* When building, the log is unavailable, see !console_log.png!
* Once the build is done, the complete log is available, but the same error 
appears on the side !console_side.png!

h4. Build configuration

* Builds cannot be launched anymore from the build page (The firebug error 
console displays the No valid crumb was included in the request error). They 
still can be launched from the dashboard though.
* Cannot add build steps (when choosing a build step type an error is reported 
in background), see !add_build_step.png!

h4. Manage Jenkins configuration

* The page loads only partially (first half is permanently greyed out, see 
!configuration.log!). The firebug error console displays the No valid crumb 
was included in the request error.

h4. Manage Jenkins plugins

* Cannot upgrade nor downgrade, see error shown !plugins.png!

--
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-12875) No valid crumb was included in the request errors all around

2012-02-23 Thread nuq...@gmail.com (JIRA)


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

Núria Aloy updated JENKINS-12875:
-

Description: 
After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) 
several parts of Jenkins have become unusable with error No valid crumb was 
included in the request:

h4. Console output

* When building, the log is unavailable, see [^console_log.png]
* Once the build is done, the complete log is available, but the same error 
appears on the side [^console_side.png]

h4. Build configuration

* Builds cannot be launched anymore from the build page (The firebug error 
console displays the No valid crumb was included in the request error). They 
still can be launched from the dashboard though.
* Cannot add build steps (when choosing a build step type an error is reported 
in background), see [^add_build_step.png]

h4. Manage Jenkins configuration

* The page loads only partially (first half is permanently greyed out, see 
[^configuration.png]). The firebug error console displays the No valid crumb 
was included in the request error.

h4. Manage Jenkins plugins

* Cannot upgrade nor downgrade, see error shown [^plugins.png]

  was:
After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) 
several parts of Jenkins have become unusable with error No valid crumb was 
included in the request:

h4. Console output

* When building, the log is unavailable, see [^console_log.png]
* Once the build is done, the complete log is available, but the same error 
appears on the side [^console_side.png]

h4. Build configuration

* Builds cannot be launched anymore from the build page (The firebug error 
console displays the No valid crumb was included in the request error). They 
still can be launched from the dashboard though.
* Cannot add build steps (when choosing a build step type an error is reported 
in background), see [^add_build_step.png]

h4. Manage Jenkins configuration

* The page loads only partially (first half is permanently greyed out, see 
[^configuration.log]). The firebug error console displays the No valid crumb 
was included in the request error.

h4. Manage Jenkins plugins

* Cannot upgrade nor downgrade, see error shown [^plugins.png]


 No valid crumb was included in the request errors all around
 --

 Key: JENKINS-12875
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12875
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: CentOS release 5.5 (Final) 64b
Reporter: Núria Aloy
Priority: Blocker
 Attachments: add_build_step.png, configuration.png, console_log.png, 
 console_side.png, plugins.png


 After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too) 
 several parts of Jenkins have become unusable with error No valid crumb was 
 included in the request:
 h4. Console output
 * When building, the log is unavailable, see [^console_log.png]
 * Once the build is done, the complete log is available, but the same error 
 appears on the side [^console_side.png]
 h4. Build configuration
 * Builds cannot be launched anymore from the build page (The firebug error 
 console displays the No valid crumb was included in the request error). 
 They still can be launched from the dashboard though.
 * Cannot add build steps (when choosing a build step type an error is 
 reported in background), see [^add_build_step.png]
 h4. Manage Jenkins configuration
 * The page loads only partially (first half is permanently greyed out, see 
 [^configuration.png]). The firebug error console displays the No valid crumb 
 was included in the request error.
 h4. Manage Jenkins plugins
 * Cannot upgrade nor downgrade, see error shown [^plugins.png]

--
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-12875) No valid crumb was included in the request errors all around

2012-02-23 Thread nuq...@gmail.com (JIRA)

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

Núria Aloy updated JENKINS-12875:
-

Description:
After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too)
several parts of Jenkins have become unusable with error No valid crumb was
included in the request:

h4. Console output

* When building, the log is unavailable, see [^console_log.png]
* Once the build is done, the complete log is available, but the same error
appears on the side [^console_side.png]

h4. Build configuration

* Builds cannot be launched anymore from the build page (The firebug error
console displays the No valid crumb was included in the request error). They
still can be launched from the dashboard though.
* Cannot add build steps (when choosing a build step type an error is reported
in background), see [^add_build_step.png]

h4. Manage Jenkins configuration

* The page loads only partially (first half is permanently greyed out, see
[^configuration.log]). The firebug error console displays the No valid crumb
was included in the request error.

h4. Manage Jenkins plugins

* Cannot upgrade nor downgrade, see error shown [^plugins.png]

was:
After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too)
several parts of Jenkins have become unusable with error No valid crumb was
included in the request:

h4. Console output

* When building, the log is unavailable, see !console_log.png!
* Once the build is done, the complete log is available, but the same error
appears on the side !console_side.png!

h4. Build configuration

h4. Manage Jenkins configuration

* The page loads only partially (first half is permanently greyed out, see
!configuration.log!). The firebug error console displays the No valid crumb
was included in the request error.

h4. Manage Jenkins plugins

* Cannot upgrade nor downgrade, see error shown !plugins.png!

No valid crumb was included in the request errors all around
--

Key: JENKINS-12875
URL: https://issues.jenkins-ci.org/browse/JENKINS-12875
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Environment: CentOS release 5.5 (Final) 64b
Reporter: Núria Aloy
Priority: Blocker
Attachments: add_build_step.png, configuration.png, console_log.png,
console_side.png, plugins.png

After upgrading Jenkins from 1.448 to 1.451 (with yum, upgraded plugins too)
several parts of Jenkins have become unusable with error No valid crumb was
included in the request:
h4. Console output
* When building, the log is unavailable, see [^console_log.png]
* Once the build is done, the complete log is available, but the same error
appears on the side [^console_side.png]
h4. Build configuration
* Builds cannot be launched anymore from the build page (The firebug error
console displays the No valid crumb was included in the request error).
They still can be launched from the dashboard though.
* Cannot add build steps (when choosing a build step type an error is
reported in background), see [^add_build_step.png]
h4. Manage Jenkins configuration
* The page loads only partially (first half is permanently greyed out, see
[^configuration.log]). The firebug error console displays the No valid crumb
was included in the request error.
h4. Manage Jenkins plugins
* Cannot upgrade nor downgrade, see error shown [^plugins.png]

--
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-12855) Unnecessary character escapes in Groovy views script

2012-02-23 Thread emanue...@java.net (JIRA)


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

emanuelez commented on JENKINS-12855:
-

and we of cours want it to stay a  instead

 Unnecessary character escapes in Groovy views script
 

 Key: JENKINS-12855
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12855
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: emanuelez
  Labels: groovy, views

 in a groovy view somthing like:
 script(
 for(i = 0; i  10; i++)
 )
 will be converted to:
 for(i = 0; i lt; 10; i++)

--
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-12855) Unnecessary character escapes in Groovy views script

2012-02-23 Thread emanue...@java.net (JIRA)


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

emanuelez commented on JENKINS-12855:
-

the second  should be escaped with (without spaces)  lt ;

 Unnecessary character escapes in Groovy views script
 

 Key: JENKINS-12855
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12855
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: emanuelez
  Labels: groovy, views

 in a groovy view somthing like:
 script(
 for(i = 0; i  10; i++)
 )
 will be converted to:
 for(i = 0; i lt; 10; i++)

--
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-12871) Save buttons hides search result in install plugin page

2012-02-23 Thread b...@java.net (JIRA)


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

bap resolved JENKINS-12871.
---

Resolution: Duplicate

JENKINS-12641

 Save buttons hides search result in install plugin page
 ---

 Key: JENKINS-12871
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12871
 Project: Jenkins
  Issue Type: Improvement
  Components: core
 Environment: Firefox 10.0.2, Windows 7, Jenkins 1.451
Reporter: Alex Lehmann
Priority: Minor

 When searching with ctrl-f in the plugin list on the manage pluings install 
 page, the save button always hides the search result, if it is displayed at 
 the bottom of the page.
 E.g. start at the top of the page and search for git, the highlighted text is 
 not visible, however if you scroll down 3 or 4 lines, the highlight becomes 
 visible. I assume that the highlight text scrolls the page to the bottom line 
 of the screen so that the hidden section covers the line.
 Maybe it would be possible to realign the page so that the highlighted 
 section is visible above the save button.

--
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-12876) Version 1.20 and later removed all comments and new-lines

2012-02-23 Thread alexan...@zia.com.br (JIRA)

Alexandre Zia created JENKINS-12876:
---

 Summary: Version 1.20 and later removed all comments and new-lines
 Key: JENKINS-12876
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12876
 Project: Jenkins
  Issue Type: Bug
  Components: envinject
Affects Versions: current
 Environment: Independent
Reporter: Alexandre Zia
Assignee: gbois
Priority: Critical


From version 1.20 and later, envinject plugin removes all comments and 
new-lines from Properties Content.
This becomes a nightmare as I have more than 300 jobs all documented with 
comments and new lines and now all comments are gone ...
Please fix this.
Alexandre 

--
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-12860) klocwork should use analysis core so it can be rolled up with its own type by static analysis portlets

2012-02-23 Thread monc...@raytheon.com (JIRA)


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

Greg Moncreaff commented on JENKINS-12860:
--

In order of preference:

1. make the static analysis collector, et al have a tool agnostic generic 
mechanism for reporting issues with tool provided types and categories.
(along the lines of xUnit where all test results are normalized to a common 
form?)
2a. have an xslt that transforms klocwork xml format to the already handled 
findbugs format or
2b. (this request) add klocwork as another tool using SA/AC
3. have warnings plugin be able to publish a portlet like SA's warnings (trend 
by type and per project) where the types of each built in or ad hoc parser gets 
its on line/column (another request made a few weeks back).
4. (what I'm currently doing) is a bunch of adhoc console parsers based on the 
text report from klocwork.

What I have works, but I thing any of 1 2 or 3 would obviously be a better 
foundation not just for klocwork, but for any other tool producing analysis 
results.

 klocwork should use analysis core so it can be rolled up with its own type by 
 static analysis portlets
 --

 Key: JENKINS-12860
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12860
 Project: Jenkins
  Issue Type: Improvement
  Components: analysis-core, klocwork
 Environment: rhel 5.5
Reporter: Greg Moncreaff
Assignee: gbois

 klocwork should use analysis core so it can be rolled up with its own type by 
 static analysis portlets

--
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-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

2012-02-23 Thread alexl...@gmail.com (JIRA)


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

Alex Lehmann commented on JENKINS-12730:


wouldn't it be easier to use getRootPath() ?

@Cees Bos: did you set the external Jenkins url in the config page?



 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-12872) Save button doesn't always move to the bottom if the page text length changes

2012-02-23 Thread alexl...@gmail.com (JIRA)


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

Alex Lehmann updated JENKINS-12872:
---

Summary: Save button doesn't always move to the bottom if the page text 
length changes  (was: Save button doesn't always move the bottom if the page 
text length changes)
Component/s: gui
 (was: core)

 Save button doesn't always move to the bottom if the page text length changes
 -

 Key: JENKINS-12872
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12872
 Project: Jenkins
  Issue Type: Improvement
  Components: gui
 Environment: Firefox 10.0.2, Windows 7, Jenkins 1.451 
Reporter: Alex Lehmann
Priority: Minor
 Attachments: Config [Jenkins] - Mozilla 
 Firefox_2012-02-23_13-32-46.png


 When a config page is scrolled all the way down, the save button moves to its 
 regular place at the end of the page, when then the text length changes, e.g. 
 by clicking on an Advanced button or a help link, the Save button stays at 
 the same position covering a section of the text in the middle (see 
 screenshot).
 (cosmetic thing, however this quite annoys me when configuring Sonar, which 
 is the last entry on the page usually)

--
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-12872) Save button doesn't always move to the bottom if the page text length changes

2012-02-23 Thread alexan...@zia.com.br (JIRA)


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

Alexandre Zia commented on JENKINS-12872:
-

I agree, this floating save button annoys more than helps.
Perhaps of not going back the way it where, add a configuration option and let 
user decides whether to use it floating or the way it where before.
thanks

 Save button doesn't always move to the bottom if the page text length changes
 -

 Key: JENKINS-12872
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12872
 Project: Jenkins
  Issue Type: Improvement
  Components: gui
 Environment: Firefox 10.0.2, Windows 7, Jenkins 1.451 
Reporter: Alex Lehmann
Priority: Minor
 Attachments: Config [Jenkins] - Mozilla 
 Firefox_2012-02-23_13-32-46.png


 When a config page is scrolled all the way down, the save button moves to its 
 regular place at the end of the page, when then the text length changes, e.g. 
 by clicking on an Advanced button or a help link, the Save button stays at 
 the same position covering a section of the text in the middle (see 
 screenshot).
 (cosmetic thing, however this quite annoys me when configuring Sonar, which 
 is the last entry on the page usually)

--
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-9937) Rebuild plugin visible to everyone, regardless of project-based matrix security settings.

2012-02-23 Thread felix.bernh...@partner.bmw.de (JIRA)


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

Felix Bernhard commented on JENKINS-9937:
-

When will be a release of this plugin, we would also need this feature.

 Rebuild plugin visible to everyone, regardless of project-based matrix 
 security settings.
 -

 Key: JENKINS-9937
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9937
 Project: Jenkins
  Issue Type: Bug
  Components: rebuild
Affects Versions: current
 Environment: Ubuntu, OS X
Reporter: James Mills
Assignee: ragesh_nair

 Hi.
 I am running Jenkins version 1.414, and I have the rebuild plugin installed.  
 My Jenkins installation is locked down with project-based matrix security, 
 allowing only read access to the anonymous user to both Jenkins and the 
 project.  However, in addition to read access, the anonymous user aso has the 
 full ability to trigger a rebuild using the plugins added rebuild link!
 Is there a way to restrict this link, as I do not want anyone who is not 
 approved to be able to (re)build on this server.
 Thanks!
 ~james

--
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-12877) Problem to configure perforce plugin and maven release plugin

2012-02-23 Thread h.lassi...@gmail.com (JIRA)

Hugo Lassiège created JENKINS-12877:
---

 Summary: Problem to configure perforce plugin and maven release 
plugin
 Key: JENKINS-12877
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12877
 Project: Jenkins
  Issue Type: Bug
  Components: perforce, release
Affects Versions: current
 Environment: unix (centos)
jenkins 1.447
perforce plugin 1.3.7
jenkins maven release plugin 0.9.0
Reporter: Hugo Lassiège
Assignee: Peter Hayes


Hi,

I try to use jenkins maven release plugin on Jenkins with a perforce SCM.

However, I have a weird error. In debug mode I see the following messages :

[DEBUG] SCM path in pom: //depot/AirTravelServer/main/
[DEBUG] Executing: /bin/sh -c p4 -p srvpar5p4p01:1992 where 
/home/www-data/.jenkins/jobs/ATS-TRUNK-RELEASE/workspace/pom.xml
[DEBUG] p4 can not support a wide charset unless

and the stacktrace :

{code}
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of 
range: -2
at java.lang.String.substring(String.java:1937)
at 
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:117)
at 
org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:61)
at 
org.apache.maven.scm.provider.perforce.PerforceScmProvider.getRepoPath(PerforceScmProvider.java:466)
at 
org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:57)
at 
org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
at 
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
{code}


The problem is due to : p4 can not support a wide charset unless

I've configured P4CHARSET to utf16le-bom and I've tried several different 
charsets for P4COMMANDCHARSET : winansi, utf8, none


The problem exists only for maven release plugin. I don't have this error with 
mvn install.

Do you know what is the right configuration to make it works ?



--
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-12309) java.lang.reflect.InvocationTargetException - warnings trend by type distribution portlet

2012-02-23 Thread ullrich.haf...@gmail.com (JIRA)


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

Ulli Hafner resolved JENKINS-12309.
---

Resolution: Fixed

 java.lang.reflect.InvocationTargetException - warnings trend by type 
 distribution portlet
 -

 Key: JENKINS-12309
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12309
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-core
Affects Versions: current
 Environment: rhel 5.5
Reporter: Greg Moncreaff
Assignee: Ulli Hafner

 saw this in the jenkins console log while waiting for the warnings trend by 
 type distribution portlet to finish displaying
 INFO: Loaded data file 
 .jenkins/jobs/.../builds/2011-12-22_08-37-34/analysis.xml for build 1
 [webapp 2012/01/05 14:53:46] - Error while serving 
 http://.../view/B.INT/portlet/dashboard_portlet_21//warningsGraph/png
 java.lang.reflect.InvocationTargetException
 at sun.reflect.GeneratedMethodAccessor372.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 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:104)
 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$4.doDispatch(MetaClass.java:196)
 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:234)
 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:234)
 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:249)
 at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
 at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
 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:195)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
 at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
 at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
 at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
 at 
 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
 at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
 at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
 at 
 hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
 at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
 at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
 at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
 at 
 winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
 at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
 at java.lang.Thread.run(Thread.java:662)
 Caused by: winstone.ClientSocketException: Failed

[JIRA] (JENKINS-12877) Problem to configure perforce plugin and maven release plugin

2012-02-23 Thread rob.pe...@gmail.com (JIRA)


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

Rob Petti updated JENKINS-12877:


Component/s: (was: perforce)

This is unrelated to the perforce plugin, and in fact may be unrelated to 
Jenkins at all... It's looks purely like a maven error to me.

 Problem to configure perforce plugin and maven release plugin
 -

 Key: JENKINS-12877
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12877
 Project: Jenkins
  Issue Type: Bug
  Components: release
Affects Versions: current
 Environment: unix (centos)
 jenkins 1.447
 perforce plugin 1.3.7
 jenkins maven release plugin 0.9.0
Reporter: Hugo Lassiège
Assignee: Peter Hayes
  Labels: perforce

 Hi,
 I try to use jenkins maven release plugin on Jenkins with a perforce SCM.
 However, I have a weird error. In debug mode I see the following messages :
 [DEBUG] SCM path in pom: //depot/AirTravelServer/main/
 [DEBUG] Executing: /bin/sh -c p4 -p srvpar5p4p01:1992 where 
 /home/www-data/.jenkins/jobs/ATS-TRUNK-RELEASE/workspace/pom.xml
 [DEBUG] p4 can not support a wide charset unless
 and the stacktrace :
 {code}
 Caused by: java.lang.StringIndexOutOfBoundsException: String index out of 
 range: -2
   at java.lang.String.substring(String.java:1937)
   at 
 org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:117)
   at 
 org.apache.maven.scm.provider.perforce.command.PerforceWhereCommand.getDepotLocation(PerforceWhereCommand.java:61)
   at 
 org.apache.maven.scm.provider.perforce.PerforceScmProvider.getRepoPath(PerforceScmProvider.java:466)
   at 
 org.apache.maven.scm.provider.perforce.command.status.PerforceStatusCommand.executeStatusCommand(PerforceStatusCommand.java:57)
   at 
 org.apache.maven.scm.command.status.AbstractStatusCommand.executeCommand(AbstractStatusCommand.java:44)
   at 
 org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
 {code}
 The problem is due to : p4 can not support a wide charset unless
 I've configured P4CHARSET to utf16le-bom and I've tried several different 
 charsets for P4COMMANDCHARSET : winansi, utf8, none
 The problem exists only for maven release plugin. I don't have this error 
 with mvn install.
 Do you know what is the right configuration to make it works ?

--
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-6965) GT seems to loose it's connection to Gerrit without re-connecting


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

evernat resolved JENKINS-6965.
--

Resolution: Fixed

This issue was fixed a year ago according to the last comment.

 GT seems to loose it's connection to Gerrit without re-connecting
 -

 Key: JENKINS-6965
 URL: https://issues.jenkins-ci.org/browse/JENKINS-6965
 Project: Jenkins
  Issue Type: Bug
  Components: gerrit-trigger
Reporter: antonystubbs
Assignee: rsandell
Priority: Critical

 Haven't managed to catch it in the act yet, but it works really well for a 
 while, then I notice it stops getting triggered. I go into 
 hudson/manage/gerrittrigger and click restart and it seems to connect ok 
 (watching gerrit logs) and it works fine again.
 This has happened consistently since setting it up. Appears to work for just 
 a few hours, before needing a kick up the pants...
 Great work!

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

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

2012-02-23 Thread m...@acronymgames.com (JIRA)


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

Mandeep Rai commented on JENKINS-12730:
---

Reading the Javadoc, it seems like getRootUrlFromRequest ignores the manually 
configured public url, which is why it would redirect from the nice configured 
url (ie: http://builds.mydomain.com/builds) to the proxy'd address instead (ie: 
http://builds-pc-1249:8001/builds)

May I suggest to using getRootUrl() instead, which does use the configured url, 
instead of trying to glean it from the request, which may pass through a proxy 
server?

 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-8860) Views select list sorting should be case-insensitive


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

evernat commented on JENKINS-8860:
--

@Rob
For me, this issue is currently fixed (using Jenkins v1.446).
Do you confirm that?

 Views select list sorting should be case-insensitive
 

 Key: JENKINS-8860
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8860
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: Rob Hruska
Priority: Minor

 In the views select list, the sort order is currently case-sensitive. For 
 example, the following entries would currently be sorted:
 Alpha
 Beta
 Gamma
 aardvark
 gorilla
 Where the ideal sorting would be:
 aardvark
 Alpha
 Beta
 Gamma
 gorilla
 The list should have a natural sort order that is case insensitive.
 It should be noted that case-insensitive ordering is Jenkins' behavior by 
 default when displaying tabs, so the current behavior of the select list 
 differs from that of Jenkins. Ultimately, the sorting should match how 
 Jenkins orders the tabs when the plugin is not installed.

--
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-12730) Going to pages via global shortcuts doesn't use the current url/url set in config


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

SCM/JIRA link daemon resolved JENKINS-12730.


Resolution: Fixed

 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

2012-02-23 Thread dogf...@java.net (JIRA)


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

dogfood commented on JENKINS-12730:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_keyboard-shortcuts 
#19|http://ci.jenkins-ci.org/job/plugins_keyboard-shortcuts/19/]
 [FIXED JENKINS-12730] rootUrl vs rootUrlFromRequest -- rev. proxies 
(Revision 81c894d6ca46e678304613fe8efb1842c1708dc3)

 Result = SUCCESS
Jesse Farinacci : 
Files : 
* 
src/main/java/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator.java


 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-12730) Going to pages via global shortcuts doesn't use the current url/url set in config


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

SCM/JIRA link daemon commented on JENKINS-12730:


Code changed in jenkins
User: Jesse Farinacci
Path:
 
src/main/java/org/jenkins/ci/plugins/keyboard_shortcuts/KeyboardShortcutsPageDecorator.java
http://jenkins-ci.org/commit/keyboard-shortcuts-plugin/81c894d6ca46e678304613fe8efb1842c1708dc3
Log:
  [FIXED JENKINS-12730] rootUrl vs rootUrlFromRequest -- rev. proxies






 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-8860) Views select list sorting should be case-insensitive

2012-02-23 Thread robhru...@gmail.com (JIRA)

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

Rob Hruska edited comment on JENKINS-8860 at 2/23/12 5:15 PM:
--

Added a new view in Jenkins 1.451 to test whether or not issue was fixed.

The new view, titled lowercase, ought to have been inserted after the two
existing uppercase Li... items, but instead was added after all of the
uppercase items in the list.

I attached a screenshot.

was (Author: robhruska):
Added a new view in Jenkins 1.451 to test whether or not issue was fixed.

The new view, titled lowercase, ought to have been inserted after the two
existing uppercase Li... items, but instead was added after all of the
uppercase items in the list.

Views select list sorting should be case-insensitive

Key: JENKINS-8860
URL: https://issues.jenkins-ci.org/browse/JENKINS-8860
Project: Jenkins
Issue Type: Bug
Components: core
Affects Versions: current
Reporter: Rob Hruska
Priority: Minor
Attachments: screenshot-1.jpg

In the views select list, the sort order is currently case-sensitive. For
example, the following entries would currently be sorted:
Alpha
Beta
Gamma
aardvark
gorilla
Where the ideal sorting would be:
aardvark
Alpha
Beta
Gamma
gorilla
The list should have a natural sort order that is case insensitive.
It should be noted that case-insensitive ordering is Jenkins' behavior by
default when displaying tabs, so the current behavior of the select list
differs from that of Jenkins. Ultimately, the sorting should match how
Jenkins orders the tabs when the plugin is not installed.

[JIRA] (JENKINS-8860) Views select list sorting should be case-insensitive

2012-02-23 Thread robhru...@gmail.com (JIRA)


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

Rob Hruska updated JENKINS-8860:


Attachment: screenshot-1.jpg

Added a new view in Jenkins 1.451 to test whether or not issue was fixed.

The new view, titled lowercase, ought to have been inserted after the two 
existing uppercase Li... items, but instead was added after all of the 
uppercase items in the list.

 Views select list sorting should be case-insensitive
 

 Key: JENKINS-8860
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8860
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
Reporter: Rob Hruska
Priority: Minor
 Attachments: screenshot-1.jpg


 In the views select list, the sort order is currently case-sensitive. For 
 example, the following entries would currently be sorted:
 Alpha
 Beta
 Gamma
 aardvark
 gorilla
 Where the ideal sorting would be:
 aardvark
 Alpha
 Beta
 Gamma
 gorilla
 The list should have a natural sort order that is case insensitive.
 It should be noted that case-insensitive ordering is Jenkins' behavior by 
 default when displaying tabs, so the current behavior of the select list 
 differs from that of Jenkins. Ultimately, the sorting should match how 
 Jenkins orders the tabs when the plugin is not installed.

--
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-12730) Going to pages via global shortcuts doesn't use the current url/url set in config

2012-02-23 Thread jie...@java.net (JIRA)


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

jieryn commented on JENKINS-12730:
--

Mandeep: Would you please try to run with this updated hpi?

http://ci.jenkins-ci.org/job/plugins_keyboard-shortcuts/19/org.jenkins-ci.plugins$keyboard-shortcuts-plugin/artifact/org.jenkins-ci.plugins/keyboard-shortcuts-plugin/1.1-SNAPSHOT/keyboard-shortcuts-plugin-1.1-SNAPSHOT.hpi

Let me know if it works for you, if it does, I will push out a 1.1 release 
incorporating it..

 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-12865) [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger

2012-02-23 Thread brad_hugg...@intuit.com (JIRA)


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

Brad Huggins reopened JENKINS-12865:



Still receiving the same error with 0.27

 [ERROR] - SEVERE - Polling error Current Project is null from FSTrigger
 ---

 Key: JENKINS-12865
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12865
 Project: Jenkins
  Issue Type: Bug
  Components: fstrigger
Affects Versions: current
 Environment: Linux master (console only no jobs process on it) and a 
 Windows slave
Reporter: Brad Huggins
Assignee: gbois
Priority: Blocker
 Attachments: Output-IUS.xml


 I receive the following error when FSTrigger attempts to poll:
 [FSTrigger] - Monitor files
 Polling for the job Output-ICA
 Polling remotely on *
 Polling started on Feb 22, 2012 5:58:09 PM
 [ERROR] - SEVERE - Polling error Current Project is null
 I have attached the configuration file though I scrubbed the server name from 
 it.  I have tried using \ or / even no path with the same error.  

--
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-8839) Failed to load hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl


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

evernat commented on JENKINS-8839:
--

I suppose that @Extension(optional = true) could fix this for the emma plugin 
(and for the cobertura plugin which has the same issue).

See
http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/493773519b31f5df
and
https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet.java


 Failed to load 
 hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl
 -

 Key: JENKINS-8839
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8839
 Project: Jenkins
  Issue Type: Bug
  Components: emma
 Environment: Emmap Plugin 1.24
 Jenkins 1.397
 Dashboard plugin not installed
Reporter: sogabe
Assignee: Kohsuke Kawaguchi

 I got the following exception.
 {code}
 2011/02/21 23:05:07 hudson.ExtensionFinder$Sezpoz find
 警告: Failed to load 
 hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl
 java.lang.InstantiationException: java.lang.NoClassDefFoundError: 
 hudson/plugins/view/dashboard/DashboardPortlet
   at net.java.sezpoz.IndexItem.instance(IndexItem.java:180)
   at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:180)
   at hudson.ExtensionFinder._find(ExtensionFinder.java:94)
   at hudson.ExtensionList.load(ExtensionList.java:261)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:218)
   at hudson.ExtensionList.getComponents(ExtensionList.java:126)
   at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:155)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:218)
   at hudson.ExtensionList.iterator(ExtensionList.java:115)
   at 
 org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
   at 
 org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
   at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
   at 
 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:63)
   at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
   at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
   at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:72)
   at 
 org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:114)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:551)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:478)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:160)
   at javax.servlet.http.HttpServlet.service(Unknown Source)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown 
 Source)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown 
 Source)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:157)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131)
   at 
 net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:82)
   at 
 org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:69)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown 
 Source)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown 
 Source)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at

[JIRA] (JENKINS-8839) Failed to load hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl


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

evernat edited comment on JENKINS-8839 at 2/23/12 6:06 PM:
---

I suppose that @Extension(optional = true) could fix this for the emma plugin 
(and for the cobertura plugin which has the same issue: JENKINS-11398).

See
http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/493773519b31f5df
and
https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet.java


  was (Author: evernat):
I suppose that @Extension(optional = true) could fix this for the emma 
plugin (and for the cobertura plugin which has the same issue).

See
http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/493773519b31f5df
and
https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet.java

  
 Failed to load 
 hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl
 -

 Key: JENKINS-8839
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8839
 Project: Jenkins
  Issue Type: Bug
  Components: emma
 Environment: Emmap Plugin 1.24
 Jenkins 1.397
 Dashboard plugin not installed
Reporter: sogabe
Assignee: Kohsuke Kawaguchi

 I got the following exception.
 {code}
 2011/02/21 23:05:07 hudson.ExtensionFinder$Sezpoz find
 警告: Failed to load 
 hudson.plugins.emma.portlet.chart.EmmaBuilderTrendChart$DescriptorImpl
 java.lang.InstantiationException: java.lang.NoClassDefFoundError: 
 hudson/plugins/view/dashboard/DashboardPortlet
   at net.java.sezpoz.IndexItem.instance(IndexItem.java:180)
   at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:180)
   at hudson.ExtensionFinder._find(ExtensionFinder.java:94)
   at hudson.ExtensionList.load(ExtensionList.java:261)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:218)
   at hudson.ExtensionList.getComponents(ExtensionList.java:126)
   at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:155)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:218)
   at hudson.ExtensionList.iterator(ExtensionList.java:115)
   at 
 org.apache.commons.jelly.expression.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101)
   at 
 org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
   at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
   at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
   at 
 org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:63)
   at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
   at 
 org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
   at 
 org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:72)
   at 
 org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:114)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:551)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:478)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:160)
   at javax.servlet.http.HttpServlet.service(Unknown Source)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Unknown 
 Source)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(Unknown 
 Source)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:157)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131)
   at 
 net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:82)
   at

[JIRA] (JENKINS-11398) Cobertura gives LinkageError in new Jenkins version


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

evernat edited comment on JENKINS-11398 at 2/23/12 6:06 PM:


it's the same with the emma plugin: JENKINS-8839

  was (Author: evernat):
it's the same with the emma plugin
  
 Cobertura gives LinkageError in new Jenkins version
 ---

 Key: JENKINS-11398
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11398
 Project: Jenkins
  Issue Type: Bug
  Components: cobertura
Affects Versions: current
 Environment: Suse linux desktop 10.2 (64-bit), Jenkins 1.434
 CentOS release 5.4 (64-bit), Jenkins 1.444-1.1
Reporter: Angela Johansson
Assignee: stephenconnolly

 After upgrading Jenkins to 1.434, I get the following error during Jenkins 
 startup:
 {code}
 WARNING: Failed to load 
 hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl
 java.lang.LinkageError: Failed to resolve class 
 hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder$SezpozModule.resolve(ExtensionFinder.java:294)
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder$SezpozModule.configure(ExtensionFinder.java:325)
   at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
   at 
 com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
   at com.google.inject.spi.Elements.getElements(Elements.java:101)
   at 
 com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
   at 
 com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
   at com.google.inject.Guice.createInjector(Guice.java:95)
   at com.google.inject.Guice.createInjector(Guice.java:72)
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder.init(ExtensionFinder.java:180)
   at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:149)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
 Source)
   at java.lang.reflect.Constructor.newInstance(Unknown Source)
   at java.lang.Class.newInstance0(Unknown Source)
   at java.lang.Class.newInstance(Unknown Source)
   at net.java.sezpoz.IndexItem.instance(IndexItem.java:181)
   at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:399)
   at hudson.ExtensionFinder._find(ExtensionFinder.java:110)
   at 
 hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:285)
   at hudson.ExtensionList.load(ExtensionList.java:258)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:229)
   at hudson.ExtensionList.iterator(ExtensionList.java:136)
   at 
 hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:278)
   at hudson.ExtensionList.load(ExtensionList.java:258)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:229)
   at hudson.ExtensionList.iterator(ExtensionList.java:136)
   at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1085)
   at 
 hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100)
   at 
 hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35)
   at hudson.PluginManager$2$1$2.run(PluginManager.java:306)
   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$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.lang.TypeNotPresentException: Type 
 hudson.plugins.view.dashboard.DashboardPortlet not present
   at 
 sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(Unknown 
 Source)
   at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Unknown 
 Source)
   at sun.reflect.generics.tree.ClassTypeSignature.accept(Unknown Source)
   at sun.reflect.generics.visitor.Reifier.reifyTypeArguments(Unknown 
 Source)
   at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Unknown 
 Source)
   at sun.reflect.generics.tree.ClassTypeSignature.accept(Unknown Source)
   at

[JIRA] (JENKINS-11398) Cobertura gives LinkageError in new Jenkins version


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

evernat commented on JENKINS-11398:
---

I suppose that @Extension(optional = true) could fix this for the cobertura and 
the emma plugins.

See
http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/493773519b31f5df
and
https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/java/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet.java


 Cobertura gives LinkageError in new Jenkins version
 ---

 Key: JENKINS-11398
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11398
 Project: Jenkins
  Issue Type: Bug
  Components: cobertura
Affects Versions: current
 Environment: Suse linux desktop 10.2 (64-bit), Jenkins 1.434
 CentOS release 5.4 (64-bit), Jenkins 1.444-1.1
Reporter: Angela Johansson
Assignee: stephenconnolly

 After upgrading Jenkins to 1.434, I get the following error during Jenkins 
 startup:
 {code}
 WARNING: Failed to load 
 hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl
 java.lang.LinkageError: Failed to resolve class 
 hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder$SezpozModule.resolve(ExtensionFinder.java:294)
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder$SezpozModule.configure(ExtensionFinder.java:325)
   at com.google.inject.AbstractModule.configure(AbstractModule.java:59)
   at 
 com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:223)
   at com.google.inject.spi.Elements.getElements(Elements.java:101)
   at 
 com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:133)
   at 
 com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:103)
   at com.google.inject.Guice.createInjector(Guice.java:95)
   at com.google.inject.Guice.createInjector(Guice.java:72)
   at 
 hudson.ExtensionFinder$AbstractGuiceFinder.init(ExtensionFinder.java:180)
   at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:149)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown 
 Source)
   at java.lang.reflect.Constructor.newInstance(Unknown Source)
   at java.lang.Class.newInstance0(Unknown Source)
   at java.lang.Class.newInstance(Unknown Source)
   at net.java.sezpoz.IndexItem.instance(IndexItem.java:181)
   at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:399)
   at hudson.ExtensionFinder._find(ExtensionFinder.java:110)
   at 
 hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:285)
   at hudson.ExtensionList.load(ExtensionList.java:258)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:229)
   at hudson.ExtensionList.iterator(ExtensionList.java:136)
   at 
 hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:278)
   at hudson.ExtensionList.load(ExtensionList.java:258)
   at hudson.ExtensionList.ensureLoaded(ExtensionList.java:229)
   at hudson.ExtensionList.iterator(ExtensionList.java:136)
   at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1085)
   at 
 hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100)
   at 
 hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35)
   at hudson.PluginManager$2$1$2.run(PluginManager.java:306)
   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$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: java.lang.TypeNotPresentException: Type 
 hudson.plugins.view.dashboard.DashboardPortlet not present
   at 
 sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(Unknown 
 Source)
   at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Unknown 
 Source)
   at sun.reflect.generics.tree.ClassTypeSignature.accept(Unknown Source)
   at sun.reflect.generics.visitor.Reifier.reifyTypeArguments(Unknown 
 Source)
   at

[JIRA] (JENKINS-12730) Going to pages via global shortcuts doesn't use the current url/url set in config


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

SCM/JIRA link daemon commented on JENKINS-12730:


Code changed in jenkins
User: Jesse Farinacci
Path:
 src/main/webapp/js/keyboard-shortcuts.js
http://jenkins-ci.org/commit/keyboard-shortcuts-plugin/7189d9cb9dd5db5dfde666f2b7528e12486fe9d3
Log:
  [JENKINS-12730] redundant / in set window location href






 Going to pages via global shortcuts doesn't use the current url/url set in 
 config
 -

 Key: JENKINS-12730
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12730
 Project: Jenkins
  Issue Type: Bug
  Components: keyboard-shortcuts
Affects Versions: current
Reporter: Mandeep Rai
Assignee: jieryn

 I have my jenkins running on port 8001 (ie: http://builds:8001) using a 
 prefix of builds (ie: http://builds:8001/builds).
 I also have an Apache instance that is forwarding from port 80 to jenkins 
 (ie: http://builds.mydomain.com/builds).
 In the jenkins main config, I have the Jenkins URL in the system config set 
 to the proper apache forwarded address (ie: 
 http://builds.mydomain.com/builds), as is the JENKINS_URL.
 If I use the keyboard shortcut to go to a job, instead of 
 http://builds.mydomain.com/builds/job/job, it goes to 
 http://builds:8001/builds/job/job, and as a result of the url change, I am 
 no longer logged in, unless I manually change the host in the location bar 
 from builds:8001 to builds.mydomain.com

--
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-12879) Verion 1.27 does not work with Tool Environment plugin

2012-02-23 Thread florian.zscho...@cycos.com (JIRA)

Florian Zschocke created JENKINS-12879:
--

 Summary: Verion 1.27 does not work with Tool Environment plugin
 Key: JENKINS-12879
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12879
 Project: Jenkins
  Issue Type: Bug
  Components: envinject
Affects Versions: current
Reporter: Florian Zschocke
Assignee: gbois


We use the Tool Environment Plugin to set environment variables with path for 
tools. We used the SetEnv plugin before together with the TE plugin and the 
tool environment variables could be used in the SetEnv configuration. This does 
not work with the EnvInject plugin, which is supposed to replace the SetEnv 
plugin.

Configuration:
We have tool environment variables
MAVEN_2_2_1_HOME
JAVA_IBM_60_81_HOME
ANT_1_6_5_HOME


The SetEnv plugin set the environment for a build using these:
PROJECT_TOP=${WORKSPACE}
PROJECT_BUILD=$PROJECT_TOP/build
PROJECT_RES=$PROJECT_TOP/delivery
PROJECT_SRC=$PROJECT_TOP

JAVA_HOME=${JAVA_IBM_60_81_HOME}

PATH=${JAVA_HOME}/bin:${MAVEN_2_2_1_HOME}/bin:${ANT_1_6_5_HOME}/bin:$PATH

This would work.

Using the EnvInject plugin on a new Jenksin 1.451 installation, I was so far 
not able to find any configuration which would work. The EnvInject plugin does 
not see the tool environment variables, or the PATH variable. This are the 
results:

[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties content 
BRANCH=trunk
PROJECT_TOP=${WORKSPACE}
PROJECT_BUILD=$PROJECT_TOP/build
PROJECT_RES=$PROJECT_TOP/delivery
PROJECT_SRC=$PROJECT_TOP
JAVA_HOME=${JAVA_IBM_60_81_HOME}
PATH=${JAVA_HOME}/bin:${MAVEN_2_2_1_HOME}/bin:${ANT_1_6_5_HOME}/bin:$PATH

[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'JAVA_HOME' variable.
[EnvInject] - Unset unresolved 'PATH' variable.
Setting ANT_1_6_5_HOME=/data/sourcecode/cbe-tools/ant/1.6.5
Setting MAVEN_2_2_1_HOME=/data/sourcecode/cbe-tools/maven/2.2.1
Setting JAVA_IBM_60_81_HOME=/data/build-env/java/ibm-java2-i386-6.0.8.1




or:

[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Executing and processing the following script content: 
BRANCH=trunk

PROJECT_TOP=${WORKSPACE}
PROJECT_BUILD=$PROJECT_TOP/build
PROJECT_RES=$PROJECT_TOP/delivery
PROJECT_SRC=$PROJECT_TOP

JAVA_HOME=${JAVA_IBM_60_81_HOME}

PATH=${JAVA_HOME}/bin:${MAVEN_2_2_1_HOME}/bin:${ANT_1_6_5_HOME}/bin:$PATH

[hourly] $ /bin/sh -xe /tmp/hudson6496656756456228415.sh
+ BRANCH=trunk
+ PROJECT_TOP=/data/sourcecode/domain/trunk/hourly
+ PROJECT_BUILD=/data/sourcecode/domain/trunk/hourly/build
+ PROJECT_RES=/data/sourcecode/domain/trunk/hourly/delivery
+ PROJECT_SRC=/data/sourcecode/domain/trunk/hourly
+ JAVA_HOME=
+ 
PATH=/bin:/bin:/bin:/data/build-env/java/ibm-java2-i386-6.0.8.1/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin
[EnvInject] - Script executed successfully.
Setting ANT_1_6_5_HOME=/data/sourcecode/cbe-tools/ant/1.6.5
Setting MAVEN_2_2_1_HOME=/data/sourcecode/cbe-tools/maven/2.2.1
Setting JAVA_IBM_60_81_HOME=/data/build-env/java/ibm-java2-i386-6.0.8.1



This came closest, but the PATH variable cannot be seen:

[EnvInject] - Injecting environment variables from a build step.
Setting ANT_1_6_5_HOME=/data/sourcecode/cbe-tools/ant/1.6.5
Setting MAVEN_2_2_1_HOME=/data/sourcecode/cbe-tools/maven/2.2.1
Setting JAVA_IBM_60_81_HOME=/data/build-env/java/ibm-java2-i386-6.0.8.1
[EnvInject] - Injecting as environment variables the properties content 
BRANCH=trunk
PROJECT_TOP=${WORKSPACE}
PROJECT_BUILD=$PROJECT_TOP/build
PROJECT_RES=$PROJECT_TOP/delivery
PROJECT_SRC=$PROJECT_TOP
JAVA_HOME=${JAVA_IBM_60_81_HOME}
PATH=${JAVA_HOME}/bin:${MAVEN_2_2_1_HOME}/bin:${ANT_1_6_5_HOME}/bin:$PATH

[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'PATH' variable.
Setting ANT_1_6_5_HOME=/data/sourcecode/cbe-tools/ant/1.6.5
Setting MAVEN_2_2_1_HOME=/data/sourcecode/cbe-tools/maven/2.2.1
Setting JAVA_IBM_60_81_HOME=/data/build-env/java/ibm-java2-i386-6.0.8.1

--
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-8634) VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1


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

Lars Gregori commented on JENKINS-8634:
---

Version 0.4.4 available as official plugin. This version integrates Virtualbox 
3.x, 4.0 and 4.1.

 VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1
 

 Key: JENKINS-8634
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8634
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Windows XP 32bit (and highly likely any other 
 environment)
Reporter: Michael Mzik
Assignee: godin
Priority: Blocker

 Upgrading VirtualBox from the former version 3.2 to 4.0.2 broke the 
 virtualbox-plugin. To be more precise, the plugin can no longer connect to 
 the virtualbox-cloud using the http server (vboxwebsrv).
 The virtualbox-webserver is started with:
 1) VBoxManage setproperty websrvauthlibrary null
 2) vboxwebsrv
 When testing the connection to the cloud from inside Hudson system-settings, 
 the following error messages is printed:
 HTTP transport error: java.net.ConnectException: Connection refused: connect
 And the main Hudson log shows no exception dump or whatsoever, only the INFO 
 message:
 INFO: Testing connection to http://csgwfcl185:18083/virtualbox with username 
 CISystem
 Instead when trying to startup a slave-node explictly, the following 
 exception-dump is printed:
 FATAL: HTTP transport error: java.net.ConnectException: Connection refused: 
 connect
 com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport 
 error: java.net.ConnectException: Connection refused: connect
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:121)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:142)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83)
   at 
 com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:105)
   at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
   at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
   at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
   at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428)
   at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211)
   at 
 com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
   at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
   at $Proxy47.iWebsessionManagerLogon(Unknown Source)
   at 
 com.sun.xml.ws.commons.virtualbox_3_1.IWebsessionManager.logon(IWebsessionManager.java:255)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.connect(VirtualBoxUtils.java:29)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.getMachines(VirtualBoxUtils.java:39)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.retrieveMachines(VirtualBoxCloud.java:56)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.getVirtualMachines(VirtualBoxCloud.java:61)
   at 
 hudson.plugins.virtualbox.VirtualBoxPlugin.getVirtualBoxMachine(VirtualBoxPlugin.java:94)
   at 
 hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:40)
   at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:184)
   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)
 Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:529)
   at java.net.Socket.connect(Socket.java:478)
   at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
   at

[JIRA] (JENKINS-8634) VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1


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

Lars Gregori reassigned JENKINS-8634:
-

Assignee: Lars Gregori  (was: godin)

 VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1
 

 Key: JENKINS-8634
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8634
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Windows XP 32bit (and highly likely any other 
 environment)
Reporter: Michael Mzik
Assignee: Lars Gregori
Priority: Blocker

 Upgrading VirtualBox from the former version 3.2 to 4.0.2 broke the 
 virtualbox-plugin. To be more precise, the plugin can no longer connect to 
 the virtualbox-cloud using the http server (vboxwebsrv).
 The virtualbox-webserver is started with:
 1) VBoxManage setproperty websrvauthlibrary null
 2) vboxwebsrv
 When testing the connection to the cloud from inside Hudson system-settings, 
 the following error messages is printed:
 HTTP transport error: java.net.ConnectException: Connection refused: connect
 And the main Hudson log shows no exception dump or whatsoever, only the INFO 
 message:
 INFO: Testing connection to http://csgwfcl185:18083/virtualbox with username 
 CISystem
 Instead when trying to startup a slave-node explictly, the following 
 exception-dump is printed:
 FATAL: HTTP transport error: java.net.ConnectException: Connection refused: 
 connect
 com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport 
 error: java.net.ConnectException: Connection refused: connect
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:121)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:142)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83)
   at 
 com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:105)
   at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
   at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
   at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
   at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428)
   at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211)
   at 
 com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
   at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
   at $Proxy47.iWebsessionManagerLogon(Unknown Source)
   at 
 com.sun.xml.ws.commons.virtualbox_3_1.IWebsessionManager.logon(IWebsessionManager.java:255)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.connect(VirtualBoxUtils.java:29)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.getMachines(VirtualBoxUtils.java:39)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.retrieveMachines(VirtualBoxCloud.java:56)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.getVirtualMachines(VirtualBoxCloud.java:61)
   at 
 hudson.plugins.virtualbox.VirtualBoxPlugin.getVirtualBoxMachine(VirtualBoxPlugin.java:94)
   at 
 hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:40)
   at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:184)
   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)
 Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:529)
   at java.net.Socket.connect(Socket.java:478)
   at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
   at sun.net.www.http.HttpClient.init(HttpClient.java:233)

[JIRA] (JENKINS-8634) VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1


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

Lars Gregori resolved JENKINS-8634.
---

Fix Version/s: current
   Resolution: Fixed

Version 0.4.4 is official available and integrates VirtualBox 3.x, 4.0 and 4.1.

 VirtualBox 4.0.2 web-server became incompatible with virtualbox plugin 0.2.1
 

 Key: JENKINS-8634
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8634
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Windows XP 32bit (and highly likely any other 
 environment)
Reporter: Michael Mzik
Assignee: Lars Gregori
Priority: Blocker
 Fix For: current


 Upgrading VirtualBox from the former version 3.2 to 4.0.2 broke the 
 virtualbox-plugin. To be more precise, the plugin can no longer connect to 
 the virtualbox-cloud using the http server (vboxwebsrv).
 The virtualbox-webserver is started with:
 1) VBoxManage setproperty websrvauthlibrary null
 2) vboxwebsrv
 When testing the connection to the cloud from inside Hudson system-settings, 
 the following error messages is printed:
 HTTP transport error: java.net.ConnectException: Connection refused: connect
 And the main Hudson log shows no exception dump or whatsoever, only the INFO 
 message:
 INFO: Testing connection to http://csgwfcl185:18083/virtualbox with username 
 CISystem
 Instead when trying to startup a slave-node explictly, the following 
 exception-dump is printed:
 FATAL: HTTP transport error: java.net.ConnectException: Connection refused: 
 connect
 com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport 
 error: java.net.ConnectException: Connection refused: connect
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:121)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:142)
   at 
 com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:83)
   at 
 com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:105)
   at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
   at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
   at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
   at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:428)
   at com.sun.xml.internal.ws.client.Stub.process(Stub.java:211)
   at 
 com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:124)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:98)
   at 
 com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
   at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
   at $Proxy47.iWebsessionManagerLogon(Unknown Source)
   at 
 com.sun.xml.ws.commons.virtualbox_3_1.IWebsessionManager.logon(IWebsessionManager.java:255)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.connect(VirtualBoxUtils.java:29)
   at 
 hudson.plugins.virtualbox.VirtualBoxUtils.getMachines(VirtualBoxUtils.java:39)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.retrieveMachines(VirtualBoxCloud.java:56)
   at 
 hudson.plugins.virtualbox.VirtualBoxCloud.getVirtualMachines(VirtualBoxCloud.java:61)
   at 
 hudson.plugins.virtualbox.VirtualBoxPlugin.getVirtualBoxMachine(VirtualBoxPlugin.java:94)
   at 
 hudson.plugins.virtualbox.VirtualBoxComputerLauncher.launch(VirtualBoxComputerLauncher.java:40)
   at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:184)
   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)
 Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:529)
   at java.net.Socket.connect(Socket.java:478)
   at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
   at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)

[JIRA] (JENKINS-8103) VirtualBox plugin stopped working in recent hudson and/or VirtualBox update


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

Lars Gregori reassigned JENKINS-8103:
-

Assignee: Lars Gregori  (was: godin)

 VirtualBox plugin stopped working in recent hudson and/or VirtualBox update
 ---

 Key: JENKINS-8103
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8103
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Linux host with latest Hudson and VirtualBox (64bit)
Reporter: psoetens
Assignee: Lars Gregori

 This plugin stopped working after a VBox upgrade or (more likely) Hudson 
 upgrade. 
 I can still test the connection in the 'Cloud setup' section, vboxwebsrv logs 
 acknowledge the connection from Hudson and Hudson reports 'Success'. The 
 virtual machine is however not started when it should. It looks like the 
 plugin thinks there are no virtual machines available.
 The dropdown box 'Virtual Machine Name' of the Virtual node's configuration 
 page remains empty, and no messages appear in the vboxwebsrv. It appears like 
 the plugin is no longer called from Hudson (or no longer calls the 
 vboxwebsrv), or that some web page form callback handler is not called.
 It's probably a trivial fix, but the plugin is now clearly broken, while it 
 still worked about two months ago.

--
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-9119) Can not add VirtualBox Cloud


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

Lars Gregori reassigned JENKINS-9119:
-

Assignee: Lars Gregori  (was: godin)

 Can not add VirtualBox Cloud
 

 Key: JENKINS-9119
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9119
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Jenkins 1.403 on Ubuntu x64 Maverick Meerkat (2.6.35-28)
Reporter: mrobinet
Assignee: Lars Gregori
Priority: Blocker
 Fix For: current


 *Steps to reproduce:*
 # Go to Manage Jenkins -- Configure System
 # Under Cloud section, click Add a new cloud and select VirtualBox.
 *Actual behavior:*
 Nothing happens.
 *Expected behavior:*
 VirtualBox cloud configuration should be presented.
 Debugging with FireBug I see the following request comes back as a 404:
 http://myjenkinshost/$stapler/bound/a3961942-2fe9-4571-856e-42a7fa313fea/render?%5B%5D=
 +*Header information:*+
 *Response Headers*
 ServerWinstone Servlet Engine v0.9.10
 Content-Length263
 ConnectionKeep-Alive
 Content-Type  text/html;charset=UTF-8
 Date  Mon, 21 Mar 2011 22:11:11 GMT
 X-Powered-By  Servlet/2.5 (Winstone/0.9.10)
 *Request Headers*
 Host  myjenkinshost
 User-AgentMozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) 
 Gecko/20110303 Ubuntu/10.10 (maverick) Firefox/3.6.15
 Accepttext/javascript, text/html, application/xml, text/xml, */*
 Accept-Language   en-US,en;q=0.7,en;q=0.3
 Accept-Encoding   gzip,deflate
 Accept-CharsetISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive115
 Connectionkeep-alive
 X-Requested-With  XMLHttpRequest
 X-Prototype-Version   1.5.1.1
 Content-Type  application/x-stapler-method-invocation;charset=UTF-8
 Crumb 282e03e6-3f8a-4386-8853-439a80a15a21
 Referer   http://myjenkinshost/jenkins/configure
 Content-Length2
 CookiescreenResolution=1600x1200; Apache=ip; country=US; 
 firstname=Mike; uid=mrobinet; pcn=341

--
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-9119) Can not add VirtualBox Cloud


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

Lars Gregori resolved JENKINS-9119.
---

Fix Version/s: current
   Resolution: Fixed

Updated plugin (version 0.4.4) and works with current Jenkins version (1.451) 
... see also https://issues.jenkins-ci.org/browse/JENKINS-8634

 Can not add VirtualBox Cloud
 

 Key: JENKINS-9119
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9119
 Project: Jenkins
  Issue Type: Bug
  Components: virtualbox
Affects Versions: current
 Environment: Jenkins 1.403 on Ubuntu x64 Maverick Meerkat (2.6.35-28)
Reporter: mrobinet
Assignee: Lars Gregori
Priority: Blocker
 Fix For: current


 *Steps to reproduce:*
 # Go to Manage Jenkins -- Configure System
 # Under Cloud section, click Add a new cloud and select VirtualBox.
 *Actual behavior:*
 Nothing happens.
 *Expected behavior:*
 VirtualBox cloud configuration should be presented.
 Debugging with FireBug I see the following request comes back as a 404:
 http://myjenkinshost/$stapler/bound/a3961942-2fe9-4571-856e-42a7fa313fea/render?%5B%5D=
 +*Header information:*+
 *Response Headers*
 ServerWinstone Servlet Engine v0.9.10
 Content-Length263
 ConnectionKeep-Alive
 Content-Type  text/html;charset=UTF-8
 Date  Mon, 21 Mar 2011 22:11:11 GMT
 X-Powered-By  Servlet/2.5 (Winstone/0.9.10)
 *Request Headers*
 Host  myjenkinshost
 User-AgentMozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) 
 Gecko/20110303 Ubuntu/10.10 (maverick) Firefox/3.6.15
 Accepttext/javascript, text/html, application/xml, text/xml, */*
 Accept-Language   en-US,en;q=0.7,en;q=0.3
 Accept-Encoding   gzip,deflate
 Accept-CharsetISO-8859-1,utf-8;q=0.7,*;q=0.7
 Keep-Alive115
 Connectionkeep-alive
 X-Requested-With  XMLHttpRequest
 X-Prototype-Version   1.5.1.1
 Content-Type  application/x-stapler-method-invocation;charset=UTF-8
 Crumb 282e03e6-3f8a-4386-8853-439a80a15a21
 Referer   http://myjenkinshost/jenkins/configure
 Content-Length2
 CookiescreenResolution=1600x1200; Apache=ip; country=US; 
 firstname=Mike; uid=mrobinet; pcn=341

--
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-12333) OOME/PermGen

2012-02-23 Thread vjura...@java.net (JIRA)


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

vjuranek commented on JENKINS-12333:


any update? Thanks

 OOME/PermGen
 

 Key: JENKINS-12333
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12333
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Debian, 64-bit, 16 GB RAM, 8 processors.
 Jenkins running in Jetty with JAVA_OPTIONS=-Xmx640m -XX:MaxPermSize=128m
 ~250-300 jobs
Reporter: carlspring
Priority: Blocker
  Labels: memory-leak

 The other day I upgraded from Jenkins 1.413 to 1.446. I migrated the data 
 which it reported as old to the new format and upgraded the plugins 
 respectively. All seemed to work fine. Then all of a sudden within an hour or 
 so we hit:
 {code}
 Exception in thread Ping thread for channel 
 hudson.remoting.Channel@5d1dce7a:bud java.lang.OutOfMemoryError: Java heap 
 space
 Exception in thread Thread-109599 java.lang.OutOfMemoryError: Java heap 
 space
 Jan 8, 2012 12:10:19 PM hudson.triggers.SafeTimerTask run
 SEVERE: Timer task hudson.diagnosis.MemoryUsageMonitor@3b9e30a1 failed
 java.lang.OutOfMemoryError: Java heap space
   at hudson.model.TimeSeries.update(TimeSeries.java:74)
   at 
 hudson.model.MultiStageTimeSeries.update(MultiStageTimeSeries.java:118)
   at 
 hudson.diagnosis.MemoryUsageMonitor$MemoryGroup.update(MemoryUsageMonitor.java:95)
   at 
 hudson.diagnosis.MemoryUsageMonitor$MemoryGroup.access$100(MemoryUsageMonitor.java:54)
   at 
 hudson.diagnosis.MemoryUsageMonitor.doRun(MemoryUsageMonitor.java:123)
   at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
   at java.util.TimerThread.mainLoop(Timer.java:512)
   at java.util.TimerThread.run(Timer.java:462)
 2012-01-08 12:25:06.254:WARN::Problem scavenging sessions
 java.lang.OutOfMemoryError: Java heap space
 {code}
 We have the following setup:
 - Linux master (6 executors)
 - 2 linux nodes (4 executors + 8 executors)
 - 2 windows nodes (both running 4 executors)
 We have 250-300 jobs. 90% of them are also producing Sonar reports.
 This totally crashes Jenkins and it is unreachable after the OOME/PermGen.
 Jenkins is running inside a Jetty.
 After hitting this problem, I tried increasing the memory settings of Jetty 
 (which was working fine without any memory settings back in 1.413) to:
 JAVA_OPTIONS=-Xmx640m -XX:MaxPermSize=128m
 This seemed to work. Until it became apparent that it only slowed the 
 re-occurrence of the problem.
 So, I started jstatd and connected via visualvm and saw:
 Permgen: 128m / 90m used.
 OldGen: 426.6m / 426.6 m used
 Please, fix as it's a blocker for us and I now have to resort to rolling back 
 to our last know good version, i.e. 1.413.
 Thanks in advance for looking into this! :)

--
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-1805) ANT task is not killed after build cancel


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

evernat commented on JENKINS-1805:
--

Thanks the ProcessTreeKiller
https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller

This issue can be closed as said in the last comments.

 ANT task is not killed after build cancel
 -

 Key: JENKINS-1805
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1805
 Project: Jenkins
  Issue Type: Bug
  Components: ant
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: 81bas

 If the project build is cancelled via WEB UI then ANT process is still shown 
 in
 OS process list.
 Possible solution: change hudson/tasks/Ant.java, method perform(...):
 ..
 Proc antProc = null;
 try {
antProc = launcher.launch(args.toCommandArray(),env,
   listener.getLogger(),proj.getModuleRoot()); 
int r = antProc.join();
return r==0;
 } catch (InterruptedException ie){
antProc.kill();
 } catch (IOException e) {
 ..
 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-10571) Git Plugin crashes when remote branch gets deleted, and its commit is not available.

2012-02-23 Thread hanrisel...@gmail.com (JIRA)


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

Eugen Paraschiv commented on JENKINS-10571:
---

I am also seeing this. I have just removed a remote branch (directly) and now 
git is failing like this. 
Any progress on this issue?

 Git Plugin crashes when remote branch gets deleted, and its commit is not 
 available.
 

 Key: JENKINS-10571
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10571
 Project: Jenkins
  Issue Type: Bug
  Components: git
Reporter: Rotem Yaari
Assignee: abayer

 I have a repository which Jenkins builds. At some point I added a remote 
 branch, with a certain commit. Jenkins built it successfully (checking it out 
 in the process).
 However, after I deleted the remote branch *without* merging the commit to 
 anywhere (practically throwing it away), Jenkins fails:
 {noformat}
 Checking out Revision eb81dffc5098004d7508aa0ddd398117d9baa524 
 (infinipy/conf, origin/conf)
 FATAL: Could not checkout null with start point 
 eb81dffc5098004d7508aa0ddd398117d9baa524
 hudson.plugins.git.GitException: Could not checkout null with start point 
 eb81dffc5098004d7508aa0ddd398117d9baa524
   at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:831)
   at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1145)
   at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1129)
   at hudson.FilePath.act(FilePath.java:758)
   at hudson.FilePath.act(FilePath.java:740)
   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1129)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1184)
   at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:537)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:425)
   at hudson.model.Run.run(Run.java:1376)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:175)
 Caused by: hudson.plugins.git.GitException: Error performing command: git 
 checkout -f eb81dffc5098004d7508aa0ddd398117d9baa524
 Command git checkout -f eb81dffc5098004d7508aa0ddd398117d9baa524 returned 
 status code 128: fatal: reference is not a tree: 
 eb81dffc5098004d7508aa0ddd398117d9baa524
   at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:744)
   at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:709)
   at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:719)
   at hudson.plugins.git.GitAPI.checkoutBranch(GitAPI.java:818)
   ... 12 more
 Caused by: hudson.plugins.git.GitException: Command git checkout -f 
 eb81dffc5098004d7508aa0ddd398117d9baa524 returned status code 128: fatal: 
 reference is not a tree: eb81dffc5098004d7508aa0ddd398117d9baa524
   at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:739)
   ... 15 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-1805) ANT task is not killed after build cancel