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

Incorporate Ansible CI for k8s module #233

Open
fabianvf opened this issue Nov 6, 2018 · 4 comments
Open

Incorporate Ansible CI for k8s module #233

fabianvf opened this issue Nov 6, 2018 · 4 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
v0.9.0

Comments

@fabianvf
Copy link
Member

fabianvf commented Nov 6, 2018

It might make sense to run the k8s full_test.yml playbook as part of the openshift client acceptance test suite.

This would help us prevent new releases from breaking Ansible builds, and I'm sure Matt Clay wouldn't mind that.
@fabianvf fabianvf added this to the release-0.9 milestone Jan 3, 2019
@fabianvf fabianvf mentioned this issue Mar 20, 2019
Closed
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 31, 2020
@willthames
Copy link
Contributor

/remove-lifecycle stale

this still seems like a good idea

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 2, 2020
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

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

fabianvf commented Dec 1, 2020

/lifecycle frozen
agreed

@openshift-ci-robot openshift-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
v0.9.0
Development

No branches or pull requests
4 participants
@willthames @openshift-bot @fabianvf @openshift-ci-robot