[ https://issues.jboss.org/browse/JBIDE-24182?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24182: ------------------------------- Description: In JBIDE-22819 I created a buildflow job to orchestrate the steps involved in staging or release of jbt/ds. However, on CCI we can now write a pipeline job [1] in groovy, which can trigger downstream builds [2] and wait for approval/input [3] before continuing. This might be an ever better visualization & control for these stages/releases. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/vscode-j... -> https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile [2] https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job [3] https://github.com/redhat-developer/vscode-java/blob/master/Jenkinsfile#L68 was: Job requires about 13 params: {code} version (JBT and JBDS) versionWithRespin (JBT and JBDS) versionWithRespin_PREV (JBT and JBDS) target platforms (min, max, central) respin # (- or a, b, c) devsuite installerExe url stream_JBT=master # or 4.4.neon stream_DS=master # or 10.0.neon {code} See https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... for the steps to convert into a job -- This message was sent by Atlassian JIRA (v7.2.3#72005)