Gitlab-plugin: Investigate getting access to GitLab env vars in Multibranch projects

Created on 16 Jan 2018 · 3Comments · Source: jenkinsci/gitlab-plugin

When GitLab triggers a Pipeline Multibranch project in Jenkins the plugin simply triggers branch polling in Jenkins and leaves it to Jenkins to decide whether to trigger any builds. This prevents us from populating any env vars with data sent from the GitLab webhook. It would be nice if this could be resolved, so that Multibranch projects can make use of those the way regular Pipeline and Freestyle jobs do.

Would fix #495.

feature request

Source

omehegan

👍8

Most helpful comment

Any workaround available? I really need this

dweggemans on 13 Jun 2018

👍20

All 3 comments

@abayer would you be able to comment on possible solutions to this problem? Our previous maintainer had concluded that we just couldn't do this for Multibranch jobs when he implemented support for them.

omehegan on 16 Jan 2018

Any workaround available? I really need this

dweggemans on 13 Jun 2018

👍20

is there any plans to implement this soon?