aboutsummaryrefslogtreecommitdiff
path: root/README.org
diff options
context:
space:
mode:
authorChristopher Baines <mail@cbaines.net>2021-01-17 19:58:16 +0000
committerChristopher Baines <mail@cbaines.net>2021-01-17 19:59:09 +0000
commit7572f18c00d628d7ac45d7ab0096af03780ae540 (patch)
treee63e147a3fe6867fd72484c4cf15d9acac4aa779 /README.org
parent6c46c2b4506dc5e6dc2f06f6afff979bf6dcb5e0 (diff)
downloadbuild-coordinator-7572f18c00d628d7ac45d7ab0096af03780ae540.tar
build-coordinator-7572f18c00d628d7ac45d7ab0096af03780ae540.tar.gz
Implement agent/build tag matching
If the agent and build tags have overlapping keys, compare the tag value, and only match the build to the agent if the value matches. There's a potential issue with some of the code here in that it doesn't cope well with tags with matching keys but differing values, but this is just a first implementation.
Diffstat (limited to 'README.org')
-rw-r--r--README.org6
1 files changed, 0 insertions, 6 deletions
diff --git a/README.org b/README.org
index 8d12aa2..973c45e 100644
--- a/README.org
+++ b/README.org
@@ -123,9 +123,3 @@ future.
With the HTTP transport for coordinator <-> agent communication, this should
happen over TLS for security if the network isn't secure. Each agent uses
basic authentication to connect to the coordinator.
-
-Unimplemented but planned features include:
-
- - Build/agent tags. Agents and builds should have key=value tags, a build
- will only be allocated to an agent if all the key=value tags it has matches
- the agent.