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.

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

[Feature]FlyteAdmin & FlytePlugins should publish its Code coverage #259

Closed
2 of 13 tasks
kumare3 opened this issue Apr 13, 2020 · 0 comments
Closed
2 of 13 tasks

[Feature]FlyteAdmin & FlytePlugins should publish its Code coverage #259

kumare3 opened this issue Apr 13, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@kumare3
Copy link
Contributor

kumare3 commented Apr 13, 2020

Motivation: Why do you think this is important?
FlyteAdmin should publish its code coverage to codecov.io. Every checkin should report the change in code coverage

Goal: What should the final outcome look like, ideally?
Every checkin should report a code coverage. Also, Codecov is a standard and we should have the coverage reported like flytepropeller and flytestdlib

Describe alternatives you've considered
NA

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlytePropeller
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlyteAdmin (Control Plane service)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other

[Optional] Propose: Link/Inline
https://github.com/lyft/flytepropeller/blob/master/Makefile#L47

Additional context
NA

Is this a blocker for you to adopt Flyte
Potentially a blocker for many to adopt flyte

@kumare3 kumare3 added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels Apr 13, 2020
@kumare3 kumare3 changed the title [Feature]FlyteAdmin should publish its Code coverage [Feature]FlyteAdmin & FlytePlugins should publish its Code coverage Apr 13, 2020
@kumare3 kumare3 added this to the 0.3.0 milestone Apr 13, 2020
@katrogan katrogan self-assigned this Apr 13, 2020
@katrogan katrogan removed the untriaged This issues has not yet been looked at by the Maintainers label Apr 13, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
* chore: tools versioning

Signed-off-by: Nastya Rusina <[email protected]>

* chore: add codeowners file

Signed-off-by: Nastya Rusina <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 9, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this issue Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants