That was it... just had to specify the branch. d'oh.
build job: '/master', wait: false
On Thursday, April 13, 2017 at 10:42:46 AM UTC+3, Idan Adar wrote:
>
> I should mention that both jobs are multi-branch jobs...
> should the job name also somehow incorporate the branch name? i.e.
>
I should mention that both jobs are multi-branch jobs...
should the job name also somehow incorporate the branch name? i.e. "develop"
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from
Yep, found "build" as well. I thought maybe it's done differently in
declarative pipelines...
Ended up with the following, however despite this, it did not start.
post {
// Run end-to-end tests, if requested
success {
script {
if (BRANCH_NAME == "develop") {
This is how I do this, should be easy enough -
pipeline {
stages {
stage ('xxx') {
steps {
...
...
build job: '', parameters: [
string(name: 'PARAM1', value: "xxx"),
string(name: 'PARAM2, value: "yyy")
]
Hi,
Lets assume there are two job:
1. a job for a micro-service repository
2. a job for end-to-end tests
I'd like, in specific cases, to start the end-to-end tests job from the
micro-service job.
For example, after introducing a change that even though passed unit
testing and integration
