[JIRA] [core] (JENKINS-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Daniel Beck commented on JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread In jobs using SSH Agent, do you see the following build log message near the end? ssh-agent Stopped. 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri created JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Issue Type: Bug Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 17/Apr/15 5:59 AM Description: I have installed Deployer Weblogic plugin 3.2 for Deploying ear/war to weblogic server. After installation when I access it from Post build options, I am facing the below issue. Can anyone please suggest what will be the solution for this. Apr 17, 2015 5:37:22 AM hudson.widgets.RenderOnDemandClosure$1 generateResponse WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: jar:file:/snmanc/.jenkins/plugins/weblogic-deployer-plugin/WEB-INF/lib/classes.jar!/org/jenkinsci/plugins/deploy/weblogic/WeblogicDeploymentPlugin/config.jelly:17:138: j:invokeStatic Could not load class: org.jenkinsci.plugins.deploy.weblogic.jdk.JdkToolService. Reason: java.lang.NoSuchMethodException: org.jenkinsci.plugins.deploy.weblogic.jdk.JdkToolService.getJDKHomeByName(java.lang.Object) at org.apache.commons.jelly.tags.core.InvokeStaticTag.createLoadClassFailedException(InvokeStaticTag.java:177) at org.apache.commons.jelly.tags.core.InvokeStaticTag.doTag(InvokeStaticTag.java:139) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at hudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:99) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:110) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:64) at org.kohsuke.stapler.Function.renderResponse(Function.java:113) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:98) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:465) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at
[JIRA] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri stopped work on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Change By: Raghuveer Karumuri (17/Apr/15 7:06 AM) Status: InProgress Open 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri started work on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Change By: Raghuveer Karumuri (17/Apr/15 7:05 AM) 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] [core] (JENKINS-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Daniel Beck commented on JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread Are you setting up SSH Agents for builds that do not use them? 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz updated JENKINS-27972 Credentials Scope dropdown is empty for new entry Change By: Florian Storz (17/Apr/15 8:34 AM) Environment: Ubuntu12.04LTS, Jenkins1.609,credentials-plugin1.22and1.21 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz edited a comment on JENKINS-27972 Credentials Scope dropdown is empty for new entry When I want to create a certificate credentials entry i get a NullPointerException (see stack_trace_Create_certificate_credentials.txt) 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-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609
Daniel Beck commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 How are the downstream jobs started? 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz resolved JENKINS-27972 as Fixed Credentials Scope dropdown is empty for new entry With the solution from JENKINS-12875 I resolved my problem. Change By: Florian Storz (17/Apr/15 9:33 AM) 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] [core] (JENKINS-27991) Unable to POST modified config.xml in Jenkins via curl API.
Daniel Beck commented on JENKINS-27991 Unable to POST modified config.xml in Jenkins via curl API. ver 1.6907 There is no such version. Make sure you're using an up to date version of the Static Analysis Utilities. 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] [global-build-stats-plugin] (JENKINS-27956) Jenkins Global Build Search - Cannot choose start date end date
NARAYAN PRADHAN commented on JENKINS-27956 Jenkins Global Build Search - Cannot choose start date end date found few more data === Uncaught TypeError: undefined is not a function dom-min.js Uncaught TypeError: undefined is not a functiondom-min.js:8 e.Dom.inDocumentbutton-min.js:10 YAHOO.extend.initelement-min.js:7 abutton-min.js:7 YAHOO.widget.Buttonhudson-behavior.js:504 makeButtonhudson-behavior.js:915 jenkinsRules.INPUT.submit-buttonbehavior.js:111 (anonymous function)behavior.js:107 (anonymous function)behavior.js:93 Behaviour.applySubtreebehavior.js:76 Behaviour.applybehavior.js:71 (anonymous function)behavior.js:125 Behaviour.addLoadEvent.window.onload == 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] [etc] (JENKINS-27988) Dead mirrors makes jenkins update process stall for a long time
Daniel Beck updated JENKINS-27988 Dead mirrors makes jenkins update process stall for a long time Change By: Daniel Beck (17/Apr/15 9:42 AM) Labels: jenkinsuser-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] [core] (JENKINS-27991) Unable to POST modified config.xml in Jenkins via curl API.
Mahendra Singh commented on JENKINS-27991 Unable to POST modified config.xml in Jenkins via curl API. My wrong: It is 1.596 not 1.6907 Correct version is 1.596 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-27345) Jenkins 1.599 blocked when using slave nodes
Daniel Beck commented on JENKINS-27345 Jenkins 1.599 blocked when using slave nodes Look into the Xmx JVM argument. Give Jenkins at least 4GB. Install the Monitoring Plugin to track memory usage. 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz commented on JENKINS-27972 Credentials Scope dropdown is empty for new entry I reinstalled jenkins, and with initial configuration it works again. But as I configured our LDAP authentication the same problem occures as mentioned above! 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] [etc] (JENKINS-27988) Dead mirrors makes jenkins update process stall for a long time
Daniel Beck commented on JENKINS-27988 Dead mirrors makes jenkins update process stall for a long time http://mirrors.jenkins-ci.org/status.html Could you please point out the specific mirror? They look fine from monitoring. Workaround could be to configure a different mirror explicitly as update center URL. Moving this to the INFRA 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Daniel Beck commented on JENKINS-27972 Credentials Scope dropdown is empty for new entry Are you using nginx? 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-27990) Startup fails on s390x/Linux - java.lang.UnsatisfiedLinkError: jnidispatch
Daniel Beck commented on JENKINS-27990 Startup fails on s390x/Linux - java.lang.UnsatisfiedLinkError: jnidispatch Try to find out whether there's a prepackaged JNA 4.1.0 for your OS/architecture and install that. Maybe that resolves the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.
Daniel Beck commented on JENKINS-25070 Subversion fails to update externals once after external is changed. We upgraded the svn plugin to 2.5 then downgraded to 2.3. Subversion Plugin 2.5 has several known issues that may play into this. FWIW I think 2.4.4 (for older Jenkins) or 2.4.5 (for Jenkins 1.585+) are pretty solid and worth a try. 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz commented on JENKINS-27972 Credentials Scope dropdown is empty for new entry After further investigation I figured out that the problem is the "Cross-Site-Request-Forgery" security option. When this option is enabled, the credentials plugin stops to work. When it is disabled everything 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] [core] (JENKINS-27986) Saving configuration changes on existing Jobs results in connection reset error
Daniel Beck commented on JENKINS-27986 Saving configuration changes on existing Jobs results in connection reset error This can happen when you submit the form before the page finished loading completely. Recording the full HTTP request sent by the browser would be helpful, as well as any possible JS errors. Badly written plugins may break the JS injected into form submission handling 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] [warnings-plugin] (JENKINS-27914) MSBuild-Parser ignores optional Subcategory
JAM Software commented on JENKINS-27914 MSBuild-Parser ignores optional Subcategory It will take some time, but we are interested. Might be possible to accomplish a pull request during the next month. What kind of test are you referring to? We have a lack of java developers so i'm a bit curious. 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-26580) For JNLP slaves the master-slave communication should be encrypted
Kieran Shaw commented on JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted I'm not sure if I can help in terms of code, but I just thought I'd throw in my 2 cents worth... This would be a really great fix for us. We have some offsite Jenkins nodes that do the initial connection through https but then as far as I can tell all following communication on the 49187 port is unprotected. This makes the security people around me very nervous so it would be great for this fix to be available. I'm a little surprised at how hard it is to find information about this on the Jenkins website, I suspect I'm not the only one who used to think that this was already encrypted as the slave startup line is something like: java -jar slave.jar -jnlpUrl https://ci.example.com:443/computer/myslave/slave-agent.jnlp -secret sadkfjasfdkjashfdakjfha That jnlpUrl being https probably makes most people think the connection is more secure than it really is 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-27991) Unable to POST modified config.xml in Jenkins via curl API.
Mahendra Singh commented on JENKINS-27991 Unable to POST modified config.xml in Jenkins via curl API. Do I need to consider any dependent plugin as per the version compatible? 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe assigned JENKINS-27884 to Ross Rowe Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Change By: Ross Rowe (17/Apr/15 7:55 AM) Assignee: KohsukeKawaguchi RossRowe 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thanks for letting us know, for the 'use latest browser' error, can you tell me what browser you had selected? The v1.125 version of the plugin does attempt to resolve the 'can't lock pidfile' error, and the sc process tends to take a while to close. It might be worth trying v1.125 again and taking a look at the errors that are written to the sc.log file. 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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz updated JENKINS-27972 Credentials Scope dropdown is empty for new entry When I want to create a certificate credentials entry i get a NullPointerException (see Unable to embed resource: stack_trace_Create_certificate_credentials.txt of type text/plain) Change By: Florian Storz (17/Apr/15 8:44 AM) Attachment: stack_trace_Create_certificate_credentials.txt 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] [jobconfighistory-plugin] (JENKINS-27643) Job Config History is not saved when perfoming config changes
Stefan Brausch
commented on JENKINS-27643
Job Config History is not saved when perfoming config changes
Your problem with 2.6 is fixed in 2.7 ("fixed history could not saved for some job types if in the system configuration "Save folder configuration changes" wasn't set")
You can also try to set this configuration property to on with 2.6.
Your problem with 2.10 could be a problem with your older Jenkins core. Plugin Version 2.10 is build against core 1.554.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] [credentials-plugin] (JENKINS-27972) Credentials Scope dropdown is empty for new entry
Florian Storz commented on JENKINS-27972 Credentials Scope dropdown is empty for new entry Yes, with following configuration: root /var/cache/jenkins/war/; proxy_pass http://127.0.0.1:8080/jenkins; proxy_pass_request_headers on; #Proxy Settings proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; 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-27887) pmd plugin and checkstyle plugin fail to install
Sylwia Kludacz commented on JENKINS-27887 pmd plugin and checkstyle plugin fail to install Hi Ulli, I did reboot the server as well but it didn't solve the problem. The strange thing is that I can see the proper folder structure created on the server inside the plugin folder with all the files being created but Jenkins still doesn't recognize the plugin as installed. How Jenkins knows which plugins are installed? 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-27976) MsBuildParser should parse Code Analysis warnings
Stuart Grassie commented on JENKINS-27976 MsBuildParser should parse Code Analysis warnings So I went through the process of forking the repo, getting maven and eclipse configured, produced some sample output, wrote a unit test... and then discovered there isn't in fact a bug at all, it does parse the code analysis warnings correctly, and the fault was in my build process not being quite right. /sigh 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-27967) Remote trigger from Fisheye webhook
Jérémie Faucher-Goulet commented on JENKINS-27967 Remote trigger from Fisheye webhook Hi Daniel Beck, I thought the Remote Access API (https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API) was part of Core... What plugins handles the REST API then? 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-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Damien Coraboeuf
created JENKINS-27994
The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
17/Apr/15 1:02 PM
Description:
Hi,
I'm using the Job DSL plug-in from another plug-in, and need to use it for my integration tests as well:
dependencies {
...
jenkinsPlugins 'org.jenkins-ci.plugins:job-dsl:1.32@jar'
...
}
I'm using the JenkinsRule and it fails because it cannot resolve job-dsl:1.32. After looking into the code of JenkinsRule, I've seen that the JAR location is fetched using Manifest information, in the Short-Name attribute.
Although this information is filled in correctly in the JPI file, it is absent in the JAR file. I had a look at other plug-ins, and the manifest information is generated for both the JAR and the HPI/JPI file. So it might have something to do with the Gradle JPI plug-in.
In order to make the Job DSL plug-in useable from other plug-ins, especially in their integration tests using the JenkinsRule, the JAR needs the Manifest information.
Best regards,
Damien.
Project:
Jenkins
Priority:
Major
Reporter:
Damien Coraboeuf
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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. If "block on upstream jobs" is set, a job (D) should not run before any pending upstream builds (C) have finished. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Daniel Beck commented on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream Would be interesting to know whether this has recently behaved as documented. I have a feeling this has been broken for a long time. 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] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Damien Coraboeuf updated JENKINS-27994 The Manifest of the job-dsl JAR is empty, making it unuseable for tests Change By: Damien Coraboeuf (17/Apr/15 2:50 PM) Component/s: gradle-jpi-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] [depgraph-view-plugin] (JENKINS-27996) dependency graph viewer plugin gives gets NaN in jsplumb mode
Maxim Nikolaev
created JENKINS-27996
dependency graph viewer plugin gives gets NaN in jsplumb mode
Issue Type:
Bug
Assignee:
wolfs
Components:
depgraph-view-plugin
Created:
17/Apr/15 2:49 PM
Description:
Jenkins version is 1.609, depgraph-view plugin version is 0.11. Several versions ago plugin worked. Something changed since and now I can see in firefox's console:
Object { 0: div#build-scripts-clone-ibd3-server-web.window.ui-droppable.ui-draggable, length: 1, prevObject: Object, context: undefined } "0[object Object][object Object][object Object]" NaN
-output from 97-th string of jsPlumb_depview.js
and later jquery.jsPlumb-1.3.16-all-min.js throws:
Unexpected value NaN parsing width attribute.
Unexpected value NaN parsing height attribute.
Project:
Jenkins
Labels:
plugin
jenkins
Priority:
Minor
Reporter:
Maxim Nikolaev
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] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Damien Coraboeuf
commented on JENKINS-27826
Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
I confirm that adding the matrix-project fixes the problem:
dependencies {
...
jenkinsPlugins 'org.jenkins-ci.plugins:matrix-project:1.4@jar'
...
}
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-27995) Add CONTRIBUTING.md file to the jenkinsci/jenkins repository.
Kamran Mackey created JENKINS-27995 Add CONTRIBUTING.md file to the jenkinsci/jenkins repository. Issue Type: New Feature Assignee: Unassigned Components: core Created: 17/Apr/15 1:34 PM Description: I think it would be nice if the Jenkins GitHub repository had a CONTRIBUTING.md file for when people want to commit new things to Jenkins, because a lot of repositories that I know of have one, and it would be useful to a lot of people if the Jenkins repository had a CONTRIBUTING.md file. Project: Jenkins Labels: jenkins core Priority: Minor Reporter: Kamran Mackey 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-27995) Add CONTRIBUTING.md file to the jenkinsci/jenkins repository.
Kamran Mackey updated JENKINS-27995 Add CONTRIBUTING.md file to the jenkinsci/jenkins repository. Change By: Kamran Mackey (17/Apr/15 1:35 PM) Description: IthinkitwouldbeniceiftheJenkinsGitHubrepositoryhadaCONTRIBUTING.mdfileforwhenpeoplewanttocommitnewthingstoJenkins,becausealotofrepositoriesthatIknowofhaveone,anditwouldbeusefultoalotofpeopleiftheJenkinsrepositoryhadaCONTRIBUTING.mdfile.LikeIcouldpossiblydoitmyself,butIdontknowwhatIcould addto putin it,especiallysinceImanewcommitertoJenkins. 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
Liam McGregor commented on JENKINS-25821 Global Mask Password are visible as a plain text in Environment Variables tab This seems like a big flaw, and now are passwords are exposed to anyone who uses the 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-27995) Add CONTRIBUTING.md file to the jenkinsci/jenkins repository.
Kamran Mackey updated JENKINS-27995 Add CONTRIBUTING.md file to the jenkinsci/jenkins repository. Change By: Kamran Mackey (17/Apr/15 1:35 PM) Description: IthinkitwouldbeniceiftheJenkinsGitHubrepositoryhadaCONTRIBUTING.mdfileforwhenpeoplewanttocommitnewthingstoJenkins,becausealotofrepositoriesthatIknowofhaveone,anditwouldbeusefultoalotofpeopleiftheJenkinsrepositoryhadaCONTRIBUTING.mdfile. LikeIcouldpossiblydoitmyself,butIdontknowwhatIcouldaddtoit,especiallysinceImanewcommitertoJenkins. 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-27995) Add CONTRIBUTING.md file to the Jenkins GitHub repository.
Kamran Mackey updated JENKINS-27995 Add CONTRIBUTING.md file to the Jenkins GitHub repository. Change By: Kamran Mackey (17/Apr/15 1:39 PM) Summary: AddCONTRIBUTING.mdfiletothe jenkinsci/jenkins JenkinsGitHub repository. 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Ross Rowe commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Okay, thanks for letting me know, and apologies for missing the bit about the use latest version...I'll try to add some functionality to the plugin to forcibly close any rogue sc processes, and I'll let you know when I have a new version available. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. If "block on upstream jobs" is set, a job (D) should not run before any pending upstream builds (C) have finished. 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-27993) /pluginManager/api/json largely useless
Andreas Kotes
created JENKINS-27993
/pluginManager/api/json largely useless
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
17/Apr/15 11:45 AM
Description:
{"plugins":{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{},{}}
.. not helping, if you want to enumerate plugins and their versions
Project:
Jenkins
Priority:
Minor
Reporter:
Andreas Kotes
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-27084) SVN authentication fails using subversion plugin v.2.5
Romuald Fleury commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Could we expect a better handling of the situation at least ? (A fix of the NullPointer, that should never be thrown in production ?) 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-27993) /pluginManager/api/json largely useless
Daniel Beck commented on JENKINS-27993 /pluginManager/api/json largely useless Try the depth parameter and similar. 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-27981) Impossible to clone git repo
Mark Waite commented on JENKINS-27981 Impossible to clone git repo I don't see any location in the git client plugin or the git plugin where they pass a "-o" argument to plink. There are two calls to ssh with a "-o" argument, but no references to plink. My Windows based installations all use OpenSSH as the provider of ssh, rather than using plink. I wondered if you might have a different plink program in your path than the plink provided by PuTTY. You might check that, though, based on at least one recommendation, you should uninstall msysgit which you had configured with PuTTY and plink and switch to install msysgit using the default OpenSSH based ssh implementation. Refer to stackoverflow.com for a screenshot of the setup screen where you need to choose OpenSSH instead of Plink. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. D cannot be executed until any pending upstream builds (C) have finished. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper commented on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C. If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. It cannot be executed until any pending upstream builds have finished. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. D cannot be executed until any pending upstream builds (C) have finished. If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C. If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. D cannot be executed until any pending upstream builds (C) have finished. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite a sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C. If "block on upstream jobs" is set, a job should never run at the same time as its upstream. But that is exactly what happens here. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. D cannot be executed until any pending upstream builds (C) have finished. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot. "When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. The dependencies include the direct as well as the transitive dependencies." 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper edited a comment on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream "Block on upstream jobs" only prevents conflicts of RUNNING jobs, a task in the queue does not prevent D from starting. I'm not quite sure I know what you mean. "Block on upstream jobs" will certainly prevent a job from running if its upstream is in the queue. Create jobs A, B, C, where C is upstream to B. Have a single executor, and start A, B, and C. Even though B was queued before C, it will run after C, because the fact that C is queued prevents B from running. Jenkins schedules a build of D because nothing says it cannot. "Block on upstream builds" says it cannot, as D's upstream C is still in the queue. "When this option is checked, Jenkins will prevent the project from building when a dependency of this project is in the queue, or building. The dependencies include the direct as well as the transitive dependencies." 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 I had no browser selected. Explained in description why. Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc defunct' process). Anyway here it is from when I had it running with 1.125, then it started to fail again: At 16:34 there was a successful run of the job. At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed. At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log" That should have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other. But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes. 20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low! 20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000. 20150410 163455.235 [01966] Trying to autodetect proxy settings 20150410 163455.235 [01966] Starting up; pid 1966 20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k -P 4445 20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API. 20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms. 20150410 163456.140 [01966] PROXY *** scproxy started *** 20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23 20150410 163456.190 [01966] Started scproxy on port 46880. 20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests. 20150410 163456.190 [01966] Starting secure remote tunnel VM... 20150410 163502.660 [01966] Secure remote tunnel VM provisioned. 20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18 20150410 163503.576 [01966] Secure remote tunnel VM is now: booting 20150410 163513.145 [01966] Secure remote tunnel VM is now: running 20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com 20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM. 20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms. 20150410 163513.166 [01966] Starting Selenium listener... 20150410 163513.167 [01966] Establishing secure TLS connection to tunnel... 20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70 20150410 163513.168 [01966] Selenium listener started on port 4445. 20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms 20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0 20150410 163516.378 [01966] Sauce Connect is up, you may start your tests. 20150410 163516.378 [01966] Connection established. 20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1' (...) many many PROXY lines when running tests (...) 20150410 164056.602 [01966] PROXY 127.0.0.1:48955 - 200 localhost:8089 (196 bytes) 20150410 164101.193 [01966] Cleaning up. 20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18. 20150410 164109.020 [01966] KGP warning: no keepalive ack for 5s 20150410 164109.424 [01966] Goodbye. 20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low! 20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000. 20150410 183415.745 [09736] Trying to autodetect proxy settings 20150410
[JIRA] [core] (JENKINS-27993) /pluginManager/api/json largely useless
Andreas Kotes commented on JENKINS-27993 /pluginManager/api/json largely useless that helps, but doesn't make it more inuitive :-/ thanks! 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-27650) Page loads slow with hundreds of throttled builds in queue
Oleg Nenashev commented on JENKINS-27650 Page loads slow with hundreds of throttled builds in queue /** Update to the previous comment: ExecutorListener is not an extension point, we cannot make this approach work There's no listeners in Jenkins core, that could reliably deliver the info */ I've tried to introduce a light-weight off-the-queue caching in PR #28. The result was not satisfactory as well. The performance of canTake() is being improved by up to 10 times on my local benchmarks, but it still no enough to resolve the issue. We could somehow merge PRs #27 and #28, but I'm afraid the solution will stay unreliable. An additional synchronisation will be required in such case = scheduling behaviour will be impacted due to the injected quietTimes. Hacking of the load balancer could help, but there will be a conflict with other 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 Np. I'm glad you are looking at it . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125 I had no browser selected. Explained in description why. Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc defunct' process). Anyway here it is from when I had it running with 1.125, then it started to fail again: At 16:34 there was a successful run of the job. At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed. At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log" That should not have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other. But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes. 20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low! 20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000. 20150410 163455.235 [01966] Trying to autodetect proxy settings 20150410 163455.235 [01966] Starting up; pid 1966 20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k -P 4445 20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API. 20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms. 20150410 163456.140 [01966] PROXY *** scproxy started *** 20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23 20150410 163456.190 [01966] Started scproxy on port 46880. 20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests. 20150410 163456.190 [01966] Starting secure remote tunnel VM... 20150410 163502.660 [01966] Secure remote tunnel VM provisioned. 20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18 20150410 163503.576 [01966] Secure remote tunnel VM is now: booting 20150410 163513.145 [01966] Secure remote tunnel VM is now: running 20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com 20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM. 20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms. 20150410 163513.166 [01966] Starting Selenium listener... 20150410 163513.167 [01966] Establishing secure TLS connection to tunnel... 20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70 20150410 163513.168 [01966] Selenium listener started on port 4445. 20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms 20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0 20150410 163516.378 [01966] Sauce Connect is up, you may start your tests. 20150410 163516.378 [01966] Connection established. 20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1' (...) many many PROXY lines when running tests (...) 20150410 164056.602 [01966] PROXY 127.0.0.1:48955 - 200 localhost:8089 (196 bytes) 20150410 164101.193 [01966] Cleaning up. 20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18. 20150410 164109.020 [01966] KGP warning: no keepalive ack for 5s 20150410 164109.424 [01966] Goodbye. 20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low! 20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000. 20150410 183415.745 [09736] Trying to autodetect proxy settings
[JIRA] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Damien Coraboeuf commented on JENKINS-27994 The Manifest of the job-dsl JAR is empty, making it unuseable for tests Hi, I've created a pull request which solves this problem: https://github.com/jenkinsci/gradle-jpi-plugin/pull/50 If accepted, the new version of the gradle-jpi-plugin should be applied to job-dsl and new version of the plug-in created. Best regards, Damien. 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-27997) Encoding issues with the logs
Tom R created JENKINS-27997 Encoding issues with the logs Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Apr/15 3:01 PM Description: Jenkins 1.590 behind an Apache 2.2 proxy. It appears that the rendered log (sent to the browser) are incorrectly encoded. If I look up the log file in the jobs folder, I can see the log file is correct, and looks like the following: exec - 124 shuffled tests into the queue. exec - Will be consumed by 8 parallel Processes. exec 5 1/124 ✔ However, when it is viewed in the browser (Project X - Console Output), the same output appears like this: exec - 124 shuffled tests into the queue. exec - Will be consumed by 8 parallel Processes. exec 5 1/124 ��� Finally, if I check the "View as plain text" it also appears correct. Project: Jenkins Priority: Minor Reporter: Tom R 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-27997) Encoding issues with the Console Output
Tom R updated JENKINS-27997 Encoding issues with the Console Output Change By: Tom R (17/Apr/15 3:01 PM) Summary: Encodingissueswiththe logs ConsoleOutput This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-27999) Expose the perforce label/tagging functionality to the command line interface (CLI)
Rob Petti assigned JENKINS-27999 to Unassigned Expose the perforce label/tagging functionality to the command line interface (CLI) Change By: Rob Petti (17/Apr/15 4:52 PM) Assignee: RobPetti 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Paul Draper commented on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream @Daniel, I suspect you are correct. It's quite possible these have never worked together. It is present in latest (1.609), and in the latest stable (1.596.2). 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raphael CHAUMIER edited a comment on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Hi, Did you select a jdk or add a jdk in the global configuration before creating your 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] [core] (JENKINS-27987) Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609
Grigoriy Milman commented on JENKINS-27987 Multiple build jobs are the waiting queue waiting to next available excutor, but no build jobs are running. Appears after migration from ver 1.606 to 1.609 I have reproduced the error again: Job A has been started by manually and executed. After execution it triggered ((placed to the queue) another 3 build jobs. At the same time other 5 build jobs have been triggered (placed to the queue) by SCM, 4 of the last 5 jobs are downstream to the first 3 build jobs but one independent (does not have upstream job at all)! No job except job A has been processed. all other are in the queue for ever. By the way there are multiple strange log entries in jenkins.err.log like the following Apr 17, 2015 9:19:45 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@f79885 failed java.lang.NullPointerException at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99) at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81) at java.util.Arrays.mergeSort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at java.util.Collections.sort(Unknown Source) at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81) at hudson.model.Queue.maintain(Queue.java:1337) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2435) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) 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-23914) Invalid null/ element added to triggers/ in job causing NPE on job load
Mike Christof edited a comment on JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load This is still happening with Jenkins ver. 1.609 Edit: The job that happened was a "Build Flow" and not a matrix job. Not sure if its relevant though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-27999) Expose the perforce label/tagging functionality to the command line interface (CLI)
Marco Marsili created JENKINS-27999 Expose the perforce label/tagging functionality to the command line interface (CLI) Issue Type: Improvement Assignee: Rob Petti Components: cli, perforce-plugin Created: 17/Apr/15 4:51 PM Description: I would be very handy from an automation perspective to expose the Perforce label/tagging of builds functionality to the command line interface. This would allow for existing builds which have been tested and verified either manually or through some other automated test system to then be automatically tagged with some label which is not known during the initial build process. Environment: Currently running Jenkins 1.584 with Perforce Plugin 1.3.34 Project: Jenkins Priority: Major Reporter: Marco Marsili 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-23914) Invalid null/ element added to triggers/ in job causing NPE on job load
Mike Christof commented on JENKINS-23914 Invalid null/ element added to triggers/ in job causing NPE on job load This is still happening with Jenkins ver. 1.609 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-27997) Encoding issues with the Console Output
Tom R resolved JENKINS-27997 as Fixed Encoding issues with the Console Output Change By: Tom R (17/Apr/15 3:25 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Dwane Pottratz commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I still see this issue with Priority 2.12. 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-27922) Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread
Jamie Doornbos commented on JENKINS-27922 Jenkins job execution becomes unstable - jobs fail with OOM: unable to create new native thread I do generally see the Stopped line on builds, but I don't watch every build. I checked using a grep on files no more than 3 days old and found a small discrepancy of 20 stray "Started" lines: /var/lib/jenkins/jobs$ find . -mtime -3 -type f /tmp/recent_logs /var/lib/jenkins/jobs$ grep -l '[ssh-agent] Started.' `cat /tmp/recent_logs` /tmp/agent-started-logs /var/lib/jenkins/jobs$ grep -l '[ssh-agent] Stopped.' `cat /tmp/recent_logs` /tmp/agent-stopped-logs /var/lib/jenkins/jobs$ wc -l /tmp/agent-st* 2578 /tmp/agent-started-logs 2558 /tmp/agent-stopped-logs 5136 total Regarding use of SSH Agent, it is configured for all builds, since the git plugin fails to work in my environment if SSH Agent is not running. (I spent a few hours trying to debug this months ago, but don't really remember the details.) Most of the builds don't require an agent other than for the git 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raphael CHAUMIER commented on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Hi, Did you select a jdk before ? 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Oleg Nenashev updated JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream Change By: Oleg Nenashev (17/Apr/15 6:55 PM) Component/s: lockable-resources-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] [xunit-plugin] (JENKINS-28000) xUnit not testing against the appropriate XSD?
Tom R created JENKINS-28000 xUnit not testing against the appropriate XSD? Issue Type: Bug Assignee: Gregory Boissinot Components: xunit-plugin Created: 17/Apr/15 7:15 PM Description: When xUnit is executed on a PHPUnit generated xml file, the following error is logged to Jenkins' logs. Attribute 'name' must appear on element 'testsuite'. However, upon inspecting the code @ https://github.com/jenkinsci/xunit-plugin/blob/xunit-1.93/src/main/java/org/jenkinsci/plugins/xunit/service/XUnitTransformer.java https://github.com/jenkinsci/xunit-plugin/blob/xunit-1.93/src/main/java/org/jenkinsci/plugins/xunit/service/XUnitValidationService.java and https://github.com/jenkinsci/xunit-plugin/tree/master/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd testsuite.name should not be a required property in any of the junit-(8|9|10).xsd files which makes me think it is using another source as validation. Environment: Jenkins 1.590 xUnit 1.93 Project: Jenkins Priority: Minor Reporter: Tom R 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-27914) MSBuild-Parser ignores optional Subcategory
Ulli Hafner commented on JENKINS-27914 MSBuild-Parser ignores optional Subcategory One additional test in the class MsBuildParserTest.java that correctly reads an example file in your message format (subcategory). (And the changed regular _expression_ should not break any of the other tests, 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] [warnings-plugin] (JENKINS-27914) MSBuild-Parser ignores optional Subcategory
Ulli Hafner edited a comment on JENKINS-27914 MSBuild-Parser ignores optional Subcategory One additional test in the class MsBuildParserTest.java that correctly reads an example file in your message format (subcategory). (And the changed regular _expression_ should not break any of the other tests, too These tests typically are just a view lines long. 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-27968) Throttle concurrent builds and lockable resource do not work with block on upstream
Oleg Nenashev commented on JENKINS-27968 Throttle concurrent builds and lockable resource do not work with block on upstream Javadoc documentation: "True to keep builds of this project in queue when upstream projects are building. False by default to keep from breaking existing behavior." Jobs in the queue and pending jobs (assigned to executor, but not started) have Run.State.NOT_STARTED status (there's also Run.State.BUILDING status). Build::isBuilding() returns try for both statuses, so there's a risk of confusion. Paul, my bad. Your case is valid. The handling of the restrictions is based on Queue::getUnblockedItems(), so Jenkins ignores dependencies on blocked tasks like throttled runs. We just need to decide if it is a functional or a documentation bug. I'd vote fore the first option. 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] [other] (JENKINS-28001) [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL glo
Tomasz Domżał created JENKINS-28001 [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Issue Type: Bug Assignee: Unassigned Attachments: 20150417-tdomzal-vncviewer-hostname.patch Components: other Created: 17/Apr/15 7:27 PM Description: VncViewer Plugin allows accessing to Xvnc desktops via browser. 'Start' button in Console Output for launching noVNC browser generates URL using hostname retrieved with: InetAddress.getLocalHost().getHostName() which will not work in general if Jenkins is available to clients under name different than jenkins server hostname. Attached patch (base: https://svn.jenkins-ci.org/trunk/hudson/plugins/vncviewer/trunk rev 41315) changes noVNC URL build behavior to following: if 'Global settings - Jenkins Location - Jenkins URL' is not empty - extracts host from it if 'Jenkins URL' is empty or malformed - fall-backs to jenkins server hostname retrieved with InetAddress.getLocalHost().getHostName() Project: Jenkins Priority: Minor Reporter: Tomasz Domż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] [checkstyle-plugin] (JENKINS-27887) pmd plugin and checkstyle plugin fail to install
Ulli Hafner commented on JENKINS-27887 pmd plugin and checkstyle plugin fail to install Can you delete the folder JENKINS_HOME/plugins/checkstyle before you start Jenkins? Then the plug-in will automatically be extracted again. Do you have a virus scanner that might block the affected file annotations-2.0.0.jar? 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-27976) MsBuildParser should parse Code Analysis warnings
Ulli Hafner resolved JENKINS-27976 as Not A Defect MsBuildParser should parse Code Analysis warnings Ups. At least you are now prepared for the next enhancement And you can still submit the additional unit test as pull request if you like! Change By: Ulli Hafner (17/Apr/15 7: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] [other] (JENKINS-28001) [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL glo
Tomasz Domżał commented on JENKINS-28001 [vncviewer-plugin] VncViewer start button in Console output does not work if jenkins instance is installed behind reverse proxy (should extract host from Jenkins URL global settings) Plugin page: https://wiki.jenkins-ci.org/display/JENKINS/VncViewer+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-22853) SEVERE: Trying to unexport an object that's already unexported
Arvind Ramalingam commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported We are currently at Jenkins ver. 1.509.4 but planning to update to the latest LTS 1.596.2. We installed the latest LTS on our Dev Box and started to see the above. Should I still go ahead with the upgrade or wait for the fix? How frequent are the job failures? Should the severity of the issues be raised to 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Christopher Carlson commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I have seen this issue as well. I just upgraded from 1.522 to 1.608. We're using an old Throttle plugin, 1.7.2, but it appears from the previous comments that this won't fix it. I was able to figure out that the problem occurs when 2 jobs that are supposed to throttle under the same category are started at exactly the same time. I created a job that started two jobs when completed. All three run with the same throttle category on the same node. The two child jobs will be started simultaneously when one should block the other. Hope this helps. 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-22853) SEVERE: Trying to unexport an object that's already unexported
Alex Earl commented on JENKINS-22853 SEVERE: Trying to unexport an object thats already unexported I see 1 out of 50 jobs fail every other build or so. 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] [websphere-deployer-plugin] (JENKINS-22393) Problem deploying EAR to WAS 7
SCM/JIRA link daemon commented on JENKINS-22393 Problem deploying EAR to WAS 7 Code changed in jenkins User: Greg Peters Path: pom.xml http://jenkins-ci.org/commit/websphere-deployer-plugin/c7c3a48c1b06364995358f927eb5cbbdaa063044 Log: Merge pull request #4 from Floww/master JENKINS-22393 : Correction of class loader issue. Compare: https://github.com/jenkinsci/websphere-deployer-plugin/compare/d7c94a35a09a...c7c3a48c1b06 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] [websphere-deployer-plugin] (JENKINS-22393) Problem deploying EAR to WAS 7
SCM/JIRA link daemon commented on JENKINS-22393 Problem deploying EAR to WAS 7 Code changed in jenkins User: fmoisson Path: pom.xml http://jenkins-ci.org/commit/websphere-deployer-plugin/82137f719de8b2c5672ec75e1fb927692dd793fb Log: Correction of class loader issue : JIRA JENKINS-22393. 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] [websphere-deployer-plugin] (JENKINS-22393) Problem deploying EAR to WAS 7
SCM/JIRA link daemon commented on JENKINS-22393 Problem deploying EAR to WAS 7 Code changed in jenkins User: fmoisson Path: pom.xml http://jenkins-ci.org/commit/websphere-deployer-plugin/b661135e593a2c3b4a88cfe98a02531e9eede743 Log: Correction of class loader issue : JIRA JENKINS-22393. 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] [websphere-deployer-plugin] (JENKINS-27945) Support for deployment on cluster
SCM/JIRA link daemon commented on JENKINS-27945 Support for deployment on cluster Code changed in jenkins User: Greg Peters Path: pom.xml src/main/java/org/jenkinsci/plugins/websphere_deployer/WebSphereDeployerPlugin.java src/main/resources/org/jenkinsci/plugins/websphere_deployer/WebSphereDeployerPlugin/config.jelly src/main/resources/org/jenkinsci/plugins/websphere_deployer/WebSphereDeployerPlugin/help-cluster.html http://jenkins-ci.org/commit/websphere-deployer-plugin/2d2c3ee661262ef15020a3b18df2375b43e9b992 Log: Merge pull request #5 from riso/master JENKINS-27945 Enable cluster support Compare: https://github.com/jenkinsci/websphere-deployer-plugin/compare/c7c3a48c1b06...2d2c3ee66126 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] [nodejs-plugin] (JENKINS-27845) Support auto install on Mac OS X
Iain Coulter commented on JENKINS-27845 Support auto install on Mac OS X Mac is supported already. Windows is not although I have a pull request to fix it (JENKINS-26828) 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-27743) Jenkins retriggers job on same changelist every time it polls
Martin Hulth updated JENKINS-27743 Jenkins retriggers job on same changelist every time it polls Here are the files from the latest build. It's now at 5030 (from 194 which I noted in the initial case) as I went on vacation and somehow it got re-enabled while I was gone and ran every two minutes for almost 7 days. There were a few more checkins that occured during that week that are visible in the polling log. Change By: Martin Hulth (17/Apr/15 10:14 PM) Attachment: build.xml Attachment: changelog.xml Attachment: log Attachment: polling.log 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-27743) Jenkins retriggers job on same changelist every time it polls
Martin Hulth commented on JENKINS-27743 Jenkins retriggers job on same changelist every time it polls I am not using variable expansion in this job. It's rather simple in that after sync it CDs to a directory for the workspace and runs a python script to build and test. 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-27997) Encoding issues with the Console Output
Tom R commented on JENKINS-27997 Encoding issues with the Console Output Works fine if I pass "-Dfile.encoding=UTF-8" as argument to java when starting jenkins as per #13838. 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-27997) Encoding issues with the Console Output
Tom R edited a comment on JENKINS-27997 Encoding issues with the Console Output Works fine if I pass "-Dfile.encoding=UTF-8" as argument to java when starting jenkins as per https://issues.jenkins-ci.org/browse/JENKINS-13838. 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-27998) Git plugin fails to connect
Jamie Doornbos created JENKINS-27998 Git plugin fails to connect Issue Type: Bug Assignee: Nicolas De Loof Attachments: git_bug_build.log, git_bug_build_with_ssh_agent.log, plugins.xml Components: git-plugin Created: 17/Apr/15 4:45 PM Description: I have a private key set up in the global credentials (named sls). I have the SCM for a test project set up to download code from a springloops git project. See attached log of the failure to connect to git. Fetching the repo with command line git works fine with the same key. If I install an SSH agent on the exact same build, it allows the fetch to work. See the other attached log for that. I have used jenkins and git in a different environment with no problems. The only difference I've noticed here is the non-standard port of 1234. Is it possible git plugin is not identifying the port? Setting the priority to major since use of SSH agent is a workaround but requires extra configuration and build overhead. Environment: Jenkins 1.598 Linux 2.6.32-431.5.1.el6.x86_64 CentOS release 6.5 (Final) Plugins: Attached file saved from pluginManager/api/xml?tree=plugins[shortName,version]pretty Project: Jenkins Priority: Major Reporter: Jamie Doornbos 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.
