-
Improvement
-
Resolution: Unresolved
-
Minor
-
Jenkins 2.227
gitlab-branch-source-plugin 1.4.4
A great addition would be to have GitLab Webhook information available as environment variable such as:
- object_kind -> GITLAB_OBJECT_KIND
- projectId -> GITLAB_PROJECT_ID
This would allow us to do different things in our scripted pipelines depending on the type of event.
An easier solution would be to provide just one env variable like GITLAB_BRANCH_TYPE that could be either NORMAL / CHANGE_REQUEST / TAG
While we do not plan to use projectId at the moment, I still think it could benefit other users of the plugin.
[JENKINS-61683] Add GitLab variables to environment
| Description |
Original:
A great addition would be to have GitLab Webhook information available as environment variable such as: * `object_kind` -> `GITLAB_OBJECT_KIND` * `projectId` -> `GITLAB_PROJECT_ID` This would allow us to do different things in our scripted pipelines depending on the type of event. An easier solution would be to provide just one env variable like `GITLAB_BRANCH_TYPE` that could be either `NORMAL` / `CHANGE_REQUEST` / `TAG` While we do not plan to use `projectId` at the moment, I still think it could benefit other users of the plugin. |
New:
A great addition would be to have GitLab Webhook information available as environment variable such as: * {{object_kind}} -> {{GITLAB_OBJECT_KIND}} * {{projectId}} -> {{GITLAB_PROJECT_ID}} This would allow us to do different things in our scripted pipelines depending on the type of event. An easier solution would be to provide just one env variable like {{GITLAB_BRANCH_TYPE}} that could be either {{NORMAL}} / {{CHANGE_REQUEST}} / {{TAG}} While we do not plan to use `projectId` at the moment, I still think it could benefit other users of the plugin. |
| Description |
Original:
A great addition would be to have GitLab Webhook information available as environment variable such as: * {{object_kind}} -> {{GITLAB_OBJECT_KIND}} * {{projectId}} -> {{GITLAB_PROJECT_ID}} This would allow us to do different things in our scripted pipelines depending on the type of event. An easier solution would be to provide just one env variable like {{GITLAB_BRANCH_TYPE}} that could be either {{NORMAL}} / {{CHANGE_REQUEST}} / {{TAG}} While we do not plan to use `projectId` at the moment, I still think it could benefit other users of the plugin. |
New:
A great addition would be to have GitLab Webhook information available as environment variable such as: * {{object_kind}} -> {{GITLAB_OBJECT_KIND}} * {{projectId}} -> {{GITLAB_PROJECT_ID}} This would allow us to do different things in our scripted pipelines depending on the type of event. An easier solution would be to provide just one env variable like {{GITLAB_BRANCH_TYPE}} that could be either {{NORMAL}} / {{CHANGE_REQUEST}} / {{TAG}} While we do not plan to use {{projectId}} at the moment, I still think it could benefit other users of the plugin. |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |