jenkins-multibranch | project template to use Jenkins Pipeline | Continuous Deployment library

It looks like both the: Branch API Plugin and the Git client plugin were sending events to Jenkins that triggered a build.

We solved the issue by suppressing automatic triggering.

This can be done either in the UI simply by going to your job, selecting configure from the left then adding the property

Suppress automatic SCM triggering.

Alternatively for a code solution (which I ended up using) add it to the seedjob.groovy as follows:

You have to encapsulate your commands with script :

For using credentials in a Jenkins Pipeline, there are a couple plugins that I would consider essentially part of the Jenkins Core (even though they are plugins):

• Credentials Plugin
• Credentials Binding Plugin

These can combine to give you a way to administratively manage credentials as well as provide for ways to consume them inside of Jobs. There are additional plugins built on top of these providing credential type implementations. For example, the SSH Credentials Plugin allows you to store SSH credentials in Jenkins.

The Credentials Binding Plugin provides the withCredentials step. The documentation has some examples on how you could use it. Here is an example from the documentation: