Issue Type: Bug Bug
Assignee: Justin Ryan
Components: job-dsl-plugin
Created: 16/May/14 10:04 PM
Description:

In the github wiki, there are examples that imply the downstreamParameterized block should go inside steps:

"Job DSL Commands"
steps {
        ...
        downstreamParameterized(downstreamClosure) // See [[Job Reference]] for downstreamClosure syntax
        ...
    }

Then in the Job Reference section

"Job Reference"
steps {
    downstreamParameterized {
        trigger('Project1, Project2', 'UNSTABLE_OR_BETTER', true,
                    ["buildStepFailure": "FAILURE",
                            "failure": "FAILURE",
                            "unstable": "UNSTABLE"]) {
            currentBuild() // Current build parameters
            propertiesFile('dir/my.properties') // Parameters from properties file
            gitRevision(false) // Pass-through Git commit that was built
            predefinedProp('key1', 'value1') // Predefined properties
            predefinedProps([key2: 'value2', key3: 'value3'])
            predefinedProps('key4=value4\nkey5=value5') // Newline separated
            matrixSubset('label=="${TARGET}"') // Restrict matrix execution to a subset
            subversionRevision() // Subversion Revision
        }
        trigger('Project2') {
            currentBuild()
        }
    }
}

I kept getting exceptions when trying to follow these instructions and it wasn't until I dug though the code myself that I found it actually belongs in the publishers block. Can someone please update these references?

Also, please consider making your github wiki editable or forkable

Project: Jenkins
Priority: Major Major
Reporter: Andrew Matheny
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to