We are using Jenkins and Bitbucket to manage our CI environment.
Our pull request jobs are triggered with the Stash pull request builder plugin.
Last week, we have updated our Jenkins PR job to launch some functional tests if the developer (or the QA) pass some parameters using this syntax:
If Jenkins find a value for testing_scope, it will trigger a PR job + a functional test job (it will use the parameter value to determine the testing scope).
It's really useful to launch some tests on a pull request.
If this comment (with the testing_scope parameter) remains on the PR, when a developer launch a new PR build with "test this please" (or the build is launched on a new commit), the plugin will find the testing_scope parameter in the old comment and will use it to trigger the Jenkins PR job.
In this case, the developer only want to trigger a PR job. .
Is it intentional to scan all the old comments to find the parameters?
If so, what we propose is to add a new parameter (in the advanced section of the plugin) to read the parameters only in the last Bitbucket comment:
Only use the parameters from the last comment
If the parameter value is true, then the plugin will ignore the parameters found in the old comment.
It will solve our issue.
Can we propose a development to add this new parameter?
Bruno, release manager at https://www.forgerock.com/