search

ipfs-inactive / dev-team-enablement

[ARCHIVED] Dev Team Enablement Working Group
3 stars 1 forks source link

Code coverage in Jenkins #84

Open victorb opened 5 years ago

victorb commented 5 years ago

From @Kubuxu on February 10, 2017 17:5

Unfortunately Jenkins doesn't expose git related Env Variables in pipelines currently, which blocks the code coverage reporting.

Working it around would have taken quite some time, it is reported here: https://issues.jenkins-ci.org/browse/JENKINS-35230

Acceptance Criteria:

Copied from original issue: ipfs/jenkins#40

victorb commented 5 years ago

it can be easily replicated for other pipelines.

I'm thinking that is gonna have to be more specific to be able to be a acceptance criteria

victorb commented 5 years ago

From @Kubuxu on February 10, 2017 18:19

What I mean is to have list of variables that have to be exposes, if it is needed, have a library that generates them.

victorb commented 5 years ago

From @Kubuxu on March 3, 2017 13:51

We will have to do something like this: https://github.com/docker/jenkins-pipeline-scripts/blob/master/vars/codecov.groovy

As BRANCH_NAME in case of PRs is modified to PR-XXXX.