Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch to use Prow to report code coverage to coverall #94

Closed
leakingtapan opened this issue Nov 3, 2018 · 1 comment
Closed

Switch to use Prow to report code coverage to coverall #94

leakingtapan opened this issue Nov 3, 2018 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@leakingtapan
Copy link
Contributor

We can do similar thing as discussed here: kubernetes/test-infra#9976
@leakingtapan leakingtapan added this to the alpha milestone Nov 3, 2018
@leakingtapan leakingtapan self-assigned this Nov 3, 2018
@leakingtapan leakingtapan modified the milestones: alpha, beta Nov 5, 2018
@leakingtapan leakingtapan mentioned this issue Nov 16, 2018
Closed
@leakingtapan leakingtapan added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 16, 2018
@leakingtapan leakingtapan removed their assignment Dec 14, 2018
@leakingtapan leakingtapan changed the title Switch to use Prow for code coverage Switch to use Prow to report code coverage to coverall Feb 1, 2019
@leakingtapan leakingtapan added priority/backlog Higher priority than priority/awaiting-more-evidence. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 1, 2019
@leakingtapan leakingtapan removed this from the beta milestone Feb 5, 2019
@leakingtapan leakingtapan added priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. and removed priority/backlog Higher priority than priority/awaiting-more-evidence. labels Feb 9, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@leakingtapan @k8s-ci-robot @fejta-bot