Automatic update of site when external content is updated

[mrbobbytables]

Currently the site is only updated when a PR to this repo is merged or a manual trigger of a build is done in netlify. Long term a prow job should be configured to trigger the rebuild webhook whenever the externally sourced content is updated.

As a short term solution, a periodic job could be configured to trigger rebuilding the site on something like a 12hr interval.

[kushthedude]

Hey @mrbobbytables How about having a github action for the automatic trigger?

[mrbobbytables]

@kushthedude As it spans multiple repos and they have prow in place I'd lean a bit more towards doing it that way. For the most part though it should be pretty similar :)

[kushthedude]

There is no prow job for contributor-site right now, should I add one here https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes-sigs ?

[mrbobbytables]

OOOH, I think I get what you were saying now. We could setup a github action for this repo to trigger on an interval to rebuild.

Long term we'd want prow jobs to trigger a rebuild targeting the places where the external content is sourced:

• kubernetes/community
  • /contributors/guide
• kubernetes/sig-release
  • /releases

That way the prow job would trigger a rebuild anytime content in those external sources is updates.

[kushthedude]

Yes, that was I was saying. We can setup up a cron github action to curl the rebuild webhook at particular interval.

…

On Fri, 4 Sep, 2020, 19:25 Bob Killen, ***@***.***> wrote: OOOH, I think I get what you were saying now. We could setup a github action for this repo to trigger on an interval to rebuild. Long term we'd want prow jobs to trigger a rebuild targeting the places where the external content is sourced: - kubernetes/community <https://github.com/kubernetes/community> - /contributors/guide - kubernetes/sig-release <https://github.com/kubernetes/sig-release> - /releases That way the prow job would trigger a rebuild anytime content in those external sources is updates. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#160 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKQMTLXF6HMQ3BGGT5CPWBDSEDWUZANCNFSM4QNAG4SQ> .

[sftim]

The GitHub Action trigger sounds like a reasonable idea, and would also work for https://k8s.io/ (which has similar needs).

[sftim]

/kind feature

[fejta-bot]

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

[mrbobbytables]

I think with the action trigger in place, this is good to close 👍

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

I think with the action trigger in place, this is good to close 👍

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.