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

[CI/CD] Migrate prowjobs out of Neighbor's Prow - Hasselhoff #9493

Closed
14 tasks done
Tracked by #10076
KacperMalachowski opened this issue Dec 8, 2023 · 5 comments
Closed
14 tasks done
Tracked by #10076
Assignees
Labels
area/ci Issues or PRs related to CI related topics kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Comments

@KacperMalachowski
Copy link
Contributor

KacperMalachowski commented Dec 8, 2023

Description
The prow jobs owned by the hasselhoff team have to be removed and if necessary substituted with something else.
To simplify the process here is a list of prow jobs that should be migrated by hasselhoff team.

  • pre-busola-backend-deployment-check
  • pull-busola-integration-cluster-k3d
  • pull-busola-integration-namespace-k3d
  • pre-busola-web-deployment-check
  • pull-busola-lighthouse
  • pre-kyma-dashboard-dev
  • pull-kyma-dashboard-integration
  • pre-kyma-dashboard-prod
  • pull-kyma-dashboard-smoke-test-prod
  • pull-kyma-dashboard-smoke-test-stage
  • pre-kyma-dashboard-stage
  • post-kyma-dashboard-dev
  • post-kyma-dashboard-prod
  • post-kyma-dashboard-stage
@KacperMalachowski KacperMalachowski added area/ci Issues or PRs related to CI related topics kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. labels Dec 8, 2023
Copy link

github-actions bot commented Feb 7, 2024

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 7, 2024
Copy link

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 14, 2024
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 14, 2024
@Sawthis Sawthis reopened this Feb 15, 2024
@Sawthis Sawthis removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 15, 2024
@Sawthis
Copy link
Contributor

Sawthis commented Feb 15, 2024

@valentinvieriu what is the status for @kyma-project/hasselhoff team about migration outside of Prow? The deadline was moved from end of January to end of February 2024.

@Sawthis
Copy link
Contributor

Sawthis commented Aug 9, 2024

@mrCherry97 could you provide the update for the issue? The deadline is end of August.

@mrCherry97
Copy link
Contributor

Hi @Sawthis
I have marked jobs that we have moved, here we have our issue for this with all of the details: kyma-project/kyma-dashboard#306
All test workflows are moved to GithubActions, local build in the busola, and dev build in the kyma-dashboard. We need to adjust the web and backend build in Busola, stage, and prod build in the kyma-dashboard.
We will plan the continuation of this task next week, so we should be fine, and out of prow till the end of August.

@Sawthis Sawthis closed this as completed Sep 2, 2024
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 kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
Projects
None yet
Development

No branches or pull requests

5 participants