OK, from what i understand git/repo sync etc. can fail on "slave" side and on "mirror" side.
I would think:
1. error on "slave" must make build fail! If not thats a bug (e.g. if repo sync exits 0 -> bug!)
2. error during "mirror" update might be ok. So, let's still go ahead and mark such builds in UI with a warning like "might have used outdated repos: <FAILED-TO-SYNC-REPO-LIST> would be appropriate.
3. if "mirror" initial sync failed, a hard fail happens and it is properly displayed in UI that this was a mirror fail.
OK, from what i understand git/repo sync etc. can fail on "slave" side and on "mirror" side.
I would think:
1. error on "slave" must make build fail! If not thats a bug (e.g. if repo sync exits 0 -> bug!)
2. error during "mirror" update might be ok. So, let's still go ahead and mark such builds in UI with a warning like "might have used outdated repos: <FAILED- TO-SYNC- REPO-LIST> would be appropriate.
3. if "mirror" initial sync failed, a hard fail happens and it is properly displayed in UI that this was a mirror fail.
4. log all mirror errors and review regularly.