HiveMinds / HiveMinds/gitlab-ci-build-statuses

Disable setting build status icon when it runs CI per commit.

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Currently the commits are evaluated in Descending order. That means the build status icon of an older commit can overwrite a more recent build status. Three solution strategies are:
- [ ] Enable pagination and run on Ascending order. (This could still allow overwriting a new build icon, if the CI is ran per repo on a commit 4 commits ahead of those that have been evaluated, then the running CI per commit would overwrite that build icon 3 times, but not the last time, because that already has been evaluated). So instead, go for option 3.
- [ ] Disable setting icon on running CI per commit, and only set build icon when CI is ran per repo (Which only evaluates the latest commit per branch).
- [ ] Sort the commits per branch on date, and then only set build icon if it pertains to a newer commit than that of the previous build status icon. Determine a way to determine to which commit the current/old build status icon belongs. Perhaps a comment in the svg.

Currently the second option is implemented, as a temporary fix.

Modify this by passing some boolean argument that makes it export the icon, or not in:
` copy_commit_build_status_to_github_status_repo()` in `run_ci_on_github_repo.sh`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in run_ci_on_github_repo.sh at copy_commit_build_status_to_github_status_repo(). Read the surrounding CI-per-commit and CI-per-repository flow, then verify how the temporary second strategy currently controls icon updates. Done means the function can receive a boolean controlling whether the icon is exported, with behavior verified for both CI execution paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, gitlab, shell
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.