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.

Sign up for GitHub

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

Jump to bottom

Initial OpenLab Integration #490

Closed
sbueringer opened this issue Nov 3, 2019 · 5 comments
Closed

Initial OpenLab Integration #490

sbueringer opened this issue Nov 3, 2019 · 5 comments
Assignees
@sbueringer

Comments

@sbueringer
Copy link
Member

sbueringer commented Nov 3, 2019 •
edited

I'd like to integrate CAPO with OpenLab testing (https://openlabtesting.org/) to provide reliable tests for our PRs. Let's see how it goes :)

In this issue an initial integration should be implemented. We'll probably need a few more to fullfill #484 completely
@sbueringer
Copy link
Member Author

/assign

@sbueringer sbueringer changed the title OpenLab Integration Initial OpenLab Integration Nov 3, 2019
@sbueringer sbueringer mentioned this issue Nov 3, 2019
Merged
@sbueringer
Copy link
Member Author

fyi, I requested the installation of https://github.com/apps/theopenlab-ci for this repo

@sbueringer sbueringer mentioned this issue Nov 3, 2019
Closed
@fejta-bot
Copy link

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

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 1, 2020
@sbueringer
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 24, 2020
@sbueringer
Copy link
Member Author

Let's just track this in #484 doesn't really make sense to have two issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sbueringer sbueringer

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sbueringer @k8s-ci-robot @fejta-bot