Baseline for quality report, coverage difference and pipeline badge status should use last pipeline from master and not last commit from master
I have configured the
codequality report and the coverage in all my projects (private Gitlab EE starter).
I also have seen the code quality report and the coverage difference in MRs, but just for the project I use to test CI after disabling automatic commits on master (I will explain those right below).
For all real my projects I can't see the code quality report and coverage difference on MRs.
Normally all my projects will have commits on master without any pipeline. Current status of master branch:
I think the reason that MRs on my projects doesn't show correct values is because my master branch will always have commits that doesn't run any job. These commits are generated using the maven release plugin and all my jobs are configured to ignore commits performed by our CI user.
Here is the current status of the project I used to test this behavior:
The first picture is also the current master branch status after seeing the unknown pipeline badge.
Pipeline is Unknown even with last master pipeline being successful. Is this happening because my master branch have commits without any associated pipeline? As an user I expected the pipeline badge to be SUCCESS since my last pipeline is green.
Code quality report and coverage difference
To test code quality report and coverage difference I modified my code to add few un-tested lines and created a MR.
My last pipeline on master (with code quality artifact):
Failed to load codeclimate report even having the baseline artifact and the new codeclimate artifact. Coverage difference is not shown even having the baseline coverage and the new coverage.
What I can do to get this working? I don't want to run all tests in every master commit and waste resources.