Changing the title of a PR will trigger CI jobs to run again. However, in most cases that is rather useless, since nothing has changed. If something failed, it will fail again. If all is well, the outcome won't change either. Thus, re-running tests on title change is a waste of resources. Besides, we already have recheck for Zuul and [citest] for Jenkins to retrigger whenever that makes sense (e.g. transient error or missing dependency becoming available).
recheck
[citest]
I, and others with me collectively maintaining packages in a SIG, use the title of the PR to indicate the status of it to other members of the SIG. For example, we set it to [BLOCKED] if the PR needs one of its dependencies updated or introduced a new dependency, which is not yet available in Fedora. We als use [WIP] and other prefixes to indicate that a PR is not yet ready to be merged.
[BLOCKED]
[WIP]
As an example for illustration, I changed the title of https://src.fedoraproject.org/rpms/python-plotnine/pull-request/4 since it needs a newer version of two of its dependencies. The first scratch build already made that clear. The second run adds nothing.
CC @msrb @fbo for awareness.
Metadata Update from @mvadkert: - Issue tagged with: Zuul CI, jenkins
Hi,
It seems that editing the pull request body triggers the Pagure web-hook event 'pull-request.initial_comment.edited'. When you try to edit the title of the PR, you can also edit the initial comment which is used by Zuul to read 'Depends-on: <pr>' lines. The zuul behavior is to retrigger when the PR description is changed. Pagure does not make any difference between the title and the initial comment. Thus a change in the title triggers a job re-run.
Could the Pagure 'tags' for PR be replacement to the "[]" flag in the PR title ? I see the tags are displayed in the PR listing.
https://opendev.org/zuul/zuul/src/branch/master/zuul/driver/pagure/pagureconnection.py#L144
Log in to comment on this ticket.