service-pipeline-test-and-publish fails when it's initiated with creating a tag on change-propagation repo. It seems like it tries to post some comment to Gerrit, but fails to find the gerrit change-id, which is reasonable, since the pipeline build was initiated by creating a tag in the sources. Change-prop is developed on GitHub for now, so commits don't have Change-IDs.
Example build:
https://integration.wikimedia.org/ci/job/service-pipeline-test-and-publish/1128/console
In case a comment to gerrit can't be left, pipeline should ignore it and still publish the artifacts.