-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very Long gitlabMergeRequestDescription environment variable breaks builds #1724
Comments
Hi @Reamer, thank you for reporting this bug! We would love to have you submit a patch for this via a PR. |
What kind of pull request should I aim for?
|
Hi @Reamer my apologies for the delayed response! I personally prefer option 3: "Drop gitlabMergeRequestDescription from env variables, with an additional plugin configuration". But from your personal experiences what would be your preference? What works best in your use case? |
From my point of view, the description should not be passed on as an environment variable, so I would simply drop it. Option 2. |
Hi @Reamer, Sure, sounds good to me! |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Ubuntu 22.04
Reproduction steps
Expected Results
The job runs smoothly
Actual Results
git execution fails
Anything else?
I only found out by luck that it was due to the long description of the merge request. The background is that I use Renovate. Renovate stores the change log of the libraries in the merge request description. Change logs can become very long.
To solve the problem, I have made the following code change. I know it's a little hack. The
1000
has no deeper meaning except to not overload the environment variable. I would prefer to remove the environment variable completely, but in my opinion this should be configurable. Perhaps some users evaluate the variable.Are you interested in contributing a fix?
How would you solve the problem? I would be happy to try to submit a pull request.
The text was updated successfully, but these errors were encountered: