| Summary: | Create autobuilder-worker container | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] CROPS | Reporter: | Tim Orling <tim.orling> |
| Component: | crops-default | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | Toaster default assignee <toaster> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | konrad.scherer, randy.macleod, tvgamblin |
| Version: | 3.1 | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Tim Orling
2019-11-22 21:12:24 UTC
Very raw command line experiment, ignoring yocto-autobuilder-helper for now. Assumes buildbot-controller is already running. See https://bugzilla.yoctoproject.org/show_bug.cgi?id=13648 On debian-10 host: $ sudo apt install jq $ docker inspect autobuilder-controller | jq .[0] | jq -r .NetworkSettings.Networks.autobuilder.IPAddress 172.19.0.2 $ docker run -it -e BUILDMASTER=172.19.0.2 -e BUILDMASTER_PORT=9989 -e WORKERNAME=ubuntu1804-ty-1 -e WORKERPASS=pass -e WORKER_ENVIRONMENT_BLACKLIST=WORKERPASS --network autobuilder --name ubuntu1804-ty-1 buildbot/buildbot-worker:v2.7.0 Nice idea, but not something I have time to work on. Bulk move from 4.99 or 0.00 to 5.99 Ideas here are probably still valid for future design considerations. Moving to future. |