[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Olivier Lamy commented on JENKINS-62068 Re: jetty ALPN incompatibility - java8 u 252 some details here https://webtide.com/jetty-alpn-java-8u252/ 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.205967.1588006254000.18625.1588020720270%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman edited a comment on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException [~stodorov]What version of Blue Ocean are your you running ? 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.205962.1588001733000.18628.1588020720309%40Atlassian.JIRA.
[JIRA] (JENKINS-62025) workflow-job plugin js error with IE11
Title: Message Title Olivier Lamy updated JENKINS-62025 Jenkins / JENKINS-62025 workflow-job plugin js error with IE11 Change By: Olivier Lamy Status: Open Fixed but Unreleased 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 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.205914.1587618166000.18630.1588020780182%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Also what happens if you downgrade multibranch to 2.20? 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.205962.1588001733000.18634.1588020780274%40Atlassian.JIRA.
[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration
Title: Message Title Daniel Beck commented on JENKINS-61438 Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration I'm surprised it took so long for my nonsense there to break :-/ 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.205116.158394316.18636.1588021140244%40Atlassian.JIRA.
[JIRA] (JENKINS-62073) Upgrade automatically causes completely reset
Title: Message Title Giacomo Boccardo created an issue Jenkins / JENKINS-62073 Upgrade automatically causes completely reset Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-27 21:33 Environment: * Any Jenkins version since years, 2.222.1 too * CentOS Linux release 7.7.1908 * JVM 1.8.0_131-b11 (probably not relevant, it happened also using JVM 7) Labels: upgrade automatically reset Priority: Critical Reporter: Giacomo Boccardo When I upgrade Jenkins through the "Or Upgrade Automatically" button the result is a completely new installation where any job and any Jenkins configuration is completely reset. It's just like installing it from scratch. Jenkins is launched using the following command /home/jenkins/java/bin/java -Dcom.sun.akuma.Daemon=daemonized -Xmn128M -Xms1024M -Xmx6144M -DJENKINS_HOME=/home/jenkins/jenkins-home -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-same-origin allow-scripts; default-src 'self'; script-src * 'unsafe-inline'; img-src * data:; style-src * 'unsafe-inline'; font-src * -jar /home/jenkins/war/jenkins.war --webroot=/home/jenkins/jenkins-home --daemon --httpPort=8080 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 --logfile=/home/jenkins/log/jenkins.log and the log after the upgrade is
[JIRA] (JENKINS-62073) Upgrade automatically causes completely reset
Title: Message Title
Giacomo Boccardo updated an issue
Jenkins / JENKINS-62073
Upgrade automatically causes completely reset
Change By:
Giacomo Boccardo
When I upgrade Jenkins through the "Or Upgrade Automatically" button the result is a completely new installation where any job and any Jenkins configuration is completely reset. It's just like installing it from scratch.Jenkins is launched using the following command {noformat} {{ /home/jenkins/java/bin/java -Dcom.sun.akuma.Daemon=daemonized -Xmn128M -Xms1024M -Xmx6144M -DJENKINS_HOME=/home/jenkins/jenkins-home -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-same-origin allow-scripts; default-src 'self'; script-src * 'unsafe-inline'; img-src * data:; style-src * 'unsafe-inline'; font-src * -jar /home/jenkins/war/jenkins.war --webroot=/home/jenkins/jenkins-home --daemon --httpPort=8080 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 --logfile=/home/jenkins/log/jenkins.log {noformat } } and the log after the upgrade is { noformat { } }{{ Running from: /home/jenkins/war/jenkins.war }}{{ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMax is now deprecated }}{{ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMaxIdle is now deprecated }}{{ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @689ms to org.eclipse.jetty.util.log.JavaUtilLog }}{{ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file }}{{ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath }}{{ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00:04:53.875Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_131-b11 }}{{ [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet }}{{ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0 }}{{ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults }}{{ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60ms }}{{ [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /home/jenkins/jenkins-home found at: SystemProperties.getProperty("JENKINS_HOME") }}{{ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@29876704 \ {Jenkins v2.204.1,/,file:///home/jenkins/jenkins-home/,AVAILABLE}{/home/jenkins/jenkins-home} }}{{ [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@1972e513 \ {HTTP/1.1,[http/1.1]}{0.0.0.0:8080} }}{{ [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @20528ms }}{{ [id=21] INFO winstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled }}{{ [id=28] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization }}{{ [id=28] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins }}{{ [id=31] INFO jenkins.InitReactorRunner$1#onAttained
[JIRA] (JENKINS-62073) Upgrade automatically causes completely reset
Title: Message Title
Giacomo Boccardo updated an issue
Jenkins / JENKINS-62073
Upgrade automatically causes completely reset
Change By:
Giacomo Boccardo
When I upgrade Jenkins through the "Or Upgrade Automatically" button the result is a completely new installation where any job and any Jenkins configuration is completely reset. It's just like installing it from scratch.Jenkins is launched using the following command{ { code:bash} /home/jenkins/java/bin/java -Dcom.sun.akuma.Daemon=daemonized -Xmn128M -Xms1024M -Xmx6144M -DJENKINS_HOME=/home/jenkins/jenkins-home -Dhudson.model.DirectoryBrowserSupport.CSP=sandbox allow-same-origin allow-scripts; default-src 'self'; script-src * 'unsafe-inline'; img-src * data:; style-src * 'unsafe-inline'; font-src * -jar /home/jenkins/war/jenkins.war --webroot=/home/jenkins/jenkins-home --daemon --httpPort=8080 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20 --logfile=/home/jenkins/log/jenkins.log {code } } and the log after the upgrade is{ { code:java } }{{ Running from: /home/jenkins/war/jenkins.war }} {{ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMax is now deprecated }} {{ [id=1] WARNING winstone.Logger#logInternal: Parameter handlerCountMaxIdle is now deprecated }} {{ [id=1] INFO org.eclipse.jetty.util.log.Log#initialized: Logging initialized @689ms to org.eclipse.jetty.util.log.JavaUtilLog }} {{ [id=1] INFO winstone.Logger#logInternal: Beginning extraction from war file }} {{ [id=1] WARNING o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath }} {{ [id=1] INFO org.eclipse.jetty.server.Server#doStart: jetty-9.4.z-SNAPSHOT; built: 2019-05-02T00:04:53.875Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_131-b11 }} {{ [id=1] INFO o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet }} {{ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0 }} {{ [id=1] INFO o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults }} {{ [id=1] INFO o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 60ms }} {{ [id=1] INFO hudson.WebAppMain#contextInitialized: Jenkins home directory: /home/jenkins/jenkins-home found at: SystemProperties.getProperty("JENKINS_HOME") }} {{ [id=1] INFO o.e.j.s.handler.ContextHandler#doStart: Started w.@29876704 \ {Jenkins v2.204.1,/,file:///home/jenkins/jenkins-home/,AVAILABLE}{/home/jenkins/jenkins-home} }} {{ [id=1] INFO o.e.j.server.AbstractConnector#doStart: Started ServerConnector@1972e513 \ {HTTP/1.1,[http/1.1]}{0.0.0.0:8080} }} {{ [id=1] INFO org.eclipse.jetty.server.Server#doStart: Started @20528ms }} {{ [id=21] INFO winstone.Logger#logInternal: Winstone Servlet Engine v4.0 running: controlPort=disabled }} {{ [id=28] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization }} {{ [id=28] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins }} {{ [id=31] INFO jenkins.InitReactorRunner$1#
[JIRA] (JENKINS-61438) IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration
Title: Message Title Nikolas Falco commented on JENKINS-61438 Re: IllegalArgumentException for ChoiceParameter on bindJSON saving job configuration Than could be the time to review this PR https://github.com/stapler/stapler/pull/182#issuecomment-620219545 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.205116.158394316.18647.1588024380608%40Atlassian.JIRA.
[JIRA] (JENKINS-46648) first build of a pull request fails with stderr: fatal: Couldn't find remote ref
Title: Message Title Martin Rheumer commented on JENKINS-46648 Re: first build of a pull request fails with stderr: fatal: Couldn't find remote ref This is also causing a large issue for us, unfrotunately after an upgrade to Bitbucket as well . Is there a fix or anyone working on this problem ? 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.184985.1504620821000.18649.1588029240273%40Atlassian.JIRA.
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title Liam Newman commented on JENKINS-61875 Re: Run an jenkins stage with an merge commit message using jenkinsfile Sorry, this is a question not an issue or feature request. It should be taken one of the help channels. Please see https://www.jenkins.io/participate/help/ for options. 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.205741.1586700128000.18655.1588030200322%40Atlassian.JIRA.
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-61875 Run an jenkins stage with an merge commit message using jenkinsfile Change By: Liam Newman Status: Open Closed 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.205741.1586700128000.18657.1588030200406%40Atlassian.JIRA.
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title
Liam Newman commented on JENKINS-61875
Re: Run an jenkins stage with an merge commit message using jenkinsfile
Ah, but while we're at it: https://stackoverflow.com/a/56483499/1637252
when {
changelog '.*RELEASE.*'
}
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.205741.1586700128000.18659.1588030500124%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62065 The bread crumb navigation on the top of the job is not responding after clicking Apply Change By: Daniel Beck Summary: REGRESSION: The BreadCrumb bread crumb navigation on the top of the job is not responding after clicking Apply 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.205964.1588002509000.18665.1588031820550%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) REGRESSION: The BreadCrumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62065 REGRESSION: The BreadCrumb navigation on the top of the job is not responding after clicking Apply Change By: Daniel Beck Labels: 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.205964.1588002509000.18663.1588031820507%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck commented on JENKINS-62065 Re: The bread crumb navigation on the top of the job is not responding after clicking Apply This started happening after may be 2.226 2.230 actually. 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.205964.1588002509000.18667.1588032300246%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title
Daniel Beck edited a comment on JENKINS-62065
Re: The bread crumb navigation on the top of the job is not responding after clicking Apply
{quote}This started happening after may be 2.226{quote}2.230 actually. It still works on 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.205964.1588002509000.18669.1588032300272%40Atlassian.JIRA.
[JIRA] (JENKINS-46669) When setting up, "Continue as Admin" button can be made less confusing
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-46669 When setting up, "Continue as Admin" button can be made less confusing Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.234 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.185009.1504680543000.18678.1588032361292%40Atlassian.JIRA.
[JIRA] (JENKINS-61812) Read-only f:password field always shows "N/A"
Title: Message Title Daniel Beck updated JENKINS-61812 Jenkins / JENKINS-61812 Read-only f:password field always shows "N/A" Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.234 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.205659.1586000462000.18683.1588032361420%40Atlassian.JIRA.
[JIRA] (JENKINS-62001) Autocompletion dropdown UI looks broken
Title: Message Title Daniel Beck updated JENKINS-62001 Jenkins / JENKINS-62001 Autocompletion dropdown UI looks broken Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.234 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.205893.1587500364000.18673.1588032361193%40Atlassian.JIRA.
[JIRA] (JENKINS-61738) Session hijacking protection hardening
Title: Message Title Daniel Beck updated JENKINS-61738 Jenkins / JENKINS-61738 Session hijacking protection hardening Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.234 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.205567.1585559723000.18680.1588032361361%40Atlassian.JIRA.
[JIRA] (JENKINS-61207) Read-only system - System log access
Title: Message Title Daniel Beck updated JENKINS-61207 Jenkins / JENKINS-61207 Read-only system - System log access Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.234 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.204757.1582563739000.18675.1588032361230%40Atlassian.JIRA.
[JIRA] (JENKINS-60508) Nodes Patterns
Title: Message Title Ben Faucher updated an issue Jenkins / JENKINS-60508 Nodes Patterns Change By: Ben Faucher Priority: Minor Major 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.203599.1576511529000.18686.1588034280370%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov updated an issue Jenkins / JENKINS-62063 BlueOcean UI is broken due to ClassCastException Change By: Steve Todorov Environment: Jenkins 2.233Pipeline: Multibranch with defaults: 2.1Pipeline: Multibranch: 2.21 Blue Ocean: 1.23.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.205962.1588001733000.18688.1588034880209%40Atlassian.JIRA.
[JIRA] (JENKINS-60508) Nodes Patterns
Title: Message Title Ben Faucher commented on JENKINS-60508 Re: Nodes Patterns I am also seeing this exact issue with a non-kubernetes deployment. Jenkins master is running out of a docker container on an Ubuntu host, agent is an Ubuntu VM permanently connected over SSH. Jenkins v2.222.1 (alpine docker image) Role-strategy v2.16 Authorize-project v1.3.0 Agent is named "foo" Create a user with global read-only access called "builder" In Security > Manage and Assign Roles > Mange roles, create a node role Name: "foo-access" Pattern: "foo" In Security > Manage and Assign Roles > Assign Roles, assign the role to "builder" Create a new pipeline job set to use agent "foo" Configure pipeline to run as user "builder" Run pipeline. Build stalls indefinitely with this error: 19:34:07 Started by user Ben Faucher 19:34:07 Running as builder 19:34:07 Running in Durability level: PERFORMANCE_OPTIMIZED 19:34:09 [Pipeline] Start of Pipeline 19:34:22 [Pipeline] node 19:34:37 Still waiting to schedule task 19:34:37 ‘builder’ lacks permission to run on ‘foo’; ‘build-1’ doesn’t have label ‘foo’ Add Comment
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Hi Liam Newman I've updated the environment info - we're using BlueOcean 1.23.0. I have tried downgrading Pipeline: Multibranch to 2.20 and Pipeline: Multibranch Defaults to 2.0, but it didn't fix it. I have a feeling it's another plugin is causing this issue but I can't seem to find which one. 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.205962.1588001733000.18695.1588035300139%40Atlassian.JIRA.
[JIRA] (JENKINS-61982) jenkins.io docs for 'wait' parameter of pipeline 'build' step are incomplete
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61982 jenkins.io docs for 'wait' parameter of pipeline 'build' step are incomplete Change By: Mark Waite Summary: jenkins. . io docs for 'wait' parameter of pipeline 'build' step are 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, 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.205872.1587443136000.18698.1588037700072%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor commented on JENKINS-61591 Re: Using Stage view with mixed in/out of stage actions causes the build status to be wrong Fixed with https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/85 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.205288.1584636193000.18702.1588043700231%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor assigned an issue to Alex Taylor Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: Alex Taylor Assignee: Sam Van Oort Alex Taylor 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.205288.1584636193000.18705.1588043760202%40Atlassian.JIRA.
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Shivam Lahoti created an issue Jenkins / JENKINS-62074 Send build failure email to approver of pull request Issue Type: New Feature Assignee: Unassigned Components: mailer-plugin Created: 2020-04-28 03:31 Priority: Minor Reporter: Shivam Lahoti The "Send separate e-mails to individuals who broke the build" option sends emails to the commit's committers. However, there are cases when it's better to send emails to the commit's authors instead. We use Gerrit for hosting our Git repositories and its workflow consists in pushing commits to pseudo-branches for review. After the commits have been approved they are submitted (integrated) automatically into the real branch, but this action is performed by Gerrit which may have to rebase the original commit in order to be able to tuck it on top of the current branch's HEAD. In these cases, the actual commit's committer becomes an administrative user. In our case we configured it to be a user called gerrit with an email like ger...@ourdomain.com. So, for these commits it doesn's work to send notifications to the commit's committer. They should be sent to the commit's author instead. What I propose is that there should exist another configuration option where we could specify a list of emails (a Regexp would also do). If the committer's email matches one of the emails specified, then the notifications should be sent to the commit's author instead. This option should be subordinated to the "Send separate e-mails to individuals who broke the build" option.
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Shivam Lahoti updated an issue Jenkins / JENKINS-62074 Send build failure email to approver of pull request Change By: Shivam Lahoti The "Send separate e-mails to individuals who broke the build" option sends emails to the commit's committers. However, there are cases when it's better to send emails to the commit's authors instead.We use [Gerrit|https://www.gerritcodereview.com/] for hosting our Git repositories and its workflow consists in pushing commits to pseudo-branches for review. After the commits have been approved they are submitted (integrated) automatically into the real branch, but this action is performed by Gerrit which may have to rebase the original commit in order to be able to tuck it on top of the current branch's HEAD. In these cases, the actual commit's committer becomes an administrative user. In our case we configured it to be a user called *gerrit* with an email like *ger...@ourdomain.com*.So, for these commits it doesn's work to send notifications to the commit's committer. They should be sent to the commit's author instead.What I propose is that there should exist another configuration option where we could specify a list of emails (a Regexp would also do). If the committer's email matches one of the emails specified, then the notifications should be sent to the commit's author instead.This option should be subordinated to the "Send separate e-mails to individuals who broke the build" option. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title prakash raj assigned an issue to Unassigned Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: prakash raj Assignee: prakash raj 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.205288.1584636193000.18713.1588045020412%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title prakash raj assigned an issue to prakash raj Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: prakash raj Assignee: Alex Taylor prakash raj 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.205288.1584636193000.18711.1588045020327%40Atlassian.JIRA.
[JIRA] (JENKINS-62039) Jenkins ping thread freezing other threads
Title: Message Title Владислав Ненашев commented on JENKINS-62039 Re: Jenkins ping thread freezing other threads Jeff Thompson it can be seen from jstack 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.205930.1587708338000.18716.1588045140229%40Atlassian.JIRA.
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Shivam Lahoti updated an issue Jenkins / JENKINS-62074 Send build failure email to approver of pull request Change By: Shivam Lahoti Issue Type: New Feature Improvement 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.205977.1588044661000.18718.1588045260126%40Atlassian.JIRA.
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Shivam Lahoti updated an issue Jenkins / JENKINS-62074 Send build failure email to approver of pull request Change By: Shivam Lahoti Component/s: email-ext-plugin Component/s: mailer-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.205977.1588044661000.18719.1588045860079%40Atlassian.JIRA.
[JIRA] (JENKINS-62074) Send build failure email to approver of pull request
Title: Message Title Shivam Lahoti updated an issue Jenkins / JENKINS-62074 Send build failure email to approver of pull request Change By: Shivam Lahoti Currently the failure email goes to the developer and Build & Release team members but not to the approver.In case the developer commits the change and then not available after that, the approver does not get to know about the failures unless someone manually contacts him/her. 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.205977.1588044661000.18720.1588046160073%40Atlassian.JIRA.
[JIRA] (JENKINS-62075) Getting the log size of multibranch job
Title: Message Title Victor Rotenberg created an issue Jenkins / JENKINS-62075 Getting the log size of multibranch job Issue Type: Task Assignee: Unassigned Components: core Created: 2020-04-28 04:17 Labels: log Priority: Minor Reporter: Victor Rotenberg I am trying to get a log size of the multibranch job. The problem is when the branch name contains some underlines for example "test_multi_underline_job_jenkins" so the Jenkins stores the log file on the strange job's folder - it changes the all underlines to the middle dash and also changes the 3th word to something random so the folder name is like "test-multi-u.v0fcf8.-job-jenkins". How can I know exactly the folder name for a specific job? Thanks. Add Comment
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title Dinesh Dharmawardena reopened an issue I don't think this is fixed This is my casc config unclassified: audit-trail: logBuildCause: true loggers: - console: dateFormat: "-MM-dd HH:mm:ss:SSS" output: STD_OUT I'm getting this error # 2020-04-28 04:12:41.495+ [id=42] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init # io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class jenkins.model.GlobalConfigurationCategory$Unclassified : audit-trail. I have the plugin installed, and i'm trying to follow this https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/test/resources/hudson/plugins/audit_trail/jcasc.yml Jenkins / JENKINS-58171 Configuration as Code - Audit Trail Configuration Change By: Dinesh Dharmawardena Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title
Dinesh Dharmawardena edited a comment on JENKINS-58171
Re: Configuration as Code - Audit Trail Configuration
I don't think this is fixedThis is my casc config{code:java}unclassified: audit-trail:logBuildCause: trueloggers: - console: dateFormat: "-MM-dd HH:mm:ss:SSS" output: STD_OUT{code} I'm getting this error{code:java}# 2020-04-28 04:12:41.495+ [id=42] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init# io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class jenkins.model.GlobalConfigurationCategory$Unclassified : audit-trail. # Available attributes : administrativeMonitorsConfiguration, artifactManager, bitbucketEndpointConfiguration, buildDiscarders, buildStepOperation, buildUser, casCGlobalConfig, checkStyleReporter, checkstyle, defaultView, dependencyCheckPublisher, findBugsReporter, findbugs, gitHubConfiguration, gitHubPluginConfig, gitSCM, globalDefaultFlowDurabilityLevel, globalLibraries, globalSettings, groovy, jacoco, jiraGlobalConfiguration, location, lockableResourcesManager, mailer, masterBuild, mavenModuleSet, myView, nodeProperties, pipeline-model, plugin, pmd, pmdReporter, pollSCM, projectNamingStrategy, quietPeriod, resourceRoot, scmRetryCount, shell, timestamperConfig, usageStatistics, viewsTabBar, warningsParsers {code}I have the plugin installed, and i'm trying to follow this https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/test/resources/hudson/plugins/audit_trail/jcasc.yml
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this mess
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title
Dinesh Dharmawardena edited a comment on JENKINS-58171
Re: Configuration as Code - Audit Trail Configuration
I don't think this is fixedThis is my casc config{code:java}unclassified: audit-trail:logBuildCause: trueloggers: - console: dateFormat: "-MM-dd HH:mm:ss:SSS" output: STD_OUT{code} I'm getting this error{code:java}# 2020-04-28 04:12:41.495+ [id=42] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init# io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration elements for type class jenkins.model.GlobalConfigurationCategory$Unclassified : audit-trail.# Available attributes : administrativeMonitorsConfiguration, artifactManager, bitbucketEndpointConfiguration, buildDiscarders, buildStepOperation, buildUser, casCGlobalConfig, checkStyleReporter, checkstyle, defaultView, dependencyCheckPublisher, findBugsReporter, findbugs, gitHubConfiguration, gitHubPluginConfig, gitSCM, globalDefaultFlowDurabilityLevel, globalLibraries, globalSettings, groovy, jacoco, jiraGlobalConfiguration, location, lockableResourcesManager, mailer, masterBuild, mavenModuleSet, myView, nodeProperties, pipeline-model, plugin, pmd, pmdReporter, pollSCM, projectNamingStrategy, quietPeriod, resourceRoot, scmRetryCount, shell, timestamperConfig, usageStatistics, viewsTabBar, warningsParsers{code} it's not in the available attributes list :( I have the plugin installed for sure , and i'm trying to follow this https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/test/resources/hudson/plugins/audit_trail/jcasc.yml
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58171) Configuration as Code - Audit Trail Configuration
Title: Message Title Dinesh Dharmawardena closed an issue as Fixed nm, I was using version 2.5 Jenkins / JENKINS-58171 Configuration as Code - Audit Trail Configuration Change By: Dinesh Dharmawardena Status: Reopened Closed 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 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://group
[JIRA] (JENKINS-62076) updategitlabcommitstatus doesn't work
Title: Message Title Victor Rotenberg created an issue Jenkins / JENKINS-62076 updategitlabcommitstatus doesn't work Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2020-04-28 04:32 Priority: Major Reporter: Victor Rotenberg I use updategitlabcommitstatus command to update the statuses of the pipelines on the Gitlab. I have 2 the same Jenkins servers and from one of them it doesn't work. How can I troubleshoot the issue? Is there any logs, anything that can help me to find the reason. Thanks. Add Comment
[JIRA] (JENKINS-62043) EC2 nodes broken
Title: Message Title John Jeffers commented on JENKINS-62043 Re: EC2 nodes broken I upgraded the plugin when I had no EC2 instances registered in Jenkins, and it seems to be fine now. So it does seem to be a problem that occurs if the plugin is upgraded when there are registered EC2 build 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.205934.1587719449000.18738.1588048980328%40Atlassian.JIRA.
