While working on build cancellation for #243 I've come across a need for being able to get the handle of the "environment" that is currently running. My current strategy is to calculate the container name and send a cancel signal to the Docker API, but this won't scale to when I eventually want to support non-docker builds.
My current thought is that I want to modify the build_stage table so that I have the following information.
build host (This column already exists)
builder type (Such as Docker, or host-level, ssh? -- I'm not tied to this column name)
process id (as a TEXT field)
We're not doing anything like registering build hosts, so I'm not quite sure how much information I want to stuff into this table. Perhaps it might be time to register builders?
While working on build cancellation for #243 I've come across a need for being able to get the handle of the "environment" that is currently running. My current strategy is to calculate the container name and send a cancel signal to the Docker API, but this won't scale to when I eventually want to support non-docker builds.
My current thought is that I want to modify the
build_stagetable so that I have the following information.We're not doing anything like registering build hosts, so I'm not quite sure how much information I want to stuff into this table. Perhaps it might be time to register builders?