Open-source Codecov

[chadwhitacre]

😁 💃

To Do

• Get Chad access to Codecov to start evaluating.
• Implement triage processes in uploader, wrappers. jumping straight in with main repos
• Sort out licensing with Legal – not much to sort out, BSL!
• Click Publish #142
• Engage on GitHub #140
• Shift Self-hosted #141
• Expand to codecov somehow eng-pipes#482
• Update docs
  • internal
  • external - punted
  • dev docs
• Publish blog post (draft🔒)

[aldy505]

Just a quick question. Will it be on a separate Github organization, or will it be on Sentry's org?

[chadwhitacre]

Likely separate, but not determined yet. Why do you ask?

[chadwhitacre]

https://docs.codecov.com/docs/installing-codecov-self-hosted
https://github.com/codecov/enterprise-resources
getsentry/vroom#165
https://github.com/orgs/codecov/repositories

https://github.com/codecov/worker
https://github.com/codecov/shared
https://github.com/codecov/codecov-api
https://github.com/codecov/gazebo

[chadwhitacre]

Draft blog post🔒

[chadwhitacre]

Click Publish

• discuss naming with eng - @eliatcodecov
• file Security Jira ticket to audit repos - @eliatcodecov

Engage on GitHub

• identify stakeholder(s) for support/PM convo - @eliatcodecov
• schedule kick-off meeting - @chadwhitacre

Shift Self-hosted

• create MVP self-hosted repo with docker compose - @eliatcodecov

[chadwhitacre]

I made tickets for each of the three:

• Click Publish #142
• Engage on GitHub #140
• Shift Self-hosted #141

[BYK]

I walso want to drop this here as I think it may become quite useful: https://github.com/formsort/action-check-codecov-config

[chadwhitacre]

Oooh, nice! @eliatcodecov have you seen this yet?

[eliatcodecov]

@chadwhitacre I was unaware of this action, thanks @BYK for pointing it out.

[chadwhitacre]

There's been a conversation about whether to keep the GitHub orgs separate or not. Hearing from Cramer that codecov probably makes more sense, so that makes #142 easier and for #140 we will need to roll out triage automations in that org, will pick up on that ticket with details.

[chadwhitacre]

Click Publish

• keep driving eng work, target is June 22 - @eliatcodecov

Engage on GitHub

• admin rights for @chadwhitacre on codecov org - @eliatcodecov
• figure out brand for app (username / profile pic) - @eliatcodecov
• create new GitHub app in codecov org - @chadwhitacre
• map out work to make eng-pipes multi-org - @chadwhitacre

Shift Self-hosted

• create MVP self-hosted repo with docker compose - @eliatcodecov

[chadwhitacre]

Click Publish

• keep driving eng work, target is July 7 - @eliatcodecov

Engage on GitHub

• keep driving eng work, target is July 7 - @chadwhitacre

Shift Self-hosted

• in progress with devops, create MVP self-hosted repo with docker compose - @eliatcodecov

Marketing

• no action item this week, team is prepped

[chadwhitacre]

Click Publish

• keep driving eng work, target is July 7 - @eliatcodecov

Engage on GitHub

• keep driving eng work, target is July 7 - @chadwhitacre

Shift Self-hosted

• finish dusting off enteprise repo, rename to self-hosted - @eliatcodecov
• implement automated change date bumping - @eliatcodecov
• run additional use grant by legal - @chadwhitacre

Marketing

• no action item this week, team is prepped

[chadwhitacre]

Short week this week.

Click Publish

• remediate gitleaks finds - likely going to slip, this is proving to be a lot of work - @eliatcodecov

Engage on GitHub

• turn CoveCod on in feedback repo - @chadwhitacre
• next week: develop punchlist

Shift Self-hosted

• implement automated change date bumping - @eliatcodecov
• run additional use grant by legal - @chadwhitacre

Marketing

• next week: meet to finalize a plan

[chadwhitacre]

Short week this week.

Click Publish

• gitleaks remediation - new target is July 14 - @eliatcodecov
• interim license plan - target July 14 - @eliatcodecov

Engage on GitHub

• turn CoveCod on in feedback repo - new target is July 11 - @chadwhitacre
• next week: develop punchlist

Shift Self-hosted

• tagging (rolling, latest-calver, latest-stable, calver) @eliatcodecov
• implement automated change date bumping - @eliatcodecov
• try it out! :) - @chadwhitacre @eliatcodecov
• run additional use grant by legal - @chadwhitacre

Marketing

• aiming to sync August Future of Open Source event

Future

• add a beacon🔒
• remove license restriction entirely

[chadwhitacre]

Clicking Publish

• Curveball: PR diffs still contain old history, so final strategy is to rebuild history and make a new repo
• worker is ready to publish (worker-archive is the old one)
• gazebo was clean already
• codecov-api and shared are in progress
• finalized BSL text is here in an old worker PR :) - needs to be propagated to 4 repos

Shift Self-hosted

• beacon - scheduling the work, aiming for early August deployment
• usage license generation - in progress

Engage on GitHub

• Expand to codecov somehow eng-pipes#482 is coming in for a landing, should ship by next Tuesday

Marketing

• podcasts are lining up

[chadwhitacre]

Clicking Publish & Self-hosted

• The four repos are ready to publish.
• CalVer conversion in flight.
• Automation of calver bumps not started.
• Beacon service written and deployed.
• More work to pipe data into Looker.
• Licensing stuff is done.

Cutover (July 26?):

• Publish latest tag in docs
• Make enterprise-resources private.
• Make four repos public.

Feedback

• Not landed, still working on it.

[chadwhitacre]

I skimmed over our OSPO docs, updated the internal ones. For open.sentry.io I think we should clone it to open.codecov.io, bumping from scope here.

[chadwhitacre]

Publish blog post

News is out, blog post scheduled for Wednesday.

[chadwhitacre]

I think that and updated dev docs are the last items here!