带指示灯和自动监测多重电路保护电路断路器装置 6m7r7
“高级知识产权管理师”岗位能力认证 正式文件 点此下载 报名对象： 企业知识产权管理人员、法务顾问、中高层管理人员；科技型企事业单位负责人；专利工程师、分析师；各企业总裁、总经理；资产评估机构相关人员; 知识产权及专利代理机构专业人士；大专院校、科研院所从事知识产权教研的学术人员；会计师、审计师、事务所会计师、审计师；律师事务所律师等。 报名条件： 1.硕士学历以上，从事相关工作的人员； 2.本科学历以上，有一年以上从事相关工作经验者； 3.大专学历以上，有二年以上从事相关工作经验者。 报名材料： 身份证、学历证明、职称证、相关工作证明原件、4张两寸彩色照片、考生登记表等 详见正式文件。 颁发证书： 培训结束组织考试，成绩合格者，由人力资源和社会保障部教育培训中心颁发“高级知识产权管理师”岗位能力培训证书（全国通用），本证书可作为人力资源管理部门或用人单位对持证人任用、考核、聘用和能力评价的重要依据。 时间： 6月6日全天报到，7、8、9、10 四天培训，10日下午考试（考试没通过者，下期免费补考）。 地点：北京 文件下载地址： 点此下载 ,若不能下载 请发邮件至 507676...@qq.com,给您重新发送；此邮件请勿直接回复。 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-17545) A new default include creates unwanted commits (without config changes).
Frédéric Camblor commented on JENKINS-17545 A new default include creates unwanted commits (without config changes). Wow that's weird ! Thanks Mathieu for pointing this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17867) Allow manual builds of different branches
Alex Vesely updated JENKINS-17867 Allow manual builds of different branches Change By: Alex Vesely (06/May/13 8:13 AM) Description: I have a Jenkins job that performs polling of an SVN trunk and launches a complex chain of jobs if the trunk was updated.What I'd like to do is to give users the ability to launch the job manually, specifying a different branch to checkout - e.g., to test the code in a branch before merging it to the trunk. Currently, I can do the following:- Set the Repository URL to https://svn/$BRANCH- Set the default value of parameter BRANCH to trunk/xyz - Let users type in the branch , OR use the List Subversion Tags optionHowever, this does not work as expected -- or maybe I have misinterpreted the behavior, in which case please correct me.The way I understand it, such configuration works like this:0) I set up the job as described above1) The job is polling the trunk, since this is the default value of the parameter2) I launch the job manually, choosing a different branch to checkout. It runs successfully3) After that, the job begins to poll the branch instead of the trunk. This is absolutely not what I expect it to do -- manual launches should not interfere with future automatic polling. I understand this is the way Jenkins works with parameters, so I am filing this as a feature request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17867) Allow manual builds of different branches
Alex Vesely created JENKINS-17867 Allow manual builds of different branches Issue Type: New Feature Assignee: Unassigned Components: subversion Created: 06/May/13 8:12 AM Description: I have a Jenkins job that performs polling of an SVN trunk and launches a complex chain of jobs if the trunk was updated. What I'd like to do is to give users the ability to launch the job manually, specifying a different branch to checkout - e.g., to test the code in a branch before merging it to the trunk. Currently, I can do the following: Set the Repository URL to https://svn/$BRANCH Set the default value of parameter BRANCH to trunk/xyz, OR use the List Subversion Tags option However, this does not work as expected – or maybe I have misinterpreted the behavior, in which case please correct me. The way I understand it, such configuration works like this: 0) I set up the job as described above 1) The job is polling the trunk, since this is the default value of the parameter 2) I launch the job manually, choosing a different branch to checkout. It runs successfully 3) After that, the job begins to poll the branch instead of the trunk. This is absolutely not what I expect it to do – manual launches should not interfere with future automatic polling. I understand this is the way Jenkins works with parameters, so I am filing this as a feature request. Project: Jenkins Labels: branch parameterized Priority: Major Reporter: Alex Vesely This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
redsolo commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Im seeing this problem also after I have upgraded to the latest version of Jenkins, not sure if it was the upgrade of the Jenkins Windows Service or if it was the Jenkins.war that provoked this. OS : Windows Server 2008 R2 Standard Service Pack 1 JDK : Java version 1.6.0_43 Jenkins : 1.518 The service does not respond, it only spams the error log with an exception for each folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17868) In a multi-config project executed on slave nodes test results are not gathered in the general build view
Tom Bujok created JENKINS-17868 In a multi-config project executed on slave nodes test results are not gathered in the general build view Issue Type: Bug Assignee: Unassigned Attachments: build_view.png, ssh_config_build_view.png, ssh_config_test_view.png Components: core Created: 06/May/13 8:48 AM Description: In a multi-config project which is executed on slave nodes test results are not gathered in the main build view (and in the config view). The tests results are visible only if a click on a specific build in a specific configuration. It used to work around 2 months ago - it's a regression. I have a multi config project with 11 configurations that are executed sequentially on a slave node. When I open the build I see the following message: Latest Test Result(no tests) The "Test Result Trend" shows no tests See screenshot: build_view.png When I click on one of the configurations, for example ssh=dev (from the screenshot), I don't see any tests either: Latest Test Result(no tests) The "Test Result Trend" shows no tests See screenshot: ssh_config_build_view.png Then while in the build view of one of the configurations, when I click on the "Latest Test Result" I see the tests results… See screenshot: ssh_config_test_view.png I can easily retest it if you provide a patch, etc. Thanks! Environment: java -version: java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) uname -a: Linux 2.6.32-5-amd64 #1 SMP Mon Feb 25 00:26:11 UTC 2013 x86_64 GNU/Linux jenkins: - version: 1.514 - running as a war on tomcat6 Project: Jenkins Labels: jenkins regression Priority: Critical Reporter: Tom Bujok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
redsolo edited a comment on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" Im seeing this problem also after I have upgraded to the latest version of Jenkins, not sure if it was the upgrade of the Jenkins Windows Service or if it was the Jenkins.war that provoked this. Downgraded to 1.510 and it did not help OS : Windows Server 2008 R2 Standard Service Pack 1 JDK : Java version 1.6.0_43 Jenkins : 1.518 The service does not respond, it only spams the error log with an exception for each folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
evernat commented on JENKINS-10468 Build Queue does not show the executor a build is waiting for Is it reproduced with a recent Jenkins 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/groups/opt_out.
[JIRA] [accurev] (JENKINS-17869) java.lang.NullPointerException after upgrade from 1.504 to 1.510
A J created JENKINS-17869 java.lang.NullPointerException after upgrade from 1.504 to 1.510 Issue Type: Bug Assignee: Scott Tatum Components: accurev Created: 06/May/13 9:59 AM Description: We upgrade from 1.504 to 1.510 and can no longer login. The default URL gives us: java.lang.NullPointerException at com.thoughtworks.xstream.converters.ConversionException.add(ConversionException.java:65) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1066) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at hudson.XmlFile.unmarshal(XmlFile.java:166) at hudson.Plugin.load(Plugin.java:239) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.(Jenkins.java:850) at hudson.model.Hudson.(Hudson.java:81) at hudson.model.Hudson.(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Project: Jenkins Priority: Critical Reporter: A J This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17868) In a multi-config project executed on slave nodes test results are not gathered in the general build view
Tom Bujok commented on JENKINS-17868 In a multi-config project executed on slave nodes test results are not gathered in the general build view BTW. I am willing to contribute or submit a patch if you guide me a bit where to look... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Peter Lamberg commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. Any word on official fix for this? Alexander Fischers github versions worked for us. Perhaps the support for older versions of Jenkins / Hudson could/should be sacrificed? Thank You! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave
Tom Bujok commented on JENKINS-15796 NoClassDefFoundError in monitoring Windows slave Getting the same error on: jenkins: version: 1.514 running as a war on tomcat6 java -version: java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) uname -a: Linux 2.6.32-5-amd64 #1 SMP Mon Feb 25 00:26:11 UTC 2013 x86_64 GNU/Linux Pretty often, because of that it's impossible to access slave nodes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave
Tom Bujok edited a comment on JENKINS-15796 NoClassDefFoundError in monitoring Windows slave Getting the same error on: jenkins: version: 1.514 running as a war on tomcat6 java -version: java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) uname -a: Linux 2.6.32-5-amd64 #1 SMP Mon Feb 25 00:26:11 UTC 2013 x86_64 GNU/Linux Pretty often, because of that it's impossible to access slave nodes since the reconnect attempt takes ages: May 6, 2013 1:36:28 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect slave_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/groups/opt_out.
[JIRA] [core] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave
Tom Bujok commented on JENKINS-15796 NoClassDefFoundError in monitoring Windows slave I have just checked: This exception may be connected to this bug: May 6, 2013 1:56:30 PM org.apache.jk.common.ChannelSocket processConnection WARNING: processCallbacks status 2 May 6, 2013 1:56:30 PM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception ClientAbortException: java.net.SocketException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:369) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:448) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:318) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:274) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:149) at org.kohsuke.stapler.compression.FilterServletOutputStream.close(FilterServletOutputStream.java:36) at java.io.FilterOutputStream.close(FilterOutputStream.java:143) at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:301) at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:130) at java.io.OutputStreamWriter.close(OutputStreamWriter.java:216) at java.io.BufferedWriter.close(BufferedWriter.java:248) at org.dom4j.io.XMLWriter.close(XMLWriter.java:286) at org.kohsuke.stapler.jelly.HTMLWriterOutput.close(HTMLWriterOutput.java:70) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:56) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) 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:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) 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
[JIRA] [core] (JENKINS-17870) From version 1.512 Url Links in Modules View have lost Job Name
Carlos Nieto created JENKINS-17870 From version 1.512 Url Links in Modules View have lost Job Name Issue Type: Bug Assignee: Unassigned Components: core Created: 06/May/13 12:09 PM Description: Url Links in modules view in a Maven project lost the project name. I observed this lost from version 1.512 and higger. The observed link is http(s)://SERVER/job/CLASS_ID$MODULE_NAME/ This url returns a 404 Error. Correct url link is http(s)://SERVER/job/JOB_NAME/CLASS_ID$MODULE_NAME/ As a workaround you can access this url directly. Due Date: 06/May/13 12:00 AM Project: Jenkins Priority: Major Reporter: Carlos Nieto This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17799) Future obj not observed when same job executed parallel
Sascha Vet updated JENKINS-17799 Future obj not observed when same job executed parallel Change By: Sascha Vet (06/May/13 12:37 PM) Summary: Parallel executed job doesn't stop processing Future obj not observed when failed same job executed parallel Assignee: Sascha Vet Description: Two sub-jobs S1 and S2 calling the same job A within seconds . Internally multijob Jenkins starts the job A only once (by the way a great behavior , very helpful because of the "Quiet period". For the second call Jenkins returns null for the future element (see docu for Queue::schedule: "return null if this task is already in my use case the queue" ). Because of the empty future obj Multijob ignores the status of the job and caused issues.One example: Job A fails and S1 stops with the status FAILED. But in sub-job S2 job A gets the status PENDING and the workflow continues whether job A fails or not.Workflow sketch:MainJob- Subjob S1-- Step 1--- Job A -> fails, subjob s2 stops and result is failed-- Step 2--- Job B -> not executed (expected)- Subjob S2-- Step 1--- Job A -> status pending and result ignored . After failing -> execution goes on -- Step 2--- Job C -> executed (BUG!) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17799) Future obj not observed when same job executed parallel
Sascha Vet updated JENKINS-17799 Future obj not observed when same job executed parallel Change By: Sascha Vet (06/May/13 12:38 PM) Description: Two sub-jobs S1 and S2 calling the same job A within seconds. Internally Jenkins starts the job A only once, because of the "Quiet period". For the second call Jenkins returns null for the future element (see docu manual for Queue::schedule: "return null if this task is already in the queue").Because of the empty future obj Multijob ignores the status of the job and caused causes issues.One example:Job A fails and S1 stops with the status FAILED. But in sub-job S2 job A gets the status PENDING and the workflow continues whether job A fails or not.Workflow sketch:MainJob- Subjob S1-- Step 1--- Job A -> fails, subjob s2 stops and result is failed-- Step 2--- Job B -> not executed (expected)- Subjob S2-- Step 1--- Job A -> status pending and result ignored.-- Step 2--- Job C -> executed (BUG!) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17774) Testing plugin in Windows fails with requested operation can't be performed on file with user-mapped section open
ikedam commented on JENKINS-17774 Testing plugin in Windows fails with requested operation can't be performed on file with user-mapped section open I wrote a patch for Jenkins in https://github.com/ikedam/jenkins/tree/feature/JENKINS-17774. I wrote a plugin to reproduce JENKINS-17774 in https://github.com/ikedam/reproduce-jenkins-17774. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17834) NPE on checkMergeable
Honza Brázdil commented on JENKINS-17834 NPE on checkMergeable Yes the version is 1.8. I don't know how to fill the "Fix Version" field, it says "no such 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/groups/opt_out.
[JIRA] [ghprb] (JENKINS-16921) Missing scheme from github API URL
Honza Brázdil closed JENKINS-16921 as Fixed Missing scheme from github API URL Change By: Honza Brázdil (06/May/13 12:42 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-16286) NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase
Honza Brázdil closed JENKINS-16286 as Fixed NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase Change By: Honza Brázdil (06/May/13 12:43 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-16305) Add support for Quiet period configuration slicing
Markus updated JENKINS-16305 Add support for Quiet period configuration slicing Change By: Markus (06/May/13 12:43 PM) Description: It would be great if thus the plugin could support slicing the Quiet period configuration item.Thanks for a great plugin! Use it all the 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/groups/opt_out.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Julien Carsique commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Having the same issue, reproduced at every build for a given slave (with nothing relevant in its logs), I tried to disconnect and reconnect the slave: [05/06/13 14:06:04] Launching slave agent $ ssh slavedns java -jar ~/bin/slave.jar <===[JENKINS REMOTING CAPACITY]===<===[JENKINS REMOTING CAPACITY]===>>channel started channel started Slave.jar version: 2.22 This is a Unix slave Slave.jar version: 2.22 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-agent.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied classworlds.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Evacuated stdout ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.IllegalStateException: Already connected at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:459) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Connection terminated channel stopped ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.NullPointerException at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:32) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:471) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) channel stopped Connection terminated Then the slaved successfully reconnected itself. It appeared there was looping thread consuming 100% CPU. Killing the process solved the issue. Strangely, some system and Java commands were not working (ps, cat, less, jstack, trace, ...) until it has been killed, whereas other commands worked (top, jps, renice, kill, ...). That could explain the weird Jenkins 4s timeout log (java.util.concurrent.TimeoutException: Ping started on 1367743028681 hasn't completed at 1367743268682): the system was partially frozen and with really unstable response times. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Julien Carsique edited a comment on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Maybe not a Jenkins issue. Having the same issue, reproduced at every build for a given slave (but with nothing relevant in its logs), I tried to disconnect and reconnect the slave: [05/06/13 14:06:04] Launching slave agent $ ssh slavedns java -jar ~/bin/slave.jar <===[JENKINS REMOTING CAPACITY]===<===[JENKINS REMOTING CAPACITY]===>>channel started channel started Slave.jar version: 2.22 This is a Unix slave Slave.jar version: 2.22 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-agent.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied classworlds.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Evacuated stdout ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.IllegalStateException: Already connected at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:459) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Connection terminated channel stopped ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.NullPointerException at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:32) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:471) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) channel stopped Connection terminated Then the slaved successfully reconnected itself. It appeared there was looping thread consuming 100% CPU. Killing the process solved the issue. Strangely, some system and Java commands were not working (ps, cat, less, jstack, trace, ...) until it has been killed, whereas other commands worked (top, jps, renice, kill, ...). That could explain the weird Jenkins 4s timeout log (java.util.concurrent.TimeoutException: Ping started on 1367743028681 hasn't completed at 1367743268682): the system was partially frozen and with really unstable response times. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17797) x-unit option not to fail if there isn't a test results file
Per Arnold Blaasmo commented on JENKINS-17797 x-unit option not to fail if there isn't a test results file I get this message after upgrading this plugin to version 1.55: ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.dtkit.metrics.hudson.api.type.MetricsType.isSkipNoTestFiles(MetricsType.java:80) at org.jenkinsci.plugins.xunit.XUnitPublisher.getXUnitToolInfoObject(XUnitPublisher.java:191) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:169) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:116) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) After going into the project config and save it it works. So maybe there are some need to save config on all projects that uses this 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/groups/opt_out.
[JIRA] [gradle] (JENKINS-17871) Gradle Plugin: Problems with Newlines in -P parameter
Oliver Drobnik created JENKINS-17871 Gradle Plugin: Problems with Newlines in -P parameter Issue Type: Bug Assignee: Gregory Boissinot Components: gradle Created: 06/May/13 1:11 PM Description: We have a test field to enter a change long for building with Jenkins + Gradle Plugin. If our CHANGELOG text parameter contains newlines then this causes the build to fail: [AutoIngest (Release)] $ /bin/sh -xe /var/folders/p5/v9glzkn926l0t4ccjrxr2ysmgq/T/hudson8002412059339489964.sh + /Users/groundskeeper/Jenkins/tools/hudson.plugins.gradle.GradleInstallation/Gradle_1.4/bin/gradle sparkle-notes sparkleZip '-DCHANGELOG=multiple lines bla bla' '-Pxcodebuild.signing.identity=Developer ID Application: Drobnik KG' -Pxcodebuild.signing.certificateURI=http://homer/Jenkins/Provisioning/Cocoanetics/Drobnik_KG_Developer_ID.p12 -Pxcodebuild.signing.certificatePassword=magic123 -Pinfoplist.version=47 -Psparkle.output=sparkle/com.cocoanetics.AutoIngest/47 added cleanup for certificate FAILURE: Could not determine which tasks to execute. What went wrong: Task '-DCHANGELOG=multiple lines bla bla' not found in root project 'AutoIngest (Release)'. Try: Run gradle tasks to get a list of available tasks. BUILD FAILED Project: Jenkins Priority: Major Reporter: Oliver Drobnik This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gradle] (JENKINS-17871) Gradle Plugin: Problems with Newlines in -P parameter
Oliver Drobnik updated JENKINS-17871 Gradle Plugin: Problems with Newlines in -P parameter Change By: Oliver Drobnik (06/May/13 1:12 PM) Description: We have a test field to enter a change long for building with Jenkins + Gradle Plugin.If our CHANGELOG text parameter contains newlines then this causes the build to fail:[AutoIngest (Release)] $ /bin/sh -xe /var/folders/p5/v9glzkn926l0t4ccjrxr2ysmgq/T/hudson8002412059339489964.sh+ /Users/groundskeeper/Jenkins/tools/hudson.plugins.gradle.GradleInstallation/Gradle_1.4/bin/gradle sparkle-notes sparkleZip '-DCHANGELOG=multiplelines- bla- bla' '-Pxcodebuild.signing.identity=Developer ID Application: Drobnik KG' -Pxcodebuild.signing.certificateURI=http://homer/Jenkins/Provisioning/Cocoanetics/Drobnik_KG_Developer_ID.p12 - Pxcodebuild.signing.certificatePassword=magic123 - Pinfoplist.version=47 -Psparkle.output=sparkle/com.cocoanetics.AutoIngest/47added cleanup for certificateFAILURE: Could not determine which tasks to execute.* What went wrong:Task '-DCHANGELOG=multiplelines- bla- bla' not found in root project 'AutoIngest (Release)'.* Try:Run gradle tasks to get a list of available tasks.BUILD FAILED This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
Julien Carsique edited a comment on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Maybe not a Jenkins issue. Having the same issue, reproduced at every build for a given slave (but with nothing relevant in its logs), I tried to disconnect and reconnect the slave: [05/06/13 14:06:04] Launching slave agent $ ssh slavedns java -jar ~/bin/slave.jar <===[JENKINS REMOTING CAPACITY]===<===[JENKINS REMOTING CAPACITY]===>>channel started channel started Slave.jar version: 2.22 This is a Unix slave Slave.jar version: 2.22 This is a Unix slave Copied maven-agent.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied maven-agent.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied maven3-agent.jar Copied maven3-interceptor.jar Copied classworlds.jar Copied maven-interceptor.jar Copied maven2.1-interceptor.jar Copied plexus-classworld.jar Copied classworlds.jar Evacuated stdout Evacuated stdout ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.IllegalStateException: Already connected at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:459) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Connection terminated channel stopped ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins (...)java.lang.NullPointerException at org.jenkinsci.modules.slave_installer.impl.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:32) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:471) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:339) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) channel stopped Connection terminated Then the slaved successfully reconnected itself. It appeared there was looping thread consuming 100% CPU. Killing the process solved the issue. Strangely, some system and Java commands were not working (ps, cat, less, jstack, trace, ...) until it has been killed, whereas other commands worked (top, jps, renice, kill, ...). That could explain the weird Jenkins 4s timeout log (java.util.concurrent.TimeoutException: Ping started on 1367743028681 hasn't completed at 1367743268682): the system was partially frozen and with really unstable response times. Note the looping thread came from a previous job which badly stopped on timeout: 03:00:16.868 Build timed out (after 180 minutes). Marking the build as aborted. 03:00:16.873 Build was aborted 03:00:16.874 Archiving artifacts 03:00:16.874 ERROR: Failed to archive artifacts: **/log/*.log, tomcat*/nxserver/config/distribution.properties 03:00:16.875 hudson.remoting.ChannelClosedException: channel is already closed 03:00:16.876 at hudson.remoting.Channel.send(Channel.java:494) 03:00:16.876 at hudson.remoting.Request.call(Request.java:129) 03:00:16.876 at hudson.remoting.Channel.call(Channel.java:672) 03:00:16.876 at hudson.EnvVars.getRemote(EnvVars.java:212) 03:00:16.876 at hudson.model.Computer.getEnvironment(Computer.java:882) 03:00:16.876 at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:28) 03:00:16.876 at hudson.model.Run.getEnvironment(Run.java:2028) 03:00:16.876 at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:927) 03:00:16.876 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:115) 03:00:16.876 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 03:00:16.876 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) 03:00:16.876 at hudson.model.Abstra
[JIRA] [gradle] (JENKINS-17871) Gradle Plugin: Problems with Newlines in -P parameter
Oliver Drobnik updated JENKINS-17871 Gradle Plugin: Problems with Newlines in -P parameter Change By: Oliver Drobnik (06/May/13 1:14 PM) Description: We have a test field to enter a change long for building with Jenkins + Gradle Plugin.If our CHANGELOG text parameter contains newlines then this causes the build to fail: [AutoIngest (Release)] $ /bin/sh -xe /var/folders/p5/v9glzkn926l0t4ccjrxr2ysmgq/T/hudson8002412059339489964.sh+ /Users/groundskeeper/Jenkins/tools/hudson.plugins.gradle.GradleInstallation/Gradle_1.4/bin/gradle sparkle-notes sparkleZip '-DCHANGELOG=multiplelines- bla- bla' '-Pxcodebuild.signing.identity=Developer ID Application: Drobnik KG' -Pxcodebuild.signing.certificateURI=http://homer/Jenkins/Provisioning/Cocoanetics/Drobnik_KG_Developer_ID.p12 -Pinfoplist.version=47 -Psparkle.output=sparkle/com.cocoanetics.AutoIngest/47added cleanup for certificate FAILURE: Could not determine which tasks to execute. * What went wrong:Task I wasn ' -DCHANGELOG=multiplelines- bla- bla' not found in root project 'AutoIngest (Release)' t able to post the full output here . * Try:Run But suffice it to say that the newlines cause the gradle tasks or the gradle plugin to get a list of available tasks be unable to parse the other parameters properly . BUILD FAILED This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xtrigger] (JENKINS-17641) Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause
kevin ran commented on JENKINS-17641 Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause BUMP. Hello? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17870) From version 1.512 Url Links in Modules View have lost Job Name
sogabe resolved JENKINS-17870 as Duplicate From version 1.512 Url Links in Modules View have lost Job Name Change By: sogabe (06/May/13 2:39 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Marco Miller created JENKINS-17872 build-pipeline-plugin seems to have lost its ability to show sub-projects Issue Type: Improvement Assignee: Marco Miller Components: build-pipeline Created: 06/May/13 2:52 PM Description: build-pipeline-plugin seems to have lost its ability to show sub-projects (alongside downstream jobs). Note: sub-projects (known as Subprojects in the UI) are brought by the parameterized-trigger plugin. Project: Jenkins Priority: Minor Reporter: Marco Miller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj updated JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Change By: hardwickj (06/May/13 2:57 PM) Priority: Major 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/groups/opt_out.
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
hardwickj commented on JENKINS-14825 winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 We've been seeing this occasionally, and cannot nail it down to a root cause. I've disabled numerous plugins to try and narrow it down, but I'm still unable to find anything that can recreate it consistently. The error seems to result in parts of the web app returning 404. Must be some of the ajax'y portions that make a call out after the initial page load. Unfortunately we also make fairly heavy use of Jenkins API's, and with the API randomly returning a 404 it's severely impacting our workflow. It seems odd to me that the API/UI return a 404 error when in the log we're seeing a straight up exception. I'd expect some sort of 500 error... This is what we see in our logs: May 06, 2013 10:55:13 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/ssd/hudson/war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/summary.jelly:49:48: Failed to write to client at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) ... Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/ssd/hudson/war/WEB-INF/lib/jenkins-core-1.514.jar!/lib/hudson/summary.jelly:49:48: Failed to write to client at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) ... Caused by: winstone.ClientSocketException: Failed to write to client at winstone.ClientOutputStream.write(ClientOutputStream.java:41) ... Caused by: java.net.SocketException: Connection reset at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17713) Maven Module links are now broken - missing Job Name
sogabe assigned JENKINS-17713 to Vincent Latombe Maven Module links are now broken - missing Job Name [1] seems to break maven module links. @Vlatombe Would you like to look into this? [1] https://github.com/jenkinsci/jenkins/commit/d54105c296965f915d2124a3b475de2b8b6efa54 Change By: sogabe (06/May/13 3:48 PM) Assignee: Vincent Latombe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17713) Maven Module links are now broken - missing Job Name
Vincent Latombe commented on JENKINS-17713 Maven Module links are now broken - missing Job Name root cause seems to be a problem in stapler, not returning ancestors relative paths correctly when the url doesn't end with / (like in /modules) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Ken Beal created JENKINS-17873 FSTrigger does not accept Parameters Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: fstrigger Created: 06/May/13 3:58 PM Description: Repro steps: 1. Create a new job, "Test-FSTrigger". 2. Configure a string Parameter "monitor", with value "c:\test". 3. Check the "[FSTrigger] - Monitor files", then click "Add file to monitor" and in the "File Path" text field, enter "$monitor". 4. In the "Schedule" text field, enter "* * * * *" so it will monitor every minute. 5. Save the job, and wait one minute. Then click on the "FSTrigger Files Log" link in the left menu. Expected results: It should have said the folder doesn't exist (and then I would create the folder, wait a minute to see what it said then; then create the file, and wait a minute to see it function). Actual results: It shows an error: "[ERROR] - Polling error The given pattern for the file to monitor must have a directory." Environment: Windows 7 Project: Jenkins Priority: Major Reporter: Ken Beal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Andrew Gallant commented on JENKINS-5552 MSBuild plugin creates malformed command line It is still failing for me. Running msbuild/devenv.com I need to use /build "Release|Win32", "Release|x64", etc and the quotes are still being stripped. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Andrew Gallant edited a comment on JENKINS-5552 MSBuild plugin creates malformed command line It is still failing for me. Running msbuild/devenv.com I need to use /build "Release|Win32", "Release|x64", etc and the quotes are still being stripped. Here's my log output: c:\progra~1\micros~2.0\common7\IDE\devenv.com /build Release|Win32 C:\JENKINS\jobs\5.3W_RCIBuild\workspace\Build_Common.sln && exit %%ERRORLEVEL%% 'Win32' is not recognized as an internal or external command This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17874) Git Plugin Does not allow Passwords to be entered.
C. Alex Reober created JENKINS-17874 Git Plugin Does not allow Passwords to be entered. Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: core, git, git-client Created: 06/May/13 4:33 PM Description: I have set up my git repo to use ssh and LDAP for authentication. CLI git works fine using the accounts in LDAP. When try to pull from the git via Jenkins git plugin or git-client plugin, the deploy fails because the plugins do not allow a password to entered for the LDAP system. Environment: AWS; Jenkins: AWS Linux AMI release 2013.03 Git: Ubuntu 12.04.2 LTS OpenLDAP: openldap-2.4.28 Project: Jenkins Priority: Major Reporter: C. Alex Reober This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xtrigger] (JENKINS-17641) Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause
Gregory Boissinot commented on JENKINS-17641 Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause Sorry for my delay. I'll try to push a new release with all updates plugins and librairies. Please could you give me your plugins list with the versions in your $JENKINS_HOME/plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable I'm encountering the same issue with 1.512. Is the problem a master JVM vs. slave JVM issue, similar to the Groovy Plugin's System Groovy script vs. groovy script difference?... "Groovy Script vs System Groovy Script The plain "Groovy Script" is run in a forked JVM, on the slave where the build is run. It's the basically the same as running the "groovy" command and pass in the script. The system groovy script, OTOH, runs inside the Hudson master's JVM. Thus it will have access to all the internal objects of Hudson, so you can use this to alter the state of Hudson. It is similar to the Jenkins Script Console functionality." https://wiki.jenkins-ci.org/display/JENKINS/Groovy+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/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Jesse Glick commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Fix should be in 1.515. Marked a candidate for backporting to 1.509.2 if that is ever produced. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17864) Mercurial URL in form email:password@host always causes the full clone
Jesse Glick resolved JENKINS-17864 as Not A Defect Mercurial URL in form email:password@host always causes the full clone If the username includes an @ then it must be escaped as %40 in the original URL too. Mercurial may happen to be nice and interpret the incorrect URL but that is a user error. This would probably not work anyway because of JENKINS-16138. Change By: Jesse Glick (06/May/13 5:06 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Alex Earl commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Did you make sure that the Mailer plugin is installed and enabled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Proof that Mailer plugin 1.4 is installed and enabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks updated JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Proof that Mailer plugin 1.4 is installed. Change By: Brian Brooks (06/May/13 5:11 PM) Attachment: mailer_plugin_1.4_is_installed.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Attached screenshot showing proof that Mailer plugin 1.4 is installed and enabled. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Here's what the failure looks like in our environment... Groovy script failed: groovy.lang.MissingPropertyException: No such property: hudson for class: SonarReports at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at SonarReports.sendSuccessMail(SonarReports.groovy:158) at SonarReports$sendSuccessMail.callCurrent(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:153) at SonarReports.doSuccess(SonarReports.groovy:192) at SonarReports$doSuccess.callCurrent(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:153) at SonarReports.run(SonarReports.groovy:224) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:627) at groovy.lang.GroovyShell$evaluate.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at Script1.run(Script1.groovy:4) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:276) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:949) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Alex Earl commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Can you post your groovy script? This looks like a different failure than described in 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/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks updated JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Attaching the SonarReports.groovy script run by the Groovy Post-Build action plugin. Execution of this script fails when line # 158 is executed mailSession = hudson.tasks.Mailer.descriptor().createSession() Change By: Brian Brooks (06/May/13 5:21 PM) Attachment: SonarReports.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Attaching the SonarReports.groovy script run by the Groovy Post-Build action plugin (https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin). Execution of this script fails when line # 158 is executed mailSession = hudson.tasks.Mailer.descriptor().createSession() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Might be related to https://issues.jenkins-ci.org/browse/JENKINS-6068 which is pointed more at Groovy Script vs System Groovy Script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Might be related to JENKINS-6068 which is pointed more at Groovy Script vs System Groovy Script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable Might be similar to JENKINS-6068 which is pointed more at Groovy Script vs System Groovy Script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable A fix might be similar to JENKINS-6068 which is pointed more at Groovy Script vs System Groovy Script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
torarvid commented on JENKINS-5552 MSBuild plugin creates malformed command line @agallant Well, my fix is for the "build variables" that is passed to msbuild and not the whole command line. Not 100% sure where you supply that '/build "Release|Win32"' part of it, but that might be why. I think - according to the description of this issue, that it is correct to set the status to "Resolved", and maybe create a separate issue (that I admit - is very much related). My own itch is scratched, so I'm sorry I don't have more time right now to fix this - But I have a quick fix suggestion for you: Try to pass these options as '/p:Configuration=Release /p:Platform=Win32' instead of using the compound /build flag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable A fix might be similar to the fix applied for the Groovy plugin defect JENKINS-6068. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks edited a comment on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable A fix for this groovy post-build defect might be similar to the fix applied for the Groovy plugin defect JENKINS-6068. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix applied for the Groovy plugin defect JENKINS-6068. At least this defect suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, hudson.model.Hudson.instance.getPluginManager().uberClassLoader)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, hudson.model.Hudson.instance.getPluginManager().uberClassLoader)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154. At least this defect suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, hudson.model.Hudson.instance.getPluginManager().uberClassLoader)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, Class.forName("hudson.tasks.Mailer", true, hudson.getPluginManager().uberClassLoader)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Earl commented on JENKINS-17838 full build log not in content of email Can you view the source of the email? I'm wondering if the content is there, but there are < > in the content which is causing it to be read as HTML. This would explain also why the content you have after is not showing up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, Class.forName("hudson.tasks.Mailer", true, hudson.getPluginManager().uberClassLoader)
Where the hudson identifier in the "hudson.getPluginManager()" part is the variable bound by the groovy post-build action 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/groups/opt_out.
[JIRA] [xcode] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
Raymond Gonzales
commented on JENKINS-12800
Can't add xcodebuild parameters including whitespace
I found a great workaround for building with jenkins.
Firstly, before setting up a job, download a jenkins plugin called:
Parameterized Trigger Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin
Once you do that, create your job and while creating the job, select the
'This build is parameterized' checkbox
Create a String Parameter. I called mine CODE_SIGN_IDENTITY.
So the name field in the String Parameter should be:
--
Name: CODE_SIGN_IDENTITY
Default Value: iPhone Developer: XXX X
Description: Whatever you want to put there
--
Then in your Xcode Plugin, find the 'Custom xcodebuild arguments' field.
In the Custom xcodebuild arguments field, place the following value:
CODE_SIGN_IDENTITY=${CODE_SIGN_IDENTITY}
Finish setting up your job and you should be all set!
This will bypass the white space issue. The plugin is a life saver as it works wonderfully and you can customize your build with other parameters.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [compact-columns] (JENKINS-15601) Main dashboard takes minutes to load in browser
Kevin Phillips commented on JENKINS-15601 Main dashboard takes minutes to load in browser I too have been experiencing similar problems with the Jenkins dashboard. I'm using the latest release as of last week (1.513). The problem seems to arise once a build / job has begun. Navigating the dashboard otherwise seems fine, but when a build kicks in it can take minutes for the dashboard to respond. Even just running a single job with minimal load on the system (e.g.: < 10% CPU usage) the dashboard becomes unusable, even on a high-end development machine (e.g.: Win7 x64, i7 3.4Ghz, 16GB RAM, SSD, etc.) Now I have been unable to find any log files in the Jenkins home folder that include the level of detail others are reporting above. Perhaps I need to increase the verbosity level somewhere in the Jenkins configuration. If anyone could suggest where to look for that I'd 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/groups/opt_out.
[JIRA] [compact-columns] (JENKINS-15601) Main dashboard takes minutes to load in browser
Kevin Phillips commented on JENKINS-15601 Main dashboard takes minutes to load in browser NOTE: Given that several comments earlier in this thread suggest that this problem may be related to one or more plugins not working correctly, I decided to disable all non-essential plugins from my test instance, leaving just one or two key plugins like the one for SVN SCM, and the dashboard seems to become responsive again. This suggests there may be something to this. I'll have to do some further ad-hoc testing to try and isolate this to a particular plugin, but there does seem - at first glance anyway - that there is a relation between the dashboard performance and one or more plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, hudson.getPluginManager().uberClassLoader)
Where the hudson identifier in the "hudson.getPluginManager().uberClassLoader" part is the variable bound by the groovy post-build action 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/groups/opt_out.
[JIRA] [shell-script-scm] (JENKINS-13784) Environment Variables do not replace in shell scripts
Rebecca Grenier
commented on JENKINS-13784
Environment Variables do not replace in shell scripts
I had the same issue where Jenkins environment variables would not replace when surrounded by quotes, but for some reason putting it inside single quotes first worked for me, as in below:
play 'set version:="'${BUILD_ID}'"' 'session save';
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7376) git - clean before build does not clean submodules
Mark Stover commented on JENKINS-7376 git - clean before build does not clean submodules If a submodule exists for a given branch, but not on other branches, git clean -fdx won't clean up the submodule directory. It requires f to be passed twice. Using the clean following clean command will remove git repositories that are not listed as part of a repositories submodules: git clean -ffdx This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
Jesse Glick commented on JENKINS-17676 ADSI mode auth no longer working after update to AD plugin v 1.31 @kohsuke says @ef66cbbb@ is the cause; under investigation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
mirumpf created JENKINS-17875 Make Jenkins environment variables available to dynamic providers Issue Type: Improvement Assignee: Unassigned Components: extensible-choice-parameter Created: 06/May/13 7:17 PM Description: For the dynamic providers (Shell, Groovy) it should be possible to get information about the current job. Example: When triggering a parameterized build job, the System Groovy script, which is executed to collect the choices, should be able to get the name of the current job. With the prefix of the current job we want to find all jobs that have the same prefix and make them available as choices. The job "prefix-admin-create-branch-job" executes a System Groovy script to collect all jobs with the same "prefix". The user selects one of the jobs to copy a job for a new subversion branch. I could not find a way how to get the name during the extensible choice provider execution. Later during the build (Ant, Maven, ...), the environment variable "JOB_NAME" is accessible, but it has not been set when the extensible choice parameter plugin is executed. Jenkins has a longer list of environment variables: https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables Environment variables could not be used for the System Groovy scripts as the script is not forked into a separate process and thus there is no chance to set the variables. For a shell provider this is possible, as the shell script is forked out into a new process anyway. Project: Jenkins Priority: Major Reporter: mirumpf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-17876) MSBuild Command Line Arguments quotes being stripped...not 5552
Andrew Gallant created JENKINS-17876 MSBuild Command Line Arguments quotes being stripped...not 5552 Issue Type: Bug Assignee: kdsweeney Components: msbuild Created: 06/May/13 7:19 PM Description: I've been following JENKINS-5552 and this seems to be a different, but same issue. No matter what I put in the Command Line Arguments section of the "Build a Visual Studio project of solution using MSBuild" the command is parsed and the quotes needed are stripped. Since we have to use devenv.com, I cannot use the /p: command parameters. Attempting to us /build "Release|Win32" results in the quotes being stripped. This only happens when there are no spaces. "Release|Any CPU" appears to get the quotes re-established as the tokenizer recognizes the space. Can we just have this field get passed verbatim? Environment: Windows 7/2008 Project: Jenkins Priority: Blocker Reporter: Andrew Gallant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17877) NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55
Jop van Raaij created JENKINS-17877 NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55 Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 06/May/13 7:35 PM Description: After upgrading from xunit plugin 1.54 to 1.55 I get a NullPointerException processing PHPUnit. Downgrading to 1.54 resolved the problem. [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing PHPUnit-3.x (default) ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.NullPointerException at com.thalesgroup.dtkit.metrics.hudson.api.type.MetricsType.isSkipNoTestFiles(MetricsType.java:80) at org.jenkinsci.plugins.xunit.XUnitPublisher.getXUnitToolInfoObject(XUnitPublisher.java:191) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:169) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:116) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Finished: FAILURE Environment: Linux 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux java version "1.7.0_21" OpenJDK Runtime Environment (IcedTea 2.3.9) (7u21-2.3.9-1ubuntu1) OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) Project: Jenkins Priority: Blocker Reporter: Jop van Raaij This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
SCM/JIRA link daemon commented on JENKINS-17566 Severe polling error when using script trigger Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/service/EnvVarsResolver.java http://jenkins-ci.org/commit/envinject-lib/c6ce1fe1d0f1d00eb55e9c349f591a2c4ef764f6 Log: Fix JENKINS-17566 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17878) HTML test output in tapResults not escaped
Real ONeil
created JENKINS-17878
HTML test output in tapResults not escaped
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Attachments:
Screen Shot 2013-05-06 at 4.30.53 PM.png, Screen Shot 2013-05-06 at 5.01.36 PM.png
Components:
tap
Created:
06/May/13 9:25 PM
Description:
On tapResults page, if the output of a given test contains HTML, it renders it out onto the tapResults report wholesale and unescaped.
If the HTML is partial, it can lead to some output being outside of a result table or missing on render entirely.
To illustrate what I mean, I've included some offending TAP file content and some screenshots of the results(masking applied by me to protect some data).
{/code}
Project:
Jenkins
Labels:
tap
html
reporting
tapResults
Priority:
Major
Reporter:
Real ONeil
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
SCM/JIRA link daemon commented on JENKINS-17566 Severe polling error when using script trigger Code changed in jenkins User: Gregory Boissinot Path: pom.xml http://jenkins-ci.org/commit/scripttrigger-plugin/304d50587c698f157438ae5d497875b17eb4c03e Log: Upgrade to xtrigger-lib 0.23 for JENKINS-17566 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
Gregory Boissinot resolved JENKINS-17566 as Fixed Severe polling error when using script trigger Please test from scripttrigger 0.27 Change By: Gregory Boissinot (06/May/13 9:33 PM) Status: Reopened 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-17877) NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55
SCM/JIRA link daemon commented on JENKINS-17877 NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55 Code changed in jenkins User: Gregory Boissinot Path: pom.xml http://jenkins-ci.org/commit/xunit-plugin/c67a290c938aaea11ad9b5a2a453d13c6a669d66 Log: Upgrade to dtkit-frmk 0.20 and dtkit-default-junit 0.35 for fix JENKINS-17877 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
owenmehegan commented on JENKINS-14475 Conditional build steps should be available as post-build actions Interesting, that might work for us. I'll experiment with it. I still would prefer to have be able to do actual conditional logic, using the Conditional Build Step plugin, in post-build steps. On matrix builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17877) NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55
Gregory Boissinot resolved JENKINS-17877 as Fixed NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55 Change By: Gregory Boissinot (06/May/13 10:28 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
owenmehegan edited a comment on JENKINS-14475 Conditional build steps should be available as post-build actions Interesting, that might work for us. I'll experiment with it. I still would prefer to be able to do actual conditional logic, using the Conditional Build Step plugin, in post-build steps. On matrix builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger Hi, I built the release tag 0.27 from github locally and uploaded the hpi file to jenkins. It seems to work: The node was down and the trigger was able to start it. I will report back if anything else goes wrong. Thank you very much, Uwe P.S.: (I think next time you don't need to build a new release for every change, testing it with a local build from github is perfectly fine to me!) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Fred G assigned JENKINS-10468 to Martin Ba Build Queue does not show the executor a build is waiting for Change By: Fred G (06/May/13 11:34 PM) Assignee: Fred G Martin Ba This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10468) Build Queue does not show the executor a build is waiting for
Fred G commented on JENKINS-10468 Build Queue does not show the executor a build is waiting for The long string of random characters was fixed with pull request https://github.com/jenkinsci/jenkins/pull/467 in Jenkins version 1.467. Not sure about the original issue. Assigning back to the reporter. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17880) Not all files are copied.
Thomas Oswald created JENKINS-17880 Not all files are copied. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 07/May/13 6:27 AM Description: The plugin follows the Ant patterns (http://ant.apache.org/manual/dirtasks.html#patterns) but does not allow me to set the defaultexcludes="no" attribute. I want to copy all my .git* files. Project: Jenkins Priority: Major Reporter: Thomas Oswald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-15542) Show whole Job name in Pipeline View
Ladislav Toldy commented on JENKINS-15542 Show whole Job name in Pipeline View Yeah, I have the same problem and my pipelines are not readable after upgrade. I am thinking about downgrading back because of 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/groups/opt_out.
