[JIRA] [core] (JENKINS-4478) Move TCP port out from under security
Jan Klass commented on JENKINS-4478 Move TCP port out from under security First of all, the port being under security was a bit unexpected on our end. Having to enable security (we have it disabled) is very unintuitive and cost us time to figure out. That the JNLP port is bound no matter the enable security setting being turned on or off, is very questionable and confusing. This should defiitely be changed ASAP, to prevent user confusion. Especially, since simply moving the setting but keeping it as is should be rather simple!? On one LTS installation, I have security enabled, but use anonymous access anyway. On a second installation, we use anonymous access with security disabled. The confusing part is that on the second installation, I can enable security to set the JNLP port, and then save the settings. Checking back, security is still disabled (I guess because no Security Realm was chosen) but the port is set. This is a very unintuitive and hidden behaviour. This is assigned to @Kohsuke Kawaguchi, I guess since 2009. Is this something you can and will do? Or would it be helpful if someone from the community jumped in? 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-4478) Move TCP port out from under security
Jan Klass edited a comment on JENKINS-4478 Move TCP port out from under security It would also be helpful, if the node configuration setting for JNLP port (tunneling) would be a bit more elaborative about the server JNLP port, and where it is configured. In our case, even when changing the JNLP port, it was not necessary to configure anything there (as jenkins sends it to the slave on initial connection by the slave). 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] [artifactdeployer-plugin] (JENKINS-25806) Artifact Deployer plugin 0.32 doing nothing
pedro reis commented on JENKINS-25806 Artifact Deployer plugin 0.32 doing nothing Am I doing something wrong? 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] [rebuild-plugin] (JENKINS-25815) Rebuild plugin doesn't load all Parameters
Daniel Beck resolved JENKINS-25815 as Duplicate Rebuild plugin doesnt load all Parameters Change By: Daniel Beck (28/Nov/14 8:44 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] [rebuild-plugin] (JENKINS-25815) Rebuild plugin doesn't load all Parameters
Sanketh PB commented on JENKINS-25815 Rebuild plugin doesnt load all Parameters Please clarify in which version of rebuild plugin is this fix available? In the latest available version 1.22, issue still exists. 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] [configurationslicing-plugin] (JENKINS-25820) javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[type] not found. is shown when saving the configration
li sky created JENKINS-25820 javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[type] not found. is shown when saving the configration Issue Type: Bug Assignee: mdonohue Components: configurationslicing-plugin Created: 28/Nov/14 9:34 AM Description: when I was trying to save the configrations of the jenkins ,this error msg is shown: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: net.sf.json.JSONException: JSONObjecttype not found. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:783) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at
[JIRA] [ec2-plugin] (JENKINS-20742) EC2 plugin does not delete slaves that failed to start
arazauci commented on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from for anyone who fixes this annoying 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] [ec2-plugin] (JENKINS-20742) EC2 plugin does not delete slaves that failed to start
arazauci edited a comment on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from me for anyone who fixes this annoying 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] [ec2-plugin] (JENKINS-20742) EC2 plugin does not delete slaves that failed to start
arazauci edited a comment on JENKINS-20742 EC2 plugin does not delete slaves that failed to start +1 $500 from me for anyone who fixes this annoying issue https://freedomsponsors.org/issue/412/ec2-plugin-does-not-delete-slaves-that-failed-to-start?alert=SPONSOR#sponsors 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] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
kutzi commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding I don't remember the details anymore, but as far as I remember setting the packet reply timeout won't help in this case. We would need to set a connection timeout, but that is not possible. Or at least was not possible at that time. As stated earlier: pull requests are welcome! 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] [ec2-plugin] (JENKINS-8618) would like to use one instance per build
arazauci commented on JENKINS-8618 would like to use one instance per build +1 $500 for whoever fixes this https://freedomsponsors.org/issue/594/would-like-to-use-one-instance-per-build?alert=SPONSOR# 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] [envinject-plugin] (JENKINS-25821) Global Mask Password are visible as a plain text in Environment Variables tab
Andrzej Obstoj created JENKINS-25821 Global Mask Password are visible as a plain text in Environment Variables tab Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin, mask-passwords-plugin Created: 28/Nov/14 9:49 AM Description: Global Mask password are visible as a plain text in Environment Variables tab. You need to go job then click on specific build and on the left menu there is Environment Variables tab. Inside this table the mask passowrd can be read as a plain text. Password which are passed to job as a Password parameter are coded in this tab. Environment: Jenkins version 1.591 Mask Password plugin version - 2.7.2 Environment Injector Plugin - 1.9 Project: Jenkins Priority: Major Reporter: Andrzej Obstoj 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] [promoted-builds-plugin] (JENKINS-8964) Promotion permalinks: for last successfull promotion
Tobias Bertelsen commented on JENKINS-8964 Promotion permalinks: for last successfull promotion One might even argue, that it is a bug that the current permalinks can point to failed promotions. If you have other jobs depending the previous promotions, they will fail because the promotion failed. 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-25822) No more connections to slaves - no log - troncated command
clement igonet created JENKINS-25822 No more connections to slaves - no log - troncated command Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Nov/14 10:03 AM Description: After updating to Jenkins V1.590, All my connections to slaves (Windows/cygwin, linux and Mac OS X) don't work anymore. Now, the situation is the following one: I can't use "Launch slave via execution of command on the Master" for 2 reasons: 1 - my ssh command is truncated: 'ssh user@slave "java -jar slave.jar -jnlpUrl http://jenkins-master/computer/win7-32/slave-agent.jnlp -secret _T_H_E___S_E_C_R_E_T_' becomes 'ssh user@slave "java -jar slave.jar' 2 - node log page remains empty I can't use "Launch slave agents on Unix machines via ssh" for this main reason: node log page is empty I tried to revert to Jenkins LTS V1.580.1 but it does not change anything. As a test, I have set upan other jenkins master installation with LTS 1.580.1. from scratch and in another hardware server. Connections to the same previous slaves are working like a charm with this master. Environment: Jenkins 1.590 Project: Jenkins Priority: Critical Reporter: clement igonet 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-25822) No more connections to slaves - no log - troncated command
clement igonet updated JENKINS-25822 No more connections to slaves - no log - troncated command Change By: clement igonet (28/Nov/14 10:05 AM) Description: AfterupdatingtoJenkinsV1.590,Allmyconnectionstoslaves(Windows/cygwin,linuxandMacOSX)dontworkanymore.Now,thesituationisthefollowingone:-IcantuseLaunchslaveviaexecutionofcommandontheMasterfor2reasons:1-mysshcommandistruncated:sshuser@slavejava-jarslave.jar-jnlpUrlhttp://jenkins-master/computer/win7-32/slave-agent.jnlp-secret_T_H_E___S_E_C_R_E_T_becomes : sshuser@slavejava-jarslave.jar2-nodelogpageremainsempty-IcantuseLaunchslaveagentsonUnixmachinesviasshforthismainreason:nodelogpageisemptyItriedtoreverttoJenkinsLTSV1.580.1butitdoesnotchangeanything.Asatest,IhavesetupanotherjenkinsmasterinstallationwithLTS1.580.1.fromscratchandinanotherhardwareserver.Connectionstothesamepreviousslavesareworkinglikeacharmwiththismaster. 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-25822) No more connections to slaves - no log - troncated command
clement igonet updated JENKINS-25822 No more connections to slaves - no log - troncated command Change By: clement igonet (28/Nov/14 10:04 AM) Description: AfterupdatingtoJenkinsV1.590,Allmyconnectionstoslaves(Windows/cygwin,linuxandMacOSX)dontworkanymore.Now,thesituationisthefollowingone:-IcantuseLaunchslaveviaexecutionofcommandontheMasterfor2reasons:1-mysshcommandistruncated: sshuser@slavejava-jarslave.jar-jnlpUrlhttp://jenkins-master/computer/win7-32/slave-agent.jnlp-secret_T_H_E___S_E_C_R_E_T_ becomes sshuser@slave java-jarslave.jar 2-nodelogpageremainsempty-IcantuseLaunchslaveagentsonUnixmachinesviasshforthismainreason:nodelogpageisemptyItriedtoreverttoJenkinsLTSV1.580.1butitdoesnotchangeanything.Asatest,IhavesetupanotherjenkinsmasterinstallationwithLTS1.580.1.fromscratchandinanotherhardwareserver.Connectionstothesamepreviousslavesareworkinglikeacharmwiththismaster. 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-25822) No more connections to slaves - no log - troncated command
clement igonet updated JENKINS-25822 No more connections to slaves - no log - troncated command Change By: clement igonet (28/Nov/14 10:07 AM) Environment: OS:Debian764bit Jenkins :V 1.590 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-25822) No more connections to slaves - no log - troncated command
clement igonet updated JENKINS-25822 No more connections to slaves - no log - troncated command Change By: clement igonet (28/Nov/14 10:06 AM) Description: AfterupdatingtoJenkinsV1.590,Allmyconnections frommaster(debian764bit) toslaves(Windows/cygwin,linuxandMacOSX)dontworkanymore.Now,thesituationisthefollowingone:-IcantuseLaunchslaveviaexecutionofcommandontheMasterfor2reasons:1-mysshcommandistruncated:sshuser@slavejava-jarslave.jar-jnlpUrlhttp://jenkins-master/computer/win7-32/slave-agent.jnlp-secret_T_H_E___S_E_C_R_E_T_becomes:sshuser@slavejava-jarslave.jar2-nodelogpageremainsempty-IcantuseLaunchslaveagentsonUnixmachinesviasshforthismainreason:nodelogpageisemptyItriedtoreverttoJenkinsLTSV1.580.1butitdoesnotchangeanything.Asatest,IhavesetupanotherjenkinsmasterinstallationwithLTS1.580.1.fromscratchandinanotherhardwareserver.Connectionstothesamepreviousslavesareworkinglikeacharmwiththismaster. 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-25822) No more connections to slaves - no log - troncated command
clement igonet updated JENKINS-25822 No more connections to slaves - no log - troncated command Change By: clement igonet (28/Nov/14 10:08 AM) Description: AfterupdatingtoJenkinsV1.590,Allmyconnectionsfrommaster(debian764bit)toslaves(Windows/cygwin,linuxandMacOSX)dontworkanymore.Now,thesituationisthefollowingone:-IcantuseLaunchslaveviaexecutionofcommandontheMasterfor2reasons:1-mysshcommandistruncated:sshuser@slavejava-jarslave.jar-jnlpUrlhttp://jenkins-master/computer/win7-32/slave-agent.jnlp-secret_T_H_E___S_E_C_R_E_T_becomes:sshuser@slavejava-jarslave.jar2-nodelogpageremainsempty-IcantuseLaunchslaveagentsonUnixmachinesviassh forthismainreason: and nodelogpageisempty .Thenitdoesnotletmeawaytounderstandwhatistherootproblem. ItriedtoreverttoJenkinsLTSV1.580.1butitdoesnotchangeanything.Asatest,IhavesetupanotherjenkinsmasterinstallationwithLTS1.580.1.fromscratchandinanotherhardwareserver.Connectionstothesamepreviousslavesareworkinglikeacharmwiththismaster. 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] [veracode-scanner-plugin] (JENKINS-25823) Sandbox and Scan Name
Matteo Castellarin created JENKINS-25823 Sandbox and Scan Name Issue Type: Improvement Assignee: Mike Bockus Components: veracode-scanner-plugin Created: 28/Nov/14 10:35 AM Description: To add the Veracode-Scanner Plugin the possibility to have extra parameters for the Veracode Sandbox and the Static Scan name (currently automatically filled with a timestamp). A little improvement for a big added value! Thank you for the great plugin, Mike Project: Jenkins Labels: plugin veracode Priority: Major Reporter: Matteo Castellarin 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] [sonar] (JENKINS-25824) FxCopCmd.exe failed and returned 1 as exit code
Jammes Lee created JENKINS-25824 FxCopCmd.exe failed and returned 1 as exit code Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 28/Nov/14 11:00 AM Description: Hi guys, I have a .NET (C#) project that fails during the execution of the FxCopCmd.exe. Follow below the Jenkins log: ... INFO 02:30:06.361 Source encoding: UTF-8, default locale: en_US INFO 02:30:06.361 Index files INFO 02:30:06.798 46 files indexed INFO 02:30:08.470 Quality profile for cs: ams-default-cs INFO 02:30:08.548 All ReSharper rules are disabled, skipping its execution. INFO 02:30:08.580 Sensor QProfileSensor... INFO 02:30:08.595 Sensor QProfileSensor done: 15 ms INFO 02:30:08.595 Sensor org.sonar.plugins.stylecop.StyleCopSensor@1221adc... INFO 02:30:08.673 Microsoft (R) Build Engine Version 4.0.30319.1 INFO 02:30:08.673 Microsoft .NET Framework, Version 4.0.30319.1 INFO 02:30:08.673 Copyright (C) Microsoft Corporation 2007. All rights reserved. INFO 02:30:08.673 INFO 02:30:08.720 Build started 28/11/2014 02:30:08. INFO 02:30:10.252 Project "G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\StyleCop-msbuild.proj" on node 1 (default targets). INFO 02:30:10.923 674 violations encountered. INFO 02:30:10.923 Done Building Project "G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\StyleCop-msbuild.proj" (default targets). INFO 02:30:10.923 INFO 02:30:10.923 Build succeeded. INFO 02:30:10.923 INFO 02:30:10.923 "G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\StyleCop-msbuild.proj" (default target) (1) - INFO 02:30:10.923 (StyleCopLaunch target) - INFO 02:30:10.970 INFO 02:30:10.970 674 Warning(s) INFO 02:30:10.970 0 Error(s) INFO 02:30:10.970 INFO 02:30:10.970 Time Elapsed 00:00:02.21 INFO 02:30:11.173 The import of some StyleCop issues were skipped. See DEBUG logs for details. INFO 02:30:11.173 Sensor org.sonar.plugins.stylecop.StyleCopSensor@1221adc done: 2578 ms INFO 02:30:11.173 Sensor org.sonar.plugins.csharp.squid.CSharpSquidSensor@1183f2... INFO 02:30:11.267 46 source files to be analyzed INFO 02:30:12.033 46/46 source files analyzed INFO 02:30:12.158 Sensor org.sonar.plugins.csharp.squid.CSharpSquidSensor@1183f2 done: 985 ms INFO 02:30:12.158 Sensor org.sonar.plugins.csharp.core.CSharpFxCopProvider$CSharpFxCopSensor@1edc066... INFO 02:30:12.158 Executing command: C:/Program Files/Microsoft Fxcop 10.0/FxCopCmd.exe /file:G:\sbs1\workspace\Projeto2\DCX.ITLC.Web\bin\DCX.ITLC.Web.dll /ruleset:=G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\fxcop-sonarqube.ruleset /out:G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\fxcop-report.xml /outxsl:none /forceoutput /searchgac /aspnet INFO 02:30:13.517 Microsoft (R) FxCop Command-Line Tool, Version 10.0 (10.0.30319.1) X86 INFO 02:30:13.517 Copyright (C) Microsoft Corporation, All Rights Reserved. INFO 02:30:13.517 INFO 02:30:13.517 Loaded aspnetconfigurationsecurityrules.dll... INFO 02:30:13.533 Loaded aspnetmvcsecurityrules.dll... INFO 02:30:13.627 Loaded aspnetsecurityrules.dll... INFO 02:30:13.689 Loaded designrules.dll... INFO 02:30:13.705 Loaded globalizationrules.dll... INFO 02:30:13.736 Loaded interoperabilityrules.dll... INFO 02:30:13.752 Loaded mobilityrules.dll... INFO 02:30:13.783 Loaded namingrules.dll... INFO 02:30:13.798 Loaded performancerules.dll... INFO 02:30:13.814 Loaded portabilityrules.dll... INFO 02:30:13.830 Loaded securityrules.dll... INFO 02:30:13.908 Loaded securitytransparencyrules.dll... INFO 02:30:13.970 Loaded usagerules.dll... INFO 02:30:15.455 Loaded DCX.ITLC.Web.dll... INFO 02:30:15.470 Initializing Introspection engine... INFO 02:30:15.595 Analyzing... INFO 02:30:15.939 Analysis Complete. INFO 02:30:15.939 * 4 total analysis engine exceptions. INFO 02:30:16.158 Writing report to G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\fxcop-report.xml... INFO 02:30:16.158 Done:00:00:03.5469885 INFO 02:30:16.267 FxCopCmd.exe ended with the exit code: 1 ERROR The execution of "C:/Program Files/Microsoft Fxcop
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25115) Recognize failures indicated by JUnit test result file
Thomas De Schampheleire commented on JENKINS-25115 Recognize failures indicated by JUnit test result file This issue can now be closed after release of 1.11.0 I do think that the description on https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer should be updated to mention the new feature (currently it's only briefly mentioned in the list of releases. 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-25822) No more connections to slaves - no log - troncated command
clement igonet commented on JENKINS-25822 No more connections to slaves - no log - troncated command Writing a specific shell script on windows/cygwin slaves temporarily resolves truncated command case. Unfortunatly, this does not resolve the bug on linux slaves... Launching my ssh command from master server as regular jenkins user works fine to start jenkins linux slave nodes. But this command does not workfrom "Launch slave via execution of command on the Master" field. I still have no log, so no way to understand... 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-24377) Create Tag (Tag this build) Not working
Rasmus Pedersen commented on JENKINS-24377 Create Tag (Tag this build) Not working After upgrading several other plugins I got the following exception when trying to tag: Tagging http://HOSTNAME/svn/PATH/TO/REPO/trunk (rev.123321) to http://HOSTNAME/svn/PATH/TO/REPO/tags/NAME_OF_TAG ERROR: Failed to tag org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/PATH/TO/REPO/trunk failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryRoot(DAVRepository.java:132) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.copyReposToRepos(SVNCopyDriver.java:194) at org.tmatesoft.svn.core.internal.wc.SVNCopyDriver.setupCopy(SVNCopyDriver.java:627) at org.tmatesoft.svn.core.internal.wc16.SVNCopyClient16.doCopy(SVNCopyClient16.java:440) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:65) at org.tmatesoft.svn.core.internal.wc2.remote.SvnNgReposToReposCopy.run(SvnNgReposToReposCopy.java:23) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc2.SvnRemoteCopy.run(SvnRemoteCopy.java:227) at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:480) at hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:307) at hudson.model.TaskThread.run(TaskThread.java:127) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 19 more Completed After changing the description of the credentials and running svn --no-auth-cache --config-dir invalid info http://HOSTNAME/svn/PATH/TO/REPO/trunk the exception disappeared and tagging fails silently again. 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] [mailer-plugin] (JENKINS-24318) Restrict which domains mail is sent to
Mads Nielsen commented on JENKINS-24318 Restrict which domains mail is sent to I'm very keen on implementing this. What would my best approach be? When looking through the code there is an @ExtenisonPoint called MailAddressFilter. The documentation suggest to implement that if you need to filter who recieves your emails in a seperate plugin, but seeing as there has lately been a movement to limit the number of new plugins contributed, what would you think about me just adding a DomainFilter class to the existing mailer plugin, and provide a global configuration option where the user specifies which regex all outgoing mails must match? Is that the preferred solution? Or do i really need to create a seperate plugin for such a simple feature? 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] [mailer-plugin] (JENKINS-24318) Restrict which domains mail is sent to
Mads Nielsen edited a comment on JENKINS-24318 Restrict which domains mail is sent to I'm very keen on implementing this. What would my best approach be? When looking through the code there is an @ExtenisonPoint called MailAddressFilter. The documentation suggest to implement that if you need to filter out emails sent by jenkins in a seperate plugin, but seeing as there has lately been a movement to limit the number of new plugins contributed, what would you think about me just adding a DomainFilter class to the existing mailer plugin, and provide a global configuration option where the user specifies which regex all outgoing mails must match? Is that the preferred solution? Or do i really need to create a seperate plugin for such a simple feature? 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-25825) Subversion plugin refuses to checkout branch at specific revision when it no longer exists in HEAD
Alan Mosely created JENKINS-25825 Subversion plugin refuses to checkout branch at specific revision when it no longer exists in HEAD Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 28/Nov/14 12:14 PM Description: When you create a branch, delete it and then try and get Jenkins to checkout the branch at a revision at which it did exist the validation fails and the checkout fails on build. This is because the checkout command in CheckoutUpdater.java uses HEAD as a parameter instead of the revision given: svnuc.doCheckout(location.getSVNURL(), local.getCanonicalFile(), SVNRevision.HEAD, r, svnDepth, true); Project: Jenkins Priority: Critical Reporter: Alan Mosely 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-8234) Latest version 1.386 not loading job configuration screen correctly
Alex Earl commented on JENKINS-8234 Latest version 1.386 not loading job configuration screen correctly Can you add the details of the _javascript_ errors you are seeing? 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] [ldap-plugin] (JENKINS-25826) Ldap login not working after upgrading jenkins 1.580.1 unless mark Remember me on this computer check box
hridyesh pant created JENKINS-25826 Ldap login not working after upgrading jenkins 1.580.1 unless mark Remember me on this computer check box Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 28/Nov/14 1:41 PM Description: Today we upgrade our Jenkins server to jenkins 1.580.1 ,after upgrading we are not able to login using ldap credential ,surprisingly we are able to login successful if we select the "Remember me on this computer" check box. We tried all the browser and cleaned the browser caches as well but getting same result. Please let me know if you need any other information. Jenkins server is running as service in linux box using "service jenkins start" command Environment: java.version 1.7.0_06 os.name Linux os.arch amd64 os.version 2.6.32-279.22.1.el6.x86_64 Jenkins version 1.580.1 (Long term support release) Jenkins Ldap plugin ldap 1.10.2 Project: Jenkins Priority: Critical Reporter: hridyesh pant 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] [rebuild-plugin] (JENKINS-25827) rebuild plugin does not support File parameters
cristian romero matesanz created JENKINS-25827 rebuild plugin does not support File parameters Issue Type: Bug Assignee: Unassigned Components: rebuild-plugin Created: 28/Nov/14 2:06 PM Description: The rebuild plugin does not work with file parameter (file uploader), so when i try to rebuild a job using this kind of parameters, the value is empty. Project: Jenkins Labels: plugin parameter rebuild-last Priority: Major Reporter: cristian romero matesanz 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] [jira-plugin] (JENKINS-25828) Jira version variable not being picked up - trigerring error
sam rock
created JENKINS-25828
Jira version variable not being picked up - trigerring error
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-plugin
Created:
28/Nov/14 2:10 PM
Description:
Jira version variable not being picked up
Followed the example on your main page. When i use the build with parameter link it pulls in the right versions and everything works
But when the build is triggered externally it triggers an error - see below
--
FATAL: Unable to generate release notes for JIRA version $JiraBuild/PTP: com.atlassian.jira.rpc.exception.RemoteValidationException: Query validation failed: The value '$JiraBuild' does not exist for the field 'fixVersion'.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: com.atlassian.jira.rpc.exception.RemoteValidationException: Query validation failed: The value '$JiraBuild' does not exist for the field 'fixVersion'.
faultActor:
faultNode:
faultDetail:
{}com.atlassian.jira.rpc.exception.RemoteException:null
--
It cannot seem to find the $jiraBuild - Can anyone help?
Environment:
Prod/Dev
Project:
Jenkins
Labels:
jira
plugin
Priority:
Major
Reporter:
sam rock
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] [jira-plugin] (JENKINS-25828) Jira version variable not picked up in jenkins - but works with 'Build with parameters'
sam rock updated JENKINS-25828 Jira version variable not picked up in jenkins - but works with Build with parameters Change By: sam rock (28/Nov/14 2:20 PM) Summary: Jiraversionvariablenot being pickedup injenkins - trigerringerror butworkswithBuildwithparameters 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] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
Paul Eipper commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Thanks for the feedback. You believe we would need a patch in Smack lib? 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-25830) Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work
martin coughlan created JENKINS-25830 Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Nov/14 3:51 PM Description: before the upgrade when the Max # of builds to keep with artifacts was set it would kick in during the build just after the perforce sync we would see "Deleting old artifacts from #XXX" this does not happen anymore for any builds. The option "Max # of builds to keep" seems to work still. Environment: CENTOS 6 Project: Jenkins Priority: Major Reporter: martin coughlan 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] [sonar] (JENKINS-25824) FxCopCmd.exe failed and returned 1 as exit code
sbrandhof closed JENKINS-25824 as Wont Fix FxCopCmd.exe failed and returned 1 as exit code This error does not relate to Jenkins plugin. Please send an email to SonarQube user mailing-list or stackoverflow with tag #sonarqube. Thanks Change By: sbrandhof (28/Nov/14 4:06 PM) Status: Open Closed Resolution: WontFix 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] [promoted-builds-plugin] (JENKINS-22068) Clicking Build Now on Promotion causes hanging promotion and requires Jenkins restart
Jan Hudec commented on JENKINS-22068 Clicking Build Now on Promotion causes hanging promotion and requires Jenkins restart The bug 24782 includes a stack-trace. It matches what I've also got. I don't however think it really matters why the job crashes. It makes no sense to run the promotion job via the "Build Now" button and the correct fix would be to remove or disable the button. If not possible, the promotion job could be made into parametrized build so it would change to "Build with Parameters" and ask for which build to promote. Copying the exception from the gist attached to #24782 here: Caught exception evaluating: h.getNearestAncestorUrl(request,it.target) in /job/mem-/promotion/process/promotionname/1/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.promoted_builds.Promotion.getTarget(Promotion.java:70) at sun.reflect.GeneratedMethodAccessor1328.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:81) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly._expression_.CompositeExpression.evaluateAsString(CompositeExpression.java:256) at org.apache.commons.jelly._expression_.CompositeExpression.evaluate(CompositeExpression.java:248) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [build-pipeline-plugin] (JENKINS-25578) Internet Explorer Compatibility
Kanstantsin Shautsou commented on JENKINS-25578 Internet Explorer Compatibility Is it reproducible with jenkins 1.580.1 LTS version and build-pipeline 1.4.5? 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] [sonar] (JENKINS-25824) FxCopCmd.exe failed and returned 1 as exit code
Jammes Lee reopened JENKINS-25824 FxCopCmd.exe failed and returned 1 as exit code Hi sbrandhof, sorry but I don't agree with your comment. The execution of the FxCopCmd runs fine, see below: C:\Program Files\Microsoft Fxcop 10.0fxcopcmd /file:G:\sbs1\workspace\Projeto2\ DCX.ITLC.Web\bin\DCX.ITLC.Web.dll /ruleset:=G:\sbs1\workspace\ Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\fxcop-sonarqube.ru leset /out:G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX.ITLC.Web\fxcop-report.xml /outxsl:none /forceoutput /searchgac /aspnet Microsoft (R) FxCop Command-Line Tool, Version 10.0 (10.0.30319.1) X86 Copyright (C) Microsoft Corporation, All Rights Reserved. Loaded aspnetconfigurationsecurityrules.dll... Loaded aspnetmvcsecurityrules.dll... Loaded aspnetsecurityrules.dll... Loaded designrules.dll... Loaded globalizationrules.dll... Loaded interoperabilityrules.dll... Loaded mobilityrules.dll... Loaded namingrules.dll... Loaded performancerules.dll... Loaded portabilityrules.dll... Loaded securityrules.dll... Loaded securitytransparencyrules.dll... Loaded usagerules.dll... Loaded DCX.ITLC.Web.dll... Initializing Introspection engine... Analyzing... Analysis Complete. 4 total analysis engine exceptions. Writing report to G:\sbs1\workspace\Projeto2\target\sonar\projeto2_projeto2_DCX. ITLC.Web\fxcop-report.xml... Done:00:00:01.6719285 The return code for this command executin is: C:\Program Files\Microsoft Fxcop 10.0echo %errorlevel% 1 So my point is, why Jenkins is setting the build as unsuccessfull for exceptions that are detected by Fxcop? The Fxcop execution itself is fine. Change By: Jammes Lee (28/Nov/14 4:48 PM) Resolution: WontFix Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonar] (JENKINS-25824) FxCopCmd.exe failed and returned 1 as exit code
Dinesh Bolkensteyn commented on JENKINS-25824 FxCopCmd.exe failed and returned 1 as exit code Jammes Lee It is the SonarQube C# plugin, and not Jenkins, which determined that the FxCop execution was not successful. To convince you, here is the code: https://github.com/SonarCommunity/sonar-fxcop-library/blob/master/src/main/java/org/sonar/plugins/fxcop/FxCopExecutor.java#L63 FxCopCmd.exe returned 1 as exit code, which is considered as a failure. Please switch to the SonarQube user mailing list for further support on this subject, as this not related to 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] [sonar] (JENKINS-25824) FxCopCmd.exe failed and returned 1 as exit code
Dinesh Bolkensteyn closed JENKINS-25824 as Not A Defect FxCopCmd.exe failed and returned 1 as exit code Change By: Dinesh Bolkensteyn (28/Nov/14 5:03 PM) Status: Reopened Closed 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] [artifactdeployer-plugin] (JENKINS-25806) Artifact Deployer plugin 0.32 doing nothing
pedro reis updated JENKINS-25806 Artifact Deployer plugin 0.32 doing nothing Change By: pedro reis (28/Nov/14 5:06 PM) Priority: Minor Blocker 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found
Al Ferguson created JENKINS-25831 Branch not found Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 28/Nov/14 5:07 PM Description: The plugin doesn't find the integration branch, it always throws an NothingToDoException (because 'found' is false). Either "client.getRemoteBranches()" or "Branch.getName()" does not work. We get same behavior using any strategy (squash no-ff). Jenkins GIT plugin is up-to-date, however the git installation on os is not. Environment: Jenkins 1.545 Jenkins GIT plugin 2.2.9 Pretested integration plugin 2.1.2 JDK 1.7.0_45 os Linux amd64 2.6.32-5 Project: Jenkins Priority: Blocker Reporter: Al Ferguson 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] [p4-plugin] (JENKINS-25648) P4_CHANGELIST variable points to unshelved cl , not synced CL
Paul Allen commented on JENKINS-25648 P4_CHANGELIST variable points to unshelved cl , not synced CL I need to be a bit careful as the buildChange is used in a few places. It would seem that removing the shelved code might be the simplest and provide another method in CheckoutTask to get the shelf number. 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] [p4-plugin] (JENKINS-25537) REST api provides incomplete information
Paul Allen commented on JENKINS-25537 REST api provides incomplete information I have not looked at this area of the code at all. Just took your changes as-is, is there a missing field or are the values incorrect? (is this related to the change number/shelf issue in JENKINS-25648)? 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] [copy-to-slave-plugin] (JENKINS-23308) CopyToSlave: Variables doesn't work in custom workspaces
Jason H commented on JENKINS-23308 CopyToSlave: Variables doesnt work in custom workspaces Variable support also needed for the Override destination folder for configuring copying files back to the master. 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] [rebuild-plugin] (JENKINS-25815) Rebuild plugin doesn't load all Parameters
Daniel Beck commented on JENKINS-25815 Rebuild plugin doesnt load all Parameters Change is unreleased. 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] [configurationslicing-plugin] (JENKINS-25820) javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[type] not found. is shown when saving the configration
Daniel Beck resolved JENKINS-25820 as Incomplete javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[type] not found. is shown when saving the configration Unrelated to Configuration Slicing Plugin. Report contains not nearly enough information. For instructions how to report an issue so it can be investigated further, please see the instructions at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (28/Nov/14 5:22 PM) Status: Open Resolved Assignee: mdonohue Resolution: Incomplete 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] [p4-plugin] (JENKINS-25537) REST api provides incomplete information
Morne Joubert commented on JENKINS-25537 REST api provides incomplete information It is not related to the other 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] [p4-plugin] (JENKINS-25537) REST api provides incomplete information
Morne Joubert commented on JENKINS-25537 REST api provides incomplete information I closed this since it was fixed by the change 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] [mailer-plugin] (JENKINS-24318) Restrict which domains mail is sent to
Daniel Beck commented on JENKINS-24318 Restrict which domains mail is sent to there has lately been a movement to limit the number of new plugins I'm not so sure about that. While there are often clarifying questions asked when hosting for a new plugin is requested, those are mostly about duplication of features. 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] [ldap-plugin] (JENKINS-25826) Ldap login not working after upgrading jenkins 1.580.1 unless mark Remember me on this computer check box
Daniel Beck updated JENKINS-25826 Ldap login not working after upgrading jenkins 1.580.1 unless mark Remember me on this computer check box The type of this issue and the presence of workaround makes this a minor issue. Critical means: crashes or loss of data. Change By: Daniel Beck (28/Nov/14 5:29 PM) Priority: Critical Minor 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-25830) Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work
Daniel Beck commented on JENKINS-25830 Since upgrading to 1.590 the Max # of builds to keep with artifacts option does not seem to work Core deletes old builds after a build is finished. Are you using p4 plugin, or perforce 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] [email-ext-plugin] (JENKINS-25719) bad html content after upgrading to Email Extension Plugin v2.39
Alex Earl started work on JENKINS-25719 bad html content after upgrading to Email Extension Plugin v2.39 Change By: Alex Earl (28/Nov/14 5:34 PM) Status: Open InProgress 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] [email-ext-plugin] (JENKINS-22713) '+' char in content encoded as #43;
Alex Earl resolved JENKINS-22713 as Cannot Reproduce + char in content encoded as #43; Change By: Alex Earl (28/Nov/14 5:35 PM) 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] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
Matt Cudmore commented on JENKINS-25433 Xcodebuild sigining fails Same issue on OS X Yosemite (v10.10.1). As Michael said, it is a matter of removing --resource-rules parameter. This works when invoked on the command line, but fails including the resource-rules parts: /usr/bin/codesign --force --preserve-metadata=identifier,entitlements --sign "..." --entitlements /var/... /var/.../Demo.app 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] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
Matt Cudmore edited a comment on JENKINS-25433 Xcodebuild sigining fails Same issue on OS X Yosemite (v10.10.1). As Michael said, it is a matter of removing --resource-rules parameter. This works when invoked on the command line, but fails including the resource-rules parts: /usr/bin/codesign --force --preserve-metadata=identifier,entitlements --sign "..." --entitlements /var/... /var/.../Demo.app I can also verify the suggested fix worked for me: http://stackoverflow.com/questions/26464577/jenkins-vs-xcode-plugin-codesign-troubles 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] [mailer-plugin] (JENKINS-24318) Restrict which domains mail is sent to
Per Arnold Blaasmo commented on JENKINS-24318 Restrict which domains mail is sent to Actually there is an implementation in the email-ext plugin (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin) that gives the possible functionality. It is called 'pre-send script'. I did some test with that and it works. Making a global pre-send script prevents all build jobs using the plugin send mail to given addresses. The problem was that I could not control whether or not the users enabled the email-ext-plugin in their build job. So I had to set up a filter on the smtp server that the build master uses. I found somewhere that i was plans to merge the mailer-plugin and the email-ext-plugin, but it does not seems to be a priotity? 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] [mailer-plugin] (JENKINS-24318) Restrict which domains mail is sent to
Per Arnold Blaasmo edited a comment on JENKINS-24318 Restrict which domains mail is sent to Actually there is an implementation in the email-ext plugin (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin) that gives the possible functionality. It is called 'pre-send script'. I did some test with that and it works. Making a global pre-send script prevents all build jobs using the plugin send mail to given addresses. The problem was that I could not control whether or not the users enabled the email-ext-plugin in their build job. So I had to set up a filter on the smtp server that the build master uses. I found somewhere that it was plans to merge the mailer-plugin and the email-ext-plugin, but it does not seems to be a priority? 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Bue Petersen updated JENKINS-25831 Branch not found (our case 12373) Change By: Bue Petersen (28/Nov/14 6:34 PM) Summary: Branchnotfound (ourcase12373) 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Bue Petersen commented on JENKINS-25831 Branch not found (our case 12373) What version of git are you using on your OS? Could you also supply us with the pretested integration plugin configuration and your git branch specifier? By the way, there is a new version on the way next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Al Ferguson commented on JENKINS-25831 Branch not found (our case 12373) Branch specifier: origin/dev Integration branch: int 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Al Ferguson edited a comment on JENKINS-25831 Branch not found (our case 12373) Branch specifier: origin/dev Integration branch: origin/int 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Bue Petersen commented on JENKINS-25831 Branch not found (our case 12373) If you by "origin/int" means the repository remote named "origin", and branch "int" you have to use just "int" in the integration branch field. Your branch specifier can still include "origin". The plugin in version 2.1.2 assumes you try to integrate to a repository called origin. This implicit assumption will be changed in next version. Note only one git repository is supported in current version. 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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Al Ferguson
commented on JENKINS-25831
Branch not found (our case 12373)
Branch specifier: origin/dev
Integration branch: int
***Console Output*
15:18:37 git rev-parse --is-inside-work-tree # timeout=10
15:18:37 Fetching changes from the remote Git repository
15:18:37 git config remote.origin.url g...@bitbucket.org:alogient/gcr-backend.git # timeout=10
15:18:37 Pruning obsolete local branches
15:18:37 Fetching upstream changes from g...@bitbucket.org:alogient/gcr-backend.git
15:18:37 git --version # timeout=10
15:18:37 git fetch --tags --progress g...@bitbucket.org:alogient/gcr-backend.git +refs/heads/:refs/remotes/origin/ --prune
15:18:38 git rev-parse refs/remotes/origin/dev^{commit} # timeout=10
15:18:38 git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10
15:18:38 Checking out Revision 939a053e91a5a0b1057733393e66473896f30f6b (refs/remotes/origin/dev)
15:18:38 git config core.sparsecheckout # timeout=10
15:18:38 git checkout -f 939a053e91a5a0b1057733393e66473896f30f6b
15:18:38 git rev-list 939a053e91a5a0b1057733393e66473896f30f6b # timeout=10
15:18:38 Cleaning workspace
15:18:38 git rev-parse --verify HEAD # timeout=10
15:18:38 Resetting working tree
15:18:38 git reset --hard # timeout=10
15:18:38 git clean -fdx # timeout=10
15:18:38 2.1.2
15:18:38 Checking out integration target branch int and pulling latest changes
15:18:38 workspace $ git checkout int
15:18:38 workspace $ git pull origin int
15:18:38 Preparing to merge changes in commit 939a053e91a5a0b1057733393e66473896f30f6b to integration branch int(948a6ba75a921cd8a649a069bef0e857289d526e)
15:18:38 Nothing to do
15:18:39 Finished: NOT_BUILT
**
***Log Recorders*
Nov 28, 2014 3:18:38 PM FINER PretestedIntegrationAction getCurrentIntegrationTip
RETURN
Nov 28, 2014 3:18:38 PM FINER Commit getId
ENTRY
Nov 28, 2014 3:18:38 PM FINER Commit getId
RETURN
Nov 28, 2014 3:18:38 PM FINER GitBridge getBranch
RETURN
Nov 28, 2014 3:18:38 PM FINER GitBridge getBranch
ENTRY
Nov 28, 2014 3:18:38 PM SEVERE org.jenkinsci.plugins.pretestedintegration.PretestedIntegrationBuildWrapper setUp
PREINT - setUp()
org.jenkinsci.plugins.pretestedintegration.exceptions.NothingToDoException: Nothing to do
at org.jenkinsci.plugins.pretestedintegration.scm.git.SquashCommitStrategy.integrate(SquashCommitStrategy.java:84)
at org.jenkinsci.plugins.pretestedintegration.AbstractSCMBridge.mergeChanges(AbstractSCMBridge.java:105)
**
It still doesn't work. I don't have access to the machine, I don't know the version of the git installation.
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] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Al Ferguson
edited a comment on JENKINS-25831
Branch not found (our case 12373)
Branch specifier: origin/dev
Integration branch: int
***Console Output*
15:18:37 git rev-parse --is-inside-work-tree # timeout=10
15:18:37 Fetching changes from the remote Git repository
15:18:37 git config remote.origin.url g...@bitbucket.org:***/**-backend.git # timeout=10
15:18:37 Pruning obsolete local branches
15:18:37 Fetching upstream changes from g...@bitbucket.org:***/**-backend.git
15:18:37 git --version # timeout=10
15:18:37 git fetch --tags --progress g...@bitbucket.org:***/*-backend.git +refs/heads/:refs/remotes/origin/* --prune
15:18:38 git rev-parse refs/remotes/origin/dev^{commit} # timeout=10
15:18:38 git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10
15:18:38 Checking out Revision 939a053e91a5a0b1057733393e66473896f30f6b (refs/remotes/origin/dev)
15:18:38 git config core.sparsecheckout # timeout=10
15:18:38 git checkout -f 939a053e91a5a0b1057733393e66473896f30f6b
15:18:38 git rev-list 939a053e91a5a0b1057733393e66473896f30f6b # timeout=10
15:18:38 Cleaning workspace
15:18:38 git rev-parse --verify HEAD # timeout=10
15:18:38 Resetting working tree
15:18:38 git reset --hard # timeout=10
15:18:38 git clean -fdx # timeout=10
15:18:38 2.1.2
15:18:38 Checking out integration target branch int and pulling latest changes
15:18:38 workspace $ git checkout int
15:18:38 workspace $ git pull origin int
15:18:38 Preparing to merge changes in commit 939a053e91a5a0b1057733393e66473896f30f6b to integration branch int(948a6ba75a921cd8a649a069bef0e857289d526e)
15:18:38 Nothing to do
15:18:39 Finished: NOT_BUILT
**
***Log Recorders*
Nov 28, 2014 3:18:38 PM FINER PretestedIntegrationAction getCurrentIntegrationTip
RETURN
Nov 28, 2014 3:18:38 PM FINER Commit getId
ENTRY
Nov 28, 2014 3:18:38 PM FINER Commit getId
RETURN
Nov 28, 2014 3:18:38 PM FINER GitBridge getBranch
RETURN
Nov 28, 2014 3:18:38 PM FINER GitBridge getBranch
ENTRY
Nov 28, 2014 3:18:38 PM SEVERE org.jenkinsci.plugins.pretestedintegration.PretestedIntegrationBuildWrapper setUp
PREINT - setUp()
org.jenkinsci.plugins.pretestedintegration.exceptions.NothingToDoException: Nothing to do
at org.jenkinsci.plugins.pretestedintegration.scm.git.SquashCommitStrategy.integrate(SquashCommitStrategy.java:84)
at org.jenkinsci.plugins.pretestedintegration.AbstractSCMBridge.mergeChanges(AbstractSCMBridge.java:105)
**
It still doesn't work. The version of the git installation on the server is 1.7.2.5.
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] [jacoco-plugin] (JENKINS-25818) Next day after a Jenkins reboot the report is empty
Daniel Beck commented on JENKINS-25818 Next day after a Jenkins reboot the report is empty Could you try downgrading to Jacoco Plugin 1.0.14? If https://github.com/jenkinsci/jacoco-plugin/commit/c8090ab9df73a20f520557a590232b20348b22d6 caused it, that should serve as possible workaround. 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Martin Weber commented on JENKINS-25807 Is this plugin still maintained? I contacted the developer, he said he would not have any time to maintain it and is no longer using it himself. (Thanks for the profile link) Maybe you could take over maintainership of the plugin rather than do a full rewrite? There are over 1000 known users of the plugin who could benefit from that. Maintainership-take-over could be an option, but I have to admit that I'm more than hesitating to deal with issues, the original developer was not willing to look at in years. Even then, a full rewrite will be necessary, since I do not work on fully undocumented code. And getting the quirks out of the existing plugin, it will require to break compatibility with any existing jobe. 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-19244) jenkins random hang during startup - Solaris and Linux
Daniel Beck resolved JENKINS-19244 as Cannot Reproduce jenkins random hang during startup - Solaris and Linux No response to comment asking for updated and additional information in over a month, so resolving as Cannot Reproduce. Please file a new issue when something like this happens to you on recent Jenkins versions, and link back to this one as possibly related. Make sure to follow the advice on: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Change By: Daniel Beck (28/Nov/14 9:53 PM) 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] [cmakebuilder-plugin] (JENKINS-25807) Is this plugin still maintained?
Daniel Beck resolved JENKINS-25807 as Fixed Is this plugin still maintained? Glad I could point you in the right direction. Consider asking for advice on the jenkinsci-dev mailing list. I'm pretty sure it's not too much effort to do a kind of "import configuration" step (basically during XML deserialization, readResolve and all that) so that your rewritten code could work with existing configuration. You can also make it a semantically versioned "2.0" and note some incompatibility to previous versions in plugin manager/update center to make users aware of the big step. I think there's value in continuing work (at least from a migration of on-disk configuration point of view), as having multiple plugins around that do essentially the same thing (assuming that's the case) is a weird situation for everyone. Plus, you'll inherit the users of the existing plugin, finding bugs for you Just my suggestion, how you decide to proceed is of course your choice. Change By: Daniel Beck (28/Nov/14 10:09 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] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Patrick Savelberg commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials If you use svn+ssh://SERVER/REPOSITORY_LOCATION for your external then use svn+ssh://SERVER as realm 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.
