jobs: don't set node where it doesn't make sense

Remove the node attribute as these can run on any node. I've configured
the three deb11 nodes with "Usage: Use this node as much as possible"
instead of previously "Only build jobs with label expression matching
this node", so simply not specifying a node is now possible. Previously
it wouldn't have any node to run on as all of them were configured that
way.

Related: OS#5793
Change-Id: I2d67daf1cc7930649d097af23c18990cc3ae55fd
This commit is contained in:
Oliver Smith 2022-11-30 15:03:33 +01:00
parent 521b83ba3a
commit 0aad1883f1
2 changed files with 0 additions and 2 deletions

View File

@ -15,7 +15,6 @@
Roll out osmo-gsm-manuals to relevant build environments.<br>
<br>
Related: <a href="https://osmocom.org/issues/4912">OS#4912</a>
node: osmocom-master-debian9
scm:
- git:
url: https://gerrit.osmocom.org/osmo-gsm-manuals

View File

@ -12,7 +12,6 @@
name: 'registry-trigger-{repos}'
description: |
Update registry.osmocom.org after changes in {repos}.
node: osmocom-master-debian9
scm:
- git:
url: https://gerrit.osmocom.org/{repos}