#42 #35 #28 set/get master coverage by repo URL instead of PR URL

[terma]

No description provided.

[snadorp]

Looks good, please merge.

[ayoub-benali]

are there any plans to get this fix merged ?

[AASyedAbbas]

Please merge the changes as it solves the problem which we are facing for long.

[rohitjha]

@terma it'll be great if you can merge this and make a new release soon.

[gouraharidas]

When is this getting merged?

[killthemyth]

@terma Any plan for the merge?

[mahyarv]

Will this get merged?

[terma]

@mahyarv let me re-test it, and I will merge it

[adiesner]

For me this is still not the correct way to store the master coverage. As soon as you have multiple projects within one repository it always compares to the project that has the latest build.

Proposal:
Use: $GIT_REPOSITORY/$PATH_TO_PROJECT/$PATH_TO_COVERAGE_REPORTS
Alternative: $GIT_REPOSITORY/$CONFIGURABLE_PROJECT_NAME

On the screenshot below one pull request is affecting multiple of our projects in the same repository. When opening the pull request multiple projects in Jenkins start to build. As you can see the reference is always 62% (which is the coverage from the last project that built on master)

I am willing to contribute with a pull request to this issue, but this pull request has been open 1,5 years now. Will my contribution ever be merged?

[dmotpan]

@adiesner yep, feel free, I will review it

[sladyn98]

LGTM:+1

[sladyn98]

@terma @dmotpan Is the maintenance of this plugin still active, because I was planning to develop an extension point to this to use in the Github Checks API Integration for jenkins