[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.
[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-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
[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 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
[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-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-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-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 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-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-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-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-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
[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-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-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-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-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-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 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 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-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-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-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-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-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-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 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-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-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 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-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-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-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
[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
[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-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-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-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-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 commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Steve Todorov What version of Blue Ocean are your 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.18620.1588020660190%40Atlassian.JIRA.
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Marc Brugger commented on JENKINS-62072 Re: The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary Hi Steven The functionality is still available, but it has to be enabled in the jenkins configuration. Use 'Disable OWASP Markup Formatter' to enable html rendering. I had to enable the OWASP Formatter to prevent vulnerabilities introduced by html injection. If html formatting is desired, the feature hast do be actively disabled by the user. Best Regards, Marc 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.205974.1588016722000.18615.1588020240321%40Atlassian.JIRA.
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title Marc Brugger started work on JENKINS-62072 Change By: Marc Brugger 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.205974.1588016722000.18617.1588020240389%40Atlassian.JIRA.
[JIRA] (JENKINS-61426) Add / remove users from github team for spotinst-plugin
Title: Message Title Spotinst team updated an issue Jenkins / JENKINS-61426 Add / remove users from github team for spotinst-plugin Change By: Spotinst team Summary: Add / remove users from github team for our spotinst- 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.205098.158392566.18609.1588017900068%40Atlassian.JIRA.
[JIRA] (JENKINS-62072) The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Title: Message Title
Steven Fransen created an issue
Jenkins / JENKINS-62072
The Badge Plugins is no longer displaying color text anywhere addHtmlBadge & createSummary
Issue Type:
Bug
Assignee:
Marc Brugger
Components:
badge-plugin
Created:
2020-04-27 19:45
Priority:
Minor
Reporter:
Steven Fransen
// code placeholder
def WhatText = "hello" def mycolor = "blue" addHtmlBadge html: "${WhatText}", id: "blue" createSummary('orange-square.gif').appendText("${WhatText}") all the test will be in black and white I am not exactly sure what version broken this . it was some version in the past month or so. I really miss this features as it help figure out what is wrong.
Add Comment
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Oleg Nenashev commented on JENKINS-62068 Re: jetty ALPN incompatibility - java8 u 252 NVM, Jesse Glick has already done it in https://github.com/jenkinsci/winstone/pull/105 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.18603.1588015800132%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Oleg Nenashev commented on JENKINS-62068 Re: jetty ALPN incompatibility - java8 u 252 Thanks for the investigation! I believe we need to update https://github.com/jenkinsci/winstone#http2-support , CC Olivier Lamy 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.18601.1588015740180%40Atlassian.JIRA.
[JIRA] (JENKINS-41940) Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies
Title: Message Title Egor Baranov commented on JENKINS-41940 Re: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies Hello! It would be very interesting for me to implement such plugin. I've looked through source code of Heavy Job Plugin and some examples of Pipeline API like lockable-resources-plugin. Unfortunately Pipeline API differs from Freestyle Projects. For now it's clear how to create custom step and wrap another step with it but I can't understand how to create something like subtasks in Heavy Job plugin. I would be very happy if someone can explain me this moment a bit more or give me a useful link. 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.178796.1486751514000.18574.1588014780607%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated JENKINS-62068 Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Status: Fixed but Unreleased Closed 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.18566.1588013100271%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong edited a comment on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Thank you very much for the response. Being able to use this with organization folders will be a huge time saver.2 and 3 - Would this be almost the same as just passing the Jenkins project name (SOURCE_PROJECT_FULL_NAME or SOURCE_PROJECT_NAME)? Actually, with the existing project name I could solve for 4 by simply executing the alternate pipeline from a centralized pipeline for action triggers. Using this method would remove the need for 2, 3, and 4. Based on this, please ignore 2, 3, and 4 :) 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.205829.1587131764000.18564.1588012800108%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Thank you very much for the response. Being able to use this with organization folders will be a huge time saver. 2 and 3 - Would this be almost the same as just passing the Jenkins project name (SOURCE_PROJECT_FULL_NAME or SOURCE_PROJECT_NAME)? Actually, with the existing project name I could solve for 4 by simply executing the alternate pipeline from a centralized pipeline for action triggers. Using this method would remove the need for 2, 3, and 4. 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.205829.1587131764000.18562.1588012740231%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated JENKINS-62068 ok, this isn't a jenkins bug. The ALPN APIs have been backported from Java 9 to OpenJDK 8u251/8u252. Therefore, since OpenJDK 8u251/8u252 there is no more need for the Jetty ALPN boot jar provided by this project. https://github.com/jetty-project/jetty-alpn#jetty-alpn What happened was: Start-Date: 2020-04-20 15:30:27 Commandline: apt upgrade Upgrade: jenkins:amd64 (2.232, 2.233) End-Date: 2020-04-20 15:30:31Start-Date: 2020-04-22 13:58:10 Commandline: apt upgrade Upgrade: ... openjdk-8-jre:amd64 (8u242-b08-0ubuntu3~18.04, 8u252-b09-1~18 .04), ... End-Date: 2020-04-22 13:58:32 Start-Date: 2020-04-27 12:14:55 Commandline: apt upgrade Requested-By: jsoref (1005) Upgrade: ..., jenkins:amd64 (2.233, 2.234), ... End-Date: 2020-04-27 12:15:15 So, I had updated to jenkins 2.233 – and things were fine. Then java updated to 8u252 (which is incompatible w/ the jetty alpn, as it integrated it), but jenkins the service wasn't restarted. Then I upgraded to jenkins 2.234 – and things exploded. But, the problem wasn't jenkins, it's just that I hadn't restarted it since the java upgrade, which is why downgrading didn't fix the problem. Solution: remove ALPN from the path, as it's no longer needed. Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Not A Defect
[JIRA] (JENKINS-62068) jetty ALPN incompatibility - java8 u 252
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-62068 jetty ALPN incompatibility - java8 u 252 Change By: Josh Soref Summary: jetty ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage java8 u 252 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.18512.1588011360300%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-62068 ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Change By: Josh Soref Summary: ALPN incompatibility - java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage 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.18508.1588011060152%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref commented on JENKINS-62068 Re: java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Ok. https://github.com/jetty-project/jetty-alpn/issues/30 it's ALPN (again). 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.18505.1588011000723%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref commented on JENKINS-62068 Re: java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Oleg Nenashev: See the second case where it's just the update server check. It feels like something screwy happened to the general SSL stack. Note: rolling back to 2.233 didn't fix this . # ok to this point Start-Date: 2020-04-27 12:14:55 Commandline: apt upgrade Requested-By: jsoref (1005) Upgrade: libcups2:amd64 (2.2.7-1ubuntu2.7, 2.2.7-1ubuntu2.8), update-manager-core:amd64 (1:18.04.11.10, 1:18.04.11.12), zabbix-agent:amd64 (1:4.0.19-1+buster, 1:4.0.20-1+buster), jenkins:amd64 (2.2 33, 2.234), libkmod2:amd64 (24-1ubuntu3.2, 24-1ubuntu3.3), kmod:amd64 (24-1ubuntu3.2, 24-1ubuntu3.3), python3-update-manager:amd64 (1:18.04.11.10, 1:18.04.11.12), distro-info-data:amd64 (0.37ubuntu 0.6, 0.37ubuntu0.7), zabbix-proxy-sqlite3:amd64 (1:4.0.19-1+buster, 1:4.0.20-1+buster) End-Date: 2020-04-27 12:15:15 # broken at this point Start-Date: 2020-04-27 12:48:13 Commandline: apt install jenkins=2.233 Requested-By: jsoref (1005) Downgrade: jenkins:amd64 (2.234, 2.233) End-Date: 2020-04-27 12:48:16 # not fixed at this point 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"
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Oleg Nenashev commented on JENKINS-62068 Re: java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Josh Soref looks like the SVN plugin is involved, right? 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.18489.1588010160170%40Atlassian.JIRA.
[JIRA] (JENKINS-62062) EC2 Plugin Null Pointer Exception IsAcceptingTask
Title: Message Title Nigel Armstrong updated an issue Jenkins / JENKINS-62062 EC2 Plugin Null Pointer Exception IsAcceptingTask Change By: Nigel Armstrong Priority: Critical 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.205961.1587980992000.18485.1588009920324%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker edited a comment on JENKINS-61356 Re: Trilead SSH does not support PKCS#8 encoded private keys Makes sense. I've updated it to minor. I've also started talking with some other Jenkins developers to try to find out whether or not we can migrate to Apache MINA SSH as our SSH client library as it's still actively developed. That may or may not be relevant in the future as default OpenSSH ciphers change over time. For example, there's no AES/GCM support, and I don't remember if ChaCha20-Poly1305 is already supported or not. Then there will be updated key exchanges and all the other supporting primitives. Not sure how much of that we want to continue maintaining if we can use an OSS dependency with a community around it. 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.204941.158343741.18482.1588009680171%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Trilead SSH does not support PKCS#8 encoded private keys Makes sense. I've updated it to minor. I've also started talking with some other Jenkins developers to try to find out whether or not we can migrate to Apache MINA SSH as our SSH client library as it's still actively developed. 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.204941.158343741.18478.1588009500150%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Trilead SSH does not support PKCS#8 encoded private keys Change By: Matt Sicker Priority: Critical Minor 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.204941.158343741.18474.1588009440377%40Atlassian.JIRA.
[JIRA] (JENKINS-62071) Overview Pie Charts can not be clicked on to go to a category (Error/High/etc)
Title: Message Title Michael Thompson created an issue Jenkins / JENKINS-62071 Overview Pie Charts can not be clicked on to go to a category (Error/High/etc) Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2020-04-27-13-34-08-952.png Components: warnings-ng-plugin Created: 2020-04-27 17:37 Environment: OS: Win 2008 Server R2 64bit Java: Amazon OpenJDK 1.8.0_222-b10 Jenkins: 2.222.1 warnings-ng 8.1.0 Client: Win 10, Chrome 81 & IE 11 Priority: Minor Reporter: Michael Thompson I can no longer click on the Pie Chart to filter the warnings list. I can click on the levels below the chart still to remove those. In the past I use to click the lower levels to disable then click on the red area to get down to the "Error" listing. I can still get there manually by entering the URL. This broke a revision or two back but I figured it might get fixed so I hadn't reported it yet. http://svn-reporting:8081/job/ZZZ/336/eclipse/error/
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
CHRISTOPHER KELLY edited a comment on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
In the same vein as [~zett42] I created a groovy library to wrap his method for easy use in my pipelines. I call the file unsafeEcho.groovy and call it via {code:java}unsafeEcho "SHORT_BUILD_VERSION: $SHORT_BUILD_VERSION"{code}{code:java}#!/usr/bin/env groovy// Workaround for "Print message" that is displayed by original echo step if the message// contains a value of an environment variable or a pipeline parameter. WARNING: This disables masking of secrets in the output, so don't call it within witCredentials{} scope! void call( String msg ) {withContext( new unsafeEchoClearer() ) {echo msg}} // Clears all environment variables, to be used from withContext{}.class unsafeEchoClearer extends org.jenkinsci.plugins.workflow.steps.EnvironmentExpander {@NonCPSvoid expand( hudson.EnvVars env ) throws IOException, InterruptedException {env.clear()}} {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.194144.1537309242000.18445.1588008240590%40Atlassian.JIRA.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
CHRISTOPHER KELLY edited a comment on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
In the same vein as [~zett42] I created a groovy library to wrap his method for easy use in my pipelines. I call the file unsafeEcho.groovy and call it via {code:java}unsafeEcho "SHORT_BUILD_VERSION: $SHORT_BUILD_VERSION"{code}{code:java}#!/usr/bin/env groovy // Workaround for "Print message" that is displayed by original echo step if the message// contains a value of an environment variable or a pipeline parameter. WARNING: This disables masking of secrets in the output, so don't call itwithin witCredentials{} scope!void call( String msg ) {withContext( new unsafeEchoClearer() ) {echo msg}} // Clears all environment variables, to be used from withContext{}.class unsafeEchoClearer extends org.jenkinsci.plugins.workflow.steps.EnvironmentExpander {@NonCPSvoid expand( hudson.EnvVars env ) throws IOException, InterruptedException {env.clear()}}{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.194144.1537309242000.18419.1588008180529%40Atlassian.JIRA.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
CHRISTOPHER KELLY commented on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
In the same vein as Andreas Meyer I created a groovy library to wrap his method for easy use in my pipelines. I call the file unsafeEcho.groovy and call it via
unsafeEcho "SHORT_BUILD_VERSION: $SHORT_BUILD_VERSION"
#!/usr/bin/env groovy// Workaround for "Print message" that is displayed by original echo step if the message
// contains a value of an environment variable or a pipeline parameter.
//
// WARNING: This disables masking of secrets in the output, so don't call it within witCredentials{} scope!void call( String msg ) {
withContext( new unsafeEchoClearer() ) {
echo msg
}
}// Clears all environment variables, to be used from withContext{}.
class unsafeEchoClearer extends org.jenkinsci.plugins.workflow.steps.EnvironmentExpander {
@NonCPS
void expand( hudson.EnvVars env ) throws IOException, InterruptedException {
env.clear()
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62070) Multibranch Job aborts cleanup upon first error.
Title: Message Title Steven Christenson created an issue Jenkins / JENKINS-62070 Multibranch Job aborts cleanup upon first error. Issue Type: Bug Assignee: Unassigned Components: workflow-multibranch-plugin Created: 2020-04-27 17:10 Environment: Dockerized Jenkins 2.222.1.1 with workflow-multibranch:2.21 and its rats nest of dependencies. Notable is cloudbees-folder:6.11 (and currently 6.12) Labels: pipeline multibranch Priority: Major Reporter: Steven Christenson This issue reported via [Cloudbees Support|https://support.cloudbees.com/hc/en-us/requests/179894], but reported here as it likely affects others. Summary: Scanner aborts at first error On the master, an nfs problem prohibits the job scanner from cleaning up an inactive PR. Unfortunately once it hits the error, it exits and does not continue to attempt to clean up the other PRs. A single error on a heavily used repo causes a significant growth in disk space, jobs, and overhead. We have seen a similar problem if other causes prevent removal like a directory without permission for Jenkins. DESIRED Behavior: Continue removing other obsolete jobs Log Will remove PR-41524 FATAL: Failed to recompute children of Team » REDACTED » pipeline jenkins.util.io.CompositeIOException: Unable to delete '/var/jenkins_home/jobs/team/jobs/REDACTED/pipeline/branches/PR-41524'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at jenkins.util.io.PathRemover.forceRemoveRecursive(PathRemover.java:99) at hudson.Util.deleteRecursive(Util.java:294) at hudson.Util.deleteRecursive(Util.java:283) at
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title richard mauchline updated an issue Jenkins / JENKINS-61942 Can this be configured to use bitbucket server Change By: richard mauchline Attachment: config1.png 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.205822.1587082749000.18388.1588006560307%40Atlassian.JIRA.
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title richard mauchline updated an issue Jenkins / JENKINS-61942 Can this be configured to use bitbucket server Change By: richard mauchline Attachment: config2.png 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.205822.1587082749000.18389.1588006560321%40Atlassian.JIRA.
[JIRA] (JENKINS-62069) Footer is overlaying instead of appending to bottom and hiding page content
Title: Message Title Jose Dominguez created an issue Jenkins / JENKINS-62069 Footer is overlaying instead of appending to bottom and hiding page content Issue Type: Bug Assignee: Unassigned Attachments: Jenkins-FooterIssue-01.PNG, Jenkins-FooterIssue-02.PNG, Jenkins-FooterIssue-03.PNG Components: workflow-job-plugin Created: 2020-04-27 16:54 Environment: Jenkins Version 2.233 Labels: footer Priority: Minor Reporter: Jose Dominguez Footer is overlaying instead of appending to bottom and hiding page content, I have attached two screenshots as examples. Looks like something related to the container Add
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61356 Re: Trilead SSH does not support PKCS#8 encoded private keys For me is not a critical issue, there are several formats supported, those formats can be generated with any modern version of OpenSSL or OpenSSH. The issue of the user is thigh attached to the restrictions and versions they use in their environment, so the overall impact on users is minimum and has a solution in most of the cases. I've documented the issue on the troubleshooting guide and in the configuration documents. 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.204941.158343741.18383.1588006380206%40Atlassian.JIRA.
[JIRA] (JENKINS-62068) java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-62068 java.lang.NoSuchFieldError: nullSession at sun.security.ssl.ClientHandshaker.getKickstartMessage Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-27 16:50 Priority: Minor Reporter: Josh Soref -- Logs begin at Thu 2018-11-01 01:50:46 EDT, end at Mon 2020-04-27 12:35:24 EDT. -- Apr 27 12:34:00 hostname jenkins[22240]: 2020-04-27 16:34:00.042+ [id=193]SEVEREh.triggers.SCMTrigger$Runner#runPolling: Failed to record SCM polling for hudson.model.FreeStyleProject@21c303b6[SomePrject] Apr 27 12:34:00 hostname jenkins[22240]: java.lang.NoSuchFieldError: nullSession Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.ClientHandshaker.getKickstartMessage(ClientHandshaker.java:1350) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.Handshaker.kickstart(Handshaker.java:1117) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1500) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1416) Apr 27 12:34:00 hostname jenkins[22240]: at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1400) Apr 27 12:34:00 hostname jenkins[22240]: at org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createSSLSocket(SVNSocketFactory.java:96) Apr 27 12:34:00 hostname jenkins[22240]: at ... ... Apr 27 12:34:10 hostname jenkins[22240]: 2020-04-27 16:34:10.783+ [id=45]INFOhudson.util.Retrier#start: Attempt #1 to do the action check updates server Apr 27
[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 Component/s: workflow-multibranch-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.205962.1588001733000.18379.1588005720208%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker assigned an issue to Ivan Fernandez Calvo Jenkins / JENKINS-61356 Trilead SSH does not support PKCS#8 encoded private keys Change By: Matt Sicker Assignee: Matt Sicker Ivan Fernandez Calvo 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.204941.158343741.18376.1588003620447%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Trilead SSH does not support PKCS#8 encoded private keys I've updated the original ticket to better reflect our understanding of the underlying issue. 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.204941.158343741.18373.1588003620400%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Trilead SSH does not support PKCS#8 encoded private keys Change By: Matt Sicker Issue Type: Bug 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.204941.158343741.18367.1588003500342%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title
Matt Sicker updated an issue
Jenkins / JENKINS-61356
Trilead SSH does not support PKCS#8 encoded private keys
Change By:
Matt Sicker
The Jenkins SSH agent plugin uses trilead-ssh which only supports the legacy PEM and new SSH2 private key file formats. In certain hardened environments, SSH keys are mandated to be encoded in PKCS#8 (presumably because they're more universal and allow for password protection and encrypting the key) to the point where OpenSSH and {{ssh-keygen}} are patched to only support PKCS#8 private keys.Attached to this ticket are various encodings of private keys as we troubleshooted the initial issue described below. Note that private keys that have a header line with {{BEGIN PRIVATE KEY}} are indicative of the file being encoded in PKCS#8. If the file header contains {{BEGIN RSA PRIVATE KEY}} (or {{EC}} or whatever other algorithm), that is the legacy PEM format. If the file header contains {{BEGIN OPENSSH PRIVATE KEY}}, then that is the new SSH2 format. The latter two encoding formats are already supported in trilead-ssh.h2. Original Details * My Jenkins exists on an Amazon EC2 instance. * I'm trying to add Red Hat 7.7 slave via ssh. * I can ssh directly using terminal from my master to slave and vice versa using that key file{code:java}jenkins@master:/var/lib/jenkins$ ssh -i .ssh/id_rsa -q 10.193.177.232jenkins@slave:/var/lib/jenkins$ ssh -i .ssh/id_rsa -q 10.193.177.209{code}I’m also able to make a successful SSH connection when I perform a SSH connection test from the *Manage Jenkins -> Configure System* section of the Master (_FYI - see attached screenshot_).But when I try to configure my slave via launch agent method, it gives me the following error:{code:java}caused by: java.io.IOException: PEM problem: it is of unknown type at com.trilead.ssh2.crypto.PEMDecoder.decpdeKeyPair(PEMDecoder.java:500){code} * How I've configured the slave (one of the method)? ** I've saved slave machine credentials as "*ssh key username with private key*" ** Launch method: Launch agents via SSH ** Hostname: slave machine private ip address. ** Host Key Verification Strategy: *Manually trusted key Verification Strategy*Note: * I cannot regenerate ssh keys as I'll not be able to access my machines again and the infrastructure is very strict. * All SSH key are 4096 bits in length and RSA. * I cannot use credentials as username/password as either there is no password. * I've tried everything whatever mentioned in other jenkins tickets for same issue or on internet, but my issue is not getting resolved.Please see the following attachments for log details and screenshots. This is a total blocker. Please advise. Thank you.
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title richard mauchline edited a comment on JENKINS-61942 Re: Can this be configured to use bitbucket server Hello [~aytuncbeken] Thanks for getting back to me. That is great if there is no such restriction, but could you guide me where we configure the URL of my bitbuckert server?I have attached a couple of screen grabs from the configuration of this plugin - but I am lost as to where to configure this.Thanks again 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.205822.1587082749000.18361.1588003200290%40Atlassian.JIRA.
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title richard mauchline commented on JENKINS-61942 Re: Can this be configured to use bitbucket server Hello Thanks for getting back to me. That is great if there is no such restriction, but could you guide me where we configure the URL of my bitbuckert server? I have attached a couple of screen grabs from the configuration of this plugin - but I am lost as to where to configure this. Thanks again 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.205822.1587082749000.18359.1588003200222%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Trilead SSH does not support PKCS#8 encoded private keys
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Trilead SSH does not support PKCS#8 encoded private keys Change By: Matt Sicker Summary: Unable to connect to slave via Launch Agent mode( Trilead SSH ) does not support PKCS#8 encoded private keys 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.204941.158343741.18355.1588003080283%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Matt Sicker Component/s: ssh-credentials-plugin Component/s: ssh-plugin Component/s: ssh-slaves-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.204941.158343741.18349.1588003020526%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Matt Sicker Environment: Jenkins: Jenkins ver. 2.204.4 Plugins: SSH plugin 2.6.1 * SSH Build Agents 1.31.0 * SSH Credentials Plugin 1.18.1 *SSH Agent Plugin 1.19OS: Master(RHEL7.7) Slave(RHEL7.7)Java: Version 1.8.0_242 (Master & Slave)Private key(SSH): RSA 4096 bit key(PKCS#8 encoded) 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.204941.158343741.18351.1588003020548%40Atlassian.JIRA.
[JIRA] (JENKINS-62067) Modal buttons look wrong on the Translation Assistance Plugin
Title: Message Title Félix Queiruga Balado created an issue Jenkins / JENKINS-62067 Modal buttons look wrong on the Translation Assistance Plugin Issue Type: Bug Assignee: Unassigned Attachments: Captura de pantalla 2020-04-27 a las 17.42.57.png Components: core Created: 2020-04-27 15:55 Labels: ui Priority: Minor Reporter: Félix Queiruga Balado Creating this issue on Core because I think the solution should be here. The buttons on the modal when clicking "Help us localize this page" look wrong. This has been introduced with the button changes on 2.233. The solution I suggest is modifying the YUI CSS that removes references to the buttons in order to override it. Add Comment
[JIRA] (JENKINS-62066) Help text too big on job forms
Title: Message Title Félix Queiruga Balado updated an issue Jenkins / JENKINS-62066 Help text too big on job forms Change By: Félix Queiruga Balado Labels: newbie-friendly ui 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.205965.1588002629000.18344.1588002660292%40Atlassian.JIRA.
[JIRA] (JENKINS-62066) Help text too big on job forms
Title: Message Title Félix Queiruga Balado created an issue Jenkins / JENKINS-62066 Help text too big on job forms Issue Type: Bug Assignee: Unassigned Attachments: Captura de pantalla 2020-04-27 a las 17.45.32.png Components: core Created: 2020-04-27 15:50 Priority: Minor Reporter: Félix Queiruga Balado The help text on the job config forms is too big. It should be 14px (0.875rem). Add Comment
[JIRA] (JENKINS-62064) CPS-transformed assignment expressions evaluate to null instead of the value of the RHS
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-62064
CPS-transformed assignment expressions evaluate to null instead of the value of the RHS
Change By:
Devin Nusbaum
As described in [https://stackoverflow.com/questions/61420959/jenkins-interpretation-of-multiple-object-declarations-on-one-line], CPS-transformed assignment expressions evaluate to {{null}} instead of the value of the RHS of the _expression_. Here is an example:{code:java}def a = b = c = 1 {code}In a Pipeline, after executing that _expression_ {{a == null}}, {{b == null}}, and {{c == 1}}.In regular Groovy, after executing that _expression_, {{a}}, {{b}}, and {{c}}, are all equal to 1.Here is a (failing) {{workflow-cps}} test case (for {{CpsFlowDefinition2Test}}) that demonstrates the bug:{code:java}@Test public void assignmentExprsReturnRhs() throws Exception {WorkflowJob p = jenkins.createProject(WorkflowJob.class);p.setDefinition(new CpsFlowDefinition("def a = b = c = 1\n" +"println( / [ a == ${a}/)\n" +"println(/ , b == ${b}/)\n" +"println(/ , c == ${c}/ ].toString( ) \n ) ", true));WorkflowRun b = jenkins.buildAndAssertSuccess(p);jenkins.assertLogContains(" a == [ 1 " , b);jenkins.assertLogContains("b == 1 , 1] ", b); jenkins.assertLogContains( // Actual output today is " c == [null, null, 1 ] " , b); . } {code}I think the relevant code is [AssignmentBlock|https://github.com/cloudbees/groovy-cps/blob/94939d33fab9b04be76b9fbd0477b9807bf1ad32/lib/src/main/java/com/cloudbees/groovy/cps/impl/AssignmentBlock.java] in {{groovy-cps}}. In particular, I think that [assignAndDone|https://github.com/cloudbees/groovy-cps/blob/94939d33fab9b04be76b9fbd0477b9807bf1ad32/lib/src/main/java/com/cloudbees/groovy/cps/impl/AssignmentBlock.java#L70] needs to create a new continuation to pass to {{lhs.set}} that calls {{k.receive(rhs)}} internally.
Add Comment
[JIRA] (JENKINS-62065) REGRESSION: The BreadCrumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Samuel Gabriel created an issue Jenkins / JENKINS-62065 REGRESSION: The BreadCrumb navigation on the top of the job is not responding after clicking Apply Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-27 15:48 Priority: Minor Reporter: Samuel Gabriel After clicking the Apply to save the job configuration the the top breadcrumb navigation that allows editing and moving to the parent view is no longer functional. When clicking on it nothing happens. This started happening after may be 2.226 Add Comment
[JIRA] (JENKINS-58813) Cannot send Email notification over office365 smtp with starttls has no effect
Title: Message Title Rakesh S edited a comment on JENKINS-58813 Re: Cannot send Email notification over office365 smtp with starttls has no effect hi [~gmesika]/[~alecharp],I am working on windows 7 machine, i have configured below but still getting the same error # extended email notification with smtp.office365.com, unchecked SSl, Port 587 # upgraded mailer plug in to 1.29 # added -Dmail.smtp.starttls.enable=true to JAVA_HOME arguments in jenkins.xml file When I am checking "Test configuration by sending test e-mail" getting error message as "javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful [BMXPR01CA0071.INDPRD01.PROD.OUTLOOK.COM]"!jenkinsError.png!!jenkinsError2.JPG!Attached the screenshots . Could you please help. Thanks,Rakesh 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.201125.1565011288000.18330.1588002420320%40Atlassian.JIRA.
[JIRA] (JENKINS-58813) Cannot send Email notification over office365 smtp with starttls has no effect
Title: Message Title Rakesh S updated an issue Jenkins / JENKINS-58813 Cannot send Email notification over office365 smtp with starttls has no effect Change By: Rakesh S Attachment: jenkinsError.png 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.201125.1565011288000.18308.1588002360850%40Atlassian.JIRA.
[JIRA] (JENKINS-58813) Cannot send Email notification over office365 smtp with starttls has no effect
Title: Message Title Rakesh S commented on JENKINS-58813 Re: Cannot send Email notification over office365 smtp with starttls has no effect hi Guy Mesika/Adrien Lecharpentier, I am working on windows 7 machine, i have configured below but still getting the same error extended email notification with smtp.office365.com, unchecked SSl, Port 587 upgraded mailer plug in to 1.29 added -Dmail.smtp.starttls.enable=true to JAVA_HOME arguments in jenkins.xml file When I am checking "Test configuration by sending test e-mail" getting error message as "javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful [BMXPR01CA0071.INDPRD01.PROD.OUTLOOK.COM]" Attached the screenshots Thanks, Rakesh 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.201125.1565011288000.18323.1588002361194%40Atlassian.JIRA.
[JIRA] (JENKINS-58813) Cannot send Email notification over office365 smtp with starttls has no effect
Title: Message Title Rakesh S updated an issue Jenkins / JENKINS-58813 Cannot send Email notification over office365 smtp with starttls has no effect Change By: Rakesh S Attachment: jenkinsError2.JPG 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.201125.1565011288000.18320.1588002361132%40Atlassian.JIRA.
[JIRA] (JENKINS-62064) CPS-transformed assignment expressions evaluate to null instead of the value of the RHS
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-62064
CPS-transformed assignment expressions evaluate to null instead of the value of the RHS
Change By:
Devin Nusbaum
As described in [https://stackoverflow.com/questions/61420959/jenkins-interpretation-of-multiple-object-declarations-on-one-line], CPS-transformed assignment expressions do not return their result evaluate to {{null}} instead of the value of the RHS of the _expression_ . Here is an example:{code:java}def a = b = c = 1 {code}In a Pipeline, after executing that _expression_ {{a == null}}, {{b == null}}, and {{c == 1}}.In regular Groovy, after executing that _expression_, {{a}}, {{b}}, and {{c}}, are all equal to 1.Here is a (failing) {{workflow-cps}} test case (for {{CpsFlowDefinition2Test}}) that demonstrates the bug:{code:java}@Test public void assignmentExprsReturnRhs() throws Exception {WorkflowJob p = jenkins.createProject(WorkflowJob.class);p.setDefinition(new CpsFlowDefinition("def a = b = c = 1\n" +"println(/a == ${a}/)\n" +"println(/b == ${b}/)\n" +"println(/c == ${c}/)\n", true));WorkflowRun b = jenkins.buildAndAssertSuccess(p);jenkins.assertLogContains("a == 1", b);jenkins.assertLogContains("b == 1", b);jenkins.assertLogContains("c == 1", b);} {code}I think the relevant code is [AssignmentBlock|https://github.com/cloudbees/groovy-cps/blob/94939d33fab9b04be76b9fbd0477b9807bf1ad32/lib/src/main/java/com/cloudbees/groovy/cps/impl/AssignmentBlock.java] in {{groovy-cps}}. In particular, I think that [assignAndDone|https://github.com/cloudbees/groovy-cps/blob/94939d33fab9b04be76b9fbd0477b9807bf1ad32/lib/src/main/java/com/cloudbees/groovy/cps/impl/AssignmentBlock.java#L70] needs to create a new continuation to pass to {{lhs.set}} that calls {{k.receive(rhs)}} internally.
Add Comment
[JIRA] (JENKINS-62064) CPS-transformed assignment expressions evaluate to null instead of the value of the RHS
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-62064 CPS-transformed assignment expressions evaluate to null instead of the value of the RHS Change By: Devin Nusbaum Summary: CPS-transformed assignment expressions do not return their result evaluate to null instead of the value of the RHS 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.205963.1588002163000.18305.1588002300065%40Atlassian.JIRA.
[JIRA] (JENKINS-62064) CPS-transformed assignment expressions do not return their result
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-62064 CPS-transformed assignment expressions do not return their result Change By: Devin Nusbaum Summary: CPS - transformed assignment expressions do not return their result 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.205963.1588002163000.18304.1588002240063%40Atlassian.JIRA.
[JIRA] (JENKINS-62064) CPS transformed assignment expressions do not return their result
Title: Message Title
Devin Nusbaum created an issue
Jenkins / JENKINS-62064
CPS transformed assignment expressions do not return their result
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2020-04-27 15:42
Environment:
workflow-cps 2.80
Labels:
pipeline groovy
Priority:
Minor
Reporter:
Devin Nusbaum
As described in https://stackoverflow.com/questions/61420959/jenkins-interpretation-of-multiple-object-declarations-on-one-line, CPS-transformed assignment expressions do not return their result. Here is an example:
def a = b = c = 1
In a Pipeline, after executing that _expression_ a == null, b == null, and c == 1. In regular Groovy, after executing that _expression_, a, b, and c, are all equal to 1. Here is a (failing) workflow-cps test case (for CpsFlowDefinition2Test) that demonstrates the bug:
@Test public void assignmentExprsReturnRhs() throws Exception {
WorkflowJob p = jenkins.createProject(WorkflowJob.class);
p.setDefinition(new CpsFlowDefinition(
"def a = b = c = 1\n" +
"println(/a == ${a}/)\n" +
[JIRA] (JENKINS-62063) BuileOcean UI is broken due to ClassCastException
Title: Message Title Steve Todorov created an issue Jenkins / JENKINS-62063 BuileOcean UI is broken due to ClassCastException Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2020-04-27 15:35 Environment: Jenkins 2.233 Pipeline: Multibranch with defaults: 2.1 Pipeline: Multibranch: 2.21 Priority: Blocker Reporter: Steve Todorov Most of our build jobs cannot be accessed through the Blue Ocean UI. For example accessing /blue/organizations/jenkins/pipelines triggers a request to /blue/rest/search/?q=type:pipeline;organization:jenkins;pipeline:;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject=no-folders=0=26 which then produces the following exception: Apr 27, 2020 3:23:45 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleException Caught unhandled exception with ID 3f5f1f8b-c409-4a3a-9ee8-9db8e549fd08 java.lang.ClassCastException:
[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 Summary: BuileOcean BlueOcean UI is broken due to ClassCastException 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.18302.1588001760408%40Atlassian.JIRA.
