Feature #23052
closed
Unify arvados/jobs and /dev-jobs
Description
One builds from Debian packages, one builds from Python packages. As far as I can tell neither is necessary. The Dockerfile for both can just be, set up dependencies and a virtualenv as dev-jobs does now, then env -C /usr/local/src/arvados /opt/arvados-py/bin/pip install sdk/python tools/crunchstat-summary sdk/cwl.
/usr/local/src/arvados is mounted into the build from $WORKSPACE on the host. The build can pass through $ARVADOS_BUILDING_VERSION to decide whether we're building development/rc/release packages, just like we do for most of our other builds. This basically eliminates the need for custom build scripts.
Updated by Brett Smith 8 months ago
- Target version set to Development 2025-07-23
- Assigned To set to Brett Smith
- Status changed from New to In Progress
Being done in #21389. The mount strategy as discussed isn't workable because I don't see a way to mount volumes into build containers. But the branch DRYs up our build code so there's a single tool that knows how to build these images in different contexts.
Updated by Brett Smith 8 months ago
- Target version changed from Development 2025-07-23 to Development 2025-08-06