[JIRA] (JENKINS-62183) Allow Jenkins.MANAGE to configure global options
Title: Message Title mike cirioli started work on JENKINS-62183 Change By: mike cirioli Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206115.1588793151000.22861.1588794240085%40Atlassian.JIRA.
[JIRA] (JENKINS-62183) Allow Jenkins.MANAGE to configure global options
Title: Message Title mike cirioli created an issue Jenkins / JENKINS-62183 Allow Jenkins.MANAGE to configure global options Issue Type: New Feature Assignee: mike cirioli Components: git-plugin Created: 2020-05-06 19:25 Priority: Minor Reporter: mike cirioli Add support for allowing users with Jenkins.MANAGE to configure some aspects of git config Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60406) Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, & PluginManager.CONFIGURE_UPDATECENTER
Title: Message Title mike cirioli started work on JENKINS-60406 Change By: mike cirioli Status: Open In Progress 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.203461.1575907415000.3131.1575916920113%40Atlassian.JIRA.
[JIRA] (JENKINS-60406) Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, & PluginManager.CONFIGURE_UPDATECENTER
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-60406
Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, & PluginManager.CONFIGURE_UPDATECENTER
Change By:
mike cirioli
Flag the following permission types as {{@Deprecated}}: * {{Jenkins.RUN_SCRIPTS}} * {{PluginManager.UPLOAD_PLUGINS}} * {{PluginManager.CONFIGURE_UPDATECENTER}} The usage of these permissions is confusing, and has been effectively hidden (unless specifically enabled) since [ 2017-4-10 | ( https://jenkins.io/security/advisory/2017-04-10/#matrix-authorization-strategy-plugin-allowed-configuring-dangerous-permissions ] ) .
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
[JIRA] (JENKINS-60406) Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, & PluginManager.CONFIGURE_UPDATECENTER
Title: Message Title mike cirioli created an issue Jenkins / JENKINS-60406 Deprecate Jenkins.RUN_SCRIPTS, PluginManager.UPLOAD_PLUGINS, & PluginManager.CONFIGURE_UPDATECENTER Issue Type: Improvement Assignee: mike cirioli Components: core Created: 2019-12-09 16:03 Priority: Minor Reporter: mike cirioli Flag the following permission types as @Deprecated: Jenkins.RUN_SCRIPTS PluginManager.UPLOAD_PLUGINS PluginManager.CONFIGURE_UPDATECENTER The usage of these permissions is confusing, and has been effectively hidden (unless specifically enabled) since 2017-4-10. Add Comment
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-57804
Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Change By:
mike cirioli
The page object that can be used to configure the {{JenkinsDatabaseSecurityRealm}} in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named " {{allowsSignup}} " but the pageobject references it using the name "{{allowSignup}}". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception.[This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution).|https://github.com/jenkinsci/jenkins/pull/3954/files#diff-aec8de1c6c772be0d3ecb3573c46ead8L29], which in turn caused some tests, which expected this to be enabled by default, to break.
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
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-57804
Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Change By:
mike cirioli
The page object that can be used to configure the {{JenkinsDatabaseSecurityRealm}} in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named {{allowsSignup}} but the pageobject references it using the name " {{ allowSignup }} ". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception.[This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution).|https://github.com/jenkinsci/jenkins/pull/3954/files#diff-aec8de1c6c772be0d3ecb3573c46ead8L29], which in turn caused some tests, which expected this to be enabled by default, to break.
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
[JIRA] (JENKINS-57804) Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method
Title: Message Title mike cirioli created an issue Jenkins / JENKINS-57804 Typo in JenkinsDatabaseSecurityRealm pageobject breaks allowSignup method Issue Type: Bug Assignee: mike cirioli Components: acceptance-test-harness Created: 2019-05-31 20:11 Priority: Minor Reporter: mike cirioli The page object that can be used to configure the JenkinsDatabaseSecurityRealm in acceptance tests has a typo in the element name used to enable/disable the ability for users to self-register (ie. signup) when using this realm. The jelly form control is named allowsSignup but the pageobject references it using the name "allowSignup". This causes any ATH tests that rely on manipulating that element to fail with an element not found/Timeout exception. This was brought to light as the result of a recent change that forces the UI behavior to disable user signup by default (as a security precaution)., which in turn caused some tests, which expected this to be enabled by default, to break. Add Comment
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's{{ ModelBuilder }} to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output: {code:json}[{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }]{code}The JSON objects in the resulting array can be used directly in a pipeline:{code:json}assert currentBuild.getBuildCauses().size() == 1assert currentBuild.getBuildCauses()[0].userId == 'tester'echo currentBuild.getBuildCauses()[0].shortDescription{code}Additionally, you can filter the result of {{currentBuild.getBuildCauses()}} by passing a class (or superclass) of the type you would like to filter by. For example, to get a list of build {{Cause}}s that only contains {{Cause}}s of type {{hudson.model.Cause$UserIdCause}}, call the method like this:{code:json}echo currentBuild.getBuildCauses(hudson.model.Cause$UserIdCause).size(){code}
Add Comment
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output:{code:json}[{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }] {code} The JSON objects in the resulting array can be used directly in a pipeline:{code:json}assert currentBuild.getBuildCauses().size() == 1assert currentBuild.getBuildCauses()[0].userId == 'tester'echo currentBuild.getBuildCauses()[0].shortDescription{code}Additionally, you can filter the result of {{currentBuild.getBuildCauses()}} by passing a class (or superclass) of the type you would like to filter by. For example, to get a list of build {{Cause}}s that only contains {{Cause}}s of type {{hudson.model.Cause$UserIdCause}}, call the method like this:{code:json}echo currentBuild.getBuildCauses(hudson.model.Cause$UserIdCause).size(){code}
Add Comment
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output: {code:json}[ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ] {code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the{{ Cause }} s of a build without using the non-whitelisted \ { code} { currentBuild.getRawBuild().getCauses() \{/code } } function. An additional drawback to that approach is that is allows direct access to the actual{{ Cause }} objects, which could potentially allow a malicious pipeline script to manipulate the{{ Cause }} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a{{ Cause }} s{{ @Exported }} fields:For example, a build with a{{ hudson.model.Cause$UserId }} cause produce the following output: < { code:json > } [{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }] { code > }
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.
For more options, visit
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the Causes of a build without using the non-whitelisted < \{ code > } currentBuild.getRawBuild().getCauses() < \{ /code > } function. An additional drawback to that approach is that is allows direct access to the actual Cause objects, which could potentially allow a malicious pipeline script to manipulate the Cause associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a Causes @Exported fields:For example, a build with a hudson.model.Cause$UserId cause produce the following output:[ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ]
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli created an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Issue Type:
New Feature
Assignee:
mike cirioli
Components:
workflow-support-plugin
Created:
2018-10-24 18:41
Labels:
pipeline plugin
Priority:
Minor
Reporter:
mike cirioli
It is currently not possible to access the Causes of a build without using the non-whitelisted currentBuild.getRawBuild().getCauses() function. An additional drawback to that approach is that is allows direct access to the actual Cause objects, which could potentially allow a malicious pipeline script to manipulate the Cause associated with an upstream build. This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a Causes @Exported fields: For example, a build with a hudson.model.Cause$UserId cause produce the following output: [ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ]
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli closed an issue as Cannot Reproduce Jenkins / JENKINS-49502 trigger properties in scripted pipeline require 2 builds to get registered Change By: mike cirioli Status: Open Closed Resolution: Cannot Reproduce 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered quick update - i have re-verified that you no longer need to run a scripted job with triggers twice in order to have them registered. Closing this issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli assigned an issue to mike cirioli Jenkins / JENKINS-49502 trigger properties in scripted pipeline require 2 builds to get registered Change By: mike cirioli Assignee: mike cirioli 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered FWIW - I just had to do a test for a blog post i am writing and when using pipeline-event-triggers, you only need to run a build once (declarative or scripted) using 2.107 core. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli edited a comment on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found FYI, this look similar to [JENKINS-27548|https://issues.jenkins-ci.org/browse/JENKINS-27548] and [JENKINS-38895|https://issues.jenkins-ci.org/browse/JENKINS-38895] and [probably many of these as well|https://issues.jenkins-ci.org/browse/JENKINS-25456?jql=project%20%3D%20JENKINS%20AND%20text%20~%20%22Failed%20to%20persist%20config.xml%22]I haven't had a chance to read through them all and see if there is a solution for your problem, but will make some time this afternoon and see if there is anything to suggest. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found FYI, this look similar to JENKINS-27548 and JENKINS-38895 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found Christian Höltje can you share any details about your environment? Are you running jenkins inside an app server? 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found Can this be reproduced? From the description it is not clear if this happens every time. Also, the XML 1.1 change was not introduced until Jenkins 2.105 and it appears this is being reported for jenkins 2.89. 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli updated an issue Jenkins / JENKINS-50867 SAX2 driver class org.apache.xerces.parsers.SAXParser not found Change By: mike cirioli Comment: thanks for the heads up [~oleg_nenashev] - i will take a look into this tonight 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-50867) SAX2 driver class org.apache.xerces.parsers.SAXParser not found
Title: Message Title mike cirioli commented on JENKINS-50867 Re: SAX2 driver class org.apache.xerces.parsers.SAXParser not found thanks for the heads up Oleg Nenashev - i will take a look into this tonight 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title mike cirioli commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Assuming you don't need to support special characters (like control characters) you could just change the xml declartion to be v1.0 and then process the file with whatever tools you currently use. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title mike cirioli commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I was also unable to reproduce this with the information provided. Nothing in the stack trace indicates to me that this is related to the XML change. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title mike cirioli commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 @reporter - if possible, can you attach the broken config.xml, as well as provide any relevant detail about the manual manipulations you had to perfrom for the the downgrade (ie. was it more than just changing the xml version in the config files?) 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-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title mike cirioli commented on JENKINS-49588 Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035) I will test this out later today 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-49450) Jenkins rollback from v2.105 to v2.104 failed
Title: Message Title
mike cirioli commented on JENKINS-49450
Re: Jenkins rollback from v2.105 to v2.104 failed
I just did a quick test of the following:
fresh install of jenkins 2.105
configured some credentials
downgrade to 2.104 (verify that it fails to start due to xml version issues)
ran this command in $JENKINS_HOME: find . -name "*.xml" -print -exec sed -i '.bak' "s/xml version='1.1'/xml version='1.0'/" {} \;
restarted jenkins 2.104, verified that it was able to start up correctly
verified that the credentials configured in step #2 were still there (they were)
I also installed the latest maven integration plugin (v3.1) and was not able to reproduce any hanging issues. I know you mentioned using an older version of this plugin, if you can provide more details on how to reproduce that particular issue i can take a look.
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
