[JIRA] [warnings-plugin] (JENKINS-25405) Warnings plugin fails
Stefan Landström commented on JENKINS-25405 Warnings plugin fails Experiencing the same issue on Jenkins LTS 1.580.1 (java.runtime.version 1.7.0_72-b14) after updating. Downgraded Static Code Analysis Plug-ins 1.64 to 1.61 Warnings Plug-in 4.43 to 4.42 and no longer get the exception. 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] [warnings-plugin] (JENKINS-25405) Warnings plugin fails
Daniel Beck commented on JENKINS-25405 Warnings plugin fails Caused by https://github.com/jenkinsci/analysis-core-plugin/commit/85faed9ae74508330b9428a309e46f640908fac1#diff-58abf9e6b6889b7667e0892d7813b435R275 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-16599) Master label settings are lost when configuring system settings
Stefan Landström closed JENKINS-16599 as Cannot Reproduce Master label settings are lost when configuring system settings Still able to reproduce this issue on LTS 1.580.1, but we're no longer depending on labels on the master so no big problem anymore. Change By: Stefan Landström (03/Nov/14 9:48 AM) Status: Resolved 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] [core] (JENKINS-25399) d:invokeBody can't parse argument number
stephenconnolly resolved JENKINS-25399 as Cannot Reproduce d:invokeBody cant parse argument number http://www.youtube.com/watch?v=amY6rzvolq4 Change By: stephenconnolly (03/Nov/14 9:50 AM) Status: Open Resolved Resolution: CannotReproduce 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] [checkstyle-plugin] (JENKINS-25408) View checkstyle 30 days slippery
Jonathan Jalouzot created JENKINS-25408 View checkstyle 30 days slippery Issue Type: Improvement Assignee: Ulli Hafner Attachments: viewgraph.png Components: checkstyle-plugin Created: 03/Nov/14 9:53 AM Description: Hi, My probleme is every 30th day of month my graph is reset to zero. I want graph in view 30 days slippery how it's possible ? Project: Jenkins Labels: plugin Priority: Minor Reporter: Jonathan Jalouzot 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] [warnings-plugin] (JENKINS-25405) Warnings plugin fails
Mike Krus commented on JENKINS-25405 Warnings plugin fails I'm having the same issue with Jenkins 1.585 and latest Warnings and Static Analysis plugins. Tried rolling back Warnings to 4.42 and Static Analysis to 1.62 (I had 1.64 which appears to have been removed) and it now works 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau edited a comment on JENKINS-25409 Add manual/scheduled commit for offline changes Is there a way to do that via a Groovy script? That would be neat for a temporary solution as a manual/scheduled job. 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau commented on JENKINS-25409 Add manual/scheduled commit for offline changes Is there a way to do that via a Groovy script? That would be neat for a temporary solution. 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] [scm-sync-configuration-plugin] (JENKINS-25409) Add manual/scheduled commit for offline changes
Andrei Neculau created JENKINS-25409 Add manual/scheduled commit for offline changes Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 03/Nov/14 10:13 AM Description: At times, changes can be made "offline", meaning not via Jenkins itself, but via awk, sed, manual editing, etc. The plugin could allow for 1) a manual sync - although this would be a manual step i.e. can easily be forgotten 2) a scheduled commit - every X minutes, sync all changes 3) sync all changes when calling "reload configuration from disk" Project: Jenkins Labels: plugin configuration Priority: Minor Reporter: Andrei Neculau 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] [mercurial-plugin] (JENKINS-25281) Mercurial plugin sometimes stalls when transferring bundle from master to slave
Kim Randell commented on JENKINS-25281 Mercurial plugin sometimes stalls when transferring bundle from master to slave We've had it happen one more time on a delta transfer. If/when it happens again I'll try to inspect the thread dumps on the master and slave and see if I can spot where FilePath.copyTo is getting stuck. 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-25144) Basic Authentication in combination with Session is broken
Christof Schoell assigned JENKINS-25144 to Unassigned Basic Authentication in combination with Session is broken Change By: Christof Schoell (03/Nov/14 10:16 AM) Assignee: KohsukeKawaguchi 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau created JENKINS-25410 Incorrect timestamp in footer status message Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 03/Nov/14 10:15 AM Description: At times, changes can be made "offline", meaning not via Jenkins itself, but via awk, sed, manual editing, etc. The plugin could allow for 1) a manual sync - although this would be a manual step i.e. can easily be forgotten 2) a scheduled commit - every X minutes, sync all changes 3) sync all changes when calling "reload configuration from disk" Project: Jenkins Labels: configuration plugin Priority: Minor Reporter: Andrei Neculau 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-25144) Basic Authentication in combination with Session is broken
Christof Schoell commented on JENKINS-25144 Basic Authentication in combination with Session is broken So is anyone going to pull the fix - it only needs to be merged after all? This is really annoying to us, since we would like to update our jenkins to a recent version and can't ... 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau updated JENKINS-25410 Incorrect timestamp in footer status message Change By: Andrei Neculau (03/Nov/14 10:18 AM) Description: Attimes,changescanbemadeoffline,meaningnotviaJenkinsitself,butviaawk,sed,manualediting,etc.Theplugincouldallowfor1)amanualsync - althoughthiswouldbeamanualstepi.e.caneasilybeforgotten2)ascheduledcommit - everyXminutes,syncallchanges3)syncallchangeswhencallingreloadconfigurationfromdisk invalid-- 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] [scm-sync-configuration-plugin] (JENKINS-25410) Incorrect timestamp in footer status message
Andrei Neculau resolved JENKINS-25410 as Not A Defect Incorrect timestamp in footer status message Sorry about this. I filed an invalid ticket. Change By: Andrei Neculau (03/Nov/14 10:17 AM) Status: Open Resolved Resolution: NotADefect 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] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu created JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 03/Nov/14 10:26 AM Description: We also tried downloading and putting correct tar.gz file in that location but the first time the plugin tries to start sauce connect it will overwrite it and set it back to size 0. Btw. problem seems to be that the file exists but with size 0. Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-10-74-140-248 FATAL: Error while expanding /usr/share/tomcat7/sc-4.3-linux.tar.gz org.codehaus.plexus.archiver.ArchiverException: Error while expanding /usr/share/tomcat7/sc-4.3-linux.tar.gz at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:101) at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:120) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.untarGzFile(SauceConnectFourManager.java:209) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.extractZipFile(SauceConnectFourManager.java:194) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.createProcessBuilder(SauceConnectFourManager.java:142) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:266) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:710) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:236) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.EOFException at java.util.zip.GZIPInputStream.readUByte(GZIPInputStream.java:246) at java.util.zip.GZIPInputStream.readUShort(GZIPInputStream.java:236) at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:140) at java.util.zip.GZIPInputStream.init(GZIPInputStream.java:56) at java.util.zip.GZIPInputStream.init(GZIPInputStream.java:65) at org.codehaus.plexus.archiver.tar.TarUnArchiver$UntarCompressionMethod.decompress(TarUnArchiver.java:191) at org.codehaus.plexus.archiver.tar.TarUnArchiver$UntarCompressionMethod.access$000(TarUnArchiver.java:112) at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:86) ... 13 more Unfortunately we cannot downgrade further to avoid this. (maybe it would work if we also downgraded Jenkins, don't know) Environment: Sauce OnDemand plugin 1.104 Jenkins 1.587 Project: Jenkins Priority: Minor Reporter: Andrei Costescu 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] [sauce-ondemand-plugin] (JENKINS-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu updated JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Change By: Andrei Costescu (03/Nov/14 10:28 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/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-23346) Path to android-sdk subfolders is incorrect
Nicolae Ghimbovschi commented on JENKINS-23346 Path to android-sdk subfolders is incorrect I'm experiencing the same with the latest Jenkins LTS version 1.580.1 and android-emulator-plugin version 2.12. It was fine with the previous version of android-emulator-plugin 2.10 and Jenkins LTS 1.565.1. The master is a windows and the slave is OS X. git clean -fdx # timeout=10 $ /opt/dailybuild/android/sdk\tools\android list target FATAL: Cannot run program "/opt/dailybuild/android/sdk\tools\android": error=2, No such file or directory java.io.IOException: Cannot run program "/opt/dailybuild/android/sdk\tools\android": error=2, No such file or directory 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] [android-emulator-plugin] (JENKINS-23346) Path to android-sdk subfolders is incorrect
Christopher Orr resolved JENKINS-23346 as Duplicate Path to android-sdk subfolders is incorrect Change By: Christopher Orr (03/Nov/14 10:47 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/d/optout.
[JIRA] [core] (JENKINS-25393) UI: Build History box looks bad with medium to long build labels
Daniel Beck updated JENKINS-25393 UI: Build History box looks bad with medium to long build labels Change By: Daniel Beck (03/Nov/14 10:46 AM) Labels: user-experience 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] [warnings-plugin] (JENKINS-25405) Warnings plugin fails
mwebber commented on JENKINS-25405 Warnings plugin fails Same problem running Jenkins 1.586. Downgrading Warnings 4.43 -- 4.42 Static Analysis 1.64 1.62 fixed the problem for me as well 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Paulo Moreira edited a comment on JENKINS-25241 svn+ssh checkout fails on remote nodes Hello, Same problem with: Jenkins ver. 1.587 SSH Slaves plugin 1.8 Subversion Plugin 2.4.4 Could this error be caused by: Updated SSH Slaves plugin to 1.8. (under version 1.585) ? 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] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
Dmitrijs Sahlovs commented on JENKINS-13940 Im trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. I am having the same issue with Jenkins 1.576 and AD plugin 1.38. Is there any workaround for this 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge updated JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Change By: Michael Niestegge (03/Nov/14 12:25 PM) Environment: Jenkins1.585RepositoryConnectorPlugin1.0.1 Artifactory2.6.6 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] [ssh-credentials-plugin] (JENKINS-25412) Update JSch to 0.1.49
theo . created JENKINS-25412 Update JSch to 0.1.49 Issue Type: Improvement Assignee: stephenconnolly Components: ssh-credentials-plugin Created: 03/Nov/14 12:41 PM Description: Hello, Today I faced an issue involving SSH with my Jenkins, the error is as follow: SSH Exception:Algorithm negotiation fail com.jcraft.jsch.JSchException: Algorithm negotiation fail at com.jcraft.jsch.Session.receive_kexinit(Session.java:520) at com.jcraft.jsch.Session.connect(Session.java:286) at com.jcraft.jsch.Session.connect(Session.java:150) at org.jvnet.hudson.plugins.SSHSite.createSession(SSHSite.java:141) at org.jvnet.hudson.plugins.SSHSite.executeCommand(SSHSite.java:151) at org.jvnet.hudson.plugins.SSHBuilder.perform(SSHBuilder.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This error happened because my OpenSSH version just upgraded from 6.6 to 6.7 (as most debian jessie users), in the OpenSSH changelog you can clearly see "The default set of ciphers and MACs has been altered to remove unsafe algorithms". OpenSSH 6.7 default key exchange algorithms: curve25519-sha...@libssh.org ecdh-sha2-nistp256 ecdh-sha2-nistp384 ecdh-sha2-nistp521 diffie-hellman-group-exchange-sha256 diffie-hellman-group14-sha1 Unfortunately ssh-credentials rely on JSch which use diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 for key exchange, and those algorithms are no longer part of OpenSSH default key exchange algos. Since version 0.1.49 JSch support diffie-hellman-group-exchange-sha256. I would suggest to update ssh-credentials dependency to rely on JSch 0.1.49, so everybody feel up to date and secure. Project: Jenkins Priority: Major Reporter: theo . 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] [multijob-plugin] (JENKINS-20846) MultiJobRunner has NullPointerException on unstable sub-builds
Mathieu Cantin resolved JENKINS-20846 as Fixed MultiJobRunner has NullPointerException on unstable sub-builds Change By: Mathieu Cantin (03/Nov/14 12:45 PM) Status: Open Resolved Resolution: Fixed 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] [logaction] (JENKINS-8233) Job restarted with Centralized Job(Re)Action plugin don't keep parameters from the original build
Tim-Christian Bloss commented on JENKINS-8233 Job restarted with Centralized Job(Re)Action plugin dont keep parameters from the original build The problem exists in "Centralized Job(Re)Action plugin" 1.2 and there's no release of a fixed version available/released yet. Even if "Naginator Plugin" may be a more modern/flexible plugin, which we're already using, the "Centralized Job(Re)Action plugin" has the advantage of being a "global" trigger, processing the log output of each and every job, while the "Naginator Plugin" requires individual configuration. Environment: Jenkins 1.565.3, Centralized Job(Re)Action plugin 1.2, Tomcat 7.0.54, JRE1.7.0_71, Debian GNU/Linux 7, amd64, de_DE.UTF-8 Besides this problem, the plugin works as expected. 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] [build-with-parameters-plugin] (JENKINS-25413) Hide job action (at least optionally) from UI
Oliver Gondža created JENKINS-25413 Hide job action (at least optionally) from UI Issue Type: Bug Assignee: Unassigned Components: build-with-parameters-plugin Created: 03/Nov/14 12:52 PM Description: Users are constantly confused about the difference between "Build with params" from plugin and "Build with parameters" from core. I expect there is no use-case where user would actually click "Build with params" as the whole point is providing get parameters. I suggest hiding the action from UI making it only available for direct URL access. Project: Jenkins Priority: Minor Reporter: Oliver Gondža 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] [build-with-parameters-plugin] (JENKINS-18692) Duplicate link
Oliver Gondža
resolved JENKINS-18692 as Duplicate
Duplicate link
I am not aware of any way to replace the core action ("Build with Parameters") from plugin. Closing this as a duplicate of JENKINS-25413 that suggests hiding the action contributed from plugin from Jenkins UI.
Change By:
Oliver Gondža
(03/Nov/14 12:57 PM)
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/d/optout.
[JIRA] [build-with-parameters-plugin] (JENKINS-21635) Security hole: Build permission is ignored, anyone that can reach the link can run the job.
Oliver Gondža updated JENKINS-21635 Security hole: Build permission is ignored, anyone that can reach the link can run the job. Change By: Oliver Gondža (03/Nov/14 1:00 PM) Priority: Critical Minor Labels: permissions security 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] [build-with-parameters-plugin] (JENKINS-21635) Build permission is ignored, anyone can reach the link
Oliver Gondža updated JENKINS-21635 Build permission is ignored, anyone can reach the link Change By: Oliver Gondža (03/Nov/14 1:03 PM) Summary: Securityhole: Buildpermissionisignored,anyone that canreachthelink canrunthejob. 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] [build-with-parameters-plugin] (JENKINS-21635) Security hole: Build permission is ignored, anyone that can reach the link can run the job.
Oliver Gondža commented on JENKINS-21635 Security hole: Build permission is ignored, anyone that can reach the link can run the job. Note that an attempt to actually build the job will be rejected with SecurityException, therefore this is not a security hole. 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] [logaction] (JENKINS-8233) Job restarted with Centralized Job(Re)Action plugin don't keep parameters from the original build
Oleg Nenashev commented on JENKINS-8233 Job restarted with Centralized Job(Re)Action plugin dont keep parameters from the original build I'm not sure if the plugin is being supported now. If you want to contribute/take the ownership, contact jie...@gmail.com and then send a e-mail to jenkinsci-...@googlegroups.com 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] [build-with-parameters-plugin] (JENKINS-25413) Hide job action (at least optionally) from UI
Oliver Gondža commented on JENKINS-25413 Hide job action (at least optionally) from UI Another option is to introduction confirm parameter for core url to do the same thing. 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] [build-with-parameters-plugin] (JENKINS-21635) Build permission is ignored, anyone can reach the link
Oliver Gondža resolved JENKINS-21635 as Duplicate Build permission is ignored, anyone can reach the link Change By: Oliver Gondža (03/Nov/14 1:13 PM) 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/d/optout.
[JIRA] [core] (JENKINS-19183) File Parameter: Creates an empty file when no file is uploaded
Oliver Gondža updated JENKINS-19183 File Parameter: Creates an empty file when no file is uploaded Change By: Oliver Gondža (03/Nov/14 1:16 PM) Component/s: core Component/s: build-with-parameters-plugin 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-21869) Github webhook using post request doen't work
Oliver Gondža updated JENKINS-21869 Github webhook using post request doent work Change By: Oliver Gondža (03/Nov/14 1:20 PM) Component/s: core Component/s: build-with-parameters-plugin 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-19266) Build section: trigger build on other project fails
Oliver Gondža updated JENKINS-19266 Build section: trigger build on other project fails Change By: Oliver Gondža (03/Nov/14 1:18 PM) Component/s: core Component/s: build-with-parameters-plugin 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Thomas Pummer commented on JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request After using the workaround (Disabling "Prevent Cross Site Request Forgery exploits") it could not be reproduced at our jenkins installation, even if it was turned back on. 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
G. Kr. commented on JENKINS-12523 Could not initialize class org.libvirt.Connect same issue with jenkins 1.587 / libvirt-slave-plugin 1.8.4 on Debian Wheezy 7.7 $ java -version java version "1.7.0_65" OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-5~deb7u1) OpenJDK Server VM (build 24.65-b04, mixed mode) javax.servlet.ServletException: java.lang.NoClassDefFoundError: Could not initialize class org.libvirt.Connect at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at
[JIRA] [sonar] (JENKINS-21607) Option to auto escape characters not allowed in sonar branches
Michael Rüegg
commented on JENKINS-21607
Option to auto escape characters not allowed in sonar branches
This feature is a must to use Sonar together with Git because nearly all Git-based workflows propose a branch naming pattern like "bugfixes/bugXY" or "features/newFeatureXY" which at least have one character ('/') that is not allowed in Sonar when using "-Dsonar.branch=". Would be highly appreciated!
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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Jarosław Strzelecki commented on JENKINS-25241 svn+ssh checkout fails on remote nodes @Paulo Moreira Problem still occurred after I've downgraded "SSH Slaves plugin" to 1.7 Downgrading to Jenkins 1.586 solved the problem. 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] [git-plugin] (JENKINS-25304) Job polling hangs while a build is running - only when branch specifier contains wildcard
Wannes Sels commented on JENKINS-25304 Job polling hangs while a build is running - only when branch specifier contains wildcard The issue is in the logic that decides how to do polling, see GitSCM.requiresWorkspaceForPolling(). If you specify one repository and one branch, the wildcard in the branchname before "/" can only be expanded to the single repository. If however you specify a wildcard in the branch name, GitAPI.getHeadRev(remoteRepoUrl, branchSpec) would return the first matching branchName instead of all matching branches. I suppose you could change GitSCM.compareRemoteRevisionWithImpl to get all branches with GitAPI.getHeadRev(remoteRepoUrl), and check each one if it has been built. 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] [junit-plugin] (JENKINS-25375) Testlink plugin throws an NoSuchMethodError
paul peschel commented on JENKINS-25375 Testlink plugin throws an NoSuchMethodError I test the snapshot and it work success. 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] [tasks-plugin] (JENKINS-25407) hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations
Syed Amer Gilani commented on JENKINS-25407 hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations The same happens with the LTS Version 1.580.1 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] [performance-plugin] (JENKINS-25415) Develop and implement a Continuous Integration Experience Index
Torsten Schlabach created JENKINS-25415 Develop and implement a Continuous Integration Experience Index Issue Type: Improvement Assignee: Manuel Carrasco Components: performance-plugin Created: 03/Nov/14 2:57 PM Description: The time it takes for a Jenkins based build pipeline to pump artifacts from source code into deployed applications matters to most agile and less agile teams and there is a phletora of attemtps underway in many organizations to "improve build time". Just there is no objective criteria at all to tell if the time it takes for a build to be processed is accetable or not. If your build takes e.g. 45 minutes, is that good or bad? Any especially there is hardly any criteria to compare hardware in terms of build performance, so there is little chance to find out if your build times would shorten if you move from VMs to phyiscal hardware, if you add more RAM, if you add slaves, if you upgrade the VCS server, ... Microsoft provides something very simple (to reads, talk about and compare) with the Windows Experience Index (WIE). Jenkins might be the natural component to perform such measurements in build pipeline as Jenkins is usually the controller which coordinates and thus would be able to measure amounts and time of VCS checkouts / updates, compilation and artifact deployment. Project: Jenkins Priority: Minor Reporter: Torsten Schlabach 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Paulo Moreira edited a comment on JENKINS-25241 svn+ssh checkout fails on remote nodes Hello, Same problem with: Jenkins ver. 1.587 SSH Slaves plugin 1.8 Subversion Plugin 2.4.4 jdk1.7.0_71 and jdk1.7.0_72 Could this error be caused by: Updated SSH Slaves plugin to 1.8. (under version 1.585) ? Roolback to Jenkins 1.583 and solved the problem. 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Paulo Moreira commented on JENKINS-25241 svn+ssh checkout fails on remote nodes Downgraded to 1.583 solved the problem not 1.586! 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Jarosław Strzelecki edited a comment on JENKINS-25241 svn+ssh checkout fails on remote nodes @Paulo Moreira Problem still occurred after I've downgraded "SSH Slaves plugin" to 1.7 Downgrading to Jenkins 1.586 solved the problem (in my case). 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] [maven-plugin] (JENKINS-25416) text parameter with newlines causing the default goal run
Thomas Wabner created JENKINS-25416 text parameter with newlines causing the default goal run Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 03/Nov/14 2:57 PM Description: I have a required build-parameter "build_reason" of type text. Our users can insert some free-text for the build reason. If the parameter contains, for example, following input in the text-box: "first line second line" then jenkins calling maven in the following way: testwebapp_svn_commit $ D:\applications\prg\ApacheMaven\current-maven\bin\mvn.bat -Dbuild_reason_org=first line scond line -Dpart_svn_url=trunk/devopts/testprojects validate This causes maven to simple run the default goal and ignore all other parameters. It seems that the text parameter is not escaped correct. This problem does not apply only to maven .. it applies to all builds where such parameter is injected. Waffel Environment: Jenkins 1.583, Windows, Java 7U72 Project: Jenkins Labels: jenkins maven3 parameter build Priority: Major Reporter: Thomas Wabner 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Jarosław Strzelecki edited a comment on JENKINS-25241 svn+ssh checkout fails on remote nodes @Paulo Moreira Problem still occurred after I've downgraded "SSH Slaves plugin" to 1.7 Downgrading to Jenkins 1.584 solved the problem (in my case). 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] [tasks-plugin] (JENKINS-25407) hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations
Antoine Aumjaud commented on JENKINS-25407 hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations same here. Error linked to this commit: https://github.com/jenkinsci/analysis-core-plugin/commit/85faed9ae74508330b9428a309e46f640908fac1 addAnnotation method returns void before and now an int. tasks-4.43 has been compiled with the old version (void). https://github.com/jenkinsci/tasks-plugin/blob/master/pom.xml - 1.58 To fix this issue, you need to rollbak to analysis-core-1.62 or wait for the pull request: https://github.com/jenkinsci/tasks-plugin/pull/1 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] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Jan Feindt commented on JENKINS-25115 Recognize failures indicated by JUnit test result file The analysis of test errors is a feature that I would also like to use. However, in context of integration testing I would like to detect communication or configuration errors. For this i would like to use a multi-line regex for failure details, failure stacktrace, failure stderr and failure stdout. Any suggestions? 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] [junit-plugin] (JENKINS-25417) Would like for a way to include setup time in the test duration
Aurelian Teglas created JENKINS-25417 Would like for a way to include setup time in the test duration Issue Type: Improvement Assignee: Unassigned Attachments: Screenshot1.png, Screenshot2.png, SomeTest.java Components: junit-plugin Created: 03/Nov/14 3:53 PM Description: The duration of the test results in the JUnit Plugin is just the time that is being reported on the testcase .../ line. This time contains only the time it took to run the @Before, @Test and @After annotated methods. The time that it took for the class creation, the object creation and for the @BeforeClass and @AfterClass annotated methods will show up in the testsuite .../ line. The way things are now, there are cases with crappy tests that show up as decently fast, just because a large bunk of the time is not taken into account. Would it be possible to add this time as well? Sample file with the times from a test class (class code attached): ?xml version="1.0" encoding="UTF-8" ? testsuite errors="0" failures="0" hostname="localhost" name="com.mypackage.SomeTest" skipped="0" tests="3" time="13.75" timestamp="2014-11-03T15:08:13" testcase classname="com.mypackage.SomeTest" name="testSomething1" time="0.215" / testcase classname="com.mypackage.SomeTest" name="testSomething2" time="0.211" / testcase classname="com.mypackage.SomeTest" name="testSomething3" time="0.211" / /testsuite Screenshot1.png This is the snapshot of the plugin output. As you can see, it only takes into account the ~210ms from before, after and test. The bulk of the time however (13sec vs 630ms) is spent in other parts of the test class and that time is not accounted for. Screenshot2.png This is a snapshot from a modified version of the plugin. This modified version will take the extra time and distribute it evenly between all the tests in the suite. So, if this is something that would be considered good to include in the plugin, my questions are: 1. Would there be a need to make this configurable (as in provide an option when publishing junit results about what to do with the extra time)? 2. Which would be the "preferred" way to include the time. I've played with more versions: create a new init test case that would be added to the suite and contain the extra time (clear extra time, but adds a non existent test case) distribute the extra time evenly to the test cases in the test suite distribute the extra time according to the time weight to the test cases in the test suite (a test case taking 2ms would get twice the amount of extra time compared to a test case taking 1ms). Project: Jenkins Priority: Minor Reporter: Aurelian Teglas 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] [tasks-plugin] (JENKINS-25407) hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations
Antoine Aumjaud commented on JENKINS-25407 hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations I have rollbacked the plugin analysis-core:1.64 'Static Analysis Utilities' to version 1.59 (proposed by Jenkins in plugins management) and it works 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] [project-inheritance] (JENKINS-22885) Creation of Inheritance Project throws Exception
Linh N commented on JENKINS-22885 Creation of Inheritance Project throws Exception Vladimir Kralik, thanks so much for the workaround, it helped a lot! I didn't have the option of "Safe HTML", so I chose "Raw HTML" and it worked! 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak created JENKINS-25418 Failed to load hudson.matrix.MatrixProject with 1.588 Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 03/Nov/14 4:47 PM Description: I updated to 1.588 from I believe 1.581 and now none of my matrix jobs load nor can I create any. Log shows this: Nov 03, 2014 8:23:12 AM WARNING hudson.ExtensionFinder$GuiceFinder instantiate Failed to load hudson.matrix.MatrixProject java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction at net.java.sezpoz.IndexItem.instance(IndexItem.java:193) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:352) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:231) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:528) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:426) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:388) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:379) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:345) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.diagnosis.NullIdDescriptorMonitor.verify(NullIdDescriptorMonitor.java:68) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89) 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 hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:886) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) Caused by: java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2484) at java.lang.Class.getMethod0(Class.java:2727) at java.lang.Class.getMethod(Class.java:1639) at hudson.model.Descriptor.init(Descriptor.java:284) at hudson.model.TopLevelItemDescriptor.init(TopLevelItemDescriptor.java:47) at hudson.model.AbstractProject$AbstractProjectDescriptor.init(AbstractProject.java:2003) at
[JIRA] [multijob-plugin] (JENKINS-24139) Stoping Multi Job should stop all downstream (phase 1/2/3 etc) jobs
Mathieu Cantin closed JENKINS-24139 as Fixed Stoping Multi Job should stop all downstream (phase 1/2/3 etc) jobs Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Resolved 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] [multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
Mathieu Cantin closed JENKINS-23161 as Fixed Aborted or failed job in a phase does not immediately cause the multi-job to fail Change By: Mathieu Cantin (03/Nov/14 4:48 PM) Status: Resolved 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] [multijob-plugin] (JENKINS-20846) MultiJobRunner has NullPointerException on unstable sub-builds
Mathieu Cantin closed JENKINS-20846 as Fixed MultiJobRunner has NullPointerException on unstable sub-builds Change By: Mathieu Cantin (03/Nov/14 4:47 PM) Status: Resolved 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] [multijob-plugin] (JENKINS-20273) Aborting the master job should abort all the downstream
Mathieu Cantin resolved JENKINS-20273 as Fixed Aborting the master job should abort all the downstream Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Open Resolved Resolution: Fixed 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] [multijob-plugin] (JENKINS-24139) Stoping Multi Job should stop all downstream (phase 1/2/3 etc) jobs
Mathieu Cantin resolved JENKINS-24139 as Fixed Stoping Multi Job should stop all downstream (phase 1/2/3 etc) jobs Change By: Mathieu Cantin (03/Nov/14 4:48 PM) Status: Open Resolved Resolution: Fixed 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] [multijob-plugin] (JENKINS-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail
Mathieu Cantin resolved JENKINS-23161 as Fixed Aborted or failed job in a phase does not immediately cause the multi-job to fail Change By: Mathieu Cantin (03/Nov/14 4:47 PM) Status: Open Resolved Resolution: Fixed 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] [multijob-plugin] (JENKINS-22292) Canceling multijob should cancel all children
Mathieu Cantin closed JENKINS-22292 as Fixed Canceling multijob should cancel all children Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Resolved 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] [multijob-plugin] (JENKINS-23968) Add the ability make a phase job conditional
Mathieu Cantin closed JENKINS-23968 as Fixed Add the ability make a phase job conditional Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Resolved 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak
updated JENKINS-25418
Failed to load hudson.matrix.MatrixProject with 1.588
Change By:
Kevin Wojniak
(03/Nov/14 4:49 PM)
Description:
Iupdatedto1.588fromIbelieve1.581andnownoneofmymatrixjobsloadnorcanIcreateany.Logshowsthis:
{code}
Nov03,20148:23:12AMWARNINGhudson.ExtensionFinder$GuiceFinderinstantiateFailedtoloadhudson.matrix.MatrixProjectjava.lang.InstantiationException:java.lang.NoClassDefFoundError:hudson/tasks/test/AggregatedTestResultAction atnet.java.sezpoz.IndexItem.instance(IndexItem.java:193) athudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:352) athudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:231) athudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:528) atcom.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) atcom.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) atcom.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) atcom.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) atcom.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) atcom.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) atcom.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) atcom.google.inject.Scopes$1$1.get(Scopes.java:65) athudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:426) atcom.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) atcom.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) atcom.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) atcom.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) athudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:388) athudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:379) athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:345) athudson.ExtensionList.load(ExtensionList.java:300) athudson.ExtensionList.ensureLoaded(ExtensionList.java:253) athudson.ExtensionList.iterator(ExtensionList.java:143) athudson.diagnosis.NullIdDescriptorMonitor.verify(NullIdDescriptorMonitor.java:68) athudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89) 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) athudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) athudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) atjenkins.model.Jenkins$7.runTask(Jenkins.java:886) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) atjava.lang.Thread.run(Thread.java:695)Causedby:java.lang.NoClassDefFoundError:hudson/tasks/test/AggregatedTestResultAction atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2484) atjava.lang.Class.getMethod0(Class.java:2727) atjava.lang.Class.getMethod(Class.java:1639) athudson.model.Descriptor.init(Descriptor.java:284) athudson.model.TopLevelItemDescriptor.init(TopLevelItemDescriptor.java:47) athudson.model.AbstractProject$AbstractProjectDescriptor.init(AbstractProject.java:2003) athudson.matrix.MatrixProject$DescriptorImpl.init(MatrixProject.java:943) athudson.matrix.MatrixProject.clinit(MatrixProject.java:941) atsun.misc.Unsafe.ensureClassInitialized(NativeMethod) atsun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25) atsun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
[JIRA] [multijob-plugin] (JENKINS-22292) Canceling multijob should cancel all children
Mathieu Cantin resolved JENKINS-22292 as Fixed Canceling multijob should cancel all children Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Open Resolved Resolution: Fixed 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] [multijob-plugin] (JENKINS-23968) Add the ability make a phase job conditional
Mathieu Cantin resolved JENKINS-23968 as Fixed Add the ability make a phase job conditional Change By: Mathieu Cantin (03/Nov/14 4:49 PM) Status: Open Resolved Resolution: Fixed 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak
updated JENKINS-25418
Failed to load hudson.matrix.MatrixProject with 1.588
Change By:
Kevin Wojniak
(03/Nov/14 4:58 PM)
Description:
Iupdatedto1.588from
Ibelieve
1.581andnownoneofmymatrixjobsloadnorcanIcreateany.Logshowsthis:{code}Nov03,20148:23:12AMWARNINGhudson.ExtensionFinder$GuiceFinderinstantiateFailedtoloadhudson.matrix.MatrixProjectjava.lang.InstantiationException:java.lang.NoClassDefFoundError:hudson/tasks/test/AggregatedTestResultAction atnet.java.sezpoz.IndexItem.instance(IndexItem.java:193) athudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:352) athudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:231) athudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:528) atcom.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) atcom.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) atcom.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) atcom.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) atcom.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) atcom.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) atcom.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) atcom.google.inject.Scopes$1$1.get(Scopes.java:65) athudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:426) atcom.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) atcom.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) atcom.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) atcom.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) athudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:388) athudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:379) athudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:345) athudson.ExtensionList.load(ExtensionList.java:300) athudson.ExtensionList.ensureLoaded(ExtensionList.java:253) athudson.ExtensionList.iterator(ExtensionList.java:143) athudson.diagnosis.NullIdDescriptorMonitor.verify(NullIdDescriptorMonitor.java:68) athudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89) 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) athudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) athudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) atjenkins.model.Jenkins$7.runTask(Jenkins.java:886) atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) atjava.lang.Thread.run(Thread.java:695)Causedby:java.lang.NoClassDefFoundError:hudson/tasks/test/AggregatedTestResultAction atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2484) atjava.lang.Class.getMethod0(Class.java:2727) atjava.lang.Class.getMethod(Class.java:1639) athudson.model.Descriptor.init(Descriptor.java:284) athudson.model.TopLevelItemDescriptor.init(TopLevelItemDescriptor.java:47) athudson.model.AbstractProject$AbstractProjectDescriptor.init(AbstractProject.java:2003) athudson.matrix.MatrixProject$DescriptorImpl.init(MatrixProject.java:943) athudson.matrix.MatrixProject.clinit(MatrixProject.java:941) atsun.misc.Unsafe.ensureClassInitialized(NativeMethod) atsun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25) atsun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
[JIRA] [svnmerge-plugin] (JENKINS-24735) Add support for build parameters in Subversion URLs.
SCM/JIRA link daemon commented on JENKINS-24735 Add support for build parameters in Subversion URLs. Code changed in jenkins User: Hugues Chabot Path: src/main/java/jenkins/plugins/svnmerge/Utility.java http://jenkins-ci.org/commit/svnmerge-plugin/344a848c5d48ce2904b42aed3ad962b73d3f7f5b Log: Merge pull request #18 from alexouzounis/JENKINS-24735 JENKINS-24735 - Add support for build parameters in Subversion URLs Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/d845cf04cb76...344a848c5d48 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] [svnmerge-plugin] (JENKINS-24735) Add support for build parameters in Subversion URLs.
SCM/JIRA link daemon commented on JENKINS-24735 Add support for build parameters in Subversion URLs. Code changed in jenkins User: Alexandros Ouzounis Path: src/main/java/jenkins/plugins/svnmerge/Utility.java http://jenkins-ci.org/commit/svnmerge-plugin/8e1a3b75d19221d1dd2c2edffac35fb23640b2ba Log: JENKINS-24735 - Add support for build parameters in Subversion URLs Add support for Global Node Properties as well 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Oleg Nenashev commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I don;t see the issue on newest cores as well 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak commented on JENKINS-25418 Failed to load hudson.matrix.MatrixProject with 1.588 Looks like it's unrelated. I downgraded to 1.581 and still the same issue. At one point I disabled some plugins I thought weren't unrelated, but looks like they are. Going to go one by one and see which one is required. 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak resolved JENKINS-25418 as Not A Defect Failed to load hudson.matrix.MatrixProject with 1.588 Change By: Kevin Wojniak (03/Nov/14 5:33 PM) Status: Open Resolved Resolution: NotADefect 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Kevin Wojniak commented on JENKINS-25418 Failed to load hudson.matrix.MatrixProject with 1.588 Disabling JUnit causes the issue. I don't use this but I guess it has some internal dependency? 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-12649) Need to activate Security to see options TCP port for JNLP slave agents and Markup Formatter
Daniel Beck resolved JENKINS-12649 as Duplicate Need to activate Security to see options TCP port for JNLP slave agents and Markup Formatter Duplicates JENKINS-4478 for the part that's not yet implemented. Change By: Daniel Beck (03/Nov/14 5:39 PM) 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/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-13940) I'm trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works.
Daniel Beck commented on JENKINS-13940 Im trying to authenticate the Jenkins command line (CLI) and the system returns an error message (user authentication with AD), but the GUI works. Could anyone confirm Gardner Bickford's workaround of using an API token instead of a password? 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] [analysis-core-plugin] (JENKINS-25405) Analysis core plugin dependent plugin fails with NoSuchMethodError
Oliver Gondža updated JENKINS-25405 Analysis core plugin dependent plugin fails with NoSuchMethodError Change By: Oliver Gondža (03/Nov/14 5:50 PM) Summary: Warnings Analysiscore plugin dependentplugin fails withNoSuchMethodError Priority: Major Critical Component/s: analysis-core-plugin Component/s: warnings-plugin 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] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Oliver Gondža updated JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Change By: Oliver Gondža (03/Nov/14 5:57 PM) Summary: Pluginsdependingon Analysis core Core plugin dependentplugin failswithNoSuchMethodError 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] [build-with-parameters-plugin] (JENKINS-25413) Hide job action (at least optionally) from UI
Daniel Beck commented on JENKINS-25413 Hide job action (at least optionally) from UI "Confirm"? Isn't this about providing different default via GET parameters? FWIW I've started work on a core change a while back: https://github.com/daniel-beck/jenkins/commit/d9f140904b7850c77f68829b2161d8d2ee39e85c 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] [nunit-plugin] (JENKINS-25295) Do not fail when no Nunit test reports found
Dale Hards commented on JENKINS-25295 Do not fail when no Nunit test reports found I'd like to check this bug has been noticed? It is causing a fairly major headache on our build system. 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-19183) File Parameter: Creates an empty file when no file is uploaded
Daniel Beck resolved JENKINS-19183 as Duplicate File Parameter: Creates an empty file when no file is uploaded Duplicates reopened JENKINS-3539 that was fixed in 1.586 Change By: Daniel Beck (03/Nov/14 6:02 PM) 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25362) Cannot start parametrized freestyle job from workflow plugin
Marcin Gawenda commented on JENKINS-25362 Cannot start parametrized freestyle job from workflow plugin The same issue exists on: jenkins-1.585 workflow-0.1-beta-6 and jenkins-1.580.1 workflow-0.1-beta-6 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] [job-dsl-plugin] (JENKINS-21216) Add support for Folder job type
kutzi commented on JENKINS-21216 Add support for Folder job type Oh, sorry for the noise. I was only looking at https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference and https://github.com/jenkinsci/job-dsl-plugin/wiki/View-Reference, since they promise to have "all options" I guess the original PR https://github.com/jenkinsci/job-dsl-plugin/pull/120 can then be closed, too? 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] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Ireneusz Makowski commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Is there any ETA for 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/d/optout.
[JIRA] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
Daniel Beck commented on JENKINS-12523 Could not initialize class org.libvirt.Connect The plugin should bundle its own JNA and usePluginFirstClassLoader. Core needed to use JNA 4 due to numerous bugs in 3.x. 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] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
timothy luksha commented on JENKINS-25070 Subversion fails to update externals once after external is changed. We have been experiencing a similar exception intermittently during updates executed when Jenkins does a build of our software. Based on James Noonan's findings, we tried changing a file in a directory that is referenced as an external. The first build's update/checkout failed with the subversion exception, and then the second build updated without any error. We have reproduced this pattern more than three times now. Our plugin is version 2.4.3. Is there any other information we could collect to assist with pinning this down? 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] [tfs-plugin] (JENKINS-4943) Unable to parse history for /author checkins
pescuma commented on JENKINS-4943 Unable to parse history for /author checkins I'm using version 3.1.1 and it is showing the committer as the author (the one in 'Checked in by:' field). Shouldn't it show the author (the one in 'User:' field)? 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] [cobertura-plugin] (JENKINS-25419) cobertura plugin - option - be able to exclude metrics from graph
Greg Moncreaff created JENKINS-25419 cobertura plugin - option - be able to exclude metrics from graph Issue Type: Improvement Assignee: stephenconnolly Components: cobertura-plugin Created: 03/Nov/14 6:38 PM Description: when working with C++, I typically see class and package coverage at 100% while line branch coverage could be considerably lower. Would like option to be able to exclude (especially package, class) from the graph (especially the zoomed) to better see what is going on with other metrics (e.g. line) if this requires filtering the tables (e.g. removing from graph also removes a column from table, that is fine) Project: Jenkins Priority: Minor Reporter: Greg Moncreaff 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] [tasks-plugin] (JENKINS-25407) hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations
Daniel Beck resolved JENKINS-25407 as Duplicate hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations Duplicates JENKINS-25405 Change By: Daniel Beck (03/Nov/14 6:40 PM) 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/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
Oliver Gondža commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Proposing fix using @WithBridgeMethods(value=void.class): https://github.com/jenkinsci/analysis-core-plugin/pull/25 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] [job-dsl-plugin] (JENKINS-21216) Add support for Folder job type
Daniel Spilker
commented on JENKINS-21216
Add support for Folder job type
I left #120 open because it adds nested jobs and folders, e.g.
folder {
...
job {
...
}
}
But the PR needs to be reworked to get 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
--
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] [build-flow-plugin] (JENKINS-25420) Stack trace thrown even with simply failure fail in parallel block
Ronald Chen
created JENKINS-25420
Stack trace thrown even with simply failure fail in parallel block
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow-plugin
Created:
03/Nov/14 6:49 PM
Description:
An ugly stack trace is thrown when a job fails within a parallel block that has more than one job. This makes it really hard to understand why the build flow failed.
For example, given a build flow:
parallel (
{
build("always-pass")
},
{
build("always-fail")
build("always-pass")
}
)
I expect the following console log:
parallel {
Schedule job always-pass
Schedule job always-fail
Build always-pass #2 started
Build always-fail #2 started
always-fail #2 completed : FAILURE
always-pass #2 completed
}
Finished: FAILURE
But I got:
parallel {
Schedule job always-fail
Schedule job always-pass
Build always-pass #3 started
Build always-fail #6 started
always-fail #6 completed : FAILURE
always-pass #3 completed
ERROR: Failed to run DSL Script
java.util.concurrent.ExecutionException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.plugins.flow.JobExecutionFailureException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at java_util_concurrent_Future$get.call(Unknown Source)
at com.cloudbees.plugins.flow.FlowDelegate$_parallel_closure6.doCall(FlowDSL.groovy:440)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.Closure.call(Closure.java:415)
at groovy.lang.Closure.call(Closure.java:428)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1379)
at org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1351)
at org.codehaus.groovy.runtime.dgm$170.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
at com.cloudbees.plugins.flow.FlowDelegate.parallel(FlowDSL.groovy:438)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1079)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:723)
at com.cloudbees.plugins.flow.FlowDelegate.invokeMethod(FlowDSL.groovy)
at hudson.util.spring.ClosureScript.invokeMethod(ClosureScript.java:83)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:72)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
at
[JIRA] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Daniel Beck commented on JENKINS-25241 svn+ssh checkout fails on remote nodes Caused by https://github.com/jenkinsci/jenkins/commit/70f5968160b0a1cf81dc451fd2aacf1e0f9201ea that was released in 1.585. Proposed workaround at https://github.com/jenkinsci/subversion-plugin/pull/102 Could someone download and install the 2.4.x snapshot build from https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/449/ (once finished) and test the result? 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] [matrix-project-plugin] (JENKINS-25418) Failed to load hudson.matrix.MatrixProject with 1.588
Daniel Beck commented on JENKINS-25418 Failed to load hudson.matrix.MatrixProject with 1.588 Yes. JUnit Plugin was extracted from Jenkins core so it's only a "implied" dependency of some plugins, not an explicit one. It's safest to not disable bundled plugins. 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] [tasks-plugin] (JENKINS-25407) hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations
Antoine Aumjaud edited a comment on JENKINS-25407 hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on channel failed: hudson.plugins.tasks.parser.TasksParserResult.addAnnotations I have downgraded the plugin analysis-core:1.64 'Static Analysis Utilities' to version 1.59 (proposed by Jenkins in plugins management) and it works 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] [subversion-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Chris Reynolds commented on JENKINS-25241 svn+ssh checkout fails on remote nodes Verified that the issue appears to be fixed with the following configuration: Jenkins: 1.588 subversion-plugin: 2.4.5-SNAPSHOT (private-11/03/2014 14:02-jenkins) 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Daniel Beck commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 Anyone still able to reproduce this issue on recent Jenkins + Plugin versions? 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] [maven-plugin] (JENKINS-25416) text parameter with newlines causing the default goal run
Daniel Beck commented on JENKINS-25416 text parameter with newlines causing the default goal run Is that a freestyle project with maven build step, or a maven project? 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-18032) Delete Project link fails with 403 Exception: No valid crumb was included in the request
Daniel Beck commented on JENKINS-18032 Delete Project link fails with 403 Exception: No valid crumb was included in the request In the security configuration where CSRF protection is selected, is the Default Crumb Issuer also selected? 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.
