Well, not exactly. I found a workaround by reworking the entire logic.
My landscape is: one master declarative pipeline kicks off multiple child
pipeline jobs.
Both the master and the child pipelines are instances created out of shared
libraries (jobBuilder, pipelineBuilder) and I want to be
Hey,
Here is my pipeline landscape:
Master pipeline is triggering smaller child pipelines.
Parent pipeline script snippet:
stage('Integration Tests') {
steps {
script {
def jobs = [:]
pipelineIntegrationJobs.each {
i ->
Hey,
I have been trying different ways to collect the result from pipeline
triggered downstream jobs without any success. Any idea how to do it?
Apprioach #1 - Mapping the build data trough Cause.UpstreamCause (as
suggested here:
I would like to collect all triggered jobs results.
My script looks like this:
stage('Integration Tests') {
steps {
script {
def jobs = [:]
def childJob
def childJobName
pipelineIntegrationJobs.each {
i -> jobs["${nirvanaMajor}.${nirvanaMinor}_${i}"] = {
childJob = build (job:
Hey,
Trying to create a script that restarts all slaves using Jenkins
Administrative Script console.
Script 1:
import hudson.util.RemotingDiagnostics;
createShellScriptCommand = "echo \"/usr/sbin/shutdown -r now"
grantExecutionPrvilige = "chmod +x /home/nirdevadm/shutdown.sh"
Yep,
My libraries are already configured there, but the DSL script is obviously
not working. Perhaps the syntax needs to be different...
On Sunday, August 26, 2018 at 6:04:36 PM UTC+3, Jan Monterrubio wrote:
>
> Manage Jenkins -> configure system -> global libraries
>
> You can add your shared
Hey,
I am looking for advice how to achieve usage of Jenkins shared library in
Job DSL –
I use this snipped to seed a job whose functionality is in Jenkins file:
job('my-small-test-job') {
parameters {
stringParam('branch', '${branch}')
}
removedJobAction: 'IGNORE'
def releaseScript =