search

metal3-io / project-infra

Metal3 testing infrastructure configuration
https://prow.apps.test.metal3.io
Apache License 2.0
17 stars 20 forks source link

Migration to dynamic worker workflow #705

Closed Sunnatillo closed 1 month ago

Sunnatillo commented 6 months ago

We decided to use dynamic jenkins worker. Here the progress of the move.

Done: ✅ clusterctl upgrade tests ✅ feature tests ✅ dev env integration tests ✅ e2e basic ✅ e2e_integration tests ✅ k8s_upgrade tests ✅ ephemeral tests ✅ bmo e2e ✅ fullstack build ✅ Nordix clone

Note! We are are also splitting pipelines for dev_env and e2e_tests, and for feature tests we have already seperate pipeline.

Sunnatillo commented 6 months ago

/triage accepted

mboukhalfa commented 6 months ago

cc @adilGhaffarDev

Sunnatillo commented 6 months ago

725 moves following tests to dynamic works:

e2e integration e2e basic k8s upgrade tests ephemeral

Sunnatillo commented 4 months ago

Following PR move artifact cleanup and Nordix repo sync jobs to dynamic workers. https://github.com/Nordix/metal3-dev-tools/pull/766

metal3-io-bot commented 1 month ago

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

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

/lifecycle stale

Rozzii commented 1 month ago

/remove-lifecycle stale

Rozzii commented 1 month ago

This is actually done and not stale we are using dynamic workflow for every relevant test AFAIK.

Rozzii commented 1 month ago

/remove-lifecycle stale

Rozzii commented 1 month ago

/close Thanks everyone!

metal3-io-bot commented 1 month ago

@Rozzii: Closing this issue.

In response to [this](https://github.com/metal3-io/project-infra/issues/705#issuecomment-2402494025): >/close >Thanks everyone! Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.