#81 Updating a Pull Request does not trigger new CI job until refreshed in browser
Closed by jimbair. Opened by churchyard.

  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


This is a pagure issue. I know we've tracked it a few times already in the past, maybe we need to track it again :(

@pingou is there an issue over in https://pagure.io/pagure/issues we could link to?

@jimbair not a recent one I fear, feel free to create one and close this ticket

@pingou thanks! Created https://pagure.io/pagure/issue/4795 and closing this one out

Metadata Update from @jimbair:
- Issue status updated to: Closed (was: Open)

Metadata