Skip to content

feat(ci, runners): Ephemeral runners build#286

Open
neo-jesse wants to merge 32 commits intoopentrons-developfrom
ephemeral-runners-build
Open

feat(ci, runners): Ephemeral runners build#286
neo-jesse wants to merge 32 commits intoopentrons-developfrom
ephemeral-runners-build

Conversation

@neo-jesse
Copy link
Copy Markdown
Contributor

No description provided.

neo-jesse and others added 23 commits January 29, 2026 08:13
This reverts commit 7b1f66c.
This will let us handle having one of two repositories kick off the
action (either the main monorepo or the fork repo). We'll keep this
around until we're comfortable with the released fork, at which point
we'll probably remove it and switch to the fork full time.
We can now run buildroot against Opentrons/opentrons-ot2 instead of
Opentrons/opentrons, and deploy to different AWS infrastructure. When we
do that, we always use ephemeral builders. This means the workflow needs
to handle three cases instead of just two: using the normal
infrastructure, using the ephemeral infrastructure setup for the
non-forked system, and using the ephemeral infrastructure setup for the
forked system.

This all keys off a new monorepo-is-fork input that builds started from
opentrons-ot2 will set, and also we can force merged ephemeral
infrastructure using a new force-ephemeral-infra input (which is now a
bool but could concievably become a random weight float).
@neo-jesse neo-jesse marked this pull request as ready for review February 24, 2026 19:21
Copy link
Copy Markdown
Member

@sfoster1 sfoster1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple things to change. let's split ccache additions into a different pr and clean up some bash stuff

Copy link
Copy Markdown
Member

@sfoster1 sfoster1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks so much better as python, that's awesome. Looks good once we just double check it all still works (and once releases are out of course)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants