[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title Andrew Erickson commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility This is a core feature in my mind. I'd love to see it fixed/added. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Andrew Erickson commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch Why was this closed? I just had a user request this functionality. It would be nice it was just an option in the git plugin. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-11337) Git plugin only triggers a build for one branch
Title: Message Title Andrew Erickson commented on JENKINS-11337 Re: Git plugin only triggers a build for one branch Scenario: Job has multiple 'branches to build' configured. User desires a build of a branch other than the first configured (usually master). 'Build now' will build the first branch. User has no way of triggering a build of the specific branch. Current solutions: push a whitespace change to the branch desired to be built create discreet jobs per branch parameterize the job and don't use the git plugin Ideal solution: git plugin option: "pick branch on 'build now'" would basically do what https://github.com/phemmer/jenkins-git-chooser-build-branches, but inside the git plugin as you suggest ... Sorry to restart a long thread. Are you open to that solution? Should I open a new ticket with the above content (happy to work on it)? Thanks, Andy Add Comment
[JIRA] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson edited a comment on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm seeing this with LTS (1.580.1). I have a test job that can ssh to the machine just fine. Update: I don't believe this is related to selenium... I'm not running it. 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson updated JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. Change By: Andrew Erickson (05/Dec/14 7:40 PM) Priority: Minor Major 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson commented on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm seeing this with LTS (1.580.1). I have a test job that can ssh to the machine just fine. 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson edited a comment on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm seeing this with LTS (1.580.1). I have a test job that can ssh to the machine just fine. Update: I don't believe this is related to selenium... I'm not running it. /// 12/05/14 19:36:05 SSH Opening SSH connection to engmetrics-slave-001.ec2.pinadmin.com:22. Connection timed out ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.IllegalStateException: Connection is not established! at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1173) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 12/05/14 19:37:08 Launch failed - cleaning up connection 12/05/14 19:37:08 SSH Connection closed. 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson edited a comment on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm seeing this with LTS (1.580.1) and 1.592. I have a test job that can ssh to the machine just fine. Update: I don't believe this is related to selenium... I'm not running it. /// 12/05/14 19:36:05 SSH Opening SSH connection to engmetrics-slave-001.ec2.pinadmin.com:22. Connection timed out ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.IllegalStateException: Connection is not established! at com.trilead.ssh2.Connection.getRemainingAuthMethods(Connection.java:1030) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.getRemainingAuthMethods(TrileadSSHPublicKeyAuthenticator.java:88) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.canAuthenticate(TrileadSSHPublicKeyAuthenticator.java:80) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:207) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.newInstance(SSHAuthenticator.java:169) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1173) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) 12/05/14 19:37:08 Launch failed - cleaning up connection 12/05/14 19:37:08 SSH Connection closed. 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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.
Andrew Erickson edited a comment on JENKINS-25583 Unexpected error in launching a slave. This is probably a bug in Jenkins. I'm seeing this with LTS (1.580.1) and 1.592. I have a test job that can ssh to the machine just fine. Update: I don't believe this is related to selenium... I'm not running it. Update 2: This was due to misconfiguration. Please disregard. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Andrew Erickson commented on JENKINS-20769 Failed to execute command Pipe.EOF From scanning the changelog, 1.558 and later have the fix. LTS does not have it (not sure if it needs to be labeled lts-candidate to be picked up or not). 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Andrew Erickson edited a comment on JENKINS-20769 Failed to execute command Pipe.EOF From scanning the changelog, 1.558 and later have the fix. LTS does not have it (not sure if it needs to be labeled lts-candidate to be picked up or not). Update: added the label 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Andrew Erickson commented on JENKINS-20769 Failed to execute command Pipe.EOF Was this really fixed in 1.554.1 (that's what the label means per https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line)? The changelog doesn't mention it. 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] [deploy] (JENKINS-18798) Please support upgrades from Ubuntu's jenkins packages
Andrew Erickson commented on JENKINS-18798 Please support upgrades from Ubuntus jenkins packages Please fix this. I experienced it recently. For anyone else experiencing this, Marius' fix on the email thread worked (https://groups.google.com/d/topic/jenkinsci-users/eW_yEWLojFc/discussion). sudo apt-get remove jenkins jenkins-common sudo apt-get install jenkins sudo rm /etc/init/jenkins.conf sudo update-rc.d jenkins defaults sudo service jenkins start 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] [core] (JENKINS-22710) Broken Debian upgrades because postinst doesn't check for present group/user
Andrew Erickson commented on JENKINS-22710 Broken Debian upgrades because postinst doesnt check for present group/user Getting this with 1.563 in Ubuntu 14.04 LTS. 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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Andrew Erickson commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Seeing this on Jenkins 1.520 with Gerrit Trigger 2.10.0. We never had the problem before, but recently started generating configs from templates and reloading from disk. Paul, could you post a diff? Robert, any opinions thoughts on Paul's approach? Thanks, Andy 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson resolved JENKINS-17590 as Duplicate Builds fail because of slave went offline during the build duplicate, moving activity to JENKINS-16778 Change By: Andrew Erickson (31/May/13 5:57 AM) Status: Open Resolved Resolution: Duplicate 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] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Andrew Erickson commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Steven, Joris, (or anyone with permissions - not sure where to see a list of people), Will you please publish a 1.5.4 with this latest fix? Thanks, Andy 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson updated JENKINS-17590 Builds fail because of slave went offline during the build This appears to be a dupe of https://issues.jenkins-ci.org/browse/JENKINS-16778 v1.5.3 of Timestamper doesn't have this fix... like the changelog makes it look like. I guess it will be in 1.5.4. 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson commented on JENKINS-17590 Builds fail because of slave went offline during the build I think I've tracked this down to the "Timestamper" plugin (https://wiki.jenkins-ci.org/display/JENKINS/Timestamper). Test setup: create a new job that just has one shell command 'sleep 30' Testing procedure: start job before job finishes, take node offline see if job fails (it should succeed) This test procedure also fails on our production server (Jenkins 1.515 with Timestamper 1.5.3) A build of git head (1.518) on a virgin local installation does not have this bug. Installing the latest version of Timestamper causes the test to fail (the job causes NPE's just like on our production server). 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson assigned JENKINS-17590 to stevengbrown Builds fail because of slave went offline during the build Steven, Do you have any ideas on this? I've used Timestamper for awhile before this... so something seems to have changed in core that brought this about. Thanks, Andy Change By: Andrew Erickson (29/May/13 1:38 AM) Assignee: stevengbrown 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson updated JENKINS-17590 Builds fail because of slave went offline during the build Change By: Andrew Erickson (24/May/13 3:11 AM) Affects Version/s: current 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson commented on JENKINS-17590 Builds fail because of slave went offline during the build I'm seeing this also when running 1.515 and the previous 2 or 3 releases before. Output found in the console log below. The slave log didn't have any other details. Looks like the node went offline during the build. Check the slave log for the details.FATAL: null java.lang.NullPointerException at hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory.getOffset(TimestampAnnotatorFactory.java:65) at hudson.plugins.timestamper.annotator.TimestampAnnotatorFactory.newInstance(TimestampAnnotatorFactory.java:52) at hudson.console.ConsoleAnnotator._for(ConsoleAnnotator.java:143) at hudson.console.ConsoleAnnotator.initial(ConsoleAnnotator.java:133) at hudson.console.AnnotatedLargeText.createAnnotator(AnnotatedLargeText.java:140) at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:157) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:599) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) 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] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson updated JENKINS-17590 Builds fail because of slave went offline during the build I'm going to up the priority on this to 'Major'. It affects whether or not jobs pass or fail which seems like core functionality. This used to work fine... the job could still pass even if it was taken offline. We frequently take nodes offline before the job finishes so that we can inspect the system state (with long running jobs)... so we see this more often and it's somewhat painful to have to rerun to get a blue/green ball even if it succeeded. Change By: Andrew Erickson (24/May/13 3:17 AM) Priority: Minor Major 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] [core] (JENKINS-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson assigned JENKINS-15808 to Francois Valdy CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Francois, Could you attempt to reproduce with a recent version? Thanks, Andy Change By: Andrew Erickson (05/Apr/13 6:17 PM) Assignee: rsandell FrancoisValdy 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration I am no longer able to reproduce. Configuration saving seems to works fine now. Tested with CVS 2.8, Gerrit Trigger 2.9.0, and Jenkins ver. 1.510-SNAPSHOT. The bug in core that was causing this must have been fixed. Recommend closing when verified by another user experiencing this. 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson edited a comment on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration I am no longer able to reproduce. Configuration saving seems to works fine now. Tested with CVS 2.8, Gerrit Trigger 2.9.0, and Jenkins versions 1.508 and 1.510-SNAPSHOT. The bug in core that was causing this must have been fixed. Recommend closing when verified by another user experiencing this. 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Yes, I will try to test this soon (if not tomorrow, definitely this week). 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-15674) Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'
Andrew Erickson commented on JENKINS-15674 Choosing strategy resets randomly from Gerrit Trigger to Default Currently on 1.499 with 1.1.25, but I haven't seen it happen in awhile (maybe I just haven't been editing my GerritTrigger jobs though...). 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-15674) Choosing strategy resets randomly from 'Gerrit Trigger' to 'Default'
Andrew Erickson commented on JENKINS-15674 Choosing strategy resets randomly from Gerrit Trigger to Default I've had this happen... it happened for me when configuring an unrelated section and saving. 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration You need to use the job config I attached. Jobs that don't use Gerrit Trigger appear to be fine. If you click 'apply' before clicking save the error doesn't occur. Something that buildFormTree does fixes the invalid form structure. 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson updated JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Change By: Andrew Erickson (28/Nov/12 7:29 PM) Summary: CVSplugin2. 0-2. 7breaksGerritTrigger(v2.5.2and2.6.0)configuration 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-15808) CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson
commented on JENKINS-15808
CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
I've done some additional testing (see procedure below). I can (unfortunately) reproduce it. CVS plugin 2.0 (the first one after 1.6) is when this behavior begins to happen.
I was suprised as well. I upgraded to 1.489 from 1.488 and also upgraded 3 plugins (CVS, Git, and Translations) and this started happening. Git and Translations seemed like the obvious suspects.
The config page form has an event listener on submit registered by buildFormTree at line 857 in hudson-behavior.js. That function seems to marshall the form data into JSON. It does have error handling, but maybe it can't alert because it's in the submit process already or something? I put an alert in the success state and it didn't pop up either.
The invalid JSON blob that appears in the failed request body ('init') is set in buildFormTree on line 863.
This isn't a huge problem for me as long as the included version of CVS doesn't change.
I'll keep digging.
Andy
/ test procedure (on os x 10.7.5) /
///
// compile latest master build (Jenkins ver. 1.492-SNAPSHOT - a8d9397)
MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m" mvn -Plight-test clean install
rm -rf /tmp/jenkins_test
mkdir -p /tmp/jenkins_test
// run compiled build
JENKINS_HOME=/tmp/jenkins_test java -jar ./war/target/jenkins.war
place job config in JENKINS_HOME/jobs/gerrit_trigger_test/config.xml
reload from disk
install gerrit trigger plugin (2.6.0, included Jenkins Git 1.1.26)
restart (ctrl-c and relaunch)
try configuring job (edit pink field in screenshot) and saving... works
update cvs plugin to 2.7
restart
try configuring job and saving... fails
disable cvs plugin
restart
try configuring job and saving... fails
downgrade to 1.6 - still disabled
restart
try configuring job and saving... fails
// unexpected... caching going on?
enable cvs 1.6 plugin
restart
try configuring job and saving... works
disable cvs plugin 1.6
restart
try configuring job and saving... fails
// again... strange...
re-enable cvs plugin 1.6
restart
try configuring job and saving... works
/// CVS Version testing ///
downgrade to 1.6; restart
try configuring... works
install 2.0; restart
try configuring... fails
downgrade to 1.6 (unpin 2.0); restart
try configuring... works
// job's config.xml /
/
?xml version='1.0' encoding='UTF-8'?
project
actions/
description/description
keepDependenciesfalse/keepDependencies
properties/
scm class="hudson.plugins.git.GitSCM" plugin="git@1.1.26"
configVersion2/configVersion
userRemoteConfigs
hudson.plugins.git.UserRemoteConfig
name/name
refspec/refspec
urlssh://GERRIT_SERVER:29418/chef-internal.git/url
/hudson.plugins.git.UserRemoteConfig
/userRemoteConfigs
branches
hudson.plugins.git.BranchSpec
name**/name
/hudson.plugins.git.BranchSpec
/branches
disableSubmodulesfalse/disableSubmodules
recursiveSubmodulesfalse/recursiveSubmodules
doGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurations
authorOrCommitterfalse/authorOrCommitter
cleanfalse/clean
wipeOutWorkspacefalse/wipeOutWorkspace
pruneBranchesfalse/pruneBranches
remotePollfalse/remotePoll
ignoreNotifyCommitfalse/ignoreNotifyCommit
useShallowClonefalse/useShallowClone
buildChooser class="hudson.plugins.git.util.DefaultBuildChooser"/
gitToolDefault/gitTool
submoduleCfg class="list"/
relativeTargetDir/relativeTargetDir
reference/reference
excludedRegions/excludedRegions
excludedUsers/excludedUsers
gitConfigName/gitConfigName
gitConfigEmail/gitConfigEmail
skipTagfalse/skipTag
includedRegions/includedRegions
scmName/scmName
/scm
canRoamtrue/canRoam
disabledfalse/disabled
blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding
blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding
triggers class="vector"
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger plugin="gerrit-trigger@2.6.0"
spec/spec
gerritProjects
com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.data.GerritProject
compareTypePLAIN/compareType
patternchef-internal/pattern
branches
[JIRA] (JENKINS-15808) CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson created JENKINS-15808 CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Issue Type: Bug Affects Versions: current Assignee: rsandell Attachments: jenkins_gerrit_trigger_configuration.png Components: core, cvs, gerrit-trigger Created: 12/Nov/12 11:55 PM Description: The CVS 2.7 plugin breaks configuration of Gerrit Trigger jobs. When attempting to save the configuration a stack is raised (see below). /// steps to reproduce Jenkins 1.483-9 (including recent github master cb41982, may exist with earlier) Gerrit Trigger 2.5.2 and 2.6, CVS Plugin 2.7 configure a job to use gerrit trigger to launch (before installing CVS 2.7 or on CLI and reloading) attempt to edit field shown in screenshot above fix: downgrade CVS to 1.6 how jenkins is being run: on ubuntu 12.04, via jenkinsci.org repo on OS X 10.7, built from source both via Winstone/default container, java -jar jenkins.war stack trace: / Nov 10, 2012 2:53:42 PM winstone.Logger logInternal SEVERE: Error while serving http://localhost:8080/job/chef-internal-gerrit/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-15808) CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson updated JENKINS-15808 CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Change By: Andrew Erickson (13/Nov/12 12:03 AM) Description: TheCVS2.7pluginbreaksconfigurationofGerritTriggerjobs.Whenattemptingtosavetheconfigurationastackisraised(seebelow).///stepstoreproduce*Jenkins1.483-9(includingrecentgithubmastercb41982,mayexistwithearlier)*GerritTrigger2.5.2and2.6,CVSPlugin2.7*configureajobtousegerrittriggertolaunch(beforeinstallingCVS2.7orbyeditingonCLIandreloading)*attempttoeditfieldshowninscreenshotabovefix:*downgradeCVSto1.6howjenkinsisbeingrun:onubuntu12.04,viajenkinsci.org repo debs onOSX10.7,builtfromsourcebothviaWinstone/defaultcontainer,java-jarjenkins.warstacktrace:/Nov10,20122:53:42PMwinstone.LoggerlogInternalSEVERE:Errorwhileservinghttp://localhost:8080/job/chef-internal-gerrit/configSubmitjava.lang.reflect.InvocationTargetException atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) atjava.lang.reflect.Method.invoke(Method.java:597) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:487) atorg.kohsuke.stapler.Stapler.service(Stapler.java:164) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
[JIRA] (JENKINS-15808) CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson updated JENKINS-15808 CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Change By: Andrew Erickson (13/Nov/12 12:03 AM) Description: TheCVS2.7pluginbreaksconfigurationofGerritTriggerjobs.Whenattemptingtosavetheconfigurationastackisraised(seebelow).///stepstoreproduce*Jenkins1.483-9(includingrecentgithubmastercb41982,mayexistwithearlier)*GerritTrigger2.5.2and2.6,CVSPlugin2.7*configureajobtousegerrittriggertolaunch(beforeinstallingCVS2.7or byediting onCLIandreloading)*attempttoeditfieldshowninscreenshotabovefix:*downgradeCVSto1.6howjenkinsisbeingrun:onubuntu12.04,viajenkinsci.orgrepoonOSX10.7,builtfromsourcebothviaWinstone/defaultcontainer,java-jarjenkins.warstacktrace:/Nov10,20122:53:42PMwinstone.LoggerlogInternalSEVERE:Errorwhileservinghttp://localhost:8080/job/chef-internal-gerrit/configSubmitjava.lang.reflect.InvocationTargetException atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) atjava.lang.reflect.Method.invoke(Method.java:597) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:487) atorg.kohsuke.stapler.Stapler.service(Stapler.java:164) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:45) atwinstone.ServletConfiguration.execute(ServletConfiguration.java:248) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:333) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
[JIRA] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Andrew Erickson commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building I just encountered this. You need to set the field in the advanced options (the second advanced option set) called "unique SCM name (optional)". It's not really optional when using this plugin (as the tip says). My builds are now not executing on every polling instance. Not sure if it's possible for plugins to make option fields required... but it would be nice if this did that. 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-15109) Stacktrace introduced in 1.481 when going to http://jenkins /computer/(master)/api/xml
Andrew Erickson commented on JENKINS-15109 Stacktrace introduced in 1.481 when going to http://jenkins /computer/(master)/api/xml The fix has been merged. 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-15109) Stacktrace introduced in 1.481 when going to http://jenkins /computer/(master)/api/xml
Andrew Erickson commented on JENKINS-15109 Stacktrace introduced in 1.481 when going to http://jenkins /computer/(master)/api/xml Sorry about this. Fixed with https://github.com/jenkinsci/jenkins/pull/565. '/computer/(master)/api/xml' output below. when online: masterComputer displayNamemaster/displayName executor/ executor/ iconcomputer.png/icon idletrue/idle jnlpAgentfalse/jnlpAgent launchSupportedtrue/launchSupported loadStatistics/ manualLaunchAllowedtrue/manualLaunchAllowed monitorData hudson.node_monitors.SwapSpaceMonitor availablePhysicalMemory266338304/availablePhysicalMemory availableSwapSpace493879296/availableSwapSpace totalPhysicalMemory8581545984/totalPhysicalMemory totalSwapSpace2147483648/totalSwapSpace /hudson.node_monitors.SwapSpaceMonitor hudson.node_monitors.ArchitectureMonitorMac OS X (x86_64)/hudson.node_monitors.ArchitectureMonitor hudson.node_monitors.ResponseTimeMonitor average6/average /hudson.node_monitors.ResponseTimeMonitor hudson.node_monitors.TemporarySpaceMonitor path /private/var/folders/mj/rjhd11f10sx43t4np9xs5fb4gn/T /path size185129209856/size /hudson.node_monitors.TemporarySpaceMonitor hudson.node_monitors.DiskSpaceMonitor path/Users/aje/.jenkins/path size185129209856/size /hudson.node_monitors.DiskSpaceMonitor hudson.node_monitors.ClockMonitor diff0/diff /hudson.node_monitors.ClockMonitor /monitorData numExecutors2/numExecutors offlinefalse/offline offlineCauseReason/ temporarilyOfflinefalse/temporarilyOffline /masterComputer when offline: masterComputer displayNamemaster/displayName executor/ executor/ iconcomputer-x.png/icon idletrue/idle jnlpAgentfalse/jnlpAgent launchSupportedtrue/launchSupported loadStatistics/ manualLaunchAllowedtrue/manualLaunchAllowed monitorData hudson.node_monitors.SwapSpaceMonitor availablePhysicalMemory409993216/availablePhysicalMemory availableSwapSpace493879296/availableSwapSpace totalPhysicalMemory8583643136/totalPhysicalMemory totalSwapSpace2147483648/totalSwapSpace /hudson.node_monitors.SwapSpaceMonitor hudson.node_monitors.ArchitectureMonitorMac OS X (x86_64)/hudson.node_monitors.ArchitectureMonitor hudson.node_monitors.ResponseTimeMonitor average4/average /hudson.node_monitors.ResponseTimeMonitor hudson.node_monitors.TemporarySpaceMonitor path /private/var/folders/mj/rjhd11f10sx43t4np9xs5fb4gn/T /path size185130684416/size /hudson.node_monitors.TemporarySpaceMonitor hudson.node_monitors.DiskSpaceMonitor path/Users/aje/.jenkins/path size185130684416/size /hudson.node_monitors.DiskSpaceMonitor hudson.node_monitors.ClockMonitor diff0/diff /hudson.node_monitors.ClockMonitor /monitorData numExecutors2/numExecutors offlinetrue/offline offlineCause/ offlineCauseReason/offlineCauseReason temporarilyOfflinetrue/temporarilyOffline /masterComputer 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-9392) Read-Only .war prevents Auto-Update
[ https://issues.jenkins-ci.org/browse/JENKINS-9392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163270#comment-163270 ] Andrew Erickson commented on JENKINS-9392: -- I just debugged why I couldn't auto-upgrade on the Mac... this functionality would seem handy for everyone. Read-Only .war prevents Auto-Update --- Key: JENKINS-9392 URL: https://issues.jenkins-ci.org/browse/JENKINS-9392 Project: Jenkins Issue Type: Improvement Components: update-center Environment: jenkins .401 Reporter: Brian Relph Priority: Minor If hudson.war is read-only, the auto-update link is not available. I am not sure how hudson.war got set to read-only, but it was an accident, and it took me awhile to figure out the problem. Would it be possible to add a message indicating why auto-update is not available? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13938) Mac installer should set owner of /Applications/Jenkins to 'jenkins' user (fix Mac auto-upgrade)
Andrew Erickson created JENKINS-13938: - Summary: Mac installer should set owner of /Applications/Jenkins to 'jenkins' user (fix Mac auto-upgrade) Key: JENKINS-13938 URL: https://issues.jenkins-ci.org/browse/JENKINS-13938 Project: Jenkins Issue Type: Improvement Components: other Affects Versions: current Reporter: Andrew Erickson Priority: Minor If this was done then Mac users could auto-upgrade. Currently the permissions are preventing 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
