Re: [workflow-plugin] Using workflow in same SCM as code

2015-08-12 Thread Michael Lasevich
Thanks, that looks awesome, but I am having some trouble with it in practice (I think these are all MultiBranch plugin problems, but still) 1 - It seems to be able to create jobs but not delete them - I get an error like this if a previously created job is to be deleted: hudson.security.Access

Re: [workflow-plugin] Using workflow in same SCM as code

2015-08-12 Thread Jesse Glick
On Tuesday, July 14, 2015 at 1:16:35 AM UTC-4, Michael Lasevich wrote: > > I want to keep my workflow script in same git repo as rest of my code and > want to avoid hard-coding URLs or branch names into the workflow. > Multibranch workflow, in beta. -- You received this message because you ar

Re: [workflow-plugin] Using workflow in same SCM as code

2015-07-15 Thread Christoph Obexer
Am 2015-07-14 um 07:16 schrieb Michael Lasevich: I want to keep my workflow script in same git repo as rest of my code and want to avoid hard-coding URLs or branch names into the workflow. I also want that, I consider that a hard requirement actually. When I use "Groovy CPS DSL from SCM" it see

[workflow-plugin] Using workflow in same SCM as code

2015-07-13 Thread Michael Lasevich
I want to keep my workflow script in same git repo as rest of my code and want to avoid hard-coding URLs or branch names into the workflow. When I use "Groovy CPS DSL from SCM" it seems to check out into a separate workspace, so I do not have access to anything in the git repo. I could check o