jenkinsci / jenkinsci/gitlab-plugin
Investigate getting access to GitLab env vars in Multibranch projects
Open
feature request
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 615
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 10
Description
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.
Contributor guide
Assessment
This issue has not been assessed yet.