You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per #2876 integrate the buildroot and opentrons repos:
As an Opentrons API developer, I want to be able to do my work without ever thinking about buildroot, with as little change from the current state of affairs as possible
As an Opentrons system developer, I want to be able to easily coordinate changes in the API server and buildroot layers
As an Opentrons devops/infrastructure person, I want to always have buildroot builds available for canonically "latest" builds
These lead to this implementation strategy:
The opentrons api (and possibly the update server / some new embodiment of the update server) are added to buildroot as python packages, built from source.
The version of the api used is determined by the following rules:
If the branch matches a branch in buildroot start a buildroot build of the matching branch (using above logic, but without the default to edge)
If the branch is edge [optional: and the diff since last build contains changes to api/, shared-data/, update-server/], build opentrons-develop of buildroot
If neither of those rules match, do not build buildroot
Change make push-api to:
remount the rootfs rw
transfer the wheel
pip install the wheel
reboot the system
(the push-api part should probably be a different target so as not to interfere with current workflows)
The text was updated successfully, but these errors were encountered:
- Adds a BR2_EXTERNAL tree from the
monorepo (Opentrons/opentrons#3217) and pulls in the opentrons api server to the build.
- Fixes some issues in systemd services and targets. Codebuild rewrites
broken (and maybe non-broken) absolute links to fit inside its chroot jail,
which was breaking the absolute links that aren’t supposed to be valid until
they’re on the robot
- Add a VERSIONS file taken from a combination of the buildroot version (from
git) and opentrons api server versions (from package.json) and save to
/etc/VERSIONS.json
- VERSIONS.json is a new artifact and also zipped up with the full images and
update images when uploaded to s3
ClosesOpentrons/opentrons#2877
- Adds a BR2_EXTERNAL tree from the
monorepo (Opentrons/opentrons#3217) and pulls in the opentrons api server to the build.
- Fixes some issues in systemd services and targets. Codebuild rewrites
broken (and maybe non-broken) absolute links to fit inside its chroot jail,
which was breaking the absolute links that aren’t supposed to be valid until
they’re on the robot
- Add a VERSIONS file taken from a combination of the buildroot version (from
git) and opentrons api server versions (from package.json) and save to
/etc/VERSIONS.json
- VERSIONS.json is a new artifact and also zipped up with the full images and
update images when uploaded to s3
ClosesOpentrons/opentrons#2877
sfoster1
added a commit
to Opentrons/buildroot
that referenced
this issue
Jan 4, 2024
- Adds a BR2_EXTERNAL tree from the
monorepo (Opentrons/opentrons#3217) and pulls in the opentrons api server to the build.
- Fixes some issues in systemd services and targets. Codebuild rewrites
broken (and maybe non-broken) absolute links to fit inside its chroot jail,
which was breaking the absolute links that aren’t supposed to be valid until
they’re on the robot
- Add a VERSIONS file taken from a combination of the buildroot version (from
git) and opentrons api server versions (from package.json) and save to
/etc/VERSIONS.json
- VERSIONS.json is a new artifact and also zipped up with the full images and
update images when uploaded to s3
ClosesOpentrons/opentrons#2877
Per #2876 integrate the buildroot and opentrons repos:
These lead to this implementation strategy:
The opentrons api (and possibly the update server / some new embodiment of the update server) are added to buildroot as python packages, built from source.
The version of the api used is determined by the following rules:
edge
is usedOn the CI side, we have the following triggers:
On push and pr open to https://github.com/opentrons/buildroot:
On push and pr open to https://github.com/opentrons/opentrons:
edge
)edge
[optional: and the diff since last build contains changes toapi/
,shared-data/
,update-server/
], buildopentrons-develop
of buildrootChange
make push-api
to:pip install
the wheel(the push-api part should probably be a different target so as not to interfere with current workflows)
The text was updated successfully, but these errors were encountered: