Fix logic for discovering new branches 15/64315/2
authorAric Gardner <agardner@linuxfoundation.org>
Thu, 18 Jun 2020 19:17:03 +0000 (15:17 -0400)
committerAric Gardner <agardner@linuxfoundation.org>
Fri, 26 Jun 2020 15:21:50 +0000 (11:21 -0400)
commitdcf5761d0c38f01d4397784870c9031d4d499441
treee6e6437c2999df6f9520afc44c096cb087c7f0f3
parent8e52d0538f6d9897ea601544a3a22a409b7de20e
Fix logic for discovering new branches

When a new branch exists on gerrit, but has never been seen by RTD
we need to trigger a job so that the branch is discovered
we can then mark it active in the following step.

API changed under out feet, where a 404 was returned before
we now get a 200 with the string null.
Change code to explicitly match the returned string of
"null"

Issue-Id: RELENG-3027
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Change-Id: I769b66384f5b53d87527faeb0f467350a847b65c
releasenotes/notes/rtd-activate-version-652c0d9730b936b1.yaml [new file with mode: 0644]
shell/rtdv3.sh