Hi there,
I am converting a series of jobs to pipeline jobs.
I am not having any luck in finding the post-action stage or finding a way
to do this.
a 'step' isn't appropriate to the situation (as it won't trigger on failed).
If someone knows the answer to this, I would be happy to go over to
build status}
}
Thanks !! for your help.. If anything, an example of try/catch finally
would be helpful. I would see what I could do to share back.
Much appreciated.
Mike Caspar
On 2016-05-05 3:12 PM, Baptiste Mathus wrote:
Hi,
There's no such concept in pipeline.
As Jesse explained
-05-05 3:24 PM, Mike Caspar wrote:
Thanks.
I like the try/catch/finally option if that would work.
I have setup a Pipeline Organization to auto-import my Scripts.
it sets up all the necessary repos to build each one.
The problem occurs that I have no way to set the typical "email on
su
ill need to set
currentBuild.status and re-throw the exception in order for the build
to be marked as failed.
Look at this example which I wrote:
https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy
--
Craig
On Thu, May 5, 2016 at 12:24 PM, Mike Caspar <mailto:m...@caspar.com&g
In a multi-branch scenario, are there some examples anywhere of how to make
sure the deploy happens only from the master branch?
I am guessing I need to build an if statement of some sort in groovy to
confirm which branch I am on?
Thanks for any help.
Mike
--
You received this message bec
correctly.
On Thu, May 5, 2016 at 9:47 PM, Mike Caspar <mailto:m...@caspar.com>> wrote:
Awesome.
This worked great.
I managed to simply wrap a try around my whole file and then a
catch/finally for success and failure.
Craig, I'll look at the example. Thanks
results into finally caused script access problems.
Mike
On 16-05-07 09:31 AM, Baptiste Mathus wrote:
Le 5 mai 2016 9:47 PM, "Mike Caspar" <mailto:m...@caspar.com>> a écrit :
>
> Awesome.
>
> This worked great.
>
> I managed to simply wrap a try a
I am working on a pipeline that does Test/Deploy after a commit.
That's all cool!
HoweverWhen I create a branch (for a new feature), and it gets
auto-launched as a new build pipeline, how do I prevent the same
Jenkinsfile from initiating the Deploy step, since it's the same
Jeniinsfile ?
i, 13 May 2016 at 11:24 Mike Caspar <mailto:mikecanbefo...@gmail.com>> wrote:
I am working on a pipeline that does Test/Deploy after a commit.
That's all cool!
HoweverWhen I create a branch (for a new feature), and it gets
auto-launched as a new build p
Awesome.
Thanks !
Mike
On 16-05-13 09:21 AM, Nigel Magnay wrote:
What we do is look at what the branch name is in the Jenkinsfile itself.
I.E:
if( branchName.equals("master") )
{
// deployment steps
}
On Fri, May 13, 2016 at 12:24 AM, Mike Caspar
mailto:mikecanbefo...@gmail.c
10 matches
Mail list logo
