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] Enable End2End tests on all repos #324

Closed
4 of 13 tasks
EngHabu opened this issue May 27, 2020 · 0 comments
Closed
4 of 13 tasks

[Feature] Enable End2End tests on all repos #324

EngHabu opened this issue May 27, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@EngHabu
Copy link
Contributor

EngHabu commented May 27, 2020

Motivation: Why do you think this is important?
Any change in all repos (at the very least propeller, admin, datacatalog) should trigger end2end tests in CI use all "current" images from flyte repo and substitute the current repo's image with the one just built in the PR. This ensures we do regression testing (all binaries should be n-1 compatible) as well as invoke somewhat expensive/complex tests that do not need to run regularly on some cadence in production environment.

Goal: What should the final outcome look like, ideally?

  • Any PR should trigger end2end tests to run.
  • Failures should block the PR.
  • Merges to master should also trigger end2end tests
  • It should use the current repo's image + everything else from flyte repo.

Flyte component

  • Overall
  • Flyte Setup and Installation scripts
  • FlytePropeller
  • FlyteAdmin (Control Plane service)
  • Flyte Documentation
  • Flyte communication (slack/email etc)
  • FlyteIDL (Flyte specification language)
  • Flytekit (Python SDK)
  • FlytePlugins
  • DataCatalog
  • FlyteStdlib (common libraries)
  • FlyteConsole (UI)
  • Other
@EngHabu EngHabu added enhancement New feature or request untriaged This issues has not yet been looked at by the Maintainers labels May 27, 2020
EngHabu added a commit that referenced this issue May 27, 2020
This PR just adds additional logging for when End2end tests fail to help debug issues.

#324
@wild-endeavor wild-endeavor removed the untriaged This issues has not yet been looked at by the Maintainers label Jun 25, 2020
@EngHabu EngHabu added this to the 0.5.0 milestone Jun 25, 2020
@EngHabu EngHabu closed this as completed Jun 25, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
…lyteorg#324)

* Added enableSchedule option on registration

Signed-off-by: Prafulla Mahindrakar <[email protected]>

* Added docs and linked missing docs

Signed-off-by: Prafulla Mahindrakar <[email protected]>
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
…lyteorg#324)

* Added enableSchedule option on registration

Signed-off-by: Prafulla Mahindrakar <[email protected]>

* Added docs and linked missing docs

Signed-off-by: Prafulla Mahindrakar <[email protected]>
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
…lyteorg#324)

* Added enableSchedule option on registration

Signed-off-by: Prafulla Mahindrakar <[email protected]>

* Added docs and linked missing docs

Signed-off-by: Prafulla Mahindrakar <[email protected]>
mhotan added a commit to mhotan/flyte that referenced this issue Jun 24, 2024
Some flyte components were lacking metrics. clustersyncresources is especially necessary now that new projects are created frequently in serverless. But we should be monitoring all internal services to some extent.

* Update clusterresourcesync to export metrics via httpendpoint
* Update clusterresourcesync deployment with Prometheus scrape annotations, disabled by default
* Update propeller deployment  with Prometheus scrape annotations, disabled by default
* Update webhook deployment  with Prometheus scrape annotations, disabled by default
* Create Webhook HPA, default disabled.

Changes are intended to be forward-compatible, specifically with Prometheus Pod and ServiceMonitor.

towards PE-912
towards PE-846
mhotan added a commit to mhotan/flyte that referenced this issue Jun 24, 2024
Some flyte components were lacking metrics. clustersyncresources is especially necessary now that new projects are created frequently in serverless. But we should be monitoring all internal services to some extent.

* Update clusterresourcesync to export metrics via httpendpoint
* Update clusterresourcesync deployment with Prometheus scrape annotations, disabled by default
* Update propeller deployment  with Prometheus scrape annotations, disabled by default
* Update webhook deployment  with Prometheus scrape annotations, disabled by default
* Create Webhook HPA, default disabled.

Changes are intended to be forward-compatible, specifically with Prometheus Pod and ServiceMonitor.

towards PE-912
towards PE-846

Signed-off-by: Mike Hotan <[email protected]>
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this issue Jul 2, 2024
…lyteorg#324)

* Added enableSchedule option on registration

Signed-off-by: Prafulla Mahindrakar <[email protected]>

* Added docs and linked missing docs

Signed-off-by: Prafulla Mahindrakar <[email protected]>
troychiu pushed a commit that referenced this issue Jul 8, 2024
Some flyte components were lacking metrics. clustersyncresources is especially necessary now that new projects are created frequently in serverless. But we should be monitoring all internal services to some extent.

* Update clusterresourcesync to export metrics via httpendpoint
* Update clusterresourcesync deployment with Prometheus scrape annotations, disabled by default
* Update propeller deployment  with Prometheus scrape annotations, disabled by default
* Update webhook deployment  with Prometheus scrape annotations, disabled by default
* Create Webhook HPA, default disabled.

Changes are intended to be forward-compatible, specifically with Prometheus Pod and ServiceMonitor.

towards PE-912
towards PE-846
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