Skip to content

Bump images to F44 #705

@mfocko

Description

@mfocko
  • Bump the release of the base image

    • Optionally tag the last build of the previous release in Quay, in case a rollback is necessary
  • Check depending images (locally if it's possible to rebuild, or if there are needed changes)

    • Sandcastle
    • Fedora Messaging consumer (it might be needed to change the destination of Python libs, if the default version of Python changes; PYTHONPATH to adjust)
    • Dashboard
    • Packit
    • Packit Service
  • Trigger rebuild of the images (rebuild for main, not for stable)

    • Sandcastle
    • Dashboard
    • Packit
    • Packit Service
  • Check the state of the deployments with the rebuilt images

    • Fedora Messaging (can initially fail because of the obtained lock on a queue)
    • Sandcastle (needs a sync-release run to occur)
    • Dashboard
    • Packit (feel free to waive with the successful build, or check locally)
    • Packit Service (both service and workers)
  • Adjust the merge requirements to require a passing RPM build and Testing Farm for the currently deployed Fedora release

    • ogr
    • requre (required as a testing dependency
    • specfile
    • packit
  • Create a duplicate of this ticket for the next Fedora release and set due date in Jira to +6 months

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/generalNot tied to a specific areacomplexity/single-taskRegular task; should be done within dayskind/internalTask that doesn't affect users directly

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions