Generate publish event for failed/broken/unresolvable. 16/139916/1
authorJunghyun Kim <jh0822.kim@samsung.com>
Fri, 21 Jul 2017 04:53:21 +0000 (13:53 +0900)
committerJunghyun Kim <jh0822.kim@samsung.com>
Fri, 21 Jul 2017 04:53:21 +0000 (13:53 +0900)
commit1ef18b22c26934c13902f8782068f8b74bdd525c
treef5bac4960e6875f30326ccbf2e7292aa5113fc1f
parent7b4a0bd2b714ea7a9d5e1564f3a48b7f50266630
Generate publish event for failed/broken/unresolvable.

PROBLEM:
- If the first building package is failed/broken/unresolable,
a publish is not generated. This is normal because no difference
made in the repo.
- However, we need to generate a publish event to update dashboard
even for this case.

SOLUTION:
- SCHEDULER:
unresolvable/broken is checked by scheduler.
Make :need_publish if we found any unresolable/broken package.
This ensures that a publish event will be generated even if the repo
has not been changed.
- REPO_SERVER:
It checks build fail.
Make :need_publish if we found any package was failed to build.
This ensures that a publish event will be generated even if the repo
has not been changed.

Change-Id: I640e3eca1b07d7cb2066423a38346c2f8ad1f20b
Signed-off-by: Junghyun Kim <jh0822.kim@samsung.com>
src/backend/BSSched/Checker.pm
src/backend/bs_repserver