Issue #81: Updating a Pull Request does not trigger new CI job until refreshed in browser - general

fedora-ci / general

#81 Updating a Pull Request does not trigger new CI job until refreshed in browser

Closed 4 years ago by jimbair. Opened 4 years ago by churchyard.

create a src.fp.o Pull Request
CI job starts, all is good
push new commits or rebase
new CI job should start but does not
...
go to the pull request URL in the web browser or refresh it if you already have it open
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

pingou commented 4 years ago

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 :(

jimbair commented 4 years ago

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

pingou commented 4 years ago

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

jimbair commented 4 years ago

@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)

4 years ago

Metadata

Assignee

None

Tags

None

Blocking

None

Depending on

None

Priority

Medium

fedora-ci / general

Source Code

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

Metadata

#81 Updating a Pull Request does not trigger new CI job until refreshed in browser

Closed 4 years ago by jimbair. Opened 4 years ago by churchyard.