Replies: 1 comment
-
@vito concourse/rfcs#66 please. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all, I'm going to try something different for this one: posting it as a Discussion instead!
Previous RFC round-ups can be found on our blog. To be honest our blog doesn't get a whole lot of natural traffic at the moment, so I'm hoping this provides better visibility and lowers the barrier to commenting and asking questions and such.
RFCs in need of feedback
If you have any thoughts on these RFCs, please contribute them as review comments on the RFC PR! 🙏
RFC #29:
across
stepThis RFC is pretty much good to go; there are no open questions. Feedback welcome!
The
across
step is a key component to v10, providing the mechanism for setting pipelines 'across' all pull requests, branches, and even matrix-style var combinations.RFC #43: task queue
The task queue RFC proposes a solution to the longstanding issue of Concourse yeeting a bunch of workloads onto workers at once, overloading them and causing builds to fail.
Open questions:
RFC #62: worker pools
Right now, workers can be registered either cluster-wide or for a single team. This RFC introduces a 'worker pool' - a group of workers which can be associated to multiple teams. This will prove especially important if/when we decide to merge Projects and Teams.
Open questions:
--public-worker-key
option forfly set-worker-pool
?Upcoming RFCs
run
step, originally introduced in RFC: Prototypes rfcs#37 but it likely needs more detail (that RFC mainly focused on the Prototype protocol).If you've submitted an RFC and would like me to include it in the next round-up, let me know! Feel free to link to it in the replies to this Discussion.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions