[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Josh Soref open /pluginManager/installed (Jenkins 2.198)Have: # a couple of plugins with dependencies (enabled) # a couple of plugins (disabled) # a couple of plugins that have never been upgraded # a couple of plugins which have been upgradedh3. Actual resultsI can't really explain what it's doing. – It appears to be stable (i.e. toggling the sort direction for one of these columns reverses the sort), but it isn't global (i.e. changing the sort key to a different column, e.g. Name, and then back to the Enabled column results in a new sort).h3. Expected resultsh5. Sorting by Enabled should sort into three sets: # Enabled (checkbox checked) # Enabled (checkbox disabled) and can't be disabled (because they're used by enabled plugins) # Disabled (checkbox unchecked)h5. Sorting by Uninstall should sort into : two sets: # Uninstall button enabled # Uninstall button disabled Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-37895) Option to "skip" a locked section if a newer build already completed it
Title: Message Title Tobias Gruetzmacher resolved as Won't Do This seems to need quite a lot of tracking and I currently consider this out of scope for the lockable-resources plugin. Feel free to reopen if you think otherwise. Jenkins / JENKINS-37895 Option to "skip" a locked section if a newer build already completed it Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Won't Do 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
[JIRA] (JENKINS-38002) Lockable Resources Plugin releases executor while waiting and executing
Title: Message Title Tobias Gruetzmacher resolved as Cannot Reproduce Sorry, but I cannot reproduce this behaviour at all. That shouldn't even be possible. If you encounter this bug again, please reopen and assign this issue to me and we can try to track down this issue. Jenkins / JENKINS-38002 Lockable Resources Plugin releases executor while waiting and executing Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-58474) Port not reachable while creating a slave agent in windows for a linux master
Title: Message Title Reuben Thomas commented on JENKINS-58474 Re: Port not reachable while creating a slave agent in windows for a linux master I'm seeing this too. The Windows 10 1903 agent is able to connect to a macOS server without problems, but fails to connect to a Fedora server. 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.200609.1562940037000.6577.1570917240209%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Daniel Beck closed an issue as Not A Defect Works as designed. Jenkins / JENKINS-59758 hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Daniel Beck commented on JENKINS-59758 Re: hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found Well, UpdateSite.Plugin is the plugin as it is being distributed by the update site. For the plugins you mention, published issues are already fixed in the releases currently being distributed as latest version. Therefore, no warnings apply to those releases. The reason this API based on UpdateSite.Plugin exists will be apparent when you filter the "available plugins" lists by the string /security/ – there are many plugins being distributed with active security warnings, i.e. even if you're on the newest release, you're affected by a known public security issue. These are typically abandoned plugins. 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.202481.1570833476000.6571.1570913580394%40Atlassian.JIRA.
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title ebundy ebundy edited a comment on JENKINS-59759 Re: localhost not allowed for jeknins with gitlab-branch-source-plugin That is very probably right for online GitLab and it makes sense for an online tool , but by installing GitLab (EE or the community/free version) on our own server, we could fortunately allow to the use of localhost in hooks and services since in these conditions the CI and the SCM may be legitimately hosted on the same machine.Here is the option in the admin->network !gitlab-admin-outboud-request.png|thumbnail! 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.202482.1570880817000.6568.1570911180224%40Atlassian.JIRA.
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title ebundy ebundy commented on JENKINS-59759 Re: localhost not allowed for jeknins with gitlab-branch-source-plugin That is very probably right for online GitLab and it makes sense for an online tool , but by installing GitLab (EE or the community/free version) on our own server, we could fortunately allow to use localhost in hooks and services since in these conditions the CI and the SCM may be legitimately hosted on the same machine. Here is the option in the admin->network 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.202482.1570880817000.6566.1570911060143%40Atlassian.JIRA.
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title ebundy ebundy updated an issue Jenkins / JENKINS-59759 localhost not allowed for jeknins with gitlab-branch-source-plugin Change By: ebundy ebundy Attachment: gitlab-admin-outboud-request.png 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.202482.1570880817000.6564.1570910820240%40Atlassian.JIRA.
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title Parichay Barpanda commented on JENKINS-59759 Re: localhost not allowed for jeknins with gitlab-branch-source-plugin Unfortunately, the GitLab doesn't support web hooks on localhost or a domain name not accessible in the internet (in lay man's term). If you are doing it for testing purpose you might want to disable the web hooks and system hooks (from the SCM traits) else host Jenkins docker in the cloud. I would like to know if you are using GitLab.com or using a self hosted GitLab server? 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.202482.1570880817000.6562.1570905900243%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title
Eric Engstrom edited a comment on JENKINS-59758
Re: hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Sorry - I thought the issue was more clear.Essentially if you attempt to get any issued warnings for an instance of {{hudson.model.UpdateSite$Plugin}}, you will ALWAYS get an empty list ({{[]}}). I believe this to be the case because the version check on line 1250 1265 is checking against the *latest* version, not the installed version.My complex example code is only me trying to figure out why. If you happen to have an instance of Jenkins around with a plugin with a security warning, try the first block of groovy code. Is that helpful? If not, I'll try again.
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.202481.1570833476000.6560.1570904280127%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Eric Engstrom commented on JENKINS-59758 Re: hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found Sorry - I thought the issue was more clear. Essentially if you attempt to get any issued warnings for an instance of hudson.model.UpdateSite$Plugin, you will ALWAYS get an empty list ([]). I believe this to be the case because the version check on line 1250 is checking against the latest version, not the installed version. My complex example code is only me trying to figure out why. If you happen to have an instance of Jenkins around with a plugin with a security warning, try the first block of groovy code. Is that helpful? If not, I'll try again. 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.202481.1570833476000.6557.1570904220267%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Beck Labels: lts-candidate symlink 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.198459.1553858983000.6556.1570904220254%40Atlassian.JIRA.
[JIRA] (JENKINS-59514) Use @POST instead of @RequirePOST for form submission endpoints
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59514 Use @POST instead of @RequirePOST for form submission endpoints Change By: Daniel Beck Labels: lts-candidate robustness 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.202137.156934393.6552.1570904160192%40Atlassian.JIRA.
[JIRA] (JENKINS-58768) Mailer doesn't authenticate properly with Gmail
Title: Message Title Daniel Beck updated JENKINS-58768 Jenkins / JENKINS-58768 Mailer doesn't authenticate properly with Gmail Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: mailer-1.26 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.201073.1564671799000.6527.1570896420765%40Atlassian.JIRA.
[JIRA] (JENKINS-59722) Old scm-api included in Jenkins LTS war file
Title: Message Title Daniel Beck closed an issue as Not A Defect It is unclear how you're running Jenkins, but it looks like it's unsupported. Jenkins will not usually extract bundled plugin versions in normal use (and if it does, it's to ensure implied dependencies are available; but in general, if you manually manage JENKINS_HOME/plugins, the expectation is that you provide correct versions of dependencies). Jenkins / JENKINS-59722 Old scm-api included in Jenkins LTS war file Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59502) Jenkins supported for RHEL 7.6
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Do not ask for help here. Try https://jenkins.io/chat/ or https://jenkins.io/mailing-lists/ Jenkins / JENKINS-59502 Jenkins supported for RHEL 7.6 Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Daniel Beck Labels: newbie-friendly 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.202313.1570043107000.6516.1570896060520%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59631 Adding different colors to history table and data filter Change By: Daniel Beck When I start or refresh a job page, the build history alternating colors start with white on the filter textbox, then grey/white/grey/white for the builds. Also, after using the filter box, or even clearing an already empty filter, the colors clashe with the filter textbox having grey, and them white/grey/white/grey for the builds. It seems that color alteration are not in the right orderIt is an inconsequential issue as the rest of page and features work very well. I think there are some minor issues with html element rendering. Thx,Matt [https://coding-bootcamps.com/] [https://myhsts.org/] [https://dcwebmakers.com/] 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
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Daniel Beck commented on JENKINS-59631 Re: Adding different colors to history table and data filter Can confirm. Interesting find 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.202313.1570043107000.6511.1570896060334%40Atlassian.JIRA.
[JIRA] (JENKINS-59333) customWorkspace relative definition isn't straight
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59333 customWorkspace relative definition isn't straight Change By: Daniel Beck Component/s: pipeline Component/s: core 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.201884.1568299963000.6509.1570895880153%40Atlassian.JIRA.
[JIRA] (JENKINS-59332) customWorkspace did not stay with specified path
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59332 customWorkspace did not stay with specified path Change By: Daniel Beck Component/s: pipeline Component/s: core 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.201883.1568298953000.6507.1570895760139%40Atlassian.JIRA.
[JIRA] (JENKINS-59199) E-mail Notification - Stack trace
Title: Message Title Daniel Beck updated JENKINS-59199 Jenkins / JENKINS-59199 E-mail Notification - Stack trace Change By: Daniel Beck Status: In Review Closed Resolution: Fixed 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.201642.1567493023000.6505.1570895700277%40Atlassian.JIRA.
[JIRA] (JENKINS-59199) E-mail Notification - Stack trace
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59199 E-mail Notification - Stack trace Change By: Daniel Beck Priority: Blocker Minor 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.201642.1567493023000.6503.1570895460162%40Atlassian.JIRA.
[JIRA] (JENKINS-59396) AWT initialized even with -Djava.awt.headless=true
Title: Message Title Daniel Beck commented on JENKINS-59396 Re: AWT initialized even with -Djava.awt.headless=true Are you sure you're setting the system property correctly? How can you tell? 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.201953.1568647597000.6500.1570895400146%40Atlassian.JIRA.
[JIRA] (JENKINS-59665) Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59665 Rework sorting for the Enabled and Uninstall columns of Installed in Plugin Manager Change By: Daniel Beck Labels: newbie-friendly 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.202357.1570213644000.6498.1570895220136%40Atlassian.JIRA.
[JIRA] (JENKINS-59684) Admin monitor "info" are not styled in popup mode
Title: Message Title Daniel Beck updated JENKINS-59684 Will be in the upcoming weekly 2.200. Jenkins / JENKINS-59684 Admin monitor "info" are not styled in popup mode Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: jenkins-2.200 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed
[JIRA] (JENKINS-59681) Version selection for Jenkins Automatic Upgrade feature
Title: Message Title Daniel Beck commented on JENKINS-59681 Re: Version selection for Jenkins Automatic Upgrade feature Would not hold my breath here as this requires a significant project infra extension for very little benefit (just hold off updating for a week, or go the manual way). Speaking as a co-maintainer of core and the update center, you can probably consider this "Won't Fix" unless you're interested in doing this yourself, or able to get someone else to take an interest here. 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.202379.1570438654000.6493.1570895160316%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Daniel Beck edited a comment on JENKINS-59758 Re: hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found [~eengstrom]Hi Erik Eric , I'm the original author of this feature. There's a bunch of technical details in this report of you digging into the internals, but I do not understand what exactly the behavior is that you're seeing, and what you expect to see instead, and why. Could you provide these?Thanks! 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.202481.1570833476000.6488.1570894980264%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-59758 hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found Change By: Daniel Beck Component/s: update-sites-manager-plugin 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.202481.1570833476000.6490.1570894980300%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title Daniel Beck commented on JENKINS-59758 Re: hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found Eric Engstrom Hi Erik, I'm the original author of this feature. There's a bunch of technical details in this report of you digging into the internals, but I do not understand what exactly the behavior is that you're seeing, and what you expect to see instead, and why. Could you provide these? Thanks! 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.202481.1570833476000.6485.1570894920215%40Atlassian.JIRA.
[JIRA] (JENKINS-42720) ConcurrentModificationException when serializing LockableResourcesManager
Title: Message Title Tobias Gruetzmacher commented on JENKINS-42720 Re: ConcurrentModificationException when serializing LockableResourcesManager I suspect this was about the same issue as JENKINS-44597, which was fixed in release 2.1 - If you see similar issues, please open a new issue with new evidence. 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.179679.1489419394000.6478.1570893660674%40Atlassian.JIRA.
[JIRA] (JENKINS-42720) ConcurrentModificationException when serializing LockableResourcesManager
Title: Message Title Tobias Gruetzmacher resolved as Fixed Jenkins / JENKINS-42720 ConcurrentModificationException when serializing LockableResourcesManager Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Fixed Released As: lockable-resources 2.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.179679.1489419394000.6480.1570893660740%40Atlassian.JIRA.
[JIRA] (JENKINS-44597) ConcurrentModificationException on releasing lock
Title: Message Title Tobias Gruetzmacher commented on JENKINS-44597 Re: ConcurrentModificationException on releasing lock This seems to have been addressed in release 2.1, please reopen with new evidence if it is still an issue. 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.182452.149630054.6468.1570893480925%40Atlassian.JIRA.
[JIRA] (JENKINS-44597) ConcurrentModificationException on releasing lock
Title: Message Title Tobias Gruetzmacher resolved as Fixed Jenkins / JENKINS-44597 ConcurrentModificationException on releasing lock Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Fixed Released As: lockable-resources 2.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.182452.149630054.6470.1570893481316%40Atlassian.JIRA.
[JIRA] (JENKINS-59760) "Fields" parameter does not work with jiraJqlSearch
Title: Message Title
Sergey Zhemzhitsky created an issue
Jenkins / JENKINS-59760
"Fields" parameter does not work with jiraJqlSearch
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2019-10-12 15:01
Environment:
JIRA Cloud
Priority:
Major
Reporter:
Sergey Zhemzhitsky
It seems that "fields" parameter does not work with jiraJqlSearch or at least it's unclear how it should be used properly. Here is the query to get 3 issues with key and summary fields only
def issues = jiraJqlSearch(
jql: "project='AM'",
fields: 'key,summary',
site: 'jira',
maxResults: 3
)
and this snippet returns the following error
[Pipeline] jiraJqlSearch
JIRA: Site - jira - Search JQL: project='AM' startAt: 0 maxResults: 3
Error Code: 400
Error Message: {"errorMessages":["Can not deserialize instance of java.util.ArrayList out of VALUE_STRING token\n at [Source: org.apache.catalina.connector.CoyoteInputStream@2e4bdc21; line: 1, column: 51] (through reference chain: com.atlassian.jira.rest.v2.search.SearchRequestBean[\"fields\"])"]}
Trying to pass fields as array like the following
[JIRA] (JENKINS-43002) Unable to lock by label in a declarative pipeline script
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-43002 Unable to lock by label in a declarative pipeline script Change By: Tobias Gruetzmacher Priority: Blocker Minor 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.180016.1490132375000.6448.157089946%40Atlassian.JIRA.
[JIRA] (JENKINS-44515) Implement lock_any option for pipelines
Title: Message Title Tobias Gruetzmacher resolved as Fixed This should be possible with the API implemented in JENKINS-40997, closing. If I'm missing something, please reopen, assign to me and describe what is missing for a proper solution (As always, pull requests welcome). Jenkins / JENKINS-44515 Implement lock_any option for pipelines Change By: Tobias Gruetzmacher Status: Open Resolved Resolution: Fixed Released As: lockable-resources 1.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-44950) Support a quantity of zero required resources
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-44950 Support a quantity of zero required resources Change By: Tobias Gruetzmacher Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 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.183025.1497643509000.6440.157000179%40Atlassian.JIRA.
[JIRA] (JENKINS-44950) Support a quantity of zero required resources
Title: Message Title
Tobias Gruetzmacher commented on JENKINS-44950
Re: Support a quantity of zero required resources
Does this fix in release 2.6 from today help? This allows an "empty" lock when using the "extra" list:
def locks = []
if (cond) {
locks << [quantity: 1, resource: 'foo']
}
lock(extra: locks) {
// some block
}
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.183025.1497643509000.6436.1570888740184%40Atlassian.JIRA.
[JIRA] (JENKINS-48375) Jenkins RSS feeds are actually Atom feeds
Title: Message Title Daniel Beck closed an issue as Fixed Fix will be released this weekend in 2.200 Jenkins / JENKINS-48375 Jenkins RSS feeds are actually Atom feeds Change By: Daniel Beck Status: Open Closed Resolution: Fixed Released As: jenkins-2.200 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
[JIRA] (JENKINS-45131) Locking Resources is slow
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-45131 Locking Resources is slow Change By: Tobias Gruetzmacher Assignee: Tobias Gruetzmacher 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.183231.1498473858000.6405.1570886160426%40Atlassian.JIRA.
[JIRA] (JENKINS-45131) Locking Resources is slow
Title: Message Title Tobias Gruetzmacher commented on JENKINS-45131 Re: Locking Resources is slow Is this still an issue, even with JENKINS-45821 fixed? If yes, can you provide a stack dump when the system is in such a state (maybe by private mail to me)? 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.183231.1498473858000.6403.1570886160395%40Atlassian.JIRA.
[JIRA] (JENKINS-38906) Remove lock resource name from global configuration when lock is released
Title: Message Title Tobias Gruetzmacher resolved as Fixed This should be fixed with the ephemeral lock support in release 2.6 - Everthing that is created automatically is now removed automatically. Jenkins / JENKINS-38906 Remove lock resource name from global configuration when lock is released Change By: Tobias Gruetzmacher Status: Open Resolved Assignee: Antonio Muñiz Tobias Gruetzmacher Resolution: Fixed Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59413) Links to plugin docs should consistently point to plugins site
Title: Message Title Zbynek Konecny assigned an issue to Unassigned Jenkins / JENKINS-59413 Links to plugin docs should consistently point to plugins site Change By: Zbynek Konecny Assignee: Zbynek Konecny 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.201975.1568760472000.6342.1570885140052%40Atlassian.JIRA.
[JIRA] (JENKINS-59413) Links to plugin docs should consistently point to plugins site
Title: Message Title Zbynek Konecny closed an issue as Duplicate Jenkins / JENKINS-59413 Links to plugin docs should consistently point to plugins site Change By: Zbynek Konecny Status: Open Closed Resolution: Duplicate 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.201975.1568760472000.6341.1570885080109%40Atlassian.JIRA.
[JIRA] (JENKINS-46235) API does not allow to remove lockable resource
Title: Message Title Tobias Gruetzmacher commented on JENKINS-46235 Re: API does not allow to remove lockable resource As I try to understand the usecase here (and the blatant violation of script security ): Is the introduction of "ephemeral" resources covering your use cases or do you need something more complex? If you need something more complex, maybe a new set of pipeline steps with proper permission checks is the better way? The LockableResourcesManager API was never designed for use in pipeline... (As always, pull requests welcome, but I suspect such a feature could even be its own plugin "extending" the lockable-resources plugin) 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.184480.1502885271000.6333.1570884840267%40Atlassian.JIRA.
[JIRA] (JENKINS-48026) can not reserve lockable resources with quot in name via UI
Title: Message Title Tobias Gruetzmacher resolved as Fixed This might haven been "accidentally" fixed by the fix for SECURITY-1361... Jenkins / JENKINS-48026 can not reserve lockable resources with quot in name via UI Change By: Tobias Gruetzmacher Status: Open Resolved Assignee: Tobias Gruetzmacher Resolution: Fixed Released As: lockable-resources 2.5? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59759) localhost not allowed for jeknins with gitlab-branch-source-plugin
Title: Message Title ebundy ebundy created an issue Jenkins / JENKINS-59759 localhost not allowed for jeknins with gitlab-branch-source-plugin Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-10-12 11:46 Environment: Ubuntu 18.04.2 LTS / Jenkins Blue Ocean on docker with the network of the host Priority: Minor Reporter: ebundy ebundy Hello, Not sure whether that is a bug. Feel free to requalify it if needed. My current scenario : running the Jenkins application in a docker container, and running the container with the network of the docker host (–network=host as arg). configuring a multibranch pipeline project with Gitlab as branch source. clicking save We get on the UI (and in the log) that exception : java.lang.IllegalStateException: Jenkins URL cannot start with http://localhost URL is: http://localhost:8081/ at io.jenkins.plugins.gitlabbranchsource.GitLabHookCreator.checkURL(GitLabHookCreator.java:167) at io.jenkins.plugins.gitlabbranchsource.GitLabHookCreator.getHookUrl(GitLabHookCreator.java:154) at io.jenkins.plugins.gitlabbranchsource.GitLabHookCreator.register(GitLabHookCreator.java:85) at io.jenkins.plugins.gitlabbranchsource.GitLabSCMSource.afterSave(GitLabSCMSource.java:752) at
[JIRA] (JENKINS-50618) Provide information in the console about who owns a lock when waiting
Title: Message Title Tobias Gruetzmacher resolved as Fixed This is now fixed (for better or worse) in 2.6 - I didn't think about the information disclosure issue, will discuss with contributors... Jenkins / JENKINS-50618 Provide information in the console about who owns a lock when waiting Change By: Tobias Gruetzmacher Status: Open Resolved Assignee: Tobias Gruetzmacher Resolution: Fixed Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-55486) If lock() creates a new resource, there should be a choice to make it temporary
Title: Message Title Tobias Gruetzmacher updated JENKINS-55486 Released with 2.6 Jenkins / JENKINS-55486 If lock() creates a new resource, there should be a choice to make it temporary Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 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,
[JIRA] (JENKINS-55182) CasC compatibility with Lockable Resource plugin
Title: Message Title Tobias Gruetzmacher resolved as Fixed Jenkins / JENKINS-55182 CasC compatibility with Lockable Resource plugin Change By: Tobias Gruetzmacher Status: Open Resolved Assignee: Tobias Gruetzmacher Resolution: Fixed Released As: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 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
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Sean Ly updated an issue Jenkins / JENKINS-59651 PIPELINE_VERSION can not export to shell environment. Change By: Sean Ly Attachment: image-2019-10-12-16-32-14-716.png 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.202341.1570157505000.6304.1570869420198%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Sean Ly edited a comment on JENKINS-59651 Re: PIPELINE_VERSION can not export to shell environment. version 1.4 has this problem, rolling back to 1.3 does not git diff: !image-2019-10-12-16-32-14-716.png! 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.202341.1570157505000.6301.1570869360287%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Sean Ly edited a comment on JENKINS-59651 Re: PIPELINE_VERSION can not export to shell environment. version 1.4 has this problem, rolling back to 1.3 does not git diff: !image-2019-10-12-16-32-14-716.png! 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.202341.1570157505000.6298.1570869180192%40Atlassian.JIRA.
[JIRA] (JENKINS-59651) PIPELINE_VERSION can not export to shell environment.
Title: Message Title Sean Ly commented on JENKINS-59651 Re: PIPELINE_VERSION can not export to shell environment. version 1.4 has this problem, rolling back to 1.3 does not 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.202341.1570157505000.6295.1570869060228%40Atlassian.JIRA.
