[JIRA] (JENKINS-59781) sshCommand fails to flush full log on failure
Title: Message Title
Damien Jiang commented on JENKINS-59781
Re: sshCommand fails to flush full log on failure
Hi Naresh Rayapati, sorry for the late response; I've been focused on some other things in the past week. I again had a failure in the deploy, so I tried again. Adding the post stage
post {
failure {
sleep 5
}
}
to the end of my pipeline does, in fact, display the error. This is not ideal, but should get the job done for now...
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202509.157108516.4832.1572377760217%40Atlassian.JIRA.
[JIRA] (JENKINS-51208) Execution time of parallel steps displayed as max time among all steps in block
Title: Message Title Damien Jiang edited a comment on JENKINS-51208 Re: Execution time of parallel steps displayed as max time among all steps in block Bump; looks like there are no plans to fix this problem? It makes monitoring / optimizing pipelines much more annoying.Btw, before the parallel block is completely finished, each parallelized step _does_ report the right runtime! It's only update updated to the "runtime of the whole parallel block" at the end of the block. 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-51208) Execution time of parallel steps displayed as max time among all steps in block
Title: Message Title Damien Jiang commented on JENKINS-51208 Re: Execution time of parallel steps displayed as max time among all steps in block Bump; looks like there are no plans to fix this problem? It makes monitoring / optimizing pipelines much more annoying. Btw, before the parallel block is completely finished, each parallelized step does report the right runtime! It's only update to the "runtime of the whole parallel block" at the end of the block. 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-51536) Blue Ocean link on Pipeline Multibranch branch page redirects to wrong page
Title: Message Title Damien Jiang created an issue Jenkins / JENKINS-51536 Blue Ocean link on Pipeline Multibranch branch page redirects to wrong page Issue Type: Bug Assignee: Denis Saponenko Components: blueocean-plugin, pipeline-multibranch-defaults-plugin Created: 2018-05-24 23:35 Environment: Blue Ocean 1.5.0, Jenkins core 2.107.3, Pipeline 2.5, Pipeline: Multibranch 2.18 Priority: Minor Reporter: Damien Jiang On the branch page (/job/JOBNAME/job/BRANCHNAME/), clicking the "Blue Ocean" link redirects to the JOBNAME's page in Blue Ocean, rather than the BRANCHNAME's page. This makes navigating to the branch's page rather annoying. A side-effect of this is that when viewing a job in Blue Ocean that's downstream of a multibranch job, clicking the "upstream job" link doesn't send you to the build that you wanted, or even the branch that you wanted, but rather to the page for the whole job. Add Comment
[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Damien Jiang resolved as Duplicate I created a new ticket to track my issue, which may be different from this one. Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Damien Jiang Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-51208) Execution time of parallel steps displayed as max time among all steps in block
Title: Message Title Damien Jiang created an issue Jenkins / JENKINS-51208 Execution time of parallel steps displayed as max time among all steps in block Issue Type: Bug Assignee: Unassigned Attachments: pmd_timing.png Components: blueocean-plugin Created: 2018-05-08 21:16 Environment: Jenkins 2.73.3, Blue Ocean 1.5.0 Labels: blueocean Priority: Minor Reporter: Damien Jiang Current behavior: In Blue Ocean, during a parallel block, the runtime reported for each individual step is reported as the max time of any step within the block, rather than its actual runtime. This reminds me of https://issues.jenkins-ci.org/browse/JENKINS-38536, which was supposedly fixed. For example, in the screenshot, the total time of the "pmd" step should have been < 10 minutes, but it's reported as 21m56s. 21m56s is actually the runtime of the "Integration-test-runner" step (not shown). Every other step in the parallel block also reports a 21m56s runtime, despite their lesser runtimes. Parallel step runtimes are also incorrectly reported in the Blue Ocean REST API, which is my actual problem—we're trying to do analytics on step runtimes, and can't do so because they're incorrect. The times are correctly reported in, say, the pipeline plugin (/flowGraphTable), but not in Blue Ocean. Desired behavior: Correctly display the runtime of each parallel step.
[JIRA] (JENKINS-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 I noticed that more "old data" warnings are still being generated; is one of my plugins out of date and generating old datatypes? When will we stop getting these warnings? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Damien Jiang reopened an issue See above comment; this issue is happening for us on the latest version of Blue Ocean. Jenkins / JENKINS-38536 Execution time of parallel blocks of in-flight jobs wrong Change By: Damien Jiang Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Damien Jiang commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 This change appears to have caused a lot of "CannotResolveClassException: org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTValue$1" warnings to show up for old WorkflowRun objects in /adminstrativeMonitor/OldData/manage ; is it okay to discard all the data here? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Damien Jiang edited a comment on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable We're trying to do analytics on the runtime of each node using a combination of the Blue Ocean REST API, the normal Jenkins REST API, and the /wfapi routes. We've run into problems collecting all the information we want: for each node, we want its: * name (from Blue Ocean API) * start time (from Blue Ocean API) * runtime (from Blue Ocean API, but runtime for nodes in parallel steps is inaccurate, as described here : https://issues.jenkins-ci.org/browse/JENKINS-38536 ) * computer (Jenkins slave) the node runs on.This last piece of data isn't accessible from the Blue Ocean API, since it [excludes stages and parallels/blocks|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#get-pipeline-steps], and we need to find the log for the `Allocate Node` block to find the computer, as far as I know?So, we: * Use `api/json?tree=actions[nodes[displayName,id,parents]]` to get a list of _all_ workflow steps * map `Allocate node : Start` steps to the nodes found in Blue Ocean (kind of fuzzy, since parallel steps aren't allocated a node but appear in Blue Ocean, while the `Declarative: Post Actions` step is allocated a node, but doesn't appear in Blue Ocean) * use `/execution/node/[node_id]/wfapi/log` to read the log for the `Allocate node : Start` step and actually get the computer nameIt seems like an API version of the flowGraphTable would simplify this process by an awful lot, since all the information we want (other than the logs for Allocate Node steps) can be found by actually viewing the flowGraphTable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Damien Jiang edited a comment on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable We're trying to do analytics on the runtime of each node using a combination of the Blue Ocean REST API, the normal Jenkins REST API, and the /wfapi routes. We've run into problems collecting all the information we want: for each node, we want its: * name (from Blue Ocean API) * start time (from Blue Ocean API) * runtime (from Blue Ocean API, but runtime for nodes in parallel steps is inaccurate, as described here) * computer (Jenkins slave) the node runs on.This last piece of data isn't accessible from the Blue Ocean API, since it [excludes stages and parallels/blocks|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#get-pipeline-steps], and we need to find the log for the `Allocate Node` block to find the computer, as far as I know?So, we: * Use `api/json?tree=actions[nodes[displayName,id,parents]]` to get a list of _all_ workflow steps * map `Allocate node : Start` steps to the nodes found in Blue Ocean (kind of fuzzy, since parallel steps aren't allocated a node but appear in Blue Ocean, while the `Declarative: Post Actions` step is allocated a node, but doesn't appear in Blue Ocean) * use `/execution/node/[node_id]/wfapi/log` to read the log for the `Allocate node : Start` step and actually get the computer nameIt seems like an API version of the flowGraphTable would simplify this process by an awful lot, since all the information we want (other than the logs for Allocate Node steps) can be found by actually viewing the flowGraphTable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-29188) api URL for REST API is not available for flowGraphTable
Title: Message Title Damien Jiang commented on JENKINS-29188 Re: api URL for REST API is not available for flowGraphTable We're trying to do analytics on the runtime of each node using a combination of the Blue Ocean REST API, the normal Jenkins REST API, and the /wfapi routes. We've run into problems collecting all the information we want: for each node, we want its: name (from Blue Ocean API) start time (from Blue Ocean API) runtime (from Blue Ocean API, but runtime for nodes in parallel steps is inaccurate, as described here) computer (Jenkins slave) the node runs on. This last piece of data isn't accessible from the Blue Ocean API, since it excludes stages and parallels/blocks, and we need to find the log for the `Allocate Node` block to find the computer, as far as I know? So, we: Use `api/json?tree=actions[nodes[displayName,id,parents]]` to get a list of all workflow steps map `Allocate node : Start` steps to the nodes found in Blue Ocean (kind of fuzzy, since parallel steps aren't allocated a node but appear in Blue Ocean, while the `Declarative: Post Actions` step is allocated a node, but doesn't appear in Blue Ocean) use `/execution/node/[node_id]/wfapi/log` to read the log for the `Allocate node : Start` step and actually get the computer name It seems like an API version of the flowGraphTable would simplify this process by an awful lot, since all the information we want (other than the logs for Allocate Node steps) can be found by actually viewing the flowGraphTable. Add Comment This
[JIRA] (JENKINS-38536) Execution time of parallel blocks of in-flight jobs wrong
Title: Message Title Damien Jiang commented on JENKINS-38536 Re: Execution time of parallel blocks of in-flight jobs wrong This problem seems to be occurring for us on a newer version of Blue Ocean (Jenkins Core 2.73.3, Blue Ocean 1.4.2 + dependencies, Pipeline 2.5, Pipeline: API 2.26). We have a parallel step where each of the individual nodes has a clearly different runtime, but Blue Ocean (and the Blue Ocean API) report all the parallel nodes as having roughly the same runtime (+/- a few ms). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44981) Developer can see node steps within the step listing
Title: Message Title Damien Jiang commented on JENKINS-44981 Re: Developer can see node steps within the step listing Hi, I noticed this has been in progress for many months; is there a projected release date for i t? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-44981) Developer can see node steps within the step listing
Title: Message Title Damien Jiang edited a comment on JENKINS-44981 Re: Developer can see node steps within the step listing Hi, I noticed this has been in progress for many months; is there a projected release date for i t it ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Damien Jiang commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline It's been over a year since There are various longer-term plans for analytic capabilities. Are there any updates on this? There are two annoyance with pipeline builds on multiple nodes: 1. It's hard to tell which nodes were used for which pipeline steps (addressed by the "setting build display name" idea in the comments here) 2. It's hard to tell which jobs/pipeline steps were run on a node, which is what this ticket was originally about. Are there any workarounds for the latter? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
