[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Ramachandra Kamath Arbettu updated an issue Jenkins / JENKINS-57796 Checkmarx affected by JEP-200 Change By: Ramachandra Kamath Arbettu Priority: Major Critical 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.199746.1559317468000.22001.1559746200386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Ramachandra Kamath Arbettu commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 I confirm this issue from the version 8.9.0 of the plugin. We are encountering the same after updating from 8.80.0. We are running on Jenkins ver. 2.164.3 Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@557f1a37: java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see https://jenkins.io/redirect/class-filter/ 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.199746.1559317468000.21998.1559746140519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47349) Parallel stage tool tip shows 0s for every stage irrespective of the execution time.
Title: Message Title Ramachandra Kamath Arbettu updated an issue Jenkins / JENKINS-47349 Parallel stage tool tip shows 0s for every stage irrespective of the execution time. Change By: Ramachandra Kamath Arbettu Priority: Minor Major 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Ramachandra Kamath Arbettu updated an issue
Jenkins / JENKINS-39203
All stages show up as UNSTABLE when only one stage should
Change By:
Ramachandra Kamath Arbettu
{panel:title=Improvement on roadmap|titleBGColor=#3878de |titleColor=white }This improvement is on the Blue Ocean project roadmap. Check the [roadmap page|https://jenkins.io/projects/blueocean/roadmap/] for updates.{panel} *Problem*When there is a build which has a stage that marks the build as unstable, all the stages, parallels and steps are marked incorrectly as unstable than just the unstable stage, parallel and step that caused the Pipeline to be unstable.*To reproduce*# Build the multibranch pipeline "kzantow/failure-project" from github# Look at the "michaelneale" branch# Note that all stages are unstable (check the api json, all stages are UNSTABLE but should not be, only the final stage should be).
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because
[JIRA] (JENKINS-48879) If a parallel stage is skipped blueocean shows "Waiting for run to start" instead of the other stage
Title: Message Title
Ramachandra Kamath Arbettu updated an issue
Jenkins / JENKINS-48879
If a parallel stage is skipped blueocean shows "Waiting for run to start" instead of the other stage
Change By:
Ramachandra Kamath Arbettu
In a pipeline with to parallel stages where one stage is skipped BlueOcean shows "Waiting for run to start", although the other stage produces log outputs. (See Waiting.PNG)It seems like the skipped stage is selected by default. However, there is no output.If there is an additional stage after the parallel stages and the pipeline reaches this stage, the pipeline is visualized properly. However, if you click on the skipped stage the message "Waiting for a run to start" is shown again. Steps to reproduce:Execute the following pipeline:{code:java}pipeline {agent anyoptions {timeout(time: 120, unit: 'MINUTES')timestamps()skipDefaultCheckout()}stages {stage('Parallel Stage') {parallel {stage("Executed Stage") { steps { script { for(i=0; i<10;i++){ echo "Temp" } } } }stage("Skipped Stage") {when { _expression_ { false } }steps { echo "I am skipped"}}}}}}{code}
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-48879) If a parallel stage is skipped blueocean shows "Waiting for run to start" instead of the other stage
Title: Message Title
Ramachandra Kamath Arbettu updated an issue
Jenkins / JENKINS-48879
If a parallel stage is skipped blueocean shows "Waiting for run to start" instead of the other stage
Change By:
Ramachandra Kamath Arbettu
A In a pipeline with two to parallel stages where one stage is skipped BlueOcean shows "Waiting for run to start", although the other stage produces log outputs. (See Waiting.PNG)It seems like the skipped stage is selected by default. However, there is no output.If there is an additional stage after the parallel stages and the pipeline reaches this stage, the pipeline is visualized properly. However, if you click on the skipped stage the message "Waiting for run to start" is shown again. Steps to reproduce:Execute the following pipeline:{code:java}pipeline {agent anyoptions {timeout(time: 120, unit: 'MINUTES')timestamps()skipDefaultCheckout()}stages {stage('Parallel Stage') {parallel {stage("Executed Stage") { steps { script { for(i=0; i<10;i++){ echo "Temp" } } } }stage("Skipped Stage") {when { _expression_ { false } }steps { echo "I am skipped"}}}}}}{code}
Add Comment
This message was sent by Atlassian JIRA
