...
- Producing the GB report
- Three sections
- Introduction that describes the current state and the set of problems.
- Describe the potential solutions for solving the CI problem and also for solving the soak/test net problem.
- Itemize the most likely solution to solve the most problems for the most teams.
- Three sections
- Notes
- Nobody is happy and it is currently unfair that companies have to pay for their things and the Fabric team is limited to what they are using.
- Current options look like this
- Short term:
- Moving Fabric minions to AWS to give the team better control over the performance and debugging and resources to get their build times down and to fix their problems easier.
- Using HL resources to reduce the cost to member companies. This is a broad brush and we'll need to work out a per-team budget and how they spend it. But in general we want to reduce the unfairness that companies are facing right now.
- CA team for metrics and security reasons need to secure visibility and influence into the existing pipelines.
- Long term:
- We develop an HL global budget for covering CI/CD costs that all of the teams can get a cut of based on the portioning rules set by and managed by the TSC
- This number will grow significantly since we're essentially only paying for one team at the moment and we want to grow to all teams.
- We bless one CI system with the tacit acceptance that this will be painful for pretty much everybody and will require some significant time and energy commitment to move all projects to the new system. We have no current recommendation (e.g. CircleCI or Gitlab CI or K8s) but if we decide on this option we can figure that out and it will be about minimizing the pain for the most people.
- We actually only care about the visibility and security and metrics requirements and being on or under budget so blessing a single solution is really of no interest. <----THIS IS THE RECOMMENDATION given the present company and place in time. This needs broader buy in.
- We develop an HL global budget for covering CI/CD costs that all of the teams can get a cut of based on the portioning rules set by and managed by the TSC
- Short term:
Action items
- David Huseby write a preliminary report with the recommendation and discussion and send to active members list asking for review and edit and check-off of reviewers at the bottom.
- review deadline is
- David Huseby send summary email to TSC mailing list announcing preliminary report with current level of buy in and itemize the specific action items for the TSC that come out of the report.