[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Created https://issues.jenkins-ci.org/browse/JENKINS-59552. 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.199434.155810265.6148.1569511740229%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Daniel Beck any update on this? Was an issue ever made that I can track? 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.199434.155810265.4391.1569346980350%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Thanks Daniel Beck. Did you need me to make a ticket or did you already? 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.199434.155810265.5107.1568724120400%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Daniel Beck commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data I'll take this. 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.199434.155810265.3634.1568466360338%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Then Jenkins should be bundling 1.5.1. 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.199434.155810265.3538.1568417520234%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Er, I'm sorry. The https://plugins.jenkins.io/pam-auth plugin is the one with the security issue. jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/pam-auth.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/pam-auth/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin PAM Authentication plugin v1.1 (pam-auth) by pool-6-thread-4 jenkins_1 | INFO: Took 0ms for Initializing plugin pam-auth by pool-6-thread-1 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.199434.155810265.3406.1568402940436%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Some logs: jenkins_1 | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/ldap.jpi jenkins_1 | WARNING: Created /var/jenkins_home/plugins/ldap/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness jenkins_1 | INFO: Took 0ms for Loading plugin LDAP Plugin v1.11 (ldap) by pool-6-thread-24 jenkins_1 | INFO: Took 0ms for Initializing plugin ldap by pool-6-thread-18 The latest version is 1.20 according to my UI. 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.199434.155810265.3398.1568402580305%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Jesse Glick I am not seeing the detached plugins being updated. At last when using the Docker container. I'm able to replicate with the https://plugins.jenkins.io/purge-build-queue-plugin# which pulls in LDAP 1.0 for example. 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.199434.155810265.3312.1568397300249%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Daniel Beck commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Fun fact: When greenballs was last released in 2015, 1.638 was the current weekly release, not 1.440 (released 2011). So the implied dependencies to… external-monitor-job ldap pam-auth mailer matrix-auth windows-slaves antisamy-markup-formatter matrix-project junit i.e. roughly 2/3 of all its dependencies, were basically the maintainer's choice. 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.199434.155810265.3237.1568393280421%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data disabling them because they aren't actually used but are pulling in ancient versions with tons of security warnings I am not aware of which ancient versions or security warnings you are referring to here. All detached plugins are expected to be updated in tandem with security advisories. If you see differently, please file a bug report (or a patch). CC Daniel Beck I don't see any point in re-releasing the plugin or upgrading core requirements See discussion in JENKINS-28942. My standing proposal would require the plugin to be re-released, with metadata indicating the most recent core version against which it has been successfully tested, but would not require the minimum core version to be changed. 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.199434.155810265.3150.1568383380632%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data I got that. But plugins may have or may have not used them, as there was no possibility to declare. If core will keep reinstantiating them, we will never be able to get rid of this functionality which was unused. For instance, I may be using Green Balls that only changes icon colors, but it incorporates 14 implied plugins. I am pretty sure it does not use LDAP, JDK installer or Windows agents, yet they keep getting installed, because of the time that the plugin was released, they were part of Jenkins. I don't see any point in re-releasing the plugin or upgrading core requirements as the functionality is quite simple and seems complete, so there is no point in artificial release. I would like to get rid of the functionality I don't need though to reduce the bloat, but the core does not want to let it go. I really believe it should be maintained by people maintaining their Docker images. At least there should be an option I could set to say: 'Yes, I know what I'm doing, thank you.' 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.199434.155810265.3088.1568379240349%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data > Apart from that, what's the point of separating functionality into plugins, when the same functionality is injected (in an outdated version) anyway? My understanding is the functionality isn't included anymore in core Jenkins so when those things got peeled out, in order to keep things from breaking, core will pull in these "implied" dependencies to keep other plugins working that may have used them. 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.199434.155810265.3061.1568377861414%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Even when disabled, these are still installed and report security issues. As a workaround I am deleting WEB-INF/detached-plugins from jenkins.war, but I believe it should be at least controllable by some property so that one can consciously opt out of that functionality. Apart from that, what's the point of separating functionality into plugins, when the same functionality is injected (in an outdated version) anyway? 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.199434.155810265.2981.1568376060552%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data This feels a little bit untenable if I'm understanding everything correctly, at least for those using the Docker images. Like I'll be playing whack-a-mole either by adding these implied dependencies to my list of installed plugins so they get updated (because of security issues) or by disabling them because they aren't actually used but are pulling in ancient versions with tons of security warnings. It also heavily relies on plugin maintainers to be constantly updating the version of Jenkins their plugin relies on to not be continually pulling in implied deps of old Jenkins core versions. For example, the simple https://plugins.jenkins.io/purge-build-queue-plugin# is referencing a really old Jenkins core version so it's pulling in a ton of implied deps, most of which are really old and some with security vulnerabilities. Whats the best way to handle this other than having that plugin updated to reference a new Jenkins version so less implied deps are pulled in? 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.199434.155810265.2751.1568374620235%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Jesse Glick commented on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
We do not use any of those detached plugins
If you are using the official Docker image as a base, you ought to be able to
RUN touch /usr/share/jenkins/ref/plugins/{whatever-id,another-id}.jpi.disabled
Untested, YMMV.
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.199434.155810265.150.1568038741047%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Krzysztof Malinowski commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Is it possible to somehow skip or remove this behavior? We do not use any of those detached plugins and they keep being instantiated (in rather ancient versions) at service startup. 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.199434.155810265.8891.1568019360368%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oliver Gondža Labels: 2.176.1-rejected 2.176.2-fixed detached-plugin docker lts-candidate plugin-manager 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.199434.155810265.12375.156196272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oliver Gondža Labels: 2.176.1-rejected 2.176.2-fixed detached-plugin docker lts-candidate plugin-manager 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.199434.155810265.12369.1561962720955%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data There was an ATH regression which it is hoped form-element-path #8 will help correct. 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.199434.155810265.25116.1560259080173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Thank you very much Jesse Glick we changed our script to use .jpi instead of .hpi and also removed the version from the file name. It worked! Thanks again really appreciate your inputs. 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.199434.155810265.10489.1558633140205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data I filed a refinement in jenkins #4039 to improve the behavior and make it more apparent what you were doing wrong. 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.199434.155810265.10446.1558632840857%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data The files in the plugins directory are expected to be named ARTIFACT_ID.jpi, so for example script-security.jpi rather than script-security-1.58.hpi (filename in Artifactory) or script-security.hpi (filename in updates.jenkins.io). 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.199434.155810265.10374.1558628760867%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oliver Gondža Labels: 2.176.1-rejected detached-plugin docker lts-candidate plugin-manager 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.199434.155810265.9799.1558599300360%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Jesse Glick Thanks for the light. We didn't know about this thing so far we are using .hpi files those are downloaded directly from the repo. All of our jenkins instances are currently running this setup only. is that just rename or do we need to do anything special after downloading those .hpi files from the repo? 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.199434.155810265.9599.1558564740416%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati edited a comment on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data [~jglick] Thanks for the light. We didn't know about this thing , so far we are using .hpi files those are downloaded directly from the repo. All of our jenkins instances are currently running on this setup only . is that just rename or do we need to do anything special after downloading those .hpi files from the repo? 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.199434.155810265.9602.1558564740471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Jesse Glick commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data script which copies over all the hpi files to plugins directory Note that $JENKINS_HOME/plugins/ is expected to contain *.jpi files, never *.hpi which is the extension used in Maven repositories and update center URLs. The Jenkins plugin manager always performs this rename when installing plugins either from an update center or the install-plugin CLI command, and official packaging scripts such as for Docker do the same, but perhaps your unsupported custom script neglected to do that? If this is the issue, then Jenkins core could be made a bit more robust here and either silently tolerate *.hpi in more cases, print a clear warning about improper file names, or try to automatically clean up. 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.199434.155810265.9424.1558547280740%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Jesse Glick edited a comment on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
bq. script which copies over all the hpi files to plugins directoryNote that {{$JENKINS_HOME/plugins/}} is expected to contain {{\*.jpi}} files, never {{\*.hpi}} which is the extension used in Maven repositories and update center URLs. The Jenkins plugin manager always performs this rename when installing plugins either from an update center or the {{install-plugin}} CLI command, and official packaging scripts such as for Docker do the same, but perhaps your unsupported custom script neglected to do that? If this is the issue, then Jenkins core could be made a bit more robust here and either silently tolerate {{\*.hpi}} in more cases, print a clear warning about improper file names, or try to automatically clean up. That would be a separate issue that could be linked to this one.
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.199434.155810265.9426.1558547280983%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data It is not this issue per se, but it is "Bring the bundled version of the Script Security plugin up to date with recent security advisories, in the unlikely case it is indeed installed from the WAR rather than the update center" which was delivered along with it in https://github.com/jenkinsci/jenkins/pull/4000 . It looks like the code triggered the downgrade somehow. CC Jesse Glick Daniel Beck Baptiste Mathus A separate issue would be appreciated 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.199434.155810265.8722.1558531440381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178.We tried both the ways: * Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178 * Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors.I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Not very sure though, can we have more documentation on this implied vs detached plugins and also required plugins and so on. Thank you.Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)? This log it has already installed the script-security 1.56 during the startup however during the actual installation it required 1.58 Here with few lines of exception:{code:java}Running from: /root/.ivy2/cache/jenkins/wars/jenkins-2.178.warwebroot: EnvVars.masterEnvVars.get("JENKINS_HOME")2019-05-22 12:43:34.013+ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @775ms to org.eclipse.jetty.util.log.JavaUtilLog2019-05-22 12:43:34.234+ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file2019-05-22 12:43:34.304+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath2019-05-22 12:43:34.427+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00:04:53.875Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_191-b122019-05-22 12:43:34.893+ [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet2019-05-22 12:43:35.021+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node02019-05-22 12:43:35.021+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults2019-05-22 12:43:35.029+ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60msJenkins home directory: /var/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")2019-05-22 12:43:35.881+ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@565f390{Jenkins v2.178,/,file:///var/jenkins/war/,AVAILABLE}{/var/jenkins/war}2019-05-22 12:43:35.924+ [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@668bc3d5{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}2019-05-22 12:43:35.926+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @2690ms2019-05-22 12:43:35.936+ [id=21] INFO winstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled2019-05-22 12:43:37.888+ [id=28] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization2019-05-22 12:43:38.261+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins/plugins/command-launcher.jpi2019-05-22 12:43:38.276+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins/plugins/jdk-tool.jpi2019-05-22 12:43:38.306+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins/plugins/script-
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178.We tried both the ways: * Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178 * Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors.I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Not very sure though, can we have more documentation on this implied vs detached plugins and also required plugins and so on. Thank you.Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)?Here with few lines of exception:{code:java} Running from: /root/.ivy2/cache/jenkins/wars/jenkins-2.178.warwebroot: EnvVars.masterEnvVars.get("JENKINS_HOME") 2019-05-22 12:43:34.013+ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @775ms to org.eclipse.jetty.util.log.JavaUtilLog2019-05-22 12:43:34.234+ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file2019-05-22 12:43:34.304+ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath2019-05-22 12:43:34.427+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00: 04: 45 53.875Z; git : 51 e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1 . 819 8.0_191-b122019-05-22 12:43:34.893 + [id= 33 1 ] SEVERE INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet2019-05-22 12:43:35.021+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node02019-05-22 12:43:35.021+ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults2019-05-22 12:43:35.029+ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60msJenkins home directory: /var/ jenkins found at: EnvVars . masterEnvVars.get("JENKINS_HOME")2019-05-22 12:43:35.881+ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@565f390{Jenkins v2.178,/,file:///var/jenkins/war/,AVAILABLE}{/var/jenkins/war}2019-05-22 12:43:35.924+ [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@668bc3d5{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}2019-05-22 12:43:35.926+ [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @2690ms2019-05-22 12:43:35.936+ [id=21] INFO winstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled2019-05-22 12:43:37.888+ [id=28] INFO jenkins. InitReactorRunner$1# onTaskFailed onAttained : Failed Started initialization2019-05-22 12:43:38.261+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin Pipeline SCM API for Blue Ocean v1 as a dependency: /var/jenkins/plugins/command-launcher . 16 jpi2019-05-22 12:43:38 . 0 (blueocean 276+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins/plugins/jdk - pipeline tool.jpi2019 - scm 05 - 22 12:43:38.306+ [id=31] INFO hudson.PluginManager#considerDetachedPlugin: Loading a detached plugin as a dependency: /var/jenkins/plugins/sc
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data And also other test use case failing with similar errors. For some instances, we test Jenkins locally before we apply any changes to actual instance, part of that we have script which copies over all the hpi files to plugins directory before we start up the jenkins, this is to make sure these new plugins don't have any security issues and also the dependencies look good. 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.199434.155810265.8241.1558501320156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title
Naresh Rayapati edited a comment on JENKINS-57528
Re: Jenkins in Docker does not install detached plugins when there is no UC data
This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178.We tried both the ways:* Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178* Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors. I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Not very sure though, can we have more documentation on this implied vs detached plugins and also required plugins and so on. Thank you. Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)?Here with few lines of exception:{code :java }2019-05-22 04:45:51.819+ [id=33] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline SCM API for Blue Ocean v1.16.0 (blueocean-pipeline-scm-api)java.io.IOException: Pipeline SCM API for Blue Ocean version 1.16.0 failed to load. - Pipeline: Multibranch version 2.21 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)2019-05-22 04:45:51.820+ [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Favorite v2.3.2 (favorite)java.io.IOException: Favorite version 2.3.2 failed to load. - Matrix Project Plugin version 1.4.1 is older than required. To fix, install version 1.7.1 or later.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)2019-05-22 04:45:51.821+ [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin REST Implementation for Blue Ocean v1.16.0 (blueocean-rest-impl)java.io.IOException: REST Implementation for Blue Ocean version 1.16.0 failed to load. - Pipeline: Groovy version 2.68 failed to load. Fix this plugin first.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868)at hudson.PluginManager$2$1$1.run(PluginManager.java:544)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenk
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Naresh Rayapati commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data This change seems to be breaking our Jenkins when we upgrade it from 2.177 to 2.178. We tried both the ways: Upgraded all plugins to latest before upgrading the Jenkins version from 2.177 to 2.178 Upgraded Jenkins to 2.178 and we see these dependency errors before we upgrade all the plugins manually with some errors. I think both the times 2.178 is trying to load lower versions of these implied plugins during the startup and when later actual plugins are being installed and if they require greater version of these base dependencies the installation of that plugin is failing and the chain continues. Is there anyway to disable this functionality of installing these plugins by default and have users an option to explicitly define all these plugins (like what we do today)? Here with few lines of exception: 2019-05-22 04:45:51.819+ [id=33] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline SCM API for Blue Ocean v1.16.0 (blueocean-pipeline-scm-api) java.io.IOException: Pipeline SCM API for Blue Ocean version 1.16.0 failed to load. - Pipeline: Multibranch version 2.21 failed to load. Fix this plugin first. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868) at hudson.PluginManager$2$1$1.run(PluginManager.java:544) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-05-22 04:45:51.820+ [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Favorite v2.3.2 (favorite) java.io.IOException: Favorite version 2.3.2 failed to load. - Matrix Project Plugin version 1.4.1 is older than required. To fix, install version 1.7.1 or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:868) at hudson.PluginManager$2$1$1.run(PluginManager.java:544) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-05-22 04:45:51.821+ [id=27] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin REST Implementation for Blue Ocean v1.16.0 (blueocean-rest-impl) java.io.IOException: REST Implementation for Blue Ocean version 1.16.0 failed to load. - Pipeline: Groovy version 2.68 failed to load. Fix this plugin first. at hudson.Plu
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated JENKINS-57528 Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.178 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.199434.155810265.7753.1558451940191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated JENKINS-57528 To be landed in 2.178 Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed 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.199434.155810265.4346.1558103340346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Labels: detached-plugin docker lts-candidate plugin-manager 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.199434.155810265.4341.1558102800262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Assignee: Carlos Sanchez Jesse Glick 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.199434.155810265.4344.1558102800302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev It is a placeholder for [https://github.com/jenkinsci/docker/issues/698] and for [https://github.com/jenkinsci/jenkins/pull/4000] which addresses it in the core Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation. 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.199434.155810265.4339.1558102680318%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Summary: Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data 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.199434.155810265.4337.1558102680297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
