[JIRA] (JENKINS-58879) EC2 plugin queue locks have resurfaced
Title: Message Title Junze He commented on JENKINS-58879 Re: EC2 plugin queue locks have resurfaced We tested it with 1.45 and didn't notice any locks. Thanks! 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.201212.1565377068000.1830.1565709480134%40Atlassian.JIRA.
[JIRA] (JENKINS-55901) Branch Rebasing Does not Update config.xml or Options
Title: Message Title Junze He created an issue Jenkins / JENKINS-55901 Branch Rebasing Does not Update config.xml or Options Issue Type: Bug Assignee: Denis Saponenko Components: pipeline, pipeline-multibranch-defaults-plugin Created: 2019-01-31 22:15 Priority: Minor Reporter: Junze He We removed the compressBuildLog() option from our pipelines after realizing https://issues.jenkins-ci.org/browse/JENKINS-54678 was causing us to not be able to read the logs in the UI after they are compressed. The pipelines created after branching off of master without that option run fine. However, the pipelines created from before the change on master and had to rebase still have the option in their config.xml on master and still compresses the logs. Their Jenkinsfile does not show the option still. We have managed to get around this by either deleting the option from the config.xml or by committing the option, running the pipeline, committing removing the option, and running again. Add Comment
[JIRA] (JENKINS-54676) Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished
Title: Message Title Junze He created an issue Jenkins / JENKINS-54676 Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-cps-plugin Created: 2018-11-16 17:57 Environment: Jenkins Version: 2.149 Pipeline Related Plugins: Pipeline: Groovy (workflow-cps): 2.60 Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.9.0 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.9.0 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.12 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 Pipeline: Declarative Agent API (pipeline-model-declarative-agent): 1.1.1 GitHub Pipeline for Blue Ocean (blueocean-github-pipeline): 1.9.0 Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.7 Pipeline: Job (workflow-job): 2.28 Blue Ocean Pipeline Editor (blueocean-pipeline-editor): 1.9.0 Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.9.0 AWS CodePipeline Plugin (aws-codepipeline): 0.38 Pipeline (workflow-aggregator): 2.6 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 Pipeline: Step API (workflow-step-api): 2.16 Docker Pipeline (docker-workflow): 1.17 Pipeline: Multibranch (workflow-multibranch): 2.20 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.9.0 Pipeline: Supporting APIs (workflow-support): 2.22 Pipeline: Basic Steps (workflow-basic-steps): 2.12 Pipeline: Declarative Extension Points API (pipeline-model-extensions): 1.3.2 Pipeline: Build Step (pipeline-build-step): 2.7 Pipeline: Stage Step (pipeline-stage-step): 2.3 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.26 Pipeline: Model API (pipeline-model-api): 1.3.2 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: SCM Step (workflow-scm-step): 2.7 Pipeline: API (workflow-api): 2.31 Pipeline: Input Step (pipeline-input-step): 2.8 Labels: pipelines workflow-cps pipeline:groovy Priority: Minor
[JIRA] (JENKINS-54190) All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Title: Message Title
Junze He created an issue
Jenkins / JENKINS-54190
All of the parallel stages with a regression post trigger will trigger if one of the stages fail.
Issue Type:
Bug
Assignee:
Mads Nielsen
Components:
blueocean-plugin, pipeline, postbuild-task-plugin
Created:
2018-10-22 19:03
Environment:
Worker Operating Systems: Debian Stretch Jenkins ver 2.138 Pipeline ver 2.5 Blue Ocean 1.8.3
Priority:
Minor
Reporter:
Junze He
This happens only if that stage fails before the other stages. If the failing stage happens last then the stages which have already completed as passing do not have their regression post conditions triggered. Otherwise, the currentBuild.currentResult of the other stages, which should be passing, become FAILURE despite all of the steps being green.
// Sample Jenkinsfile to test this
#!groovy
pipeline {
agent {
node {
label ""
customWorkspace "workspace/test_regression"
}
}
options {
buildDiscarder(logRotator(numToKeepStr: '50'))
compressBuildLog()
timestamps()
}
stages {
stage('Parallel'){
parallel {
stage("Passing Stage 1") {
options {
timeout(time: 120, unit: 'MINUTES')
}
steps {
sh "ls"
}
post {
regression {
echo "This stage has a regression"
echo "Current Result: ${currentBuild.currentResult}"
echo "Previous Build Result: ${currentBuild.previousBuild.result}"
}
}
}
stage("Failing Stage 1") {
options {
