e6653ea2aa
Previously it was possible for an acl push to fail then we would record successful acl push via our project cache's sha entry for that acl file. The reason for this is despite success or failure of the acl push we continue on without "problems". Unfortunately this can lead to projects failing to update without any indication this has happened. Update jeepyb to raise an exception if there is a failure pushing. THis should prevent the project cache file from being updated and will cause manage-projects to try again later. The downside to this is we will short circuit our project handling if there are many updates to perform. THis seems preferable to silently "succeeding". Note that we special case read only projects by detecting the error pushing an acl to a read only project and treating this as success. This will allow us to delete our cache file and update everythin while passing over read only projects as is. Change-Id: I0d1c1160f2a28fc023fd71c8010ddcf6555efa14 |
||
|---|---|---|
| .. | ||
| cmd | ||
| config | ||
| __init__.py | ||
| gerritdb.py | ||
| log.py | ||
| projects.py | ||
| translations.py | ||
| utils.py | ||