[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ Sure. Does it work? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23930.1588982160144%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick commented on JENKINS-61937 Re: hpi:run fails on Java 8 when the plugin depends on 2.230+ This clearly looks like a case of maven-hpi-plugin being insufficiently robust. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23832.1588962540198%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.23830.1588962480160%40Atlassian.JIRA.
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick started work on JENKINS-55973 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23676.1588946949761%40Atlassian.JIRA.
[JIRA] (JENKINS-55973) Update Jenkins POM and Core to SpotBugs
Title: Message Title Jesse Glick commented on JENKINS-55973 Re: Update Jenkins POM and Core to SpotBugs What is the overall status here? Core is patched; do we need something done in plugin POMs? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197384.1549366215000.23679.1588946949923%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated JENKINS-62181 Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23226.1588863960268%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Labels: deadlock lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23223.1588863660166%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Component/s: core Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23214.1588863600894%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick started work on JENKINS-62181 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23221.1588863601389%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Assignee: Jeff Thompson Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23218.1588863601005%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62181 Remoting deadlock when launching remote agent Change By: Jesse Glick Labels: deadlock regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23209.1588863600713%40Atlassian.JIRA.
[JIRA] (JENKINS-62181) Remoting deadlock when launching remote agent
Title: Message Title Jesse Glick commented on JENKINS-62181 Re: Remoting deadlock when launching remote agent The “new” method was just an override of an existing synchronized method, though the deadlock does smell like a regression in the new code before the super call. You have a custom logger on hudson.remoting.Channel (or hudson.remoting) at FINE or below I think? As a workaround, try removing that logger. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206113.1588790553000.23205.1588863240399%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title Jesse Glick commented on JENKINS-49073 Re: build job propagate true propagates FAIL when state is UNSTABLE Should this bug be re-opened As a general rule: no, not unless the originally described bug was not in fact fixed. If a change causes some undesirable behavior, file a separate bug with a Link to the original. In this case there is no bug, your script was simply relying on undocumented behavior. The FlowInterruptedException does include all the same information, just in a DownstreamFailureCause rather than the Throwable.message. Anyway using a catch block and the exception here was the wrong idiom even before this change. Set propagate: false and inspect the resulting build object’s status and other fields. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187899.1516619705000.22560.1588765920379%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick started work on JENKINS-61937 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21137.1588600800290%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated JENKINS-61937 Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21139.1588600800404%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick assigned an issue to Daniel Beck Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21135.1588600740147%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick commented on JENKINS-61959 Re: CpsThread(Timeout) raises InterruptedException https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-an-asynchronous-step Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205843.1587205537000.21059.1588594020239%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 I should add that the motivating use case for JEP-222 is Jenkins running behind a reverse proxy (such as Kubernetes ingress), in which case TLS is typically terminated at the proxy. If the problem involves some sort of incompatibility between the TLS implementation in Tyrus (or whatever library it is using for that) on the client side vs. the TLS implementation in Jetty running on Java 11 on the server side, then it would presumably not affect this environment. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204765.1582603216000.21052.1588593960233%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 I have no immediate plans to work on this—Java 11 support in Jenkins remains more or less experimental. I would recommend running on Java 8 unless you have a particular reason you must run on 11. (In which case you can continue to use TCP inbound agents.) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204765.1582603216000.20431.1588362900209%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick resolved as Not A Defect A library is not a “custom step”, that would be implemented in Java (and there is one for HTTP calls already). You may not block the CPS VM thread. All operations must be asynchronous. Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-61959 CpsThread(Timeout) raises InterruptedException Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205843.1587205537000.20379.1588352040361%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title
Jesse Glick resolved as Won't Fix
I was trying
diff --git core/src/main/resources/lib/hudson/executors.jelly core/src/main/resources/lib/hudson/executors.jelly
index 4cd01bcadd..62eb9d3276 100644
--- core/src/main/resources/lib/hudson/executors.jelly
+++ core/src/main/resources/lib/hudson/executors.jelly
@@ -155,7 +155,7 @@ THE SOFTWARE.
-"${ajax==null and h.hasPermission(app.READ)}">
+"${ajax==null and h.hasPermission(app.READ) and not h.isCollapsed('executors')}">
"defer">
refreshPart('executors',"${rootURL}/${h.hasView(it,'ajaxExecutors')?it.url:''}ajaxExecutors");
diff --git core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/lib/hudson/queue.jelly
index 776c4ed46a..93b6eb5560 100644
--- core/src/main/resources/lib/hudson/queue.jelly
+++ core/src/main/resources/lib/hudson/queue.jelly
@@ -101,7 +101,7 @@ THE SOFTWARE.
- "${ajax==null and h.hasPermission(app.READ)}">
+ "${ajax==null and h.hasPermission(app.READ) and not h.isCollapsed('buildQueue')}">
"defer">
refreshPart('buildQueue',"${rootURL}/${h.hasView(it,'ajaxBuildQueue')?it.url:''}ajaxBuildQueue");
until I realized that the original feature included dynamic updates to the pane titles, which still require HTTP requests to the master. Perhaps those should be dropped, to minimize load, but this would be a minor functional regression. And a three-way toggle (full, minimized, nonrefreshing) seems too awkward. The best we could do is slow down the refresh to, say, once per minute when minimized? Or use a lighter-weight REST call that does not involve rendering HTML?
Jenkins / JENKINS-62129
ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Change By:
Jesse Glick
Status:
In Progress Resolved
Resolution:
Won't Fix
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-62129 ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed Change By: Jesse Glick Labels: lts-candidate performance Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206043.1588266927000.20075.1588267620188%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick started work on JENKINS-62129 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206043.1588266927000.20071.1588266960195%40Atlassian.JIRA.
[JIRA] (JENKINS-62129) ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-62129 ajaxExecutors/ajaxBuildQueue posted even when pane is collapsed Issue Type: Bug Assignee: Jesse Glick Components: core Created: 2020-04-30 17:15 Labels: performance lts-candidate Priority: Major Reporter: Jesse Glick Normally Jenkins will post to ajaxBuildQueue and ajaxExecutors every few seconds to refresh these widgets. If you click the - button to collapse them, the results are not displayed...but the web requests are still sent, putting load on the master! We should just skip the refresh on a collapsed pane. Note that toggling the collapsed state involves a page refresh, so there is no risk of missing updates if you click + to expand. Add Comment
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick updated JENKINS-61787 Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.20006.1588260600093%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation No, I am not maintaining these plugins, sorry. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.19939.1588250940195%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation Not sure offhand. Bug somewhere. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.19925.1588250340249%40Atlassian.JIRA.
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick updated JENKINS-62097 Jenkins / JENKINS-62097 Permit multiple webhook secrets to be registered Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206007.1588186126000.19642.1588187100087%40Atlassian.JIRA.
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick started work on JENKINS-62097 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206007.1588186126000.19628.1588186320085%40Atlassian.JIRA.
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-62097 Permit multiple webhook secrets to be registered Issue Type: Improvement Assignee: Jesse Glick Components: github-plugin Created: 2020-04-29 18:48 Priority: Minor Reporter: Jesse Glick It is good that you can verify signatures of webhooks from GitHub (JENKINS-33974) but an unfortunate restriction that you are limited to listing only one webhook secret. This would make it more difficult to configure multiple webhooks, or mixtures of manual webhooks and Apps, on a single Jenkins service. It would be useful to be able to set a list of webhook secrets, where an incoming hook would just need to match one of them. Add Comment
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Jesse Glick commented on JENKINS-60480 Re: github is deprecating basic authentication using password You can certainly use a PAT, but note that JENKINS-57351 was released which allows github-branch-source to use App authentication. Not currently available for non-multibranch use cases, though it has been proposed to push this code down into the github-api library. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203567.1576268869000.19493.1588175280338%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Released As: https://github.com/jenkinsci/github-branch-source-plugin/releases/tag/github-branch-source- 2.7. 0 1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.19445.1588175162146%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated JENKINS-57351 Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.19469.1588175162484%40Atlassian.JIRA.
[JIRA] (JENKINS-48762) Unsigned Webhooks are always accepted
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-48762 Unsigned Webhooks are always accepted Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187529.1514927303000.19441.1588174860413%40Atlassian.JIRA.
[JIRA] (JENKINS-48012) Webhook signature checking is skipped if incoming webhook has no signature
Title: Message Title Jesse Glick updated JENKINS-48012 Jenkins / JENKINS-48012 Webhook signature checking is skipped if incoming webhook has no signature Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/github-plugin/releases/tag/v1.29.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186551.1510689021000.19434.1588174800588%40Atlassian.JIRA.
[JIRA] (JENKINS-48012) Webhook signature checking is skipped if incoming webhook has no signature
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48012 Webhook signature checking is skipped if incoming webhook has no signature Change By: Jesse Glick Labels: security Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186551.1510689021000.19427.1588174740404%40Atlassian.JIRA.
[JIRA] (JENKINS-33974) Add option to verify "secret" token
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-33974 Add option to verify "secret" token Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/github-plugin/releases/tag/v1.21.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169465.1459504593000.19422.1588174620422%40Atlassian.JIRA.
[JIRA] (JENKINS-41827) JenkinsRule mode to use realistic class loading
Title: Message Title Jesse Glick commented on JENKINS-41827 Re: JenkinsRule mode to use realistic class loading Optional dependencies (JENKINS-19508) could also be verified by a harness which allowed some of the plugins in the test classpath to be omitted from the set. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178674.1486499544000.18241.1587992340967%40Atlassian.JIRA.
[JIRA] (JENKINS-61972) Time is wrongly displayed on running Jobs
Title: Message Title Jesse Glick commented on JENKINS-61972 Re: Time is wrongly displayed on running Jobs Daniel Beck says this is due to JENKINS-19887. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205861.1587378754000.17635.1587763320159%40Atlassian.JIRA.
[JIRA] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Jesse Glick commented on JENKINS-21942 Re: Unreliable defaulting of Jenkins.workspaceDir Needs core changes I think. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153719.1393283635000.17633.1587763140663%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Jesse Glick commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Sorry, I am not familiar with ProtocolStack really. You can try WebSocket mode to see if it behaves any better. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.17480.1587753060484%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Jesse Glick Labels: remoting Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.17478.1587753060406%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: @libs pseudo-workspace collision due to branch name truncation The workspace management system introduced in JENKINS-2111 is enabled for all projects, not merely multibranch. I had thought this would affect the pseudo-workspaces used by workflow-cps-global-lib, but on closer inspection that seems to not be the issue. Possibly a bug in WorkspaceLocatorImpl. Would need to dig into a reproduction test case. Is /var/jenkins_home/workspace/workspaces.txt not tracking the various branch projects? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.17475.1587752700259%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60969 @libs pseudo-workspace collision due to branch name truncation Change By: Jesse Glick Summary: Unwanted job interaction if using global pipeline libraries @libs pseudo-workspace collision due to branch name truncation Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.17374.1587745440223%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Jesse Glick commented on JENKINS-60969 Re: Unwanted job interaction if using global pipeline libraries try -Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.17371.1587745380380%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60969 Unwanted job interaction if using global pipeline libraries Change By: Jesse Glick Component/s: branch-api-plugin Component/s: workflow-cps-global-lib-plugin Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick updated JENKINS-61787 Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.29 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.16771.1587678720119%40Atlassian.JIRA.
[JIRA] (JENKINS-61997) EmptyStackException from CpsFlowExecution.onProgramEnd
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61997 EmptyStackException from CpsFlowExecution.onProgramEnd Change By: Jesse Glick Environment: CloudBees Core 2.222.2.1-rolling (I think) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205888.1587492081000.15015.1587492180061%40Atlassian.JIRA.
[JIRA] (JENKINS-61997) EmptyStackException from CpsFlowExecution.onProgramEnd
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61997 EmptyStackException from CpsFlowExecution.onProgramEnd Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2020-04-21 18:01 Priority: Minor Reporter: Jesse Glick No idea how to reproduce; saw this after startup about a possibly stuck/broken build: ... WARNING org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService reportProblem Unexpected exception in CPS VM thread: CpsFlowExecution[Owner[...]] java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onProgramEnd(CpsFlowExecution.java:1236) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:423) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$400(CpsThreadGroup.java:96) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:312) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:276) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:67) Not entirely obvious what the most graceful response is here. Call createPlaceholderNodes?
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Jesse Glick commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Our pipeline is triggered by GitLab's Merge Request events. Note that an alternate solution in this case is to use the GitLab branch source plugin, so that each MR corresponds to a distinct job. Obviously that is a big change with other impacts. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187125.1513079616000.15001.1587488520348%40Atlassian.JIRA.
[JIRA] (JENKINS-61950) Environment variables with '$' have '$$' when used in sh step inside a container step.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61950 Environment variables with '$' have '$$' when used in sh step inside a container step. Change By: Jesse Glick Labels: kubernetes-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205830.1587134969000.13202.1587138120157%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Jesse Glick updated JENKINS-61340 Jenkins / JENKINS-61340 Cannot launch windows pods Change By: Jesse Glick Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204921.1583349755000.13178.1587133020842%40Atlassian.JIRA.
[JIRA] (JENKINS-61340) Cannot launch windows pods
Title: Message Title Jesse Glick resolved as Not A Defect Jenkins / JENKINS-61340 Cannot launch windows pods Change By: Jesse Glick Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204921.1583349755000.13180.1587133020902%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick commented on JENKINS-61371 Re: API tokens not persisted until user config screen is saved FTR: https://feedback.cloudbees.com/app/#/case/20344 https://feedback.cloudbees.com/app/#/case/23357 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205024.1583509348000.13137.1587128460188%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.12858.1587074943876%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick commented on JENKINS-61371 Re: API tokens not persisted until user config screen is saved James Nord may have seen this recently. Just happened to me now in CloudBees Core. There was an empty in $JENKINS_HOME/users/*/config.xml. Not sure what triggers this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205024.1583509348000.12711.1587064980268%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Jesse Glick commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Rather than messing around with workarounds, you should stop abusing the build description for this purpose. It is designed for a small one-line description, like a short phrase. If you want to display some big blob of text on the build main page, find or write a plugin with a publisher which lets you create an action with a main view. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.12001.1586973841738%40Atlassian.JIRA.
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title Jesse Glick commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 Jesse Glick, any plan to fix it? Me? No, I do not work on this plugin. If it has a maintainer, it would be up to them. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11783.1586961121474%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title Jesse Glick commented on JENKINS-49073 Re: build job propagate true propagates FAIL when state is UNSTABLE The second part of the "unstable -> success" stage is never executed. As designed. Your parent job should terminate at that point with an UNSTABLE status. This change does not make the build step complete normally; it just makes the exception thrown indicate to the Pipeline machinery that (if uncaught) the build should have the indicated status. If you do not want that, then use propagate: false as before. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187899.1516619705000.11566.1586953380685%40Atlassian.JIRA.
[JIRA] (JENKINS-61893) Warn about CLI command overrides or avoid them all
Title: Message Title Jesse Glick commented on JENKINS-61893 Re: Warn about CLI command overrides or avoid them all Yes but this is just the regular behavior of extension points, not an error, and it is more apparent what is going on. It seems much less likely that the author of this plugin would have accidentally copied a CLICommand implementation than what actually happened, which is that they overrode a method and copied the annotations from the supertype (possibly prompted by an IDE, possibly by analogy with nullness annotations and the like). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205766.1586868666000.10905.1586871900133%40Atlassian.JIRA.
[JIRA] (JENKINS-61893) Warn about CLI command overrides or avoid them all
Title: Message Title Jesse Glick commented on JENKINS-61893 Re: Warn about CLI command overrides or avoid them all If a particular code pattern leads to a runtime error like this, we should define an annotation process for CLIMethod which reports the situation as an error. Then when the plugin is built against a newer core version the build will fail with an explanation. More broadly, I would recommend deprecating CLIMethod in favor of explicit CLICommand using the regular extension point mechanism. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205766.1586868666000.10874.1586870940810%40Atlassian.JIRA.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Jesse Glick commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Support Blue Ocean - alike browsing of Pipelines inside Jenkins web UI Makes no sense. B.O. already supports this. I would also remove the component, because it is likely to become a separate plugin if it gets implemented. Also makes no sense. The limitation is specifically in the stage view plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168557.1456509661000.10585.1586864883788%40Atlassian.JIRA.
[JIRA] (JENKINS-28942) Allow plugins to declare that they do not use certain implied dependencies
Title: Message Title Jesse Glick commented on JENKINS-28942 Re: Allow plugins to declare that they do not use certain implied dependencies This issue has nothing to do with Java versions. Maybe you are referring to JENKINS-55681? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163400.1434531203000.8972.1586520900234%40Atlassian.JIRA.
[JIRA] (JENKINS-47510) RemoteLauncher.isUnix() is not overridden - always returns master OS
Title: Message Title Jesse Glick resolved as Not A Defect Hah, indeed. https://github.com/jenkinsci/ssh-slaves-plugin/pull/179 Jenkins / JENKINS-47510 RemoteLauncher.isUnix() is not overridden - always returns master OS Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-47010) Jenkins should not deploy installer GUI to headless SSH Agents
Title: Message Title Jesse Glick commented on JENKINS-47010 Re: Jenkins should not deploy installer GUI to headless SSH Agents I think it is not about whether the agent is “headless”, it is whether it is inbound (JNLPLauncher) or not (SSH and many others). So I think the bug is in SlaveInstallerModule. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185390.1505974475000.8272.1586354880143%40Atlassian.JIRA.
[JIRA] (JENKINS-47510) RemoteLauncher.isUnix() is not overridden - always returns master OS
Title: Message Title Jesse Glick commented on JENKINS-47510 Re: RemoteLauncher.isUnix() is not overridden - always returns master OS This launcher is only used to do a JDK installation. Actual build steps would be using the core RemoteLauncher instead. So I think this is invalid. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185967.1508353562000.8270.1586354700224%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb It is still a high-risk change due to patches under the hood of Remoting engine (JNLP4 might be potentially affected by changes) I cannot see how. None of the affected code is outside the WebSocket-specific handler method used in the -webSocket mode new in 2.222.x, except for a new method in AbstractByteBufferCommandTransport which is newly called in that modified code. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.7888.1586300340496%40Atlassian.JIRA.
[JIRA] (JENKINS-61808) Always encrypt f:password values, not just those backed by Secret
Title: Message Title Jesse Glick updated JENKINS-61808 Jenkins / JENKINS-61808 Always encrypt f:password values, not just those backed by Secret Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205653.1585961043000.7652.1586276101065%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Jesse Glick commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Anyway presence of another version of the library in an unrelated plugin should not cause errors. Jenkins would load each in an independent class loader. We need steps to reproduce from scratch. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.7522.1586261340430%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Jesse Glick commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Oleg Nenashev that search URL does not mention anything about a CloudBees Flow plugin. Where are you getting this from? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.7519.1586261280256%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title Jesse Glick resolved as Fixed Laurent Hory please do not reopen. If you believe you have discovered a regression, file a separate issue linked to this one with complete, minimal steps to reproduce from scratch. Jenkins / JENKINS-58290 WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick updated JENKINS-61787 Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.5368.1585844160181%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick started work on JENKINS-61787 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.5367.1585844160152%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.5366.1585844100315%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick commented on JENKINS-61787 Re: jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Only apparent implementation: https://github.com/jenkinsci/scala-junit-name-decoder-plugin/blob/e172d93fd3e74f3610db658f0b94d029321d2305/src/main/java/org/jenkinsci/plugins/scalajunitnamedecoder/ScalaTestNameTransformer.java Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.5346.1585843560118%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2020-04-02 15:58 Labels: remoting Priority: Blocker Reporter: Jesse Glick https://ci.jenkins.io/job/Plugins/job/github-branch-source-plugin/job/PR-291/4/console failed with Recording test results Remote call on EC2 (aws) - Ubuntu 18.04 LTS (i-011fe09e35adc9532) failed Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (aws) - Ubuntu 18.04 LTS (i-011fe09e35adc9532) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at hudson.FilePath.act(FilePath.java:1069) at hudson.FilePath.act(FilePath.java:1058) at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137) at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:52) at hudson.tasks.junit.pipeline.JUnitResultsStepExecution.run(JUnitResultsStepExecution.java:25) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) java.lang.NoClassDefFoundError: Could not
[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change
Title: Message Title Jesse Glick resolved as Cannot Reproduce Hard to say offhand what might be wrong. Most likely something in your environment / configuration. Jenkins / JENKINS-59096 Mercurial plugin stops working after password change Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60455) Credentials block in mercurial plugins shows Oops!
Title: Message Title Jesse Glick resolved as Incomplete Perhaps you somehow updated the mercurial plugin without a matching update to credentials plugin. Should not happen if you use the update center but who knows. Jenkins / JENKINS-60455 Credentials block in mercurial plugins shows Oops! Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated JENKINS-30182 Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164765.1440703818000.4514.1585763401118%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.4516.1585763401206%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Released As: 2.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164765.1440703818000.4500.1585762381140%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.4498.1585762381096%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title
Jesse Glick updated JENKINS-30182
Not sure about the rest, but the {{java.lang.ClassCastException: hudson.views.BuildFilterColumn$JobWrapper cannot be cast to hudson.model.TopLevelItem at jenkins.model.Jenkins.getRootDirFor(Jenkins.java:306)}} should have been fixed by PR 17 (was causing a test failures when updating the Jenkins baseline).
Jenkins / JENKINS-30182
view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Change By:
Jesse Glick
Status:
Open Fixed but Unreleased
Assignee:
Jacob Robertson Jesse Glick
Resolution:
Fixed
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Labels: folders Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.20.1564983968000.4477.1585762080188%40Atlassian.JIRA.
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Component/s: cloudbees-folder-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.20.1564983968000.4474.1585762020186%40Atlassian.JIRA.
[JIRA] (JENKINS-56813) Job filter: exclude disabled jobs does not work
Title: Message Title Jesse Glick resolved as Not A Defect To create a view showing all enabled jobs, add a Job Statuses Filter with Disabled checked and select Include Unmatched - Add jobs that don't match this filter. Do not select jobs or check the regular _expression_ filter option. Or you can use the core built-in filter without using this plugin. See JENKINS-51143 for a fuller explanation. Using a GUI to define a boolean predicate is not great, and the particular way this is handled in Jenkins list views is especially confusing. Jenkins / JENKINS-56813 Job filter: exclude disabled jobs does not work Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.4446.1585761300616%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Since I do not much trust the mock-based tests in this plugin, here is my interactive verification: Run 2.222.1, setup wizard to get admin user but skipping plugin installation. From Available, install view-job-filters (from UC: 2.1.1), workflow-basic-steps, workflow-cps, workflow-job. Create an enabled freestyle project, a disabled one, an enabled Pipeline project, and a disabled one. (Otherwise empty—no need for build steps or any builds.) Create a custom list view using the core Status Filter of Disabled jobs only, selecting also Use a regular _expression_ to include jobs into the view with .+; and another with Enabled jobs only. These views correctly show the disabled or enabled freestyle and Pipeline projects, respectively. Create a custom list view using the plugin-provided Job Statuses Filter with Disabled checked and Include Matched - Add jobs that match this filter; and another with Include Unmatched - Add jobs that don't match this filter. Note that the former includes the disabled freestyle project yet omits the disabled Pipeline project, while the latter omits the disabled freestyle project yet includes the disabled Pipeline project, reproducing the bug. Build view-job-filter.hpi from #18, install via Plugin Manager » Advanced, restart. Now running 2.2-SNAPSHOT. See that the plugin-based views now correctly handle the disabled Pipeline project, matching the behavior of the core-based views. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-51143 Re: List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs #12 was a continuation of #11 Yes, but actually the three lines of code in #11 which actually fixed this issue were right, and #12 did something different and unnecessarily complex. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.4305.1585754400310%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Component/s: pipeline Component/s: sectioned-view-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.3817.1585689121157%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick assigned an issue to Jesse Glick #11 has the right fix (replace AbstractProject with ParameterizedJob) but is not mergeable as is. Trying to do some preparatory cleanup in separate PRs. Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Assignee: Timothy Bingaman Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190437.1525450293000.3819.1585689121184%40Atlassian.JIRA.
[JIRA] (JENKINS-61742) host network not saved
Title: Message Title Jesse Glick assigned an issue to Unassigned Please do not assign issues (except to yourself, if and when planning to work on a fix). Jenkins / JENKINS-61742 host network not saved Change By: Jesse Glick Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205571.1585574166000.3573.1585657860187%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jesse Glick commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Antonio Muñiz Scripted? (or “Declarative” with script blocks?) It is unknown whether a general fix is feasible for Scripted. Would likely require a redesign of the CPS transformer, which is possible in principle but this is one of the most difficult areas of Jenkins to edit. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.3078.1585584721975%40Atlassian.JIRA.
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick resolved as Cannot Reproduce Hmm, cannot reproduce now. I know I have seen this at least twice. Jenkins / JENKINS-61371 API tokens not persisted until user config screen is saved Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Oliver Gondža remember that if backporting to 2.222.x, we would want to create a component backport so as to get something like remoting.version=4.2.1. Otherwise we would be including https://github.com/jenkinsci/remoting/pull/369 in LTS, which includes a couple of production source code changes, albeit small (Util.mkdirs → Files.createDirectories). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.482.1585230300247%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick updated JENKINS-61409 Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.229 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.473.158523850%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick updated JENKINS-61409 Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.10358.1584728400698%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Released As: 2. 6 7 . 1 or later 0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199127.1557217283000.10141.1584708541925%40Atlassian.JIRA.
