Re: Jenkins pipeline with github organization folder, avoiding multiple checkouts

On Thu, Dec 22, 2016 at 12:39 AM, Jordan Soet wrote: > I'm trying to set up Jenkins with the Github Organization Folder plugin but > I'm finding that it's checking out our entire repository twice, once in the > @script directory and once in the actual workspace directory. This is a > problem for u

Re: Declarative Piepline: conditional execution of stage/steps depending on branch

I think that should be doable already? Just remember that if "currentBuild.result == null", that's success. A. On Wed, Dec 21, 2016 at 1:54 PM, Omeka wrote: > Thanks andrew it works very well. > > do you have any intention to make failire/success/etc... usable in normal > stages so i can execut

How To Execute a stage even if previous stage has failed?

In scripted pipeline the use of try/catch/finaly allows a stage to be executed even though the previous stage has failed, let say unit tests, checkstyles have failed and we still want to execute a sonaqube analysis (why would we want to do that is another question for another group). In the dec

Re: Encryping credentials in a format that Jenkins can read

This is what openshift is using to encode login passwords: https://github.com/openshift/jenkins/blob/master/1/contrib/jenkins/jenkins-common.sh#L32-L41 It may also work in this case. On Friday, December 23, 2016 at 6:59:12 AM UTC, Ali Ok wrote: > > Ah, also, I saw in this thread >