[JIRA] [envinject-plugin] (JENKINS-27313) Environment variable Injection failing after upgrading from 1.90 to 1.91
Oleg Nenashev assigned JENKINS-27313 to Oleg Nenashev Environment variable Injection failing after upgrading from 1.90 to 1.91 Change By: Oleg Nenashev (19/Mar/15 5:49 AM) Assignee: Gregory Boissinot Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27287) EnvInject plugin 1.91 causes javax.servlet.ServletException in job view
Oleg Nenashev resolved JENKINS-27287 as Duplicate EnvInject plugin 1.91 causes javax.servlet.ServletException in job view Change By: Oleg Nenashev (19/Mar/15 5:41 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mstest-plugin] (JENKINS-27469) MSTest Plugin instable when use Ignore flag
SCM/JIRA link daemon resolved JENKINS-27469 as Fixed MSTest Plugin instable when use Ignore flag Change By: SCM/JIRA link daemon (19/Mar/15 5:37 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] [copyartifact-plugin] (JENKINS-27475) rename job cause NPE exception and break job config history
hiteswar kumar updated JENKINS-27475 rename job cause NPE exception and break job config history Change By: hiteswar kumar (19/Mar/15 5:36 AM) Description: our current jenkins master(ver. 1.554.2, copyartifact version=1.32.1 ),throwing below NPE exception but successful rename of job but config history is disparaged after rename job.there is only one job(latest changed name) directory under .jenkins/job butthere are 2 job(old and ltest changed name) directory under .jenkins//config-history/jobs/.=configure different history directory than default at jobconfighistory in Jenkins global system configurationwhile another jenkins with same environment(ver. 1.554.2,copyartifact version=1.32.1 , jobconfighistory-2.10) working fine only difference is using default config history instead .STACKTRACE and Message after rename job:A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerExceptionat org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)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.Stapler.invoke(Stapler.java:631)at org.kohsuke.stapler.Stapler.service(Stapler.java:225)at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)at com.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198)at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176)at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85)at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:97)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)at hudson.security.ChainedServletFilter$1.
[JIRA] [mstest-plugin] (JENKINS-27469) MSTest Plugin instable when use Ignore flag
SCM/JIRA link daemon commented on JENKINS-27469 MSTest Plugin instable when use Ignore flag Code changed in jenkins User: nilleb Path: src/test/java/hudson/plugins/mstest/MSTestReportConverterTest.java src/test/resources/hudson/plugins/mstest/nilleb_HOST18468 2015-03-18 08_03_36.xml http://jenkins-ci.org/commit/mstest-plugin/5e72a6ee84fd9de0d704fea232fc33f71d3f5483 Log: [FIXED JENKINS-27469] unit test for ignored unittests Compare: https://github.com/jenkinsci/mstest-plugin/compare/d48dde553cd5...5e72a6ee84fd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-21540) NPE while renaming job
hiteswar kumar commented on JENKINS-21540 NPE while renaming job In previous comment, I have updated stacktrace received on GUI after job rename done. please let me know if need any other information to fix 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] [copyartifact-plugin] (JENKINS-21540) NPE while renaming job
hiteswar kumar edited a comment on JENKINS-21540 NPE while renaming job Thanks Daniel for information. sorry for delay in updating here. at what version of copyartifact this was fixed. our current jenkins master(ver. 1.554.2, copyartifact version=1.32.1 ),throwing below NPE exception but successful rename of job but config history is disparaged after rename job. there is only one job(latest changed name) directory under .jenkins/job but there are 2 job(old and ltest changed name) directory under .jenkins//config-history/jobs/. =configure different history directory than default at jobconfighistory in Jenkins global system configuration jobconfighistory installed plugin version=2.10(latest) while another jenkins with same environment(ver. 1.554.2,copyartifact version=1.32.1 , jobconfighistory-2.10) working fine only difference is using default config history instead . STACKTRACE: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) 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.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedS
[JIRA] [golang-plugin] (JENKINS-27499) Global config page is broken when loaded before the tool installer data has been fetched
Christopher Orr created JENKINS-27499 Global config page is broken when loaded before the tool installer data has been fetched Issue Type: Bug Assignee: Christopher Orr Components: golang-plugin Created: 19/Mar/15 4:40 AM Description: Loading the global configure screen gets stuck "LOADING" when it hits the Go plugin, if the tool installer update data for this plugin has not yet been downloaded. The workaround is to force a download of the data via Plugin Manager > Advanced > Check Now. Environment: Tested on versions between Jenkins 1.565 and 1.605 Project: Jenkins Priority: Minor Reporter: Christopher Orr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-cloudformation] (JENKINS-27498) Configure screen stack traces on me
Christopher Orr commented on JENKINS-27498 Configure screen stack traces on me Could you possibly post the stacktrace? Does this happen every time, or only when enabling the cloudformation build environment, or the post-build action, for example? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-cloudformation] (JENKINS-27498) Configure screen stack traces on me
Gregg Lowrimore created JENKINS-27498 Configure screen stack traces on me Issue Type: Bug Assignee: Unassigned Attachments: cloudbees-support.zip Components: jenkins-cloudformation Created: 19/Mar/15 4:17 AM Description: Some king of Jelly NPE exception I think. But it renders the configure screen useless, though Jenkins never crashes. Environment: 1.605 on RHEL5 Linux Project: Jenkins Labels: jenkins Priority: Major Reporter: Gregg Lowrimore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-27497) Set a environment variable EMULATOR(S)
Sebastian Roth commented on JENKINS-27497 Set a environment variable EMULATOR(S) I'm sorry, this is in fact already there. Thanks for the clarification. (Will RTFM next 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] [android-emulator-plugin] (JENKINS-27497) Set a environment variable EMULATOR(S)
Sebastian Roth closed JENKINS-27497 as Fixed Set a environment variable EMULATOR(S) RTFM. Change By: Sebastian Roth (19/Mar/15 3:58 AM) Status: Open Closed 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] [hp-application-automation-tools-plugin] (JENKINS-25087) Unable to execute BPT on remote UFT machine with Quality Center 11.52
rachel liu commented on JENKINS-25087 Unable to execute BPT on remote UFT machine with Quality Center 11.52 Hi, I have the same issue. But just to update some more information. Our machine has very strict security control . We have a temporary account with administrator access to local machine but in a different domain. All helpdesk approved application will be pushed to local machine automatically. What I found is , by default, the Jenkin service is started using "local user". If I run the ALM test case from Jenkin web console, I will receive the "Could not lock the host. Another test may be running. Try later" error msg . But, if I run the test case using command line, (launch cmd using local user), then run C:\Jenkins\workspace\POC\HpToolsLauncher.exe -paramfile props19032015110329904.txt Then it works. I don't know the difference between running it from cmd and running it from web console. If I run it from command line, the result will be published to ALM also, but the Jenkin web console is not updated, it still showing the previous fail log. This has been block us using Jenkin for months, hope it can be solved. 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] [android-emulator-plugin] (JENKINS-27497) Set a environment variable EMULATOR(S)
Christopher Orr commented on JENKINS-27497 Set a environment variable EMULATOR(S) There are already a lot of environment variables set during a build, including the name of the AVD being used: https://wiki.jenkins-ci.org/display/JENKINS/Android+Emulator+Plugin#AndroidEmulatorPlugin-Buildexecution Jenkins builds are independent from one another, so I'm not sure where there would be a list, or what "available" emulators would mean, or who should have access to this environment variable. Could you perhaps clarify a bit further? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Christopher Orr resolved JENKINS-12998 as Won't Fix Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ As noted, there are defined extension points in core for this and plugins which implement them, so this won't be reimplemented in core. Change By: Christopher Orr (19/Mar/15 3:24 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-27497) Set a environment variable EMULATOR(S)
Sebastian Roth created JENKINS-27497 Set a environment variable EMULATOR(S) Issue Type: Improvement Assignee: Christopher Orr Components: android-emulator-plugin Created: 19/Mar/15 3:13 AM Description: Would it be possible to set a environment variable (maybe called EMULATOR, or EMULATORS if multiple are started) which contain the list of started & available emulators? Just in case there are multiple builds running on the same machine for different projects, it might be helpful to know which one exactly is active for a certain build. Project: Jenkins Priority: Minor Reporter: Sebastian Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
SCM/JIRA link daemon commented on JENKINS-26414 Add support for new C4 instance types Code changed in jenkins User: Francis Upton Path: pom.xml http://jenkins-ci.org/commit/ec2-plugin/b59267e0e2624f2d2ff11056d33b1c536dc81084 Log: Merge pull request #141 from cbek/JENKINS-26414 JENKINS-26414 - Add support for new C4 instance types Compare: https://github.com/jenkinsci/ec2-plugin/compare/ba77bb7f9c78...b59267e0e262 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
SCM/JIRA link daemon commented on JENKINS-26414 Add support for new C4 instance types Code changed in jenkins User: Christoph Beckmann Path: pom.xml http://jenkins-ci.org/commit/ec2-plugin/42364b4d7523dcb30e382331a7dfb1ccf14834d5 Log: JENKINS-26414 - Add support for new C4 instance types upgrade aws-java-sdk ot version 1.9.24 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
jay hendren edited a comment on JENKINS-27488 gss.conf file not found hi kutzi, i've been debugging this issue with dylan. we were able to work around the problem by downgrading the plugin version to 1.25 and unchecking "use SASL authentication" in the jenkins/jabber configuration. by downgrading, we removed the dependency on smack 4. afaik, smack 4 can only use sasl auth, and sasl auth is the general cause of our issue. "PLAIN"/simple auth works just fine. we would like to stay on top of the latest version of jenkins and all of our plugins, so obviously, this is a non-optimal workaround. i accept the fact that upgrading to the latest version may mean that we are forced to use sasl auth, in which case we would need to resolve the errors in the attached debug output. also, as dylan mentioned, we were able to eventually get the jenkins user authenticated to our openfire server using sasl auth and the latest jabber plugin (1.34), but with two HUGE caveats: to clear the error in the attached debug output, we had to create a file called /gss.conf and give it some contents that we snagged from another bug report on the web. there is NO documentation on where this gss.conf file should be located, how to configure its location, or what its contents should be. we needed to strace the jenkins server to even figure out where jenkins was looking for it, and we have no idea what the contents of the file mean or what this file is used for. it's necessary to manually kinit to please gssapi. we provide the password for the jenkins principal to the jabber plugin, so this shouldn't be necessary; a ticket should be automatically created when jenkins successfully auths to the openfire server. so though this bug report was originally filed for the first issue, the second one seems very closely related. let us know if you think a new bug report should be opened for that issue. thanks, jay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
jay hendren edited a comment on JENKINS-27488 gss.conf file not found hi kutzi, i've been debugging this issue with dylan. we were able to work around the problem by downgrading the plugin version to 1.25 and unchecking "use SASL authentication" in the jenkins/jabber configuration. by downgrading, we removed the dependency on smack 4. afaik, smack 4 can only use sasl auth, and sasl auth is the general cause of our issue. "PLAIN"/simple auth works just fine. we would like to stay on top of the latest version of jenkins and all of our plugins, so obviously, this is a non-optimal workaround. i accept the fact that upgrading to the latest version may mean that we are forced to use sasl auth, in which case we would need to resolve the errors in the attached debug output. also, as dylan mentioned, we were able to eventually get the jenkins user authenticated to our openfire server using sasl auth, but with two HUGE caveats: to clear the error in the attached debug output, we had to create a file called /gss.conf and give it some contents that we snagged from another bug report on the web. there is NO documentation on where this gss.conf file should be located, how to configure its location, or what its contents should be. we needed to strace the jenkins server to even figure out where jenkins was looking for it, and we have no idea what the contents of the file mean or what this file is used for. it's necessary to manually kinit to please gssapi. we provide the password for the jenkins principal to the jabber plugin, so this shouldn't be necessary; a ticket should be automatically created when jenkins successfully auths to the openfire server. so though this bug report was originally filed for the first issue, the second one seems very closely related. let us know if you think a new bug report should be opened for that issue. thanks, jay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
jay hendren commented on JENKINS-27488 gss.conf file not found hi kutzi, i've been debugging this issue with dylan. we were able to work around the problem by downgrading the plugin version to 1.25 and unchecking "use SASL authentication" in the jenkins/jabber configuration. by downgrading, we removed the dependency on smack 4. afaik, smack 4 can only use sasl auth, and sasl auth is the general cause of our issue. "PLAIN"/simple auth works just fine. we would like to stay on top of the latest version of jenkins and all of our plugins, so obviously, this is a non-optimal workaround. i accept the fact that upgrading to the latest version may mean that we are forced to use sasl auth, in which case we would need to resolve the errors in the attached debug output. also, as dylan mentioned, we were able to eventually get the jenkins user authenticated to our openfire server using sasl auth, but with two HUGE caveats: we had to create a file called /gss.conf and give it some contents that we snagged from another bug report on the web. there is NO documentation on where this gss.conf file should be located, how to configure its location, or what its contents should be. we needed to strace the jenkins server to even figure out where jenkins was looking for it, and we have no idea what the contents of the file mean or what this file is used for. it's necessary to manually kinit to please gssapi. we provide the password for the jenkins principal to the jabber plugin, so this shouldn't be necessary; a ticket should be automatically created when jenkins successfully auths to the openfire server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Waldek M commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations Thanks, Oleg! I appreciate 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] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1
Per Arnold Blaasmo commented on JENKINS-27476 Plugin casue deadlock on Jenkins LTS 1.596.1 Thanks for looking into this. Just for the record, my company is not currently a CloudBees customer. Some more info: To try to cope with the problem I downgraded to version 1.2 of the Durable Task Plugin. This seems to make things much more stable. We might still get a deadlock, but more seldom. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25261) Missing dependency on RPM package
Michael Prokop commented on JENKINS-25261 Missing dependency on RPM package Just ran into this issue on CentOS 6.5 with Jenkins v1.596.1-1.1 and java-1.8.0-openjdk-headless, "yum -y install fontconfig dejavu-sans-fonts" fixed this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
Dylan Canfield commented on JENKINS-27488 gss.conf file not found I see. Alternately, how do I configure the gss.conf file so that I can properly get a ticket without having to "kinit" as the jenkins user? My keberos client config is in the standard /etc/krb5.conf location. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
kutzi commented on JENKINS-27488 gss.conf file not found It does matter because bugs are many times only manifest themselves when specific versions are used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
Dylan Canfield edited a comment on JENKINS-27488 gss.conf file not found Why does it matter what OpenFire version I am running (it's 3.9.3, BTW)? This is an issue with the plugin. The connection configuration is very simple: JabberID (username@FQDN) and Password are set Accept all SSL/TLS certificates is set Expose Presence is set I was able to find the file that it is trying to load, using lsof and strace. Java is trying to load '/gss.conf'. I even tracked down the class that is trying to do the loading, org.jivesoftware.smack.sasl which does a relative path load. So, I tried to create a gss.conf file based on what I can glean from http://docs.oracle.com/javase/7/docs/jre/api/security/jaas/spec/com/sun/security/auth/module/Krb5LoginModule.html but I really just want to proceed with PLAIN auth and not use GSSAPI. There should be a way to bypass GSSAPI authentication and just use PLAIN auth or fail to PLAIN auth when GSSAPI fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
Dylan Canfield commented on JENKINS-27488 gss.conf file not found Why does it matter what OpenFire version I am running (it's 3.9.3, BTW)? This is an issue with the plugin. The connection configuration is very simple: JabberID (username@FQDN) and Password are set Accept all SSL/TLS certificates is set Expose Presence is set I was able to find the file that it is trying to load, using lsof and strace. The server is trying to load '/gss.conf'. I even tracked down the class that is trying to do the loading, org.jivesoftware.smack.sasl which does a relative path load. So, I tried to create a gss.conf file based on what I can glean from http://docs.oracle.com/javase/7/docs/jre/api/security/jaas/spec/com/sun/security/auth/module/Krb5LoginModule.html but I really just want to proceed with PLAIN auth and not use GSSAPI. There should be a way to bypass GSSAPI authentication and just use PLAIN auth or fail to PLAIN auth when GSSAPI fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy-plugin] (JENKINS-24096) Jenkins Tomcat deploymet error
Thomas Hatley commented on JENKINS-24096 Jenkins Tomcat deploymet error I too ran into this issue when running IIS in front of Tomcat 7 - as a test, I opened an http port in Tomcat and bypassed IIS altogether using the new port, and that eliminated the errornext attempt at deployment from Jenkins was successful. Don't have a viable solution for those who must go through IIS, but I did see a post which mentioned 'chunking' of the PUT request as a potential cause. Jenkins v1.580.2 Deploy to container Plugin v1.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-67) consoleText does not stream
Silver Scar commented on JENKINS-67 consoleText does not stream Hey guys, is this currently on a roadmap? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
kutzi commented on JENKINS-27488 gss.conf file not found Which is your Openfire version? What does your connection configuration look like? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27496) NPE during submission of EnvInject JobProperty when the formis empty
SCM/JIRA link daemon commented on JENKINS-27496 NPE during submission of EnvInject JobProperty when the formis empty Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java http://jenkins-ci.org/commit/envinject-plugin/b78c45cc336b2875ca7e4da4c25c95c2235a4e1c Log: [FIX JENKINS-27496] reconfigure may return null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27496) NPE during submission of EnvInject JobProperty when the formis empty
SCM/JIRA link daemon commented on JENKINS-27496 NPE during submission of EnvInject JobProperty when the formis empty Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java http://jenkins-ci.org/commit/envinject-plugin/e5e3143c50f01e77aa901855423ed2914b0f3c1f Log: [FIX JENKINS-27496] reconfigure may return null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis-plugin] (JENKINS-25660) Dynamic axis does not handle quotes in input variables
SCM/JIRA link daemon commented on JENKINS-25660 Dynamic axis does not handle quotes in input variables Code changed in jenkins User: Oleg Nenashev Path: src/test/java/ca/silvermaplesolutions/jenkins/plugins/daxis/DynamicAxisTest.java http://jenkins-ci.org/commit/dynamic-axis-plugin/51475b3ab12a39f036b453f5da883df825dd8b85 Log: JENKINS-25660 - Added a regression test for the issue Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis-plugin] (JENKINS-27243) Default value appears in axes when there's an input variable
SCM/JIRA link daemon commented on JENKINS-27243 Default value appears in axes when there's an input variable Code changed in jenkins User: Oleg Nenashev Path: src/test/java/ca/silvermaplesolutions/jenkins/plugins/daxis/DynamicAxisTest.java http://jenkins-ci.org/commit/dynamic-axis-plugin/229a41c18f5c95bd47bd1bc308095d37366a23ba Log: JENKINS-27243 - Added Unit test for the issue The commit also adds a test of the basic functionality Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis-plugin] (JENKINS-27243) Default value appears in axes when there's an input variable
SCM/JIRA link daemon resolved JENKINS-27243 as Fixed Default value appears in axes when there's an input variable Change By: SCM/JIRA link daemon (18/Mar/15 9:50 PM) Status: In Progress 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] [dynamic-axis-plugin] (JENKINS-27243) Default value appears in axes when there's an input variable
SCM/JIRA link daemon commented on JENKINS-27243 Default value appears in axes when there's an input variable Code changed in jenkins User: Oleg Nenashev Path: src/main/java/ca/silvermaplesolutions/jenkins/plugins/daxis/DynamicAxis.java src/test/java/ca/silvermaplesolutions/jenkins/plugins/daxis/DynamicAxisTest.java http://jenkins-ci.org/commit/dynamic-axis-plugin/b8732442adfac7d3a3de27e2dd6386aaf6f82a7e Log: Merge pull request #5 from oleg-nenashev/master JENKINS-27243 - Fix the improper Axis values initialization on buildEnvironment() with circular dependencies Compare: https://github.com/jenkinsci/dynamic-axis-plugin/compare/bbac467585d2...b8732442adfa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis-plugin] (JENKINS-27243) Default value appears in axes when there's an input variable
SCM/JIRA link daemon commented on JENKINS-27243 Default value appears in axes when there's an input variable Code changed in jenkins User: Oleg Nenashev Path: src/main/java/ca/silvermaplesolutions/jenkins/plugins/daxis/DynamicAxis.java http://jenkins-ci.org/commit/dynamic-axis-plugin/9b4b0d526d7d5bec525113ad91d1c59831f4d470 Log: [FIXED JENKINS-27243] - Properly handle axis values cache to avoid issues on nested calls. The change also improves logging in the plugin. Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27483) Repository URL containg double points couldn't be resolved correctly.
Michael Hauf commented on JENKINS-27483 Repository URL containg double points couldn't be resolved correctly. Yep. The third slash is added by the plugin. ssh://g...@github.com:/github/git.git results in ssh:///g...@github.com:/github/git.git and that's an invalid url. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daniel Beck
updated JENKINS-27447
LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Change By:
Daniel Beck
(18/Mar/15 9:36 PM)
Description:
Upgrade to LTS 1.596.1. Same call works on prior version (1.565.3). Some data is returned, then oops page.
Original exception:
{noformat} Caused by: java.lang.NullPointerExceptionat java.text.SimpleDateFormat.parse(SimpleDateFormat.java:1439)at java.text.DateFormat.parse(DateFormat.java:364)at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:195){noformat}
depth=0 is fine, 1, 2 fail:Stack trace
{noformat}
java.io.IOException: Failed to write timestamp at org.kohsuke.stapler.export.Property.writeTo(Property.java:122) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:172) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:211) at sun.reflect.GeneratedMethodAccessor546.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.Metric
[JIRA] [git-plugin] (JENKINS-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daniel Beck updated JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page Change By: Daniel Beck (18/Mar/15 9:35 PM) Environment: LTS 1.596.1 Git Plugin 2.2.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daniel Beck updated JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page Let's move this over to Git plugin. You can always resolve as Not A Defect or Cannot Reproduce if the newest version doesn't have this problem. Change By: Daniel Beck (18/Mar/15 9:34 PM) Component/s: git-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daniel Beck reopened JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page Change By: Daniel Beck (18/Mar/15 9:34 PM) Resolution: Fixed Status: Resolved Reopened Assignee: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27496) NPE during submission of EnvInject JobProperty when the formis empty
Oleg Nenashev started work on JENKINS-27496 NPE during submission of EnvInject JobProperty when the formis empty Change By: Oleg Nenashev (18/Mar/15 9:34 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daniel Beck updated JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page Change By: Daniel Beck (18/Mar/15 9:34 PM) Status: Reopened 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] [envinject-plugin] (JENKINS-19852) NPE during submission of EnvInject JobProperty configurations
Oleg Nenashev commented on JENKINS-19852 NPE during submission of EnvInject JobProperty configurations @Waldek, your issue has not been fixed in 1.91.1 I've created JENKINS-27496 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27496) NPE during submission of EnvInject JobProperty when the formis empty
Oleg Nenashev created JENKINS-27496 NPE during submission of EnvInject JobProperty when the formis empty Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin Created: 18/Mar/15 9:33 PM Description: The issue is a follow-up to the discussion in JENKINS-19852... The issue happens due to the improper fix in https://github.com/jenkinsci/envinject-plugin/commit/f28c26b7c4e346157fcaf2f284582e29457bb1ff JobProperty::reconfigure(req, form) may return null if the property should be removed See http://javadoc.jenkins-ci.org/hudson/model/JobProperty.html#reconfigure%28org.kohsuke.stapler.StaplerRequest,%20net.sf.json.JSONObject%29 property.info != null check fails javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(Compres
[JIRA] [core] (JENKINS-27472) Exception on default view and other list views
Demitrius Nelon commented on JENKINS-27472 Exception on default view and other list views I've been trying for quite a while. I removed most of the plugins that were brought in and never used. My best guess is that it has something to do with how jelly loads the jobs in from the config.xml or some other place if it doesn't come from there. One of the stack trace results gave me the impression that something was trying to treat a number as a string or some other object type that wasn't compatible. I'm approaching the point of building a new master and bringing jobs over one at a time At least my builds are still running, and I've been able to create individual user based views without problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27363) envinject-lib and envinject-plugin should handle null sensitive variables
Oleg Nenashev commented on JENKINS-27363 envinject-lib and envinject-plugin should handle null sensitive variables @Michael I suppose your issue is similar to https://issues.jenkins-ci.org/browse/JENKINS-19852?focusedCommentId=222997&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-222997 from JENKINS-19852. Nothing to do with this issue, but seems the case should be moved into a separate issue. I'll do 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] [core] (JENKINS-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daryl Spartz commented on JENKINS-27447 LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page yes, saw it last night. The original stack trace did not have that. Apparently, Java stacktrace can be limited (log4j?). The Jenkins web page also didn't show it. After I eliminated enough of the plugins, where was space available for the useful stuff. 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] [core] (JENKINS-27447) LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page
Daryl Spartz resolved JENKINS-27447 as Fixed LTS 1.596.1 REST api /api/json?depth=1 produces ERROR 500, Oops page Error in git-plugin, will pursue there, if not fixed in latest Change By: Daryl Spartz (18/Mar/15 9:24 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] [core] (JENKINS-27268) "dumb" slave?
Daniel Beck commented on JENKINS-27268 "dumb" slave? Kohsuke Kawaguchi didn't show up to the meeting, so this got postponed to April 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] [core] (JENKINS-26398) Fix createSlave for RestartableJenkinsRule
Jesse Glick commented on JENKINS-26398 Fix createSlave for RestartableJenkinsRule Could do that, but some of the tests also seem to require use of a JNLP slave, which is rather more complicated to model. Punting for the moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27495) ListView doesn't support recurse
Vincent Janelle commented on JENKINS-27495 ListView doesn't support recurse https://github.com/jenkinsci/job-dsl-plugin/pull/411 PR submmitted 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] [job-dsl-plugin] (JENKINS-27495) ListView doesn't support recurse
Vincent Janelle created JENKINS-27495 ListView doesn't support recurse Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 18/Mar/15 9:09 PM Description: The ListView dsl doesn't support the recurse parameter, which makes it hard to include entries in folders. Project: Jenkins Priority: Trivial Reporter: Vincent Janelle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27363) envinject-lib and envinject-plugin should handle null sensitive variables
Michael Shuler commented on JENKINS-27363 envinject-lib and envinject-plugin should handle null sensitive variables env: Jenkins LTS 1.596.1, EnvInject 1.91.1 (everything current as of commenting) I receive a traceback when attempting to simply save a job configuration, so I'm currently unable to edit any job configs. I would like to verify this is the same issue: WARNING: Error while serving http://cassci.datastax.com/job/scratch_mshuler2/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(Se
[JIRA] [core] (JENKINS-26399) Utility method in JenkinsRule to wait for build to complete
Jesse Glick started work on JENKINS-26399 Utility method in JenkinsRule to wait for build to complete Change By: Jesse Glick (18/Mar/15 8:57 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27494) Support for PHPUnit 4.* reports
Matteo Pescarin created JENKINS-27494 Support for PHPUnit 4.* reports Issue Type: Bug Assignee: Gregory Boissinot Components: xunit-plugin Created: 18/Mar/15 8:14 PM Description: As currently reported in the issue tracker of Codeception, it seems like test results published by PHPUnit 4.* are making xUnit fail the build, complaining it's not in a readable format. The error I get is the following: > Attribute 'feature' is not allowed to appear in element 'testcase'. The current XML that gives me these errors is the following: https://bpaste.net/show/2fd99120add6 Environment: jenkins latest version, phpunit 4.5 (via Codeception 2 and Yii2) Project: Jenkins Labels: phpunit reporting test-results test codeception, Priority: Critical Reporter: Matteo Pescarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloverphp-plugin] (JENKINS-27493) Allow multiple reports to be published
Matteo Pescarin created JENKINS-27493 Allow multiple reports to be published Issue Type: Improvement Assignee: sogabe Components: cloverphp-plugin Created: 18/Mar/15 8:07 PM Description: This is currently a very specific case, but I can't see why this won't be used by someone else. I'm working with Codeception and Yii2. Functional and unit tests coverage reports are aggregated together while the acceptance tests coverage reports are kept separate as long story short it's a remote code coverage generated by c3. Now I'm able to publish the first report, but not the second. I was wondering if you would consider including this feature in a future release, either by displaying a completely separate coverage report, or by aggregating the additional ones to the first (which would be sweet). Thanks! Project: Jenkins Priority: Minor Reporter: Matteo Pescarin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1
stephenconnolly commented on JENKINS-27476 Plugin casue deadlock on Jenkins LTS 1.596.1 Ultimately fixing this is part of https://github.com/jenkinsci/jenkins/pull/1596 If this is a CloudBees customer we have two hotfixes that seem to work around the deadlock with the side-effect of degrading UI performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline
updated JENKINS-27491
kicking off of build via curl command not working in 1.16.1 version of plugin
Change By:
Peter Kline
(18/Mar/15 7:55 PM)
Description:
We are migrating our old Jenkins instance to a new machine so we are moving from Jenkins 1.538 to 1.605. Our Jenkins plugin is moving from 1.5 to the latest release. We have been using a git hook to run the curl command to fire off a polling task for years now without problem. This no longer works.In our older version 1.3.0 we see the polling output of the job looking like (not the same job so don't take it as it doesn't work in the old one either):{code}Started on Mar 18, 2015
2
3
:
25
38
:
58
19
PMUsing strategy: Default[poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0)Done. Took 1
.1
sec
No changes
Changes found
{code}New Instance with git 1.8.0.6 and git client 1.16.1{code}Started on Mar 18, 2015 2:28:23 PMUsing strategy: Default[poll] Last Built Revision: Revision 742f5171deb7fcb7a80d00174003f5ffb9b1e396 (refs/remotes/origin/release_team1) > /usr/local/bin/git --version # timeout=10 > /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git # timeout=10Done. Took 1.6 secNo changes{code}Now in the second instance there were changes and the job was imported from our old instance. We are not sure why the job is never fired off. The output "refs/remotes..." is different between the old job and the new one and not sure if that might be the issue or not.We have tried tweaking the branch specifier to various things but nothing seems to work.If I run the ls-remote by hand the output shows the sha1 changed:{code}-bash-4.1$ /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git |grep release_teamfff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1{code}
We have tried doing the polling on the slaves but we don't keep our workspaces around after we build so this doesn't work if we don't already have a workspace waiting for the next poll.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 2.2 version of plugin
Peter Kline
updated JENKINS-27491
kicking off of build via curl command not working in 2.2 version of plugin
Change By:
Peter Kline
(18/Mar/15 7:52 PM)
Description:
We are migrating our old Jenkins instance to a new machine so we are moving from Jenkins 1.538 to 1.605. Our Jenkins plugin is moving from 1.5 to the latest release. We have been using a git hook to run the curl command to fire off a polling task for years now without problem. This no longer works.In our older version 1.
5
3.0
we see the polling output of the job looking like (not the same job so don't take it as it doesn't work in the old one either):{code}Started on Mar 18, 2015 2:25:58 PMUsing strategy: Default[poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0)Done. Took 1.1 secNo changes{code}New Instance with git 1.8.0.6 and git client 1.16.1{code}Started on Mar 18, 2015 2:28:23 PMUsing strategy: Default[poll] Last Built Revision: Revision 742f5171deb7fcb7a80d00174003f5ffb9b1e396 (refs/remotes/origin/release_team1) > /usr/local/bin/git --version # timeout=10 > /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git # timeout=10Done. Took 1.6 secNo changes{code}Now in the second instance there were changes and the job was imported from our old instance. We are not sure why the job is never fired off. The output "refs/remotes..." is different between the old job and the new one and not sure if that might be the issue or not.We have tried tweaking the branch specifier to various things but nothing seems to work.If I run the ls-remote by hand the output shows the sha1 changed:{code}-bash-4.1$ /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git |grep release_teamfff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Change By: Peter Kline (18/Mar/15 7:52 PM) Summary: kicking off of build via curl command not working in 2 1 . 2 16.1 version of 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] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 2.2 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Just as a note, the branch specifier for both the old and new instance is: remotes/origin/release_team1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27492) Permission deprecation warning in authorization context
Nicholas Russell
updated JENKINS-27492
Permission deprecation warning in authorization context
Change By:
Nicholas Russell
(18/Mar/15 7:42 PM)
Description:
When iterating over a collection with .each, the permission method seems to call the deprecated job permission method with logs a warning (Warning: permission is deprecated){code
:groovy
}def builderNames = ['john', 'jill', 'bob']freeStyleJob('jobName') {// authorization {builderNames.each {permission(Permissions.ItemBuild, it)}}// }{code}However, something like this works and does not log the warning:{code
:groovy
}def builderNames = ['john', 'jill', 'bob']freeStyleJob('jobName') {// authorization {for (builderName in builderNames) {permission(Permissions.ItemBuild, builderName)}}// }{code}This seems to be related to https://issues.jenkins-ci.org/browse/JENKINS-27321 but I've updated the description of this issue to specify that it only seems to be happening in .each (though I haven't tried other methods that take Closures as arguments)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-27492) Permission deprecation warning in authorization context
Nicholas Russell
created JENKINS-27492
Permission deprecation warning in authorization context
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
18/Mar/15 7:40 PM
Description:
When iterating over a collection with .each, the permission method seems to call the deprecated job permission method with logs a warning (Warning: permission is deprecated)
Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javadef builderNames = ['john', 'jill', 'bob']
freeStyleJob('jobName') {
//
authorization {
builderNames.each {
permission(Permissions.ItemBuild, it)
}
}
//
}
However, something like this works and does not log the warning:
Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, javadef builderNames = ['john', 'jill', 'bob']
freeStyleJob('jobName') {
//
authorization {
for (builderName in builderNames) {
permission(Permissions.ItemBuild, builderName)
}
}
//
}
This seems to be related to https://issues.jenkins-ci.org/browse/JENKINS-27321 but I've updated the description of this issue to specify that it only seems to be happening in .each (though I haven't tried other methods that take Closures as arguments)
Project:
Jenkins
Priority:
Minor
Reporter:
Nicholas Russell
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-26762) notifyCommit should trigger builds with trailing / defined in SCM URL
Jesse Glick assigned JENKINS-26762 to Unassigned notifyCommit should trigger builds with trailing / defined in SCM URL I am just the default assignee for the component. As a rule, anyone wishing to take over an issue can just self-assign, assuming it is not already “In Progress”. Change By: Jesse Glick (18/Mar/15 7:30 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27458) Serialization error at end of flow not reported properly in build log, only Jenkins log
Jesse Glick commented on JENKINS-27458 Serialization error at end of flow not reported properly in build log, only Jenkins log Marcus Jacobsson It will work so long as SomeClass implements Serializable. Alternately, you can use an instance of SomeClass locally in a method marked @NonCps (in this case it cannot be used across asynchronous steps like node). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-27476) Plugin casue deadlock on Jenkins LTS 1.596.1
Jesse Glick assigned JENKINS-27476 to stephenconnolly Plugin casue deadlock on Jenkins LTS 1.596.1 stephenconnolly these are your changes; any idea? Change By: Jesse Glick (18/Mar/15 7:26 PM) Assignee: Jesse Glick stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 2.2 version of plugin
Peter Kline created JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 18/Mar/15 6:40 PM Description: We are migrating our old Jenkins instance to a new machine so we are moving from Jenkins 1.538 to 1.605. Our Jenkins plugin is moving from 1.5 to the latest release. We have been using a git hook to run the curl command to fire off a polling task for years now without problem. This no longer works. In our older version 1.5 we see the polling output of the job looking like (not the same job so don't take it as it doesn't work in the old one either): Started on Mar 18, 2015 2:25:58 PM Using strategy: Default [poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0) Done. Took 1.1 sec No changes New Instance with git 1.8.0.6 and git client 1.16.1 Started on Mar 18, 2015 2:28:23 PM Using strategy: Default [poll] Last Built Revision: Revision 742f5171deb7fcb7a80d00174003f5ffb9b1e396 (refs/remotes/origin/release_team1) > /usr/local/bin/git --version # timeout=10 > /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git # timeout=10 Done. Took 1.6 sec No changes Now in the second instance there were changes and the job was imported from our old instance. We are not sure why the job is never fired off. The output "refs/remotes..." is different between the old job and the new one and not sure if that might be the issue or not. We have tried tweaking the branch specifier to various things but nothing seems to work. If I run the ls-remote by hand the output shows the sha1 changed: -bash-4.1$ /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git |grep release_team fff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1 Project: Jenkins Priority: Minor Reporter: Peter Kline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 2.2 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Change By: Peter Kline (18/Mar/15 6:41 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns-plugin] (JENKINS-27490) Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns
Daniel Beck commented on JENKINS-27490 Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns This cannot even be implemented, as there's no record which of the checked out URLs were actually configured (and therefore added to SVN_REVISION_xxx environment variables), and which were only pulled in from svn:externals. Also, this request does not account for multiple such locations (which to display? Or all of them?), or mention which builds' should be shown (last successful build? last stable build? last completed build?) The "extra pages" is the main page of the build, usually one click away. And for rarely compiled reports, it's a sensible approach to write a script to extract that information from Jenkins. Could even be done via the JSON/XML API if the relevant data is exposed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27188) BUILDID and BUILD_TAG from previous project
Daniel Beck commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project If you prefer another issue for this behavior, I can raise a new one. Yes please. Unless the environment variables mentioned in the original report are still broken for you, it's a different (but possibly related) 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] [extra-columns-plugin] (JENKINS-27490) Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns
Richard Spooner created JENKINS-27490 Extra-columns plug-in: Request for SVN_REVISION and SVN_URL columns Issue Type: Improvement Assignee: Fred G Components: extra-columns-plugin Created: 18/Mar/15 5:48 PM Description: Please provide the ability to include the SVN_REVISION and SVN_URL values in the list of available columns. I have to compile reports which include build numbers and svn information. I have to navigate to extra pages to retrieve the svn information. Being able to see the information I need in a single page - the Views utilizing Extra-Columns - would be a great time-saver. Thanks for your consideration. Environment: Jenkins 1.554, Extra-Columns plugin v1.15 Project: Jenkins Priority: Minor Reporter: Richard Spooner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27472) Exception on default view and other list views
Daniel Beck commented on JENKINS-27472 Exception on default view and other list views Weird, the stack trace looks like it's missing something. Still, please try to determine which plugin / which configuration causes this. Check the Jenkins log, or Manage Old Data for clues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27483) Repository URL containg double points couldn't be resolved correctly.
Daniel Beck commented on JENKINS-27483 Repository URL containg double points couldn't be resolved correctly. It is not clear what the problem is... the third slash? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27489) Allow GIT Publisher to work with Clone Workspace
Peter lai created JENKINS-27489 Allow GIT Publisher to work with Clone Workspace Issue Type: New Feature Assignee: Nicolas De Loof Components: git-plugin Created: 18/Mar/15 5:18 PM Description: When using Jenkins clone workspace, we can copy the .git repository information. So in scenarios like, where one jobs does the build and another does the deploy later on, we may choose to tag the source code only after it's been deployed. And if we're using Clone workspace to copy the artefacts over to the deploy job, we can't currently use GIT publisher to create tags etc. even though the .git repository is there. https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitPublisher.java# Line 467 } Can we have the option to do use GitPublisher, if it detects the workspace contains a .GIT repo, and then the option to select the Credential to use appears. Project: Jenkins Priority: Minor Reporter: Peter lai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found
Dylan Canfield created JENKINS-27488 gss.conf file not found Issue Type: Bug Assignee: kutzi Attachments: debug Components: jabber-plugin Created: 18/Mar/15 5:07 PM Description: GSSAPI authentication is failing when trying to connect to my OpenFire server. It looks like an uncaught exception is preventing PLAIN authentication from being attempted. Attached is the debug output that I have collected from hudson.plugins.jabber logging. I would configure a gss.conf file, however, I have had no luck finding any useful or complete documentation about what needs to be included in this file and/or where it should be placed (do additional java options needto be passed to the Jenkins process?). Thank you, in advance, for your assistance. Environment: Jenkins 1.605 Java OpenJDK 1.7.0_75 jabber-plugin 1.34 Project: Jenkins Priority: Major Reporter: Dylan Canfield This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildgraph-view-plugin] (JENKINS-27487) If first child build is in progress then no build graph is seen at all
Vassil Keremidchiev created JENKINS-27487 If first child build is in progress then no build graph is seen at all Issue Type: Improvement Assignee: Unassigned Components: buildgraph-view-plugin Created: 18/Mar/15 5:05 PM Description: 1. Run a job that spawns another one 2. Open build graph of parent job You'll see blank screen during child job is still in progress. It will be great if I could see in-progress jobs, too. Project: Jenkins Priority: Major Reporter: Vassil Keremidchiev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
SCM/JIRA link daemon commented on JENKINS-25666 Wrong view for build pipeline plugin Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/399fa3afb6ff3a3488e6d98f728a23e3dd96f467 Log: Merge pull request #71 from KostyaSha/fixLayout [FIXED JENKINS-25666] Adopt for new jenkins core UI Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/ff490cb5ed1c...399fa3afb6ff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
SCM/JIRA link daemon commented on JENKINS-25666 Wrong view for build pipeline plugin Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/565c4e84c9a4771e35f7bb4a0c26de11f6f87a01 Log: [FIXED JENKINS-25666] Adopt for new jenkins core UI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
SCM/JIRA link daemon resolved JENKINS-25666 as Fixed Wrong view for build pipeline plugin Change By: SCM/JIRA link daemon (18/Mar/15 4:53 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] [workflow-plugin] (JENKINS-27486) Workflow step to mask console output
Kohsuke Kawaguchi
created JENKINS-27486
Workflow step to mask console output
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
18/Mar/15 4:41 PM
Description:
We want to have a block statement that allows sensitive tokens to be masked from the console output inside the body, such as:
maskPassword("s3cr3t!") {
echo "Hello s3cr3t!" // this should produce "Hello ***" or something
}
The exact syntax can be anything, but the above one would prove the concept that this can be done in a composable manner.
Project:
Jenkins
Priority:
Major
Reporter:
Kohsuke Kawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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
Rasmus Pedersen reopened JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Change By: Rasmus Pedersen (18/Mar/15 4:16 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Rasmus Pedersen commented on JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 I've reopened the issue because the workaround doesn't work in all cases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobrequeue-plugin] (JENKINS-27485) define license for 'jobrequeue-plugin'
Ray Kivisto created JENKINS-27485 define license for 'jobrequeue-plugin' Issue Type: Improvement Assignee: Unassigned Components: jobrequeue-plugin Created: 18/Mar/15 3:59 PM Description: The pom.xml does not define the tag. A clear declaration of the license of this plugin would help me use it at my job. An example of a plugin that defines the license is: https://github.com/jenkinsci/email-ext-plugin/blob/master/pom.xml Project: Jenkins Priority: Minor Reporter: Ray Kivisto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27484) Collapsing steps and parameters in Jenkins configuration
Maciej Jaros
updated JENKINS-27484
Collapsing steps and parameters in Jenkins configuration
Change By:
Maciej Jaros
(18/Mar/15 3:45 PM)
Description:
One of main issues with Jenkins is editing configuration. It's just not readable because it's too long. You cannot get a glimpse at a job and say what steps are made within it, what are its parameters and so on.The idea is to collapse all those steps and parameters into something that will allow you to glimpse over configuration and still be able to change order of steps or add more steps.I'm attaching a working proof-of-concept that can collapse all parameters and steps and adds abstracted information to some of them. Obviously it needs work to support more step types (and maybe some exotic parameter types). Some extension points might be added to {{getCollapser}} for plugins - e.g. a simple {{addCollapser}} function that takes two functions {{isMine(container)}} and {{collapser(rows, container)}}. Extension point already explained in {{getCollapser}} function.Some ideas for specific collapsing behavior: * Parameters - collapse to name (done in POC). * Execute shell - inline display of command with lines separated with {{;}} (done in POC) -- might be user-configured to choose lines separator or number of lines to show.
* Execute Windows batch... - as above.* Copy artifacts... - collapse to project name.* Invoke top-level... - goals.* SSH - server name, number of transfer sets.* Archive... - files to archive
filed
field
.* Build other... - projects.* Jenkins Text Finder - filesIf someone is willing to integrate this with Jenkins core I would be glad to work on everything else :-). I see this as a bunch of _javascript_ functions in a class that implements collapsers and another class that handles user actions like collapse all, collapse step (and their un-collapse counterpart and/or toggle functions). I'm guessing most other work is adding buttons for those functions to jelly templates.Just to clarify - I'm not using the latest Jenkins version so the POC might not be working with the latest version. It would probably need minor tweaks 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] [core] (JENKINS-27484) Collapsing steps and parameters in Jenkins configuration
Maciej Jaros created JENKINS-27484 Collapsing steps and parameters in Jenkins configuration Issue Type: New Feature Assignee: Unassigned Attachments: jenkins-collapser.js Components: core Created: 18/Mar/15 3:42 PM Description: One of main issues with Jenkins is editing configuration. It's just not readable because it's too long. You cannot get a glimpse at a job and say what steps are made within it, what are its parameters and so on. The idea is to collapse all those steps and parameters into something that will allow you to glimpse over configuration and still be able to change order of steps or add more steps. I'm attaching a working proof-of-concept that can collapse all parameters and steps and adds abstracted information to some of them. Obviously it needs work to support more step types (and maybe some exotic parameter types). Some extension points might be added to getCollapser for plugins - e.g. a simple addCollapser function that takes two functions isMine(container) and collapser(rows, container). Extension point already explained in getCollapser function. Some ideas for specific collapsing behavior: Parameters - collapse to name (done in POC). Execute shell - inline display of command with lines separated with ; (done in POC) – might be user-configured to choose lines separator or number of lines to show. Execute Windows batch... - as above. Copy artifacts... - collapse to project name. Invoke top-level... - goals. SSH - server name, number of transfer sets. Archive... - files to archive filed. Build other... - projects. Jenkins Text Finder - files If someone is willing to integrate this with Jenkins core I would be glad to work on everything else . I see this as a bunch of _javascript_ functions in a class that implements collapsers and another class that handles user actions like collapse all, collapse step (and their un-collapse counterpart and/or toggle functions). I'm guessing most other work is adding buttons for those functions to jelly templates. Just to clarify - I'm not using the latest Jenkins version so the POC might not be working with the latest version. It would probably need minor tweaks though. Project: Jenkins Labels: user-experience Priority: Major Reporter: Maciej Jaros This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-24355) Unable to claim builds using the build-flow plugin [bis]
Mattias Persson commented on JENKINS-24355 Unable to claim builds using the build-flow plugin [bis] We were able to solve this by checking the "Build needs workspace" - checkbox. That way the buildflow is created as a AbstractRunner instead of RunExecution (we checked the code). Claim-plugin works if buildflow is AbstractRunner, but this is deprecated. We even tried to revert from RunExecution to ActractRunner, and then all jobs works with the claim-plugin. Not sure if Claim-plugin should be changed or the BuildFlow update to be visible for the Claim-plugin. class FlowRun protected class FlyweightTaskRunnerImpl extends RunExecution //Not working with claim protected class BuildWithWorkspaceRunnerImpl extends AbstractRunner //Works with claim, this is used when "Build needs workspace" is checked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection
Paul Sokolovsky commented on JENKINS-27093 Spurious gits scm poll change detection Kevin Normoyle: Thanks for this survey and cross-referencing other issues. Just for information, our job, for which this issue was originally reported (https://ci.linaro.org/job/trigger-linux-ltsi), doesn't have branch parametrized, it is set statically in the job config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-client-plugin] (JENKINS-27483) Repository URL containg double points couldn't be resolved correctly.
Michael Hauf created JENKINS-27483 Repository URL containg double points couldn't be resolved correctly. Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin, git-plugin Created: 18/Mar/15 3:12 PM Description: I have to reach my Repository with the following Repository URL: ssh://g...@github.com:/github/git.git But the URL ends up like this in the Joblog: Fetching upstream changes from ssh:///g...@github.com:/github/git.git and the Repository is not reachable via this URL... The only workaround is to use the short notation for ssh protocol: g...@github.com:/github/git.git Seems like the double point is escaped or something? Environment: Jenkins ver. 1.580.3 git client plugin: 1.16.1 git plugin: 2.3.5 Project: Jenkins Priority: Major Reporter: Michael Hauf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-26876) Option to mark a phase/job as non-blocking/asynchron
lx last commented on JENKINS-26876 Option to mark a phase/job as non-blocking/asynchron @ Mathieu Cantin added a comment - 18/Mar/15 2:46 PM I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59 Hi and thanks for this info. Unfortunately i don't see the solution in that. I do not want the throttle a job respectively to another job in the same phase, i want a surrounding multi-job to be able to finish although a job in the pipeline is still running. Important is, that this job should be shown in the pipeline. If not, it could just be realized with a "trigger build on other project". regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27188) BUILDID and BUILD_TAG from previous project
Krzysztof Malinowski commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project Actually it's rather JENKINS-27197 which was duplicated to this issue. Moreover, you asked if it is still visible, so I reported. If you prefer another issue for this behavior, I can raise a new one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27392) API to decorate console output
Tom FENNELLY edited a comment on JENKINS-27392 API to decorate console output Just stashing something I experimented with for this last week (before this JIRA was created). Not based on TaskListener, but instead filtering the logs inside a block based on an Action. We'll more than likely throw this away but just wanted to attach in case. https://github.com/tfennelly/workflow-plugin/tree/mask-log-entries (link to the branch - press "Compare" etc if you want) (totally incomplete and only kinda works) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27392) API to decorate console output
Tom FENNELLY edited a comment on JENKINS-27392 API to decorate console output Just stashing something I experimented with for this last week (before this JIRA was created). Not based on TaskListener, but instead filtering the logs inside a block based on an Action. We'll more than likely throw this away but just wanted to attach in case. https://github.com/tfennelly/workflow-plugin/tree/mask-log-entries (link to the branch - press "Compare" etc if you want) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27392) API to decorate console output
Tom FENNELLY commented on JENKINS-27392 API to decorate console output Just stashing something I experimented with for this last week (before this JIRA was created). Not based on TaskListener, but instead filtering the logs inside a block. We'll more than likely throw this away but just wanted to attach in case. https://github.com/tfennelly/workflow-plugin/tree/mask-log-entries (link to the branch - press "Compare" etc if you want) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-26876) Option to mark a phase/job as non-blocking/asynchron
Mathieu Cantin commented on JENKINS-26876 Option to mark a phase/job as non-blocking/asynchron I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-27482) CVS changes returning duplicate entries
Gerson Carlos created JENKINS-27482 CVS changes returning duplicate entries Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 18/Mar/15 2:23 PM Description: Using CVS plugin to get the nightly changes of my project is returning duplicate entries. It looks like it might be breaking the commit in smaller bunches of changes. I don't think that it is the correct behaviour, as the changes should return just one commit at time. For example, the changes page of my project is returning: Changes #75 (Mar 18, 2015 6:08:51 AM) Big commit - gerson23 Big commit - gerson23 Big commit - gerson23 Big commit - gerson23 Big commit - gerson23 Big commit - gerson23 Big commit - gerson23 Although I have just one commit called Big commit, the page shows some, and each one has a different bunch of the files originally changed. Environment: Jenkins v1.602 CVS Plug-in 2.12 Project: Jenkins Labels: cvs Priority: Major Reporter: Gerson Carlos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-27438) Gerrit Trigger NPE causes folder not to load
rsandell commented on JENKINS-27438 Gerrit Trigger NPE causes folder not to load Have you tried with the latest 2.13.0-beta-x release? The implementation of the start has changed in that version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27188) BUILDID and BUILD_TAG from previous project
Daniel Beck commented on JENKINS-27188 BUILDID and BUILD_TAG from previous project Krzysztof Malinowski Please file a new issue and provide as much detail has you can. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+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.
