Use BRANCH_NAME in environment as fallback #1288
Conversation
There was a problem hiding this comment.
This PR tries to fix the situation
Does this PR try to fix the situation, or do you know for sure that it fixes the situation? That is, are you running this PR in production and have you verified this PR fixes the problem? I am more of an interim maintainer than a maintainer, I don't use GitLab, and I have no way of testing this change. I would only feel comfortable merging and releasing this PR if you have tested it on a production Jenkins server.
It actually fixes the situation.
The problem is not hard to reproduce so I just tested the fix in my local (docker) test environment (set up by following https://github.com/jenkinsci/gitlab-plugin/blob/master/src/docker/README.md). |
|
Any chance you could download the incremental build from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/gitlab-plugin/1.5.33-rc1406.50cf09d3a_6fd/ and do a functional test on a production server? For instructions on how to install a custom plugin build, see: https://www.jenkins.io/doc/book/managing/plugins/#advanced-installation |
|
Sorry to leave you halfway through review, but I recently removed myself as the maintainer of this plugin in jenkins-infra/repository-permissions-updater#2605, so I will not be able to merge this PR. You can consider adopting the plugin to merge and release the PR. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin. |
krisstern
changed the title
|
@martinnemec3 Thanks for the PR! The solution looks intuitive enough for me. |
|
An ideal situation is if someone can test this out on a production server... |
krisstern
added
bug
krisstern
changed the title
|
Thanks @martinnemec3! |
Using ff only merging strategy in gitlab results in having same commit on a feature branch and on the main branch (there it appears after the merging is done). This PR tries to fix the situation when jenkins multibranch pipeline job is used to build both the feature branch and main branch. The problem is that status update request does not contain the "ref" parameter needed to set the status for branch correctly.
Fixes #1010.