-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not existing revision ID used #161
Comments
ok, it´s not depending on specific branch: If review is merged, pipeline is triggered with non/never existing revision id: If I copy revision id shown in VSM view, and search for it in gerrit web UI, it is not found. If I run pipeline manually with revision id copied from gerrit web UI after the merge is shown in web UI, it works. But this is a different revision id! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use Gerrit Change Set plugin 1.4.0-RC4 and Gerrit Change Set status notifier 1.7.0-107
I have created a pipeline B which has two materials, one is a gerrit repo 1, second is a upstream pipeline A which has a different gerrit repo 2 as material. Pipeline B fetches a build artifact from pipeline A.
If pipeline A has been successfully run, pipeline B starts, but with a gerrit revision which does not exist.
If I manually trigger pipeline B with an existing repo 1 number, it works perfect, also if I upload a change to gerrit repo 1, it triggers automatically with correct revision.
I think the problem has to do with this: The plugin materials of the repos are based on a devel branch. If a merge to the master branch is done, pipeline starts with a revision ID which only is temporary.
The text was updated successfully, but these errors were encountered: