-
Notifications
You must be signed in to change notification settings - Fork 16
Setup nightly builds for resolution #41
Comments
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
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. |
Feature request
Nightly builds for resolution
Use case
Nightly builds enable installing the project from a known / signed version so we can be used in environments beyond dev - like the robocat and dogfooding cluster, or users who'd like to experiment with this.
Specifically I would like to do nightly installs on robocat like for other projects, to catch update issues, and I would like to run the service in dogfooding and start using it to refactor some of the logic used for nightly builds (today we rely on kustomize's ability to clone remote git repos on the fly).
The text was updated successfully, but these errors were encountered: