Re: How can one get the last job ran in a pipeline script?

2018-09-14 Thread pisymbol
On Fri, Sep 14, 2018 at 2:49 PM pisymbol wrote: > I need to figure out when was the last job ran in the active pipeline > running, i.e. the current job. > > Putting it another way, I want to programmatically in the current job find > out WHEN the LAST job was ran and what was i

How can one get the last job ran in a pipeline script?

2018-09-14 Thread pisymbol
I need to figure out when was the last job ran in the active pipeline running, i.e. the current job. Putting it another way, I want to programmatically in the current job find out WHEN the LAST job was ran and what was its build RESULT (success or fail). Is there a way to do this? -aps --

Re: How to kickstart a multibranch pipeline scan?

2018-08-18 Thread pisymbol
On Sat, Aug 18, 2018 at 11:39 AM Steven Foster wrote: > That depends on the behaviors configured on the multibranch project. I > think by default newly discovered tag jobs don't automatically build. > > if you have a multibranch project called "myproject" and it has a couple > of branches under

Re: How to kickstart a multibranch pipeline scan?

2018-08-18 Thread pisymbol
uld a normal job. > > On Friday, August 17, 2018 at 4:29:24 PM UTC+1, pisymbol wrote: >> >> I have a job that creates a new branch/tag in SVN. IT does so by >> modifying some internal build files and then tagging it. >> >> What I would like to do is kickstart a multi

How to kickstart a multibranch pipeline scan?

2018-08-17 Thread pisymbol
I have a job that creates a new branch/tag in SVN. IT does so by modifying some internal build files and then tagging it. What I would like to do is kickstart a multibranch pipeline scan when that job completes. How can one accomplish this? Googling has not proven very fruitful. I thought I

Re: How to keep a running docker container after a build fails?

2018-02-13 Thread pisymbol .
On Tue, Feb 13, 2018 at 7:56 AM, Reinhold Füreder wrote: > Hi aps, > > > > Just in case the problem is still there and to avoid a misunderstanding: > > > > Based on (a) Victor’s hint “tr[y] with the docker.inside syntax […] It > might give you the chance to debug it

Re: Multibranch Project Parameterized Drop-down?

2018-02-09 Thread pisymbol .
On Fri, Feb 9, 2018 at 8:53 AM, Victor Martinez < victormartinezru...@gmail.com> wrote: > Although I'm not aware of any dsl for that parameters, but the below URL > might help you to convert UI configuration to pipelines easily: > >

Re: Multibranch Project Parameterized Drop-down?

2018-02-08 Thread pisymbol
On Thursday, February 8, 2018 at 3:02:16 PM UTC-5, pisymbol wrote: > > How do I add build parameters to a multibranch project that is a drop down > menu? > > I can't find an example anyway and I know there has to be a way to do > this! :-) > > I was hoping some

Multibranch Project Parameterized Drop-down?

2018-02-08 Thread pisymbol
How do I add build parameters to a multibranch project that is a drop down menu? I can't find an example anyway and I know there has to be a way to do this! :-) I was hoping some kind soul can give a DSL and/or Groovy script syntax example. Thanks! -aps -- You received this message

Re: How to keep a running docker container after a build fails?

2018-02-08 Thread pisymbol
On Thursday, February 8, 2018 at 5:37:05 AM UTC-5, Victor Martinez wrote: > > Just an idea, you have tried with the docker.inside syntax? ( > https://jenkins.io/doc/book/pipeline/docker/#running-sidecar-containers) > It might give you the chance to debug it somehow. > > What's the difference

Re: How to keep a running docker container after a build fails?

2018-02-07 Thread pisymbol .
On Wed, Feb 7, 2018 at 2:43 PM, niristotle okram wrote: > for debugging, > why not put some more echo/ls commands to check if the file you are > looking is there or not from the container. > Sure, but it takes 30+ minutes just to get to this spot. > > The documentation

Re: How to keep a running docker container after a build fails?

2018-02-07 Thread pisymbol
On Monday, February 5, 2018 at 3:16:04 PM UTC-5, pisymbol wrote: > > withDockerContainer(image: "centos:7", args: "--privileged") { > stage ('Negotiate World Peace') {} > stage ("Cure Cancer") {} > > Anyone do this?

Re: How to keep a running docker container after a build fails?

2018-02-05 Thread pisymbol
withDockerContainer(image: "centos:7", args: "--privileged") { stage ('Negotiate World Peace') {} stage ("Cure Cancer") {} etc. -aps -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and

How to keep a running docker container after a build fails?

2018-02-05 Thread pisymbol
I have Googled this and still can't find as simple answer. Is there a way to have Jenkins not clean up the container after a build? I am having a build failure and I don't quite understand why (a file doesn't exist when it should). But I have to replay the entire build which takes about 40

Re: How do you iteratively work on a Jenkinsfile?

2018-02-02 Thread pisymbol
On Friday, February 2, 2018 at 7:28:26 AM UTC-5, Oleg Nenashev wrote: > > For this purpose I am using FileSystem SCM plugin to retrieve scripts > without committing + local Docker snapshot of the production instance. You > can find some info about my approach in these slides >