Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve waiting for the Copr builds during weekly deployment #646

Open
1 of 2 tasks
mfocko opened this issue Mar 3, 2025 · 2 comments
Open
1 of 2 tasks

Improve waiting for the Copr builds during weekly deployment #646

mfocko opened this issue Mar 3, 2025 · 2 comments
Assignees
@majamassarini
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@mfocko
Copy link
Member

mfocko commented Mar 3, 2025 •
edited by majamassarini
Loading

As of the latest ogr changes (forgejo support that's not supported on EL9, F40), it is not possible to build ogr in RPM.

Since the script for moving stable branches checks the version in the latest successful build (all targets), it hangs…

Possible options:

  • Do not build stable for targets that are not being deployed…
    • it wastes Copr resources
    • we build from both prod and stage
    • also for alternative architectures… though that may be required for the images
  • Only check for the target that's actually being deployed
    • might require implementation on our side…
    • we need to be careful about hard-coding the target…
@mfocko mfocko added area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Mar 3, 2025
@mfocko
Copy link
Member Author

mfocko commented Mar 3, 2025

Also setting a due date till Monday, as it may annoy the next in “the line of succession”…

@mfocko mfocko mentioned this issue Mar 3, 2025
Closed
9 tasks
@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Mar 4, 2025
@majamassarini majamassarini self-assigned this Mar 13, 2025
@majamassarini
Copy link
Member

packit/packit#2549 and packit/ogr#897 should fix the problem as suggested in the first point.
I let this card open until next deployment to verify this is actually solved.

@majamassarini majamassarini moved this from priority-backlog to in-review in Packit Kanban Board Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@majamassarini majamassarini

Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: in-review
Milestone
No milestone
Development

No branches or pull requests
2 participants
@majamassarini @mfocko