search

kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
30 stars 112 forks source link

Prow job to periodically build website img #716

Closed mazzystr closed 2 years ago

mazzystr commented 3 years ago

Img building is getting streamlined via https://github.com/kubevirt/kubevirt.github.io/issues/715

Once complete Prow should periodically build the website img and push to KubeVirt org in Docker Hub

kubevirt-bot commented 3 years ago

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.

/lifecycle stale

mazzystr commented 3 years ago

/remove-lifecycle stale

kubevirt-bot commented 2 years ago

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.

/lifecycle stale

tylerauerbeck commented 2 years ago

@mazzystr Is this related to https://github.com/kubevirt/project-infra/pull/1332 ? Or are those two different?

mazzystr commented 2 years ago

I think kubevirt/project-infra#1332 is no longer valid since the functionality was implemented via a different pull req created by dhiller.

This issue is to get a periodic job created so the post submit job can also run like a cron job. This allows the website to have scheduled publishing of blogs posts or other website updates.

On Mon, Sep 27, 2021 at 12:12 PM Tyler Auerbeck @.***> wrote:

@mazzystr https://github.com/mazzystr Is this related to kubevirt/project-infra#1332 https://github.com/kubevirt/project-infra/pull/1332 ? Or are those two different?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubevirt/kubevirt.github.io/issues/716#issuecomment-928192078, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAS5KZ2YFEWDLA6WLBUMRLDUEC6YTANCNFSM42BALOIA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

kubevirt-bot commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

mazzystr commented 2 years ago

/remove-lifecycle rotten

On Fri, Oct 29, 2021 at 9:54 AM kubevirt-bot @.***> wrote:

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubevirt/kubevirt.github.io/issues/716#issuecomment-954897328, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAS5KZ6554SLELUZERW5AHLUJLNVPANCNFSM42BALOIA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

kubevirt-bot commented 2 years ago

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.

/lifecycle stale

kubevirt-bot commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

kubevirt-bot commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 2 years ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/issues/716#issuecomment-1081016222): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close 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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.