0

We are trying to integrate pull request based testing into our legacy code and the problem is there are lot of errors and warnings needs to be fixed.

So, our first step is while merging new branches into the master not increasing the existing warnings.

Is there a plug-in for checking current problems in master and if there are new warnings with new pull request automatically decline and show only those new issues ?

Improve this question
2
  • Voting for reopening for it is related to build-testing processes and tools.
    – João Farias
    Mar 2, 2017 at 16:56
  • 2
    @JoãoGFarias I 100% agree. There's multiple reasons why this question is perfectly on topic here. Yes, this question is also perfectly legitimate for software engineering, but it's fine here too. And it's targeted at people with testing experience. What more could we want?
    – corsiKa ♦
    Mar 2, 2017 at 21:02

1 Answer 1

Reset to default
2

You will need some steps to get there:

  1. Have you repository system to notify Jenkins about the PR.

    That will depend on your system. GitHub and Bitbucket have system to do it.

  2. Build the PR branch.

  3. Report the job status.

You can mitigate conflicts using a branching model like Gitflow, so developers can merge more frequently and only send PR without conflicts.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.