[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron commented on JENKINS-60093 Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character got it, but we have not yet reproduced the condition where the ESC char was emitted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202938.1573148951000.798.1573740960659%40Atlassian.JIRA.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron commented on JENKINS-60093 Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character but why was it there My guess is Maven color codes, along with broken build, ... We continue to monitor, but we do not have any retained logs at this moment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202938.1573148951000.13339.1573654440505%40Atlassian.JIRA.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron created an issue Jenkins / JENKINS-60093 WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-11-07 17:49 Environment: centos 7 Priority: Minor Reporter: Jason Pyeron ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /var/lib/jenkins/workspace/REDACTED_master@tmp/withMaven90609b9c/maven-spy-20191107-123951-371640815890573653522.log|mailto:/var/lib/jenkins/workspace/proval-devint-deploy-war2_master@tmp/withMaven90609b9c/maven-spy-20191107-123951-371640815890573653522.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/] ERROR: org.xml.sax.SAXParseException; lineNumber: 2267; columnNumber: 39; An invalid XML character (Unicode: 0x1b) was found in the element content of the document.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron commented on JENKINS-60093 Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character the log file is gone, the "tmp" workspace is empty of all files. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202938.1573148951000.10745.1573149360117%40Atlassian.JIRA.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title
Jason Pyeron updated an issue
Jenkins / JENKINS-60093
WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Change By:
Jason Pyeron
{noformat}ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /var/lib/jenkins/workspace/REDACTED_master@tmp/withMaven90609b9c/maven-spy-20191107-123951-371640815890573653522.log |mailto:/var/lib/jenkins/workspace/proval-devint-deploy-war2_master@tmp/withMaven90609b9c/maven-spy-20191107-123951-371640815890573653522.log , ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/]ERROR: org.xml.sax.SAXParseException; lineNumber: 2267; columnNumber: 39; An invalid XML character (Unicode: 0x1b) was found in the element content of the document.{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron commented on JENKINS-60093 Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character not sure if it a proper duplicate, but these seem similar. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202938.1573148951000.10735.1573149060113%40Atlassian.JIRA.
[JIRA] (JENKINS-16731) Common slave service for multiple masters
Title: Message Title Jason Pyeron commented on JENKINS-16731 Re: Common slave service for multiple masters Thoughts on the design pattern: On resource management, the slave has a # of concurrent executors, this value needs to be the same across all masters Can this property be set on the slave and queried by the master, not set? A master should only have detailed job status for its job A master would need to know of a foreign job execution status, at a minimum Job name Job number Master (public/login) URL job start time On authentication The node may want a shared or individual authentication key for each master Individual keys could support an easy way of identifying / tagging jobs to a master? While not needed at first, a queuing ticket issuance for master/master job ordering. Think like a bakery, take a number and wait. For now, think hungry hungry hippos game, if you get the slot, you have a scheduled job - someone will get it and eventually you should get one Are there other ways to minimize the impact/change to the master/node protocol? Add Comment
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron commented on JENKINS-59078 Re: jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' seems to be slightly relevant Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201460.1566802604000.7.1566845580071%40Atlassian.JIRA.
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron commented on JENKINS-59078 Re: jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' I gave a small effort to patch https://github.com/jenkinsci/maven-plugin , but I hit a brick wall on trying to update the maven-core to 3.6.x maven barf on 3.6.0 [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (display-info) @ maven-plugin --- [INFO] Adding ignore: module-info [INFO] Ignoring requireUpperBoundDeps in com.google.guava:guava [INFO] Ignoring requireUpperBoundDeps in com.google.code.findbugs:jsr305 [WARNING] Rule 4: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message: Failed while enforcing RequireUpperBoundDeps. The error(s) are [ Require upper bound dependencies error for org.codehaus.plexus:plexus-utils:3.1.0 paths to dependency are: +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven3-agent:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven35-agent:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven31-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven32-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven33-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven35-interceptor:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.jenkins-ci.main.maven:maven3-interceptor-commons:1.13 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-core:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-compat:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-repository-metadata:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-resolver-provider:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven:maven-embedder:3.6.1 +-org.codehaus.plexus:plexus-utils:3.2.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.eclipse.sisu:org.eclipse.sisu.plexus:0.3.3 +-org.codehaus.plexus:plexus-utils:3.0.17 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-http:3.3.2 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-file:3.3.2 +-org.codehaus.plexus:plexus-utils:3.1.0 and +-org.jenkins-ci.main:maven-plugin:3.4.0.4 +-org.apache.maven.wagon:wagon-ssh:3.3.2
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron commented on JENKINS-59078 Re: jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' A similar example... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201460.1566802604000.9380.1566803040113%40Atlassian.JIRA.
[JIRA] (JENKINS-59078) jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm'
Title: Message Title Jason Pyeron created an issue Jenkins / JENKINS-59078 jenkins Malformed POM Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-08-26 06:56 Environment: centos 7 x64 JDK 1.8 Priority: Major Reporter: Jason Pyeron It builds just fine in maven 3.6.1, Jenkins configured to use 3.6.1 > git submodule update --init --recursive mojo-lombok-issue-fix-18 Parsing POMs ERROR: Failed to parse POMs hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Malformed POM /var/lib/jenkins/workspace/xxx/pom.xml: Unknown attribute 'child.scm.url.inherit.append.path' for tag 'scm' (position: START_TAG seen ...\n\n "false">... @39:50) @ /var/lib/jenkins/workspace/xxx/pom.xml, line 39, column 50 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1390) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1126) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron commented on JENKINS-51280 Re: Support skipping the checkout step for the git scm plugin mildly related in concept Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron commented on JENKINS-51280 Re: Support skipping the checkout step for the git scm plugin I need to make tests, but to start: https://github.com/jenkinsci/git-plugin/pull/591 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51280) Support skipping the checkout step for the git scm plugin
Title: Message Title Jason Pyeron created an issue Jenkins / JENKINS-51280 Support skipping the checkout step for the git scm plugin Issue Type: Improvement Assignee: Jason Pyeron Components: git-plugin Created: 2018-05-13 10:03 Priority: Minor Reporter: Jason Pyeron When performing complex SCM actions, it may be desirable to let the script perform all the actions after polling and fetch. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-38956) can't add clover publisher
Title: Message Title Jason Pyeron commented on JENKINS-38956 Re: can't add clover publisher Using 4.6.0 http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/clover/4.6.0/clover-4.6.0.hpi does not produce any error messages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38956) can't add clover publisher
Title: Message Title Jason Pyeron updated an issue Jenkins / JENKINS-38956 can't add clover publisher Change By: Jason Pyeron Environment: Jenkins ver. 1.651.1 , 2.19.4 clover plugin ver 4.7.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title Jason Pyeron commented on JENKINS-39410 Re: Clover-Plugin crash (InvocationTargetException) same root cause Caused by: java.lang.IllegalArgumentException: Unable to convert to class hudson.plugins.clover.targets.CoverageTarget at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:465) at org.kohsuke.stapler.RequestImpl.bindParameters(RequestImpl.java:441) at hudson.plugins.clover.CloverPublisher$DescriptorImpl.newInstance(CloverPublisher.java:405) at hudson.plugins.clover.CloverPublisher$DescriptorImpl.newInstance(CloverPublisher.java:380) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:1050) at hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:1012) at hudson.util.DescribableList.rebuildHetero(DescribableList.java:208) at hudson.model.Project.submit(Project.java:236) at hudson.model.Job.doConfigSubmit(Job.java:1246) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:796) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) ... 58 more Add Comment
[JIRA] (JENKINS-38956) can't add clover publisher
Title: Message Title Jason Pyeron commented on JENKINS-38956 Re: can't add clover publisher is there a downgrade workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27176) plugin management must log details about upgrades to support forensic analysis
Jason Pyeron commented on JENKINS-27176 plugin management must log details about upgrades to support forensic analysis yes I self assigned because I would like to take a crack at it. I think this should be fixable by someone who has never hacked Jenkins code before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron commented on JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins No, that would not disable securtiy. In fact the case which happened here, commenting out that block, resulted in no-access. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27177) There should be a command line mechism to disable plugins
Jason Pyeron commented on JENKINS-27177 There should be a command line mechism to disable plugins Justification: It is a best practice to have documentation for a server on the server. Take for example systems and networks without internet access. Even if there was internet access, the sysadmin would expect the docs to be with the program, for THAT version. What is needed: docs installed with Jenkins. What is not needed: "support" for mucking with jenkins file system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27177) There should be a command line mechanism to disable plugins
Jason Pyeron updated JENKINS-27177 There should be a command line mechanism to disable plugins Change By: Jason Pyeron (01/Mar/15 12:50 PM) Summary: Thereshouldbeacommandline mechism mechanism todisableplugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron commented on JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins 1. A stack trace would not be exposed to the users (or the internet, etc) 2. depending on what failed, some operations may still function. 3. there is a hope of being able to use the web UI to manage the ofending plugin. But lets start with #1, giving out the file path to the whole internet saying, hey I have my files in this path if you would like to start your hacking attemptins on a known target. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not crash Jenkins
Jason Pyeron updated JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not crash Jenkins Good to know, I'll recomend that be addded to the Jenkins STIG and I'll deploy it to our instances. But what if that plugin fails? I still think that failing to read the config.xml or process a plugin dependent section should not "crash" Jenkins. Change By: Jason Pyeron (01/Mar/15 2:15 PM) Summary: Loadingconfig.xmlsectionsdependentonfailedplugins,mustnot disable crash Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not crash Jenkins
Jason Pyeron commented on JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not crash Jenkins My colleagues say I have a non-IT cloud over my head. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27176) plugin management must log details about upgrades to support forensic analysis
Jason Pyeron commented on JENKINS-27176 plugin management must log details about upgrades to support forensic analysis The UI may also benefit from this change. On restart Jenkins crashed and the admin was left with: Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity Success GitHub Plugin Downloaded Successfully. Will be activated during the next boot Git Client Plugin Downloaded Successfully. Will be activated during the next boot Git Plugin Downloaded Successfully. Will be activated during the next boot Script Security Plugin Downloaded Successfully. Will be activated during the next boot JUnit Plugin Downloaded Successfully. Will be activated during the next boot Matrix Project Plugin Downloaded Successfully. Will be activated during the next boot Mailer Downloaded Successfully. Will be activated during the next boot Git Client Plugin Downloaded Successfully. Will be activated during the next boot Restarting Jenkins Running on the screen. If there were version numbers, the SA would have a place to start with debugging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron created JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins Issue Type: Bug Assignee: Unassigned Components: core Created: 01/Mar/15 2:24 AM Description: config.xml contained authorizationStrategy class="hudson.security.ProjectMatrixAuthorizationStrategy", which relied on a failed plugin. As such the loading of Jenkins was halted. There was no ability to admin Jenkins from the web UI, such as downgrading the ofending plugin. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Minor Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27177) There should be a command line mechism to disable plugins
Jason Pyeron commented on JENKINS-27177 There should be a command line mechism to disable plugins related: https://wiki.jenkins-ci.org/display/JENKINS/Removing+and+disabling+plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27176) plugin management must log details about upgrades to support forensic analysis
Jason Pyeron created JENKINS-27176 plugin management must log details about upgrades to support forensic analysis Issue Type: Bug Assignee: Jason Pyeron Components: core Created: 01/Mar/15 2:34 AM Description: The current loging is insufficient level of detial and criticality upgrade: Feb 28, 2015 10:49:57 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of GitHub Plugin on behalf of jpyeron Feb 28, 2015 10:49:57 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading GitHub Plugin Feb 28, 2015 10:49:58 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Client Plugin on behalf of jpyeron Feb 28, 2015 10:49:59 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Client Plugin Feb 28, 2015 10:50:00 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Plugin on behalf of jpyeron Feb 28, 2015 10:50:00 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Plugin Feb 28, 2015 10:50:01 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Script Security Plugin on behalf of jpyeron Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Script Security Plugin Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of JUnit Plugin on behalf of jpyeron Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading JUnit Plugin Feb 28, 2015 10:50:02 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Matrix Project Plugin on behalf of jpyeron Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Matrix Project Plugin Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Mailer on behalf of jpyeron Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Mailer Feb 28, 2015 10:50:03 AM hudson.model.UpdateCenter$DownloadJob run INFO: Starting the installation of Git Client Plugin on behalf of jpyeron Feb 28, 2015 10:50:04 AM hudson.model.UpdateCenter$UpdateCenterConfiguration download INFO: Downloading Git Client Plugin Feb 28, 2015 11:20:02 AM hudson.model.UpdateCenter doSafeRestart INFO: Scheduling Jenkins reboot downgrade: Feb 28, 2015 12:28:10 PM hudson.model.UpdateCenter$PluginDowngradeJob run INFO: Starting the downgrade of Matrix Project Plugin on behalf of anonymous Feb 28, 2015 12:28:10 PM hudson.model.UpdateCenter$PluginDowngradeJob run INFO: Downgrade successful: Matrix Project Plugin The upgrade and downgrade actions need to log the old and new version numbers for each plugin change at the warning level, to ensure it being recorded to the log. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Critical Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [core] (JENKINS-27177) There should be a command line mechism to disable plugins
Jason Pyeron created JENKINS-27177 There should be a command line mechism to disable plugins Issue Type: New Feature Assignee: Unassigned Components: core Created: 01/Mar/15 2:45 AM Description: The typical system administrator, to urgently recover from a problem, will need to use local system commands to disable plugins indicated a problem in the Jenkins logs. The first step is to include a "README" in the install and/or plugin directories. This readme file may be as simple as to link to the Jenkins online documentation describing the file structure and configurations. Secondly, there should be clear documentation on the "manual" backup/restore/disabling plugins and their configurations. Lastly, if it is not currently possible to disable a plugin via the command line and/or config update a process should be added to Jenkins to do so. See thread https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com Project: Jenkins Priority: Major Reporter: Jason Pyeron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27175) Loading config.xml sections dependent on failed plugins, must not disable Jenkins
Jason Pyeron updated JENKINS-27175 Loading config.xml sections dependent on failed plugins, must not disable Jenkins Change By: Jason Pyeron (01/Mar/15 2:45 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
