The plan is to tag a specific revision on both the service and the ui repo and then point to that tag here, right? I think this may be a pain in case we want to update one of the two component but not both (for a quick fix for example). Why don't we consider the ui and the service as 2 separate projects, with a update.py script in each repo? The ui-update script could contain the code update and the grunt build command, while everything else could keep staying here.