[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann commented on JENKINS-7566 Could you add a verbose option to cli Sorry, I meant that an option should show what the cli is accessing before it is reading the build log or similar things. I think what me confused when I wrote the issue was that the cli doesn't say anything when it starts a build or even when it fails. Currently, failures are reported (connection refused etc), so that is good. I'm not sure if you consider it useful to add a option to reporting something like (starting job foo) when build without -f is giving or similar. If you do not consider this relevant, you can close the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann edited a comment on JENKINS-7566 Could you add a verbose option to cli Sorry, I meant that an option should show what the cli is accessing before it is reading the build log or similar things. I think what me confused when I wrote the issue was that the cli doesn't say anything when it starts a build or even when it fails. Currently, failures are reported (connection refused etc), so that is good. I'm not sure if you consider it useful to add a option to reporting something like (starting job foo) when build without -f is giving or similar. When waiting for start of the job, a message that it is waiting would be nice. If you do not consider this relevant, you can close the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann reopened JENKINS-7566 Could you add a verbose option to cli Change By: Alex Lehmann (25/May/14 2:49 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-7566) Could you add a verbose option to cli
Alex Lehmann commented on JENKINS-7566 Could you add a verbose option to cli That is entirely not what I meant, Jenkins provides a CLI command interface client that can be used to trigger operations from a shell script or manually on the command line https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16979) Discard old builds broken in 1.503
Alex Lehmann commented on JENKINS-16979 Discard old builds broken in 1.503 I noticed the same problem, I assume the old configuration class doesn't migrate the settings to the new one leaving the settings empty. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8019) When hudson is a private build, the version check for plugin updates doesn't work
Alex Lehmann commented on JENKINS-8019 When hudson is a private build, the version check for plugin updates doesnt work The message is still the same, though to reproduce the setup is a bit complicated. When I first install 1.502 and then pin the maven plugin by manually creating the .pinned file then I update to a build of 1.503-SNAPSHOT, the update manager will say that the new plugin version is build for 1.503 or newer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10569) When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times
Alex Lehmann commented on JENKINS-10569 When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times i believe this is not 100% fixed in 1.490, I got one duplicated dependency (though the static analysis plugin is not downloaded for each plugin) http://imgur.com/5EdnY (not quite sure how to attach in image to a comment) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-13304. Resolution: Duplicate unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13304 stopped by Alex Lehmann. unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann closed JENKINS-13304. -- unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161877#comment-161877 ] Alex Lehmann commented on JENKINS-13304: this was fixed by Kohsuke a few days ago independently https://github.com/jenkinsci/jenkins/commit/d98926aebb0859dc63a57283df237fff7fb1f76f unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13401) Provide md5 checksums for updates.jenkins-ci.org download files
Alex Lehmann created JENKINS-13401: -- Summary: Provide md5 checksums for updates.jenkins-ci.org download files Key: JENKINS-13401 URL: https://issues.jenkins-ci.org/browse/JENKINS-13401 Project: Jenkins Issue Type: New Feature Components: www Reporter: Alex Lehmann Priority: Minor following up on a discussion we had on irc, it would be helpful to have md5 checksums for the download files on updates.jenkins-ci.org. if downloading a file fails for some reason, e.g. due to a mirror issue or a timeout, this can be used to verify the file manually. (this could be used by the jenkins application itself to verify file downloads, however for starters, providing just the checksums would be sufficient) -- 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-13401) Provide md5 checksums for updates.jenkins-ci.org download files
[ https://issues.jenkins-ci.org/browse/JENKINS-13401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-13401: --- Summary: Provide md5 checksums for updates.jenkins-ci.org download files (was: Provide md5 checksums for updates.jenkins-ci.org download files) Provide md5 checksums for updates.jenkins-ci.org download files --- Key: JENKINS-13401 URL: https://issues.jenkins-ci.org/browse/JENKINS-13401 Project: Jenkins Issue Type: New Feature Components: www Reporter: Alex Lehmann Priority: Minor following up on a discussion we had on irc, it would be helpful to have md5 checksums for the download files on updates.jenkins-ci.org. if downloading a file fails for some reason, e.g. due to a mirror issue or a timeout, this can be used to verify the file manually. (this could be used by the jenkins application itself to verify file downloads, however for starters, providing just the checksums would be sufficient) -- 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-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-13129. Resolution: Fixed fixed in jenkins_main_trunk#1623 Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup -- Key: JENKINS-13129 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista Reporter: Alex Lehmann Assignee: Alex Lehmann I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. -- 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-13066) unable to update CVS plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-13066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161071#comment-161071 ] Alex Lehmann commented on JENKINS-13066: fixed with issue JENKINS-13129 unable to update CVS plugin --- Key: JENKINS-13066 URL: https://issues.jenkins-ci.org/browse/JENKINS-13066 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins: 1.454 Current CVS version:1.6 Available version:2.0 Reporter: Mingjiang Shi Assignee: Michael Clarke Priority: Blocker Unable to install the new plugin. Once I tried to install it as other plugins and resart Jenkins, cvs plugin version 1.6 is displayed and the button revert to 1.6 is also displayed. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
Alex Lehmann created JENKINS-13304: -- Summary: unset root url causes MalformedURLException in DNSMultiCast Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-13304) unset root url causes MalformedURLException in DNSMultiCast
[ https://issues.jenkins-ci.org/browse/JENKINS-13304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161089#comment-161089 ] Alex Lehmann commented on JENKINS-13304: https://github.com/alexlehm/jenkins/commit/a2284981bc9571b891cf601aa158c91b7db6ba06 [Fixed JENKINS-13304] unset root url causes MalformedURLException in DNSMultiCast skip mdns initialization if rootURL is not set unset root url causes MalformedURLException in DNSMultiCast --- Key: JENKINS-13304 URL: https://issues.jenkins-ci.org/browse/JENKINS-13304 Project: Jenkins Issue Type: Bug Components: core Environment: windows xp, jenkins 1.457 Reporter: Alex Lehmann Priority: Minor when starting jenkins for the first time (or before the config was saved for the first time) then startup messages end with an exception when initializing the mdns service. 01.04.2012 19:29:45 hudson.DNSMultiCast init WARNUNG: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:601) at java.net.URL.init(URL.java:464) at java.net.URL.init(URL.java:413) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) this is in fact a null pointer exception, since rootURL is null when the corresponding config file doesn't exist (Mailer config rootURL) if the files haven't been created yet. This should check for null and simply disable the mdns server I think. -- 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-12585) SECURITY: LDAP authenticated users switch accounts randomly
[ https://issues.jenkins-ci.org/browse/JENKINS-12585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160882#comment-160882 ] Alex Lehmann commented on JENKINS-12585: I forgot to mention yesterday, I compared one jenkins instance with logged-in access only to one that has anonymous, both set a cookie on the start page, the logged-in instance has 403 and no no-cache header, the anonymous instance has Cache-Control: no-cache,must-revalidate. Both looks correct and the static files do not send a set-cookie header. SECURITY: LDAP authenticated users switch accounts randomly --- Key: JENKINS-12585 URL: https://issues.jenkins-ci.org/browse/JENKINS-12585 Project: Jenkins Issue Type: Bug Components: security Affects Versions: current Environment: Mac OSX: 10.6.8 Desktop Java version: 1.6.0_29 Access Control * Security Realm: LDAP * Authorization: Project-based Matrix Authorization Strategy Jenkins: 1.448 Apache * Server version: Apache/2.2.17 (Unix) * Server built: Dec 1 2010 09:58:15 Reporter: guillermo c Assignee: Kohsuke Kawaguchi Priority: Critical Running Jenkins behind Apache: mod_proxy with HTTPS https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache So our setup is Open Directory group jenkins-admin - Jenkins Admins all dev-group-a - Developers can view kick off builds Project-based Matrix Authorization Strategy Admin all checked dev-group-a checked: Overall:Read Job:Read,Build Run:Update dev-group-b checked: Overall:Read Job:Read issue is I'm an admin and random developer will login and see that there user id is mine and can admin jenkins. there has been reported cases that developer A will login and actually be reported by jenkins as Developer B were they can no longer trigger CI builds My biggest concern is when users login and are reporting as admins and have full access to jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160841#comment-160841 ] Alex Lehmann commented on JENKINS-13129: I should note that this is not a specific Windows issue, I have had the same problem with 1.456 on linux as well Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup -- Key: JENKINS-13129 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista Reporter: Alex Lehmann I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. -- 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-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reassigned JENKINS-13129: -- Assignee: Alex Lehmann Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup -- Key: JENKINS-13129 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista Reporter: Alex Lehmann Assignee: Alex Lehmann I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13227) CVS plugin 2.1 does not detect changes
[ https://issues.jenkins-ci.org/browse/JENKINS-13227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160845#comment-160845 ] Alex Lehmann commented on JENKINS-13227: I wonder if if would be possible to set up a mock repository locally to test accessing it during a test case this would require running a cvs pserver locally though CVS plugin 2.1 does not detect changes -- Key: JENKINS-13227 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227 Project: Jenkins Issue Type: Bug Components: cvs Reporter: Guillaume Bilodeau Labels: cvs As presented in the user group: https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4 We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS repository for a few weeks now, without any problems. The CVS plugin (v1.6) was using the local cvsnt install. We've since upgraded the CVS plugin to version 2.1 (by manually pinning the plugin) and since then, CVS changes are not detected. The CVS polling log is triggered properly, tons of cvs rlog instructions are sent, but at the end No changes is displayed. Using CVS plugin 1.6 the cvs polling command looked like this (executed at 5:26:21 PM EDT): cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D Thursday, March 22, 2012 9:26:21 PM UTC Using CVS plugin 2.1, the last cvs checkout command looked like this (executed at 11:56:16 AM EDT): cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 11:56:16 EDT -d portailInt portailInt We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9877) Static Code Analysis Plug-ins is updated between each plug-in update
[ https://issues.jenkins-ci.org/browse/JENKINS-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-9877: -- Environment: linux ubuntu jenkins 1.457 tomcat 7.0.26 was:linux sles jenkins 1.414 tomcat 6.0.32 this still happens in the current jenkins version Static Code Analysis Plug-ins is updated between each plug-in update Key: JENKINS-9877 URL: https://issues.jenkins-ci.org/browse/JENKINS-9877 Project: Jenkins Issue Type: Bug Components: plugin Environment: linux ubuntu jenkins 1.457 tomcat 7.0.26 Reporter: Alex Lehmann Priority: Minor Fix For: current Attachments: screenshot-1.jpg When updating plug-ins today, I got the Static Code Analysis plug-in each time another plugin is listed for update (see attached screenshot) This includes the plug-ins that depend on it as well as the ones that don't (cvs plugin) -- 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-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[ https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann reopened JENKINS-12104: issue is still present or appeared again in 2.1 cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch) -- Key: JENKINS-12104 URL: https://issues.jenkins-ci.org/browse/JENKINS-12104 Project: Jenkins Issue Type: Bug Components: cvs Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6 Reporter: Alex Lehmann Assignee: Michael Clarke Priority: Minor Fix For: current When checking out a cvs repository with Branch and Use HEAD revision if tag not found, the Changes list is always empty even though the build was triggered by scm changes that are picked up the by cvs update in the build log. Since the use Head function was introduced by me in 1.5, maybe the update check is broken in a way I didn't notice, I will try to fix 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-12104) cvs-plugin doesn't catch file changes if the files are checked out with -f -r (HEAD or branch)
[
https://issues.jenkins-ci.org/browse/JENKINS-12104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160869#comment-160869
]
Alex Lehmann edited comment on JENKINS-12104 at 3/27/12 9:43 PM:
-
$ cvs rlog -d14 Feb 2012 09:26:21 +010027 Mar 2012 12:00:00 +0100 -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
cvstest
=
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
was (Author: alexlehm):
{{monospaced}}
$ cvs rlog -d14 Feb 2012 09:26:21 +010027 Mar 2012 12:00:00 +0100 -S
-rBRANCHTEST home/lehmann/cvstest
cvs rlog: Logging home/lehmann/cvstest
RCS file: /usr/local/cvsroot/home/lehmann/cvstest/branch1,v
head: 1.3
branch:
locks: strict
access list:
symbolic names:
BRANCHTEST: 1.1.0.2
keyword substitution: kv
total revisions: 6; selected revisions: 1
description:
revision 1.1.2.3
date: 2012-03-21 11:37:34 +0100; author: lehmann; state: Exp; lines: +3 -1;
commitid: 100d4f69af6e4567;
cvstest
=
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file1,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file2,v'
cvs rlog: warning: no revision `BRANCHTEST' in
`/usr/local/cvsroot/home/lehmann/cvstest/file3,v'
{{monospaced}}
cvs-plugin doesn't catch file changes if the files are checked out with -f -r
(HEAD or branch)
--
Key: JENKINS-12104
URL: https://issues.jenkins-ci.org/browse/JENKINS-12104
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: suse linux, java 1.6.0-30, Jenkins 1.443, cvs-plugin 1.6
Reporter: Alex Lehmann
Assignee: Michael Clarke
Priority: Minor
Fix For: current
When checking out a cvs repository with Branch and Use HEAD revision if tag
not found, the Changes list is always empty even though the build was
triggered by scm changes that are picked up the by cvs update in the build
log.
Since the use Head function was introduced by me in 1.5, maybe the update
check is broken in a way I didn't notice, I will try to fix 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-13169) Dropdown menu hides tooltips
Alex Lehmann created JENKINS-13169: -- Summary: Dropdown menu hides tooltips Key: JENKINS-13169 URL: https://issues.jenkins-ci.org/browse/JENKINS-13169 Project: Jenkins Issue Type: Bug Components: gui Environment: jenkins 1.456, firefox 11, windows 7 Reporter: Alex Lehmann Priority: Minor Attachments: tooltips.png When hovering the mouse over a built queue entry, first the tool tip shows and the dropdown menu which covers the tool tip partially -- 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-13082) Breadcrumb popup menu gives javascript error on Internet Explorer 8
[ https://issues.jenkins-ci.org/browse/JENKINS-13082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160531#comment-160531 ] Alex Lehmann commented on JENKINS-13082: the patch is planned for 1.457 I think you can check on the ci.jenkins-ci.org server if that is working Breadcrumb popup menu gives javascript error on Internet Explorer 8 --- Key: JENKINS-13082 URL: https://issues.jenkins-ci.org/browse/JENKINS-13082 Project: Jenkins Issue Type: Bug Components: www Affects Versions: current Environment: jenkins 1.455 running on linux, client is internet explorer 8 running on windows xp also happens on ci.jenkins-ci.org (1.456 rc) with client internet explorer 8 Reporter: Alex Lehmann Assignee: OHTAKE Tomohiro Priority: Blocker Labels: gui, windows when moving the mouse over the breadcrumb tabs, a javascript error shows in Internet Explorer 8 User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E) Timestamp: Wed, 14 Mar 2012 22:55:57 UTC Message: 'left' is null or not an object Line: 8 Char: 5672 Code: 0 URI: http://ci.jenkins-ci.org/static/6c4cb891/scripts/yui/dom/dom-min.js -- 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-13161) cvs plugin 2.x fails to update readonly checked out files
Alex Lehmann created JENKINS-13161: -- Summary: cvs plugin 2.x fails to update readonly checked out files Key: JENKINS-13161 URL: https://issues.jenkins-ci.org/browse/JENKINS-13161 Project: Jenkins Issue Type: Bug Components: cvs Environment: jenkins 1.456, cvs plugin 2.1, java 1.6.0-31 Reporter: Alex Lehmann Priority: Minor I found a migration issue when switching from cvs-plugin 1.6 to 2.x. The regular cvs client support checking out all files readonly to facilitate cvs edit/unedit and watchers, apparently this is not supported by the netbeans cvsclient. If a job was checked out with the old version of the plugin (1.x), updating the workspace fails due to java.io.FileNotFoundException: some_filename (Permission denied) This is not a big issue since the file permissions can be changed with find, nevertheless maybe it is possible to change the file handling to change write permissions before trying to overwrite the files. -- 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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored under some conditions
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160417#comment-160417
]
Alex Lehmann commented on JENKINS-12582:
sorry, you're right, I missed the part about setting the cvs password for each
job, changed the changelog entry accordingly
CVS-Plugin: Password file ${user.home}/.cvspass is ignored under some
conditions
--
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Assignee: Michael Clarke
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-13129: --- Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista was: jenkins 1.457-snapshot, tomcat 7.0.25, java 1.6.0-31 running on windows vista jenkins 1.455, tomcat 7.0.26, java 1.6.0-31 running on ubuntu 11.10 Description: I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. was: I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. This is probably related to JENKINS-12514, but wasn't fixed then issue is still present in 1.456 Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup -- Key: JENKINS-13129 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista Reporter: Alex Lehmann I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. -- 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-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160449#comment-160449 ] Alex Lehmann commented on JENKINS-13129: i think i found the cause, there is problem with the isBundled property in plugins, I will write a patch tomorrow. Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup -- Key: JENKINS-13129 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista Reporter: Alex Lehmann I still cannot update cvs or subversion plugins without manually creating a .pinned file. When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory. -- 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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored under some conditions
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Lehmann updated JENKINS-12582:
---
Summary: CVS-Plugin: Password file ${user.home}/.cvspass is ignored under
some conditions (was: CVS-Plugin: Password file ${user.home}/.cvspass is
ignored)
CVS-Plugin: Password file ${user.home}/.cvspass is ignored under some
conditions
--
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Assignee: Alex Lehmann
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12334) jenkins does not start in jboss container
[ https://issues.jenkins-ci.org/browse/JENKINS-12334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160263#comment-160263 ] Alex Lehmann edited comment on JENKINS-12334 at 3/14/12 10:52 PM: -- JENKINS-12867: this is the indentical error message, however the fix wasn't out at the time the 2nd issue was written was (Author: alexlehm): this is the indentical error message, however the fix wasn't out at the time the 2nd issue was written jenkins does not start in jboss container - Key: JENKINS-12334 URL: https://issues.jenkins-ci.org/browse/JENKINS-12334 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: JBoss 5.1 EAP Reporter: Terry Sposato Assignee: Kohsuke Kawaguchi Priority: Blocker Labels: jenkins Using latest RC version of jenkins, starting jboss up gives these errors: 2012-01-09 16:07:06,859 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)] Started in 32s:316ms 2012-01-09 16:07:07,305 INFO [jenkins.InitReactorRunner] (pool-14-thread-2) Started initialization 2012-01-09 16:07:09,553 INFO [jenkins.InitReactorRunner] (pool-14-thread-4) Listed all plugins 2012-01-09 16:07:13,601 INFO [jenkins.InitReactorRunner] (pool-14-thread-2) Prepared all plugins 2012-01-09 16:07:18,630 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: slf4j-api 1.6.x (or later) is incompatible with this binding. 2012-01-09 16:07:18,630 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: Your binding is version 1.5.5 or earlier. 2012-01-09 16:07:18,630 ERROR [STDERR] (Initializing plugin copyartifact) SLF4J: Upgrade your binding to version 1.6.x. or 2.0.x 2012-01-09 16:07:18,637 WARNING [hudson.ExtensionFinder$GuiceFinder] (Initializing plugin copyartifact) Failed to instantiate. Skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.NoSuchMethodError: org.slf4j.impl.StaticLoggerBinder.getSingleton()Lorg/slf4j/impl/StaticLoggerBinder; at org.jenkinsci.main.modules.sshd.SSHD.init(SSHD.java:40) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at hudson.ExtensionFinder$AbstractGuiceFinder$2$1.get(ExtensionFinder.java:365) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:54) at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:118) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:117) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:259) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:59) at hudson.ExtensionFinder$AbstractGuiceFinder$2$1.get(ExtensionFinder.java:365) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961) at hudson.ExtensionFinder$AbstractGuiceFinder._find(ExtensionFinder.java:336) at hudson.ExtensionFinder$AbstractGuiceFinder.find(ExtensionFinder.java:327) at hudson.ExtensionFinder._find(ExtensionFinder.java:147) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1046) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100) at
[JIRA] (JENKINS-12679) Matrix-Build Console Links to Hudson instead of Jenkins
[ https://issues.jenkins-ci.org/browse/JENKINS-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160145#comment-160145 ] Alex Lehmann commented on JENKINS-12679: some links are created based on the request, some use the base url if it is present (there are two methods in the Jenkins class to get a base url) Matrix-Build Console Links to Hudson instead of Jenkins --- Key: JENKINS-12679 URL: https://issues.jenkins-ci.org/browse/JENKINS-12679 Project: Jenkins Issue Type: Bug Components: matrix Affects Versions: current Reporter: Daniel Schaarschmidt Labels: console, matrix Fix For: current I have configured a Matrix-Build using multiple slave nodes. The parent console output contains the following: Löse OS11.4-64 aus OS11.4-64 beendet mit Ergebnis SUCCESS Löse OS11.1-32 aus OS11.1-32 beendet mit Ergebnis SUCCESS Finished: SUCCESS The Labels OSS11.4-64 and OS11.1-32 are links, but instead of pointing to http://myserver/jenkins/job/myjob/label=OS11.4-64/ they link to http://myserver/hudson/job/myjob/label=OS11.4-64/ Even better would be a direct link to the corresponding console log:http://myserver/jenkins/job/myjob/6/label=OS11.1-32/console -- 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-12679) Matrix-Build Console Links to Hudson instead of Jenkins
[ https://issues.jenkins-ci.org/browse/JENKINS-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160123#comment-160123 ] Alex Lehmann commented on JENKINS-12679: stoyan: are you using a reverse proxy for jenkins? if you are seeing links to the tomcat url, take a look at the wiki page about reverse proxy (https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache) Matrix-Build Console Links to Hudson instead of Jenkins --- Key: JENKINS-12679 URL: https://issues.jenkins-ci.org/browse/JENKINS-12679 Project: Jenkins Issue Type: Bug Components: matrix Affects Versions: current Reporter: Daniel Schaarschmidt Labels: console, matrix I have configured a Matrix-Build using multiple slave nodes. The parent console output contains the following: Löse OS11.4-64 aus OS11.4-64 beendet mit Ergebnis SUCCESS Löse OS11.1-32 aus OS11.1-32 beendet mit Ergebnis SUCCESS Finished: SUCCESS The Labels OSS11.4-64 and OS11.1-32 are links, but instead of pointing to http://myserver/jenkins/job/myjob/label=OS11.4-64/ they link to http://myserver/hudson/job/myjob/label=OS11.4-64/ Even better would be a direct link to the corresponding console log:http://myserver/jenkins/job/myjob/6/label=OS11.1-32/console -- 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-12679) Matrix-Build Console Links to Hudson instead of Jenkins
[ https://issues.jenkins-ci.org/browse/JENKINS-12679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160126#comment-160126 ] Alex Lehmann commented on JENKINS-12679: getting back to the original question, are you sure you have the correct url set on the config page? Matrix-Build Console Links to Hudson instead of Jenkins --- Key: JENKINS-12679 URL: https://issues.jenkins-ci.org/browse/JENKINS-12679 Project: Jenkins Issue Type: Bug Components: matrix Affects Versions: current Reporter: Daniel Schaarschmidt Labels: console, matrix I have configured a Matrix-Build using multiple slave nodes. The parent console output contains the following: Löse OS11.4-64 aus OS11.4-64 beendet mit Ergebnis SUCCESS Löse OS11.1-32 aus OS11.1-32 beendet mit Ergebnis SUCCESS Finished: SUCCESS The Labels OSS11.4-64 and OS11.1-32 are links, but instead of pointing to http://myserver/jenkins/job/myjob/label=OS11.4-64/ they link to http://myserver/hudson/job/myjob/label=OS11.4-64/ Even better would be a direct link to the corresponding console log:http://myserver/jenkins/job/myjob/6/label=OS11.1-32/console -- 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-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-12980: --- Affects Version/s: (was: current) Component/s: keyboard-shortcuts (was: www) With IE8 any page displays a javascript error about sortable.js --- Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: keyboard-shortcuts Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors -- 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-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159921#comment-159921 ] Alex Lehmann commented on JENKINS-12980: After further analysis of the problem, the error is triggered by installation of the keyboard-shortcut plugin 1.0, probably related to the prototype version. When installing a trunk build of the plugin 1.1-SNAPSHOT, it works again. With IE8 any page displays a javascript error about sortable.js --- Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: keyboard-shortcuts Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors -- 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-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-12980. Resolution: Fixed probably fixed with commit 79cdfd2169e3015883b914febcd3d064d821cd8d With IE8 any page displays a javascript error about sortable.js --- Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: keyboard-shortcuts Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors -- 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-12980) With IE8 any page displays a javascript error about sortable.js
Alex Lehmann created JENKINS-12980: -- Summary: With IE8 any page displays a javascript error about sortable.js Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: www Affects Versions: current Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. -- 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-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann updated JENKINS-12980: --- Description: When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors was: When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. With IE8 any page displays a javascript error about sortable.js --- Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: www Affects Versions: current Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors -- 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-12980) With IE8 any page displays a javascript error about sortable.js
[ https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159884#comment-159884 ] Alex Lehmann commented on JENKINS-12980: The error is apparently related to the keyboard-shortcut plugin, if I remove that, the error goes away. With IE8 any page displays a javascript error about sortable.js --- Key: JENKINS-12980 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980 Project: Jenkins Issue Type: Bug Components: www Affects Versions: current Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8 Reporter: Alex Lehmann Priority: Minor When accessing Jenkins with IE8, each page displays a javascript error about sortable.js Line 242 Character 9 Object doesn't support this property or method Code 0 http://(host)/jenkins/static/99210c85/scripts/sortable.js (the text is roughly translated back to English since I do not have an English Windows to test) When skipping the error message, the page works, but the error shows up on any page again. The same page works on IE6, IE7, IE9 and current Firefox without errors -- 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=159628#comment-159628 ] Alex Lehmann commented on JENKINS-12730: this is still not working in plugin release 1.0 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:all-tabpanel ] Alex Lehmann reopened JENKINS-12730: 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=159641#comment-159641 ] Alex Lehmann commented on JENKINS-12730: the head version works, looks like the fix didn't make it into version 1.0 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:all-tabpanel ] Alex Lehmann 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-7209) Editing description results in broken utf-8 chars
[ https://issues.jenkins-ci.org/browse/JENKINS-7209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Lehmann resolved JENKINS-7209. --- Fix Version/s: current Resolution: Cannot Reproduce this doesn't happen anymore, probably a locale issue Editing description results in broken utf-8 chars - Key: JENKINS-7209 URL: https://issues.jenkins-ci.org/browse/JENKINS-7209 Project: Jenkins Issue Type: Bug Components: description-setter Affects Versions: current Environment: Linux SLES, Tomcat 6.0.26, Java 1.6.0-20 Reporter: Alex Lehmann Assignee: huybrechts Priority: Minor Fix For: current When editing the description for a job, utf-8 characters get encoded twice resulting in broken characters (or rather 2 byte chars get encoded to 4 bytes). When editing the appropriate config.xml file manually, the text comes through ok, so this probably an error when processing the input text that is passed as url encoded form values. I couldn't reproduce this with hudson running on Windows, so it is probably a environment dependency or is affected by locale settings, but I couldn't get it right in Linux. -- 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
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-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=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
[ 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-12628) Executable file permission not set anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159377#comment-159377 ] Alex Lehmann commented on JENKINS-12628: this needs to be in a try block that catches NoSuchMethodError similar to the permission method in hudson.utils Executable file permission not set anymore -- Key: JENKINS-12628 URL: https://issues.jenkins-ci.org/browse/JENKINS-12628 Project: Jenkins Issue Type: Bug Components: cvs Environment: CentOS release 5.7 (affected system, Slave), Windows Server 2003 (Master) Reporter: Marco Borm Assignee: Michael Clarke Fix For: current Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the fact that our compile scripts don't have executable permission bit set anymore. The bit is correctly set on the affected files on cvs server side. cvs plugin 1.6: -rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release cvs plugin 2.0: -rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release -- 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-12753) Instant update of plugins doesn't work in nfs directory
[
https://issues.jenkins-ci.org/browse/JENKINS-12753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159258#comment-159258
]
Alex Lehmann commented on JENKINS-12753:
the way open files are handled is different on local filesystems and nfs, the
issue may be nfs specific, however if Kohsuke is right, it doesn't work on
local storage either but it doesn't give an obvious error message in that case.
if the plugin is in use, the different jar files for the plugin are all loaded
into the jvm and are open (this is visible with lsof), if the plugin is
updated, the files are still open even though they are already delete (this is
perfectly ok on local filesystems), e.g. like this (this is the output of
lsof|grep java.*xunit.*guice as one example file):
before:
{code}
java 1430lehmann mem REG 8,1 807021 4067923
/home/lehmann/.jenkins/plugins/xunit/WEB-INF/lib/guice-2.0.1.jar
java 1430lehmann 237r REG 8,1 807021 4067923
/home/lehmann/.jenkins/plugins/xunit/WEB-INF/lib/guice-2.0.1.jar
{code}
after:
{code}
java 1430lehmann DEL REG 8,1 4067923
/home/lehmann/.jenkins/plugins/xunit/WEB-INF/lib/guice-2.0.1.jar
java 1430lehmann 237r REG 8,1 807021 4067923
/home/lehmann/.jenkins/plugins/xunit/WEB-INF/lib/guice-2.0.1.jar (deleted)
{code}
the jars will not be reloaded even if they were written to the directory in a
new version.
on nfs, open deleted files are not directly possible, so instead each file is
changed to a .nfs file which causes the exception when trying to delete the
directory, but reloading wouldn't work either if the files could be deleted (or
e.g. are moved to another dir and delete later).
When updating a plugin when the directory is on a local filesystem, the update
page still says xunit plugin is already installed. Jenkins needs to be
restarted for the update to take effect with a yellow ball, so the update
process notices that it cannot update the files and forces suggests to restart.
With nfs he never gets to the stage where the message appears, but the problem
is the same in both cases.
Instant update of plugins doesn't work in nfs directory
---
Key: JENKINS-12753
URL: https://issues.jenkins-ci.org/browse/JENKINS-12753
Project: Jenkins
Issue Type: Bug
Components: plugin
Environment: linux, nfs, jenkins 1.450, any plugin
Reporter: Alex Lehmann
Priority: Minor
Got the question from the irc channel, this was initially discussed on the
fosdem jenkins booth.
Updating plugins doesn't work when the jenkins home directory is located on
nfs, the failure looks like this
Caused by: java.io.IOException: Unable to delete
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/.nfs000e897d0096
The .nfs files appear when deleting a file on nfs that is still open, in this
case the jar files in the lib directory are still open and cannot be deleted.
--
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-12826) empty repository browser url gives tomcat error page on different scm plugins
Alex Lehmann created JENKINS-12826: -- Summary: empty repository browser url gives tomcat error page on different scm plugins Key: JENKINS-12826 URL: https://issues.jenkins-ci.org/browse/JENKINS-12826 Project: Jenkins Issue Type: Bug Components: cvs, git, mercurial, subversion Environment: jenkins 1.451, tomcat 7.0.25, cvs 2.0, git 1.1.15, svn 1.39, mercurial 1.38 Reporter: Alex Lehmann Assignee: abayer Priority: Minor i was trying the mercurial plugin and selected repository browser bitbucket but didn't enter an url, this causes an error 500 from tomcat, which make it a bit difficult to figure out what is actually wrong (I though that the repository url was wrong initially). javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.mercurial.MercurialSCM root cause java.net.MalformedURLException: no protocol: the same happens on the config page for cvs, git and svn (at least, thats all scm plugins I have installed), it would be nice if the url is validated on the config page similar to other config parameters to get a red error message. -- 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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Lehmann reassigned JENKINS-12582:
--
Assignee: Alex Lehmann
CVS-Plugin: Password file ${user.home}/.cvspass is ignored
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Assignee: Alex Lehmann
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159040#comment-159040
]
Alex Lehmann commented on JENKINS-12582:
I think I found the reason why the password is not picked up in my jobs, the
format for CVSROOT is a bit flexible, you can either user
:pserver:user@host/path or :pserver:user@host:/path, most examples use the
additional colon (i didn't notice that you could leave that out before today).
The matching function for .cvspass entries removes the port including the colon
so that only the version without colon is matched.
That should be easy to fix, I will try to write something.
CVS-Plugin: Password file ${user.home}/.cvspass is ignored
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159048#comment-159048
]
Alex Lehmann commented on JENKINS-12582:
doesn't build on ci.jenkins-ci.org right now due to another change before, but
it should work once the other build issue is fixed
CVS-Plugin: Password file ${user.home}/.cvspass is ignored
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12582) CVS-Plugin: Password file ${user.home}/.cvspass is ignored
[
https://issues.jenkins-ci.org/browse/JENKINS-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158976#comment-158976
]
Alex Lehmann commented on JENKINS-12582:
I tried migrating a cvs test job from cvs-plugin 1.6 to 2.0, that didn't pick
up the password from the .cvspass file.
CVS-Plugin: Password file ${user.home}/.cvspass is ignored
Key: JENKINS-12582
URL: https://issues.jenkins-ci.org/browse/JENKINS-12582
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: Tomcat6 / RHEL5
Reporter: chrisabit
Priority: Blocker
Jenkins' new Netbeans-based CVS-Plugin doesn't use the .cvspass file.
Setting the password on every job isn't a suitable solution (huge number of
jobs, security issues). The .cvspass file should be used instead.
--
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-12753) Instant update of plugins doesn't work in nfs directory
Alex Lehmann created JENKINS-12753: -- Summary: Instant update of plugins doesn't work in nfs directory Key: JENKINS-12753 URL: https://issues.jenkins-ci.org/browse/JENKINS-12753 Project: Jenkins Issue Type: Bug Components: plugin Environment: linux, nfs, jenkins 1.450, any plugin Reporter: Alex Lehmann Priority: Minor Got the question from the irc channel, this was initially discussed on the fosdem jenkins booth. Updating plugins doesn't work when the jenkins home directory is located on nfs, the failure looks like this Caused by: java.io.IOException: Unable to delete /var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/.nfs000e897d0096 The .nfs files appear when deleting a file on nfs that is still open, in this case the jar files in the lib directory are still open and cannot be deleted. -- 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-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158805#comment-158805 ] Alex Lehmann commented on JENKINS-12583: Are you sure that you have the plugin pinnned? I have the following files in the jenkins/plugins dir: cvs cvs.jpi cvs.jpi.pinned if that is the case, the main jenkins should update the plugin to the old version anymore in 1.450 it is supposed to be fixed, but I haven't tried that yet. update for cvs plugin to 2.0 doesn't work - Key: JENKINS-12583 URL: https://issues.jenkins-ci.org/browse/JENKINS-12583 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: jenkins 1.449, cvs plugin 1.6 Reporter: Alex Lehmann Fix For: current I tried to update to the cvs plugin 2.0 today but this doesn't work, I assume there is a name problem due to the extension *.jpi on the new plugin. Before update, the file is called cvs.hpi, the update process creates a new file cvs.jpi that is ignored with the following message: Jan 30, 2012 5:04:26 PM hudson.PluginManager$1$3$1 isDuplicate INFO: Ignoring /home/lehmann/.jenkins/plugins/cvs.jpi because /home/lehmann/.jenkins/plugins/cvs.hpi is already loaded I assume it may work if it were the other way around. The version displayed by the plugin page remains 1.6 but there are a few exceptions in the log about missing classes like this java.lang.NoClassDefFoundError: org/netbeans/lib/cvsclient/admin/AdminHandler these classes are included in the cvs.jpi zip but that is not used. I was able to fix the update manually by copying cvs.jpi to cvs.hpi, which resulted in a pinned plugin 2.0, but the automatic process has to be fixed somehow. -- 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-12628) Executable file permission not set anymore
[
https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158792#comment-158792
]
Alex Lehmann edited comment on JENKINS-12628 at 2/8/12 9:02 PM:
chmod isn't necessary on windows anyway, if you have a wrapper the checks if
the target system is unix-like and run chmod or do nothing otherwise
if it is possible to check for java5/java6, this could be used before if
possible, something like this
{code}
if(isUnix) {
if(isJava6) {
File.setExecutable();
} else {
System.execute(chmod ...);
}
} else {
warn(ignoring execute permission for ...);
}
{code}
if this is properly wrapped in a method, this will not even look bad in the
actual code since that only has to do Wrapper.setExecutable(file);
was (Author: alexlehm):
chmod isn't necessary on windows anyway, if you have a wrapper the checks
if the target system is unix-like and run chmod or do nothing otherwise
if it is possible to check for java5/java6, this could be used before if
possible, something like this
{code}
if(isUnix) {
if(isJava6) {
File.setExecutable();
} else {
System.execute(chmod ...);
}
} else {
warn(ignoring execute permission for ...);
}
{code}
Executable file permission not set anymore
--
Key: JENKINS-12628
URL: https://issues.jenkins-ci.org/browse/JENKINS-12628
Project: Jenkins
Issue Type: Bug
Components: cvs
Environment: CentOS release 5.7 (affected system, Slave), Windows
Server 2003 (Master)
Reporter: Marco Borm
Fix For: current
Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the
fact that our compile scripts don't have executable permission bit set
anymore. The bit is correctly set on the affected files on cvs server side.
cvs plugin 1.6:
-rwxrwx--- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release
cvs plugin 2.0:
-rw-rw-r-- 1 jenkins jenkins261 15. Mai 2007 compile.linux.so.release
--
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-12650) jenkins running in Tomcat doesn't initalize slf4j properly
Alex Lehmann created JENKINS-12650: -- Summary: jenkins running in Tomcat doesn't initalize slf4j properly Key: JENKINS-12650 URL: https://issues.jenkins-ci.org/browse/JENKINS-12650 Project: Jenkins Issue Type: Bug Components: ssh Environment: jenkins 1.450, tomcat 7.0.23, java 1.6.0-30 Reporter: Alex Lehmann Priority: Minor when running tomcat, the slf4j library isn't correctly initialized, this is not a problem by itself since it simply turns off logging completely for the components that use slf, however if the logging output is needed for a component it would be better to provide the simple logger. SLF4J: Failed to load class org.slf4j.impl.StaticLoggerBinder. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. when I put the necessary jar into the war, the log output becomes this: 16 [NullIdDescriptorMonitor.verifyId] INFO org.apache.sshd.common.util.SecurityUtils - Trying to register BouncyCastle as a JCE provider 511 [NullIdDescriptorMonitor.verifyId] INFO org.apache.sshd.common.util.SecurityUtils - Registration succeeded so this is used by the sshd module in the default installation. Alternatively, the binding for jdk14 logging or log4j could be used (which ever is more fitting for the rest of jenkins). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
