[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
David Ehrenberger commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly FYI I downgraded to 1.513 and am still seeing the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17910) groovy.lang.MissingMethodException in sidepanel.jelly
David Ehrenberger commented on JENKINS-17910 groovy.lang.MissingMethodException in sidepanel.jelly Started seeing this after the 1.514 upgrade. A restart resolves the error for a short time, however it comes back shortly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15218) Dependency tree should be constrained to only contain relevant nodes in the path
David Ehrenberger commented on JENKINS-15218 Dependency tree should be constrained to only contain relevant nodes in the path In my organization we have a very wide dependency trees where numerous projects utilize our core library package (i.e., Test.Job.1). When inside the job page of a particular project (i.e., Test.Job.3), I don't care about all of the other jobs (i.e., Test.Job.4) that also happen to utilize Test.Job.1. In my mind, I think it more intuitive that only those jobs that are actually dependencies are shown. Could this be made configurable? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
David Ehrenberger commented on JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs I've restarted our Jenkins instance several times since this occurred and haven't seen this error appear. You can close this issue for now and I'll reopen if it occurs again and I have more information. I saw this error in the same logs which exhibited the behavior noted in JENKINS-10318 so it may just be a symptom of another problem as you noted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
David Ehrenberger updated JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs config.xml attached for a job that utilizes CVS. Since the warning doesn't indicate what job it applies to, this is just a guess. CVS plugin version is v2.6 Change By: David Ehrenberger (06/Nov/12 12:43 PM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
David Ehrenberger created JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs Issue Type: Bug Assignee: Unassigned Components: cvs Created: 02/Nov/12 1:34 PM Description: Getting the following in the system log at startup. Not sure of the ramifications. Nov 2, 2012 9:23:30 AM hudson.util.RobustReflectionConverter doUnmarshal WARNING: Failed to resolve a type java.lang.InstantiationError: hudson.scm.AbstractCvs at sun.reflect.GeneratedSerializationConstructorAccessor507.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.thoughtworks.xstream.converters.reflection.Sun14ReflectionProvider.newInstance(Sun14ReflectionProvider.java:76) at hudson.util.RobustReflectionConverter.instantiateNewInstance(RobustReflectionConverter.java:375) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:220) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:137) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at hudson.XmlFile.unmarshal(XmlFile.java:160) at hudson.model.Run.reload(Run.java:291) at hudson.model.Run.(Run.java:280) at hudson.model.AbstractBuild.(AbstractBuild.java:182) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor33.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at hudson.model.Abst
[JIRA] (JENKINS-10318) ConcurrentModificationException reading config.xml on startup
David Ehrenberger commented on JENKINS-10318 ConcurrentModificationException reading config.xml on startup For what its worth, the following error looks to be related to a coverity publisher: Nov 2, 2012 9:23:25 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job Job.Coverity hudson.util.IOException2: Unable to read /jenkins/jobs/Job.Coverity/config.xml at hudson.XmlFile.read(XmlFile.java:141) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$17.run(Jenkins.java:2507) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) 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) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.util.ConcurrentModificationException cause-message : null class : hudson.model.FreeStyleProject required-type : jenkins.plugins.coverity.CoverityPublisher path: /project/publishers/jenkins.plugins.coverity.CoverityPublisher/invocationAssistance line number : 76 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:89) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:263) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:137) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926) at hudson.util.XStream2.unmarshal(XStream2.java:103) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:864) at hudson.XmlFile.read(XmlFile.java:137) ... 10 more Caused by: java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1100) at java.util.TreeMap$KeyIterator.next(TreeMap.java:1154) at com.thoughtworks.xstream.core.util.PrioritizedList$PrioritizedItemIterator.next(PrioritizedList.java:91) at com.thoughtworks.xstream.core.DefaultConverterLookup.lookupConverterForType(DefaultConverterLookup.java:62) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarsh
[JIRA] (JENKINS-11017) Consolidate Slave logs
David Ehrenberger commented on JENKINS-11017 Consolidate Slave logs This has been resolved in a later version of Jenkins; this should be 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
[JIRA] (JENKINS-10318) ConcurrentModificationException reading config.xml on startup
David Ehrenberger commented on JENKINS-10318 ConcurrentModificationException reading config.xml on startup This occurring often on v1.487. Please elevate in priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) "+" in the Page name not supported
David Ehrenberger commented on JENKINS-15308 "+" in the Page name not supported Your questions led me to try this combination and it worked: Confluence page name is "Release Notes Test Page" URL shows "Release+Notes+Test+Page" Jenkins configuration for Page is "Release Notes Test Page" (says OK: Release Notes Test Page) If I change the Jenkins configuration for Page to be "Release+Notes+Test+Page" I'll still get the "OK: Release Notes Test Page" but at runtime I get the error mentioned in the description. Running Confluence v3.4.3 for what its worth. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) "+" in the Page name not supported
David Ehrenberger commented on JENKINS-15308 "+" in the Page name not supported Well, to clarify, when it works it is all run together This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) "+" in the Page name not supported
David Ehrenberger commented on JENKINS-15308 "+" in the Page name not supported When I visit the page it shows the "+" signs in the address bar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) "+" in the Page name not supported
David Ehrenberger created JENKINS-15308 "+" in the Page name not supported Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher Created: 25/Sep/12 8:45 PM Description: Even though by the time I apply my configuration changes and everything looks valid (i.e., I get the OK), running the job gives me the following output: [confluence] Unable to locate page: JENKINS/Release+Notes+Test+Page. [confluence] Check that the page still exists. If the Space and/or Page name contain build-time parameters, check that the parameter(s) are set to the proper value(s). Where my full URL is something like http://confluence/display/JENKINS/Release+Notes+Test+Page If I change the Page name to ReleaseNotesTestPage everything is published okay: [confluence] Uploading attachments to Confluence page: http://confluence/display/JENKINS/ReleaseNotesTestPage [confluence] Uploading 0 file(s) to Confluence... [confluence] Done [confluence] Performing wiki edits: Append content Environment: Jenkins v1.481, Confluence Publisher v1.7.1 Project: Jenkins Priority: Major Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11626) Intermittent SQL error when publishing to Confluence
David Ehrenberger commented on JENKINS-11626 Intermittent SQL error when publishing to Confluence I get this exception intermittently when I go into the Configure section of the job where the Space and Page were previously considered valid. If I click in the Text Field and then off of it, it seems to go away. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15218) Dependency tree should be constrained to only contain relevant nodes in the path
David Ehrenberger created JENKINS-15218 Dependency tree should be constrained to only contain relevant nodes in the path Issue Type: Bug Assignee: wolfs Attachments: graphviewbug.png Components: depgraph-view Created: 18/Sep/12 1:21 PM Description: When on the job page for Test.Job.3 and I click the sidebar link for the dependency graph (URL looks something like http://jenkins.url/job/Test.Job.3/depgraph-view/?), the graph should not include Test.Job.4. Project: Jenkins Priority: Major Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14152) Configuration Matrix combination filter ignored
David Ehrenberger commented on JENKINS-14152 Configuration Matrix combination filter ignored Upgrading from 1.475 to 1.481 has resolved this defect. This can be 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
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job Sure, no problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14152) Configuration Matrix combination filter ignored
David Ehrenberger updated JENKINS-14152 Configuration Matrix combination filter ignored Change By: David Ehrenberger (06/Aug/12 6:53 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
[JIRA] (JENKINS-14152) Configuration Matrix combination filter ignored
David Ehrenberger commented on JENKINS-14152 Configuration Matrix combination filter ignored Changed priority to 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
[JIRA] (JENKINS-14680) CVS Plugin v2.5 throws NPE
David Ehrenberger created JENKINS-14680 CVS Plugin v2.5 throws NPE Issue Type: Bug Assignee: Unassigned Components: cvs Created: 03/Aug/12 1:40 PM Description: Getting this error with the new CVS v2.5 plugin: FATAL: null java.lang.NullPointerException at hudson.scm.CVSSCM$2.cleanup(CVSSCM.java:895) at hudson.scm.CVSSCM$2.invoke(CVSSCM.java:874) at hudson.scm.CVSSCM$2.invoke(CVSSCM.java:869) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.scm.CVSSCM.checkout(CVSSCM.java:869) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: CVS Plugin v2.5 Project: Jenkins Priority: Critical Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14652) Failed to parse form data when modifying job name
David Ehrenberger updated JENKINS-14652 Failed to parse form data when modifying job name Change By: David Ehrenberger (01/Aug/12 12:26 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14652) Failed to parse form data when modifying job name
David Ehrenberger
created JENKINS-14652
Failed to parse form data when modifying job name
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
01/Aug/12 12:25 PM
Description:
When attempting to change the name of a job from "something.here" to "something.here.now", I get this error:
Error
Failed to parse form data. Please report this problem as a bug
JSON={"":"HEAD of the solinet repository","builder":[{"buildStepId":"org.jenkinsci.plugins.managedscripts.ScriptConfig1339367687827","defineArgs":{"buildStepArgs":{"arg":"-t unittest"}},"kind":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep","stapler-class":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep"},{"buildStepId":"org.jenkinsci.plugins.managedscripts.ScriptConfig1339436515182","defineArgs":{"buildStepArgs":{"arg":"-x ./bin/unitTestRunner"}},"kind":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep","stapler-class":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep"},{"buildStepId":"org.jenkinsci.plugins.managedscripts.ScriptConfig1339422351591","kind":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep","stapler-class":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep"},{"buildStepId":"org.jenkinsci.plugins.managedscripts.ScriptConfig1339612308312","kind":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep","stapler-class":"org.jenkinsci.plugins.managedscripts.ScriptBuildStep"}],"core:apply":"","description":"HEAD of the solinet repository","displayNameOrNull":"","hudson-triggers-SCMTrigger":{"scmpoll_spec":"@hourly"},"logrotate":{"logrotate_artifact_days":"","logrotate_artifact_nums":"","logrotate_days":"","logrotate_nums":"50"},"name":"solinet.HEAD.Analysis","properties":{"hudson-model-ParametersDefinitionProperty":{},"hudson-plugins-sidebar_link-ProjectLinks":{},"org-jenkinsci-plugins-envinject-EnvInjectJobProperty":{},"stapler-class-bag":"true"},"publisher":[{"coberturaReportFile":"gcovReport.xml","inst":[{"healthy":"61","metric":"CLASSES","unhealthy":"62","unstable":"62"},{"healthy":"61","metric":"FILES","unhealthy":"62","unstable":"62"},{"healthy":"3","metric":"LINE","unhealthy":"4","unstable":"4"},{"healthy":"-1","metric":"METHOD","unhealthy":"0","unstable":"0"}],"kind":"hudson.plugins.cobertura.CoberturaPublisher","onlyStable":false,"sourceEncoding":"ASCII","stapler-class":"hudson.plugins.cobertura.CoberturaPublisher"},{"docs":{"description":"Doxygen generated API documentation and class hierarchy diagrams","directory":"docs/html/","file":"","id":"1","recursive":true,"title":"Toolkit API"},"kind":"hudson.plugins.doclinks.DocLinksPublisher","stapler-class":"hudson.plugins.doclinks.DocLinksPublisher"},{"kind":"org.jenkinsci.plugins.xunit.XUnitPublisher","stapler-class":"org.jenkinsci.plugins.xunit.XUnitPublisher","thresholds":[{"failureNewThreshold":"1","failureThreshold":"1","kind":"org.jenkinsci.plugins.xunit.threshold.FailedThresholdDescriptor","stapler-class":"org.jenkinsci.plugins.xunit.threshold.FailedThreshold","unstableNewThreshold":"1","unstableThreshold":"1"},{"failureNewThreshold":"1","failureThreshold":"1","kind":"org.jenkinsci.plugins.xunit.threshold.SkippedThresholdDescriptor","stapler-class":"org.jenkinsci.plugins.xunit.threshold.SkippedThreshold","unstableNewThreshold":"1","unstableThreshold":"1"}],"tools":{"deleteOutputFiles":true,"faildedIfNotNew":true,"kind":"class com.thalesgroup.dtkit.junit.BoostTest","pattern":"unitTestReport.xml","stapler-class":"com.thalesgroup.dtkit.metrics.hudson.model.BoostTestJunitHudsonTestType","stopProcessingIfError":true}},{"kind":"hudson.tasks.Mailer","mailer_notifyEveryUnstableBuild":false,"mailer_recipients":"john","mailer_sendToIndividuals":true,"stapler-class":"hudson.tasks.Mailer"},{"childProjects":"solimath.HEAD, slate.HEAD, tadil.HEAD, dis.HEAD, vmf.HEAD, msct.HEAD, dfuseCORE.HEAD, dfuseSIS.HEAD","kind":"hudson.tasks.BuildTrigger","stapler-class":"hudson.tasks.BuildTrigger","threshold":"SUCCESS"}],"scm":{"":["hudson.plugins.git.util.DefaultBuildChooser","7"],"authorOrCommitter":false,"branches":{"name":"origin/master"},"browser":{"stapler-class":"hudson.plugins.git.browser.GitWeb","url":"
[JIRA] (JENKINS-14652) Failed to parse form data when modifying job name
David Ehrenberger updated JENKINS-14652 Failed to parse form data when modifying job name Change By: David Ehrenberger (01/Aug/12 12:25 PM) Environment: Jenkins v1.475 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11017) Consolidate Slave logs
David Ehrenberger
commented on JENKINS-11017
Consolidate Slave logs
Additionally, it would be nice if they didn't all get placed directly in ${JENKINS_HOME} (i.e., put them in a sub directory)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14394) The version 1.1.21 breaks
David Ehrenberger commented on JENKINS-14394 The version 1.1.21 breaks Same thing happened to me (no job configuration changes); had to roll back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14141) CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled
David Ehrenberger commented on JENKINS-14141 CVS always creates module name folder in workspace since 1.470, legacy mode is stuck on enabled Manually editing the config.xml does work, however after doing so, you cannot configure anything about the job without the setting reverting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job Behind the scenes it doesn't really matter to me how the environment variables are injected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job I'm not sure I understand your first question, but you can check which shell you're in by querying the SHELL environment variable. For instance, my jenkins log indicates SHELL as: /bin/bash, but on a separate machine my SHELL environment variable indicates: /bin/tcsh. I think shells of type csh have setenv, but ksh uses export. For what its worth, I believe Jenkins run in a BASH environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14152) Configuration Matrix combination filter ignored
David Ehrenberger created JENKINS-14152 Configuration Matrix combination filter ignored Issue Type: Bug Assignee: Unassigned Attachments: configMatrixSettings.png, matrixViewJobPage.png Components: core Created: 19/Jun/12 6:08 PM Description: I'm attempting to configure a job that should run on several machines with differing compilers. My machines have OS-related labels (i.e., linux.rh.5, linux.rh.6) as well as supported compiler labels (i.e., gcc-4.5.3, etc.). Attached is a screenshot of my matrix settings, where I'm selecting three different compiler labels and two different OS labels and I'm attempting to use a combination filter in order to not attempt a label combination of linux.rh.6 and gcc-3.4.6, but allow all other combinations. After saving these settings, the combination matrix view available in the job page gives me a gray ball for the combination I want to weed out, however, as shown below, the job is hung attempting the combination anyway. Started by user someUser Building on master in workspace /var/lib/jenkins/jobs/Test.Job/workspace Triggering gcc-4.5.3,linux.rh.5 Triggering gcc-4.5.3,linux.rh.6 Triggering gcc-3.4.6,linux.rh.5 Triggering gcc-4.6.3,linux.rh.5 Triggering gcc-4.6.3,linux.rh.6 Triggering gcc-3.4.6,linux.rh.6 gcc-4.5.3,linux.rh.5 completed with result SUCCESS gcc-4.5.3,linux.rh.6 completed with result SUCCESS gcc-3.4.6,linux.rh.5 completed with result SUCCESS gcc-4.6.3,linux.rh.5 completed with result SUCCESS gcc-4.6.3,linux.rh.6 completed with result SUCCESS Configuration gcc-3.4.6,linux.rh.6 is still in the queue: All nodes of label 'gcc-3.4.6&&linux.rh.6' are offline Aborted Aborted by someUser Cancelled gcc-3.4.6,linux.rh.6 Finished: ABORTED Project: Jenkins Priority: Major Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14150) $NODE_NAME empty for master, exists in $NODE_LABELS
David Ehrenberger commented on JENKINS-14150 $NODE_NAME empty for master, exists in $NODE_LABELS For what its worth, echoing the $NODE_LABELS on a slave has the form "SlaveNameIsFirst label_1 label_2" whereas on the master it is the opposite: "label_1 label_2 master" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14150) $NODE_NAME empty for master, exists in $NODE_LABELS
David Ehrenberger created JENKINS-14150 $NODE_NAME empty for master, exists in $NODE_LABELS Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Jun/12 3:18 PM Description: Made a simple job on the master with one shell execution to echo both $NODE_NAME and $NODE_LABELS. $NODE_NAME is empty but "master" is echo'd for $NODE_LABELS. Project: Jenkins Priority: Major Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14150) $NODE_NAME empty for master, exists in $NODE_LABELS
David Ehrenberger commented on JENKINS-14150 $NODE_NAME empty for master, exists in $NODE_LABELS Seems like the same problem identified back in JENKINS-9671. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job -e means that if any command fails (which it indicates by returning a nonzero status), the script will terminate immediately. -x causes the shell to print an execution trace. So you are saying there is no "one" job environment currently available in Jenkins? Do you know the existing Jenkins JIRA issue? If there were "one" environment, then your plugin change would work since a sub-shell environment can add to/modify existing environment variables from the main shell via the export (in bash) or setenv (in tcsh). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger edited a comment on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job I use the bash built-in 'source' command which executes the script in the context of the current shell. For the purposes of this plugin, doing so will load any exported environment variables into the shell environment. Once the shell is closed, the variables exported into it are gone as well. This is why, if I execute 5 different shell build steps, I must source the environment file in each build step. As an example, if my script called environment.anything contains: #!/bin/bash export MY_VARIABLE="Test Variable" This would be possible in a shell: source environment.anything echo $MY_VARIABLE Test Variable You can read about shells Here but the 'source' command should be supported by most major shell types. Ultimately, I'd like to be able to source a script which sets up my job environment such that all my build steps also share that environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger commented on JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job I use the bash built-in 'source' command which executes the script in the context of the current shell. For the purposes of this plugin, doing so will load any exported environment variables into the shell environment. Once the shell is closed, the variables exported into it are gone as well. This is why, if I execute 5 differed shell build steps, I must source the environment file in each build step. As an example, if my script called environment.anything contains: #!/bin/bash export MY_VARIABLE="Test Variable" This would be possible in a shell: source environment.anything echo $MY_VARIABLE Test Variable You can read about shells Here but the 'source' command should be supported by most major shell types. Ultimately, I'd like to be able to source a script which sets up my job environment such that all my build steps also share that environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14097) Allow Script Path/Content to add/override environment variables for the build job
David Ehrenberger created JENKINS-14097 Allow Script Path/Content to add/override environment variables for the build job Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Attachments: systemInfo.pdf Components: envinject Created: 13/Jun/12 12:58 PM Description: Currently the help indication for Script Path/Content states: ... adding or overriding environment variables in the script doesn't have any impacts in the build job. It would be extremely useful to be able to source a script (i.e., bash) which exports environment variables such that they persist for use in the build job. Currently to work around this, I need to source the script at the top of every Execute Shell build step. Environment: Environment Injector Plugin v1.55 Project: Jenkins Priority: Major Reporter: David Ehrenberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
