community
community copied to clipboard
tektoncd
New org for tekton experiments?
tektoncd/experimental can be hard to work with - this is the only monorepo style repo we have and it contains a bunch of inactive experiments. A failing test in one inactive project means we cannot merge a PR in another project (https://github.com/tektoncd/experimental/pull/896)
Most of our CI is optimized for single repo use cases not mono repos. One option is we create a tektoncd-experimental org and create new experiments as separate repos in that org.
There is some initial overhead with setting up a new org but I think it's still probably worth it:
- Setting up Prow/Tekton for CI
- Setting up Peribolos for org administration
- Update docs to mention this as the new org for experiments
- Potentially migrate some of the active experiments from tektoncd/experimental
@tektoncd/governing-board what do you think?
It sounds like a good idea. If you could prepare a detailed plan about what would be required, I'd be happy to help implementing it.
@dibyom the idea is that this would hold experiments done from some tekton community members and could (or not) be promoted at some point right ? It sounds very similar to https://github.com/knative-sandbox/ I guess 🙃.
I do feel this is extra work that might not necessarily needed, aka compared to have the experiment in one repository or in a non-tekton organization, but I don't feel too strongly about that as well.
So, it sounds like a good idea yes 👍🏼
@dibyom the idea is that this would hold experiments done from some tekton community members and could (or not) be promoted at some point right ? It sounds very similar to https://github.com/knative-sandbox/ I guess 🙃.
Yup! exactly!
I do feel this is extra work that might not necessarily needed, aka compared to have the experiment in one repository or in a non-tekton organization, but I don't feel too strongly about that as well.
You might be right though I do feel that working in experimental can be bit more challenging due to having to fit into the monorepo pattern. I'll try to scope out the things we need to do to get a new org running (we already have a new org for the catalog, so we might have to do some setup anyway)
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
+1 to this! (I raised this separately at the community meeting today)
This would be super useful for managing security alerts (which there are many 😅) and archiving unmaintained projects.
There's probably going to be a lot of work for setting up CI - we don't have a great story for onboarding new projects, but perhaps this is a way to drive this dogfooding?
@lbernick this is related to https://github.com/tektoncd/community/pull/956 (but not a blocker, just wanted to make sure you're aware)
There's probably going to be a lot of work for setting up CI - we don't have a great story for onboarding new projects, but perhaps this is a way to drive this dogfooding?
@QuanZhang-William recently setup org management and CI for the new catalog org...maybe we could write up a guide based on that experience?
There's probably going to be a lot of work for setting up CI - we don't have a great story for onboarding new projects, but perhaps this is a way to drive this dogfooding?
@QuanZhang-William recently setup org management and CI for the new catalog org...maybe we could write up a guide based on that experience?
Yeah I can definitely help documenting the process of setting up new orgs. I think the org management (Prow) part should be very similar for all the orgs, but the CI setup can be quite different based on the test infrastructure and tests themselves.
But I can at least write out the CI settings for catalog org as an example.
Maybe I can add a how-to doc here: https://github.com/tektoncd/community/tree/main/org, WDYT?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.
/close
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopenwith a justification. Mark the issue as fresh with/remove-lifecycle rottenwith a justification. If this issue should be exempted, mark the issue as frozen with/lifecycle frozenwith a justification./close
Send feedback to tektoncd/plumbing.
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.