Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Owen Mehegan
Some comments inline... On Thu, Nov 12, 2015 at 10:37 AM, Jesse Glick wrote: > On Wed, Nov 11, 2015 at 6:22 PM, Owen B. Mehegan > wrote: > > I can't figure out how to access the branch parameters that the > > plugin is setting. If you look at the

Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Robert Sandell
It seems like when the job is not an AbstractProject e.g. a WorkflowJob then the job isn't scheduled with parameters https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java#L204 [1] and [2] are some examples on how to schedule a job

Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Kanstantsin Shautsou
@Robert both examples shows how hacky workflow support. Imho API should be clear for plugin developers. @Owen If you unsure whether variables was put into build, then check build.xml content. If unsure what SCMs code see, then place breakpoint in IDE and view available data. Usually trigger

Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Jesse Glick
On Wed, Nov 11, 2015 at 6:22 PM, Owen B. Mehegan wrote: > I can't figure out how to access the branch parameters that the > plugin is setting. If you look at the 'Using it with a job' section of the > readme, it has you configure Git to expect variables like

Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Owen Mehegan
Some comments inline... On Thu, Nov 12, 2015 at 2:51 AM, Robert Sandell wrote: > It seems like when the job is not an AbstractProject e.g. a WorkflowJob > then the job isn't scheduled with parameters >

Re: Help needed with Workflow support in gitlab-plugin

2015-11-12 Thread Jesse Glick
On Thu, Nov 12, 2015 at 3:01 PM, Owen Mehegan wrote: > that the plugin should move toward the > multibranch project model, rather than one job which takes a parameter of > branch (and whose current "status" is therefore usually meaningless). Exactly. > I suspect it will be

Re: Help needed with Workflow support in gitlab-plugin

2015-11-11 Thread Mirko Friedenhagen
Hello Owen, as far I know environment variables need to be prefixed with env when accessing them from Groovy, so maybe it should be "origin/${env.gitlabSourceBranch}" …? Regards Mirko -- Sent from my mobile Am 12.11.2015 00:22 schrieb "Owen B. Mehegan" : > Earlier this