Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add option to exclude long description
See original GitHub issueCould an option be added to exclude ghprbPullLongDescription from the build. This seems to be the field that we hit escaping issues with. The issue we see is sometimes the escaping results in commands executing from the description. In our internal PR descriptions, we have started adding testing or verification notes / suggestions, which in one case included a tail -f /var/log/messages command, which executed.
Observed on ghprb-plugin 1.39.0
From what I can tell, we personally don’t use the long description in our build process. Till execution of descriptions is resolved, perhaps give us the option to not attempt to pass it through?
Similar issues: #410, which was closed as a duplicate of #327 https://issues.jenkins-ci.org/browse/JENKINS-29919
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’ve worked around this problem by using the EnvInject plugin and setting the ghprbPullLongDescription and ghprbPullTitle variables to empty before the build:
I have faced the same issue with the double quotes in the PR description. more details in https://github.com/jenkinsci/ghprb-plugin/issues/364#issuecomment-1055508888