[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg edited a comment on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build.Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell.And stages that were skipped are showing up as taking 2 seconds in the traditional UI in Jenkins_matrix_skip_bug3 . 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.205925.1587662025000.19184.1588110960257%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins_matrix_skip_bug3.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.205925.1587662025000.19182.1588110960226%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Jenkins_matrix_skip_bug2.PNG shows the matrix output where the no status is rendered for Matrix entry of COLOR='red' and 'SHAPE'='none' which failed in the build. Jenkins-62304_1_consoleText.txt shows that the job had an execution error for that cell. And stages that were skipped are showing up as taking 2 seconds in the traditional 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.205925.1587662025000.19180.1588110900156%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins-62304_1_consoleText.txt 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.205925.1587662025000.19178.1588109760197%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg updated an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Change By: John Malmberg Attachment: Jenkins_matrix_skip_bug2.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.205925.1587662025000.19174.1588109040363%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Also reproduced on Jenkins 2.231 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.205925.1587662025000.16662.1587663360053%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg created an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile, Jenkins_matrix_skip_bug.PNG Components: pipeline Created: 2020-04-23 17:13 Environment: CentOS Linux release 7.5.1804 (Core) jenkins.noarch 2.222.1-1.1 java-1.8.0-openjdk.i686 1:1.8.0.181-3.b13.el7_5 Blue Ocean 1.23.0 Labels: pipeline matrix Priority: Major Reporter: John Malmberg A matrix job where some stages are excluded is showing some of the stages as "skipped" in the Blue Ocean UI, or as having no steps in the traditional UI. The logs are showing that the steps have been run as expected. Even if a step fails in a stage, it does not show up in the UI. This makes the Jenkins Web UI useless for tracking the progress of a Matrix job. Attached is a Jenkinsfile that reproduces the problem with a single stage in the Matrix step. If more stages are added to the step, some of those additional stages are not shown on the web UI. This looks similar to: https://issues.jenkins-ci.org/browse/JENKINS-53816
[JIRA] (JENKINS-58897) Completed Pipeline job showing up on Executor
Title: Message Title John Malmberg created an issue Jenkins / JENKINS-58897 Completed Pipeline job showing up on Executor Issue Type: Bug Assignee: Unassigned Attachments: jenkins_zombie_executor_dump.txt, plugin_info.txt, pr_773_build_19_build.xml Components: pipeline Created: 2019-08-12 16:31 Environment: CentOS Linux release 7.5.1804 (Core) Jenkins 2.176.2 Jenkins is run directly. Build agents are either CentOS 7.5 or Docker Containers. docker.x86_64 2:1.13.1-75.git8633870.el7.centos Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Build agents launched via SSH. Priority: Minor Reporter: John Malmberg We are seeing pipeline jobs taking up executor slots as if they were running, even though the job page for the Jenkins Job shows it to be completed. Add Comment
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg reopened an issue Still not working. Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: John Malmberg Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191646.1529444715000.11458.1563208080196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. Still not working. Only change is now nothing is logged to the /var/log/jenkins/log on failure. Did you try reproducing this by temporarily moving where the nc command is located on the build agent? That is what I see different on the for the distros where it works and does not work, and that also goes along with the original bug report. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191646.1529444715000.11456.1563208020143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58055) NPE Cannot get property 'closure' after resume on Jenkins restart
Title: Message Title John Malmberg created an issue Jenkins / JENKINS-58055 NPE Cannot get property 'closure' after resume on Jenkins restart Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-06-17 17:59 Environment: CentOS Linux release 7.5.1804 (Core) 64 bit. java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) jenkins.noarch 2.164.3-1.1 @jenkins Jenkins running in a CentOS 7.5 VM as a service via the rpm. Jenkins running via reverse proxy HA-PROXY. Slave node launched by SSH. Web Browser: Firefox 67.0.1 Plugins: blue-ocean 1.16.0 branch-api 2.5.2 credentials-binding 1.20 credentials 2.2.20 github-branch-source 2.5.3 pipeline-build-step 2.9 pipeline-github 2.5 pipeline-github-lib 1.0 pipeline-githubnotify-step 1.0.4 pipeline-graph-analysis 1.10 pipeline-input-step 2.1.0 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.8 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.8 pipeline-model-extensions 1.3.8 pipeline-rest-api 2.11 pipeline-stage-step 2.3 pipeline-stage-tages-metadata 1.3.8 pipeline-stage-view 2.11 pipeline-utility-steps 2.3.0 workflow-aggregator 2.6 workflow-api 2.3.4 workflow-basic-steps 2.16 workflow-cps-global-lib 2.1.3 workflow-cps 2.68 workflow-durable-task-step 2.3.0 workflow-job 2.32 workflow-multibranch 2.21 workflow-scm-step 2.7 workflow-step-api 2.19 workflow-support 3.3 Priority: Minor Reporter: John Malmberg This issue occurred after doing an upgrade of Plugins: branch-api from 2.5.0 to 2.5.2 credentials-binding 1.18 to 2.19 credentials 2.1.19 to 2.2.0 github-branch-source 2.5.2 to 2.5.3 workflow-basic-steps 2.16 to 2.18 workflow-cps 2.68 to
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. Changing the repository entry to have the ssh credentials with it did not change the behavior. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. Except for the error message, the behavior seems to be the same. It is only working if the build agent is running CentOS, It is not working if the build agent is running Ubuntu 14.04, or SLES 12SP2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title
John Malmberg edited a comment on JENKINS-52051
Re: git-parameter exec: nc: not found.
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.It is generating a different message in the log.{code}WARNING: [ argobots-release ] Download tags from the repository failedhudson.plugins.git.GitException: Command "git ls-remote -t ssh://review. hpdd example . intel. com:29418/daos/argobots v1" returned status code 128:stdout:stderr: Permission denied (publickey).fatal: Could not read from remote repository.{code}The repository is access via a SSH-AGENT supplied credentials.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title
John Malmberg edited a comment on JENKINS-52051
Re: git-parameter exec: nc: not found.
It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents.It looks like it is still coded to use generating a different message in the log.{code}WARNING: [ argobots-release ] Download tags from the repository failedhudson.plugins.git.GitException: Command "git ls-remote -t ssh: / usr / bin review.hpdd.intel.com:29418 / nc instead of checking to see where the nc program really daos/argobots v1" returned status code 128:stdout:stderr: Permission denied (publickey).fatal: Could not read from remote repository.{code}The repository is access via a SSH-AGENT supplied credentials .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg reopened an issue Jenkins / JENKINS-52051 git-parameter exec: nc: not found. Change By: John Malmberg Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. It is still failing to find the releases when using Ubuntu or SLESS/(Open SUSE Leap) build agents. It looks like it is still coded to use /usr/bin/nc instead of checking to see where the nc program really is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52051) git-parameter exec: nc: not found.
Title: Message Title John Malmberg commented on JENKINS-52051 Re: git-parameter exec: nc: not found. I will try to verify this week. The issue appears to be that the code was looking only for "/usr/bin/nc", and on the systems where the plugin was failing for me, the path needed is "/bin/nc". So it should have been easy to reproduce by temporary moving nc to /bin/nc on a test system. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
