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

Disable Prow tide component for ALL teams #11628

Open
Tracked by #10076
Sawthis opened this issue Aug 9, 2024 · 3 comments
Open
Tracked by #10076

Disable Prow tide component for ALL teams #11628

Sawthis opened this issue Aug 9, 2024 · 3 comments
Labels
area/ci Issues or PRs related to CI related topics

Comments

@Sawthis
Copy link
Contributor

Sawthis commented Aug 9, 2024

Description

We should disable tide and provide information about it to ALL teams upfront. We should provide information what should be used instead with the link to the Github documentation.

Reasons

Removal of Prow.

Acceptance Criteria

[ ] Teams are notified upfront about disablement of the Tide
[ ] Teams are notified what they should use instead of Tide
[ ] Prow tide component is disabled for ALL teams

Attachments

#12139

@Sawthis Sawthis added the area/ci Issues or PRs related to CI related topics label Aug 9, 2024
@Sawthis Sawthis changed the title Disable Prow tide component for the teams Disable Prow tide component for ALL teams Aug 26, 2024
@mrCherry97
Copy link
Contributor

If you are planning to remove Tide, there is a small problem with GitHub actions, because if someone approves PR before passing all of the checks, then PR is merged without checks.
Adding workflows to branch protection on Github doesn't make sense, because paths (old run_if_change) is not working, when I want to change something in the Busola backend, I don't want to trigger the build of the web image.
If it will be possible to create one Github workflow to have one check to add in branch protection in repo settings which will be checking if all checks passed, I'd appreciate it.
Goats have some potential solutions: kyma-project/istio@4f3ee64

@Sawthis
Copy link
Contributor Author

Sawthis commented Oct 29, 2024

@mrCherry97 our research results about this topic: #12139

@Sawthis
Copy link
Contributor Author

Sawthis commented Oct 30, 2024

This issue can be done after #12285 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Issues or PRs related to CI related topics
Projects
None yet
Development

No branches or pull requests

2 participants