Skip to content

not existing revision ID used #161

@weaky

Description

@weaky

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions