Open omehegan opened 6 years ago
@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.
Any workaround available? I really need this
is there any plans to implement this soon?
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.