Reduce TravisCI jobs about jenkins-library HOT 6 CLOSED

Cannot confirm that behavior. I have only one travis job triggered. See e.g. here.

I'm not an expert for the .travis.yml, but I can't see two configured jobs in that file (I'm even not sure if more than one job can be configured ...)

Right now we have a switch depending on ${TRAVIS_PULL_REQUEST} in our build. But that is not used for preventing builds to start, it only controls what happens inside the - already started - build. Would be possible to use an if: trigger condition, see here.

But first I would like to clarify the diff between your setup (getting two builds) and my setup (getting only one build)

from jenkins-library.

Here is the job link.

from jenkins-library.

For your PR we have two build

• one build (the "pr" build) builds the merge commit between github/master and the HEAD of the PR branch.
• one build (the "push" build) builds the HEAD of the PR branch.

For my PRs I get only the "pr" build.

IMO the "pr" build is the interesting one, since this build reflects what happens if the PR would be merged. The "push" build is more the less nice to have.

I see one difference in our working mode. Your PR is based on a PR-branch located in SAP/jenkins-library. My PR is located in marcusholl/jenkins-library.

When I have time I will setup the travis build for my repo and try to introduce the ifcondition. Something like if: "${TRAVIS_PULL_REQUEST}" != "false" .

from jenkins-library.

This is what I meant, the branch is located in this repo and therefore receives a branch job. I think we should limit these branch jobs to master.

from jenkins-library.

I not convinced master in not a cool solution. We are interested in all branch which are bound to a pull request.

As already outlined above, what about: if: "${TRAVIS_PULL_REQUEST}" != "false"? Regarding TRAVIS_PULL_REQUEST see here.

from jenkins-library.

fix with #245

from jenkins-library.