pagure

Clone

#4795 Updating a Pull Request does not trigger new CI job until refreshed in browser
Opened 4 years ago by jimbair. Modified a year ago

Open
Close issue as:
Invalid Insufficient data Fixed Duplicate Won't Fix

Copied over from here: https://pagure.io/fedora-ci/general/issue/81

  1. create a src.fp.o Pull Request
  2. CI job starts, all is good
  3. push new commits or rebase

  4. new CI job should start but does not
    ...

  5. go to the pull request URL in the web browser or refresh it if you already have it open

  6. new CI job should starts now

It seems that Pagure only notifies the Jenkins about new commits after the Pull Request page is displayed in browser (or maybe GET by HTTP is enough).

cc @pingou @churchyard

Metadata Update from @ngompa:
- Issue set to the milestone: 5.11
3 years ago

Metadata Update from @pingou:
- Issue set to the milestone: 5.12 (was: 5.11)
3 years ago

Metadata Update from @wombelix:
- Issue set to the milestone: 5.13 (was: 5.12)
a year ago

Login to comment on this ticket.

Metadata
None
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.