ci: Poll the internal pipeline every 60s instead of every 10 - #217
Open
DanielKellerM wants to merge 1 commit into
Open
ci: Poll the internal pipeline every 60s instead of every 10#217DanielKellerM wants to merge 1 commit into
DanielKellerM wants to merge 1 commit into
Conversation
poll-period was never set, so the default of 10 seconds applied and the budget was 10800 polls x 10s = 30 hours, not the 3 the comment claimed; only timeout-minutes bounded the job. The internal pipeline runs for tens of minutes, so polling that often buys nothing and costs about 1200 API calls per run. 60s x 180 is the 3 hours the comment always intended, and matches the setting gwaihir already uses.
DanielKellerM
force-pushed
the
ci/gitlab-poll-period
branch
from
August 19, 2026 12:10
0e6a699 to
240923f
Compare
DanielKellerM
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
poll-periodwas never set, sopulp-actions/gitlab-ciused its default of 10 seconds:The comment divides by 60 as if the period were one second. The real budget is
10800 x 10s= 30 hours; onlytimeout-minutes: 200bounded the job. The internal pipeline runs for tens of minutes, so polling that often costs roughly 1200 API calls per run against iis-git for no benefit.60s x 180is the 3 hours the comment always intended, and matches what gwaihir already uses.What other pulp repos do
cheshire carries the identical comment and the same unset period, so it has the same 30 hour budget.
Whether the polling can be removed
Holding a GitHub runner for up to 200 minutes purely to wait is the real cost, so the push-based options were checked:
iis-git.ee.ethz.chruns GitLab 19.2.4 Community Edition (enterprise=false) and the API rejects thegithubintegration slug outright; it is Premium/Ultimate only..gitlab-ci.ymljob POSTing to/repos/pulp-platform/iDMA/statuses/<sha>is feasible and needs no extra infrastructure: the internal runners already reach github.com, sincebender checkoutfetches dependencies from there on every job. It needs a PAT with commit-status write stored as a masked CI variable, which is a credential decision rather than a code change. This is the commonly recommended approach for CE.Nothing native to CE removes the wait, so this PR fixes the interval and leaves the push-based change to a follow-up.