Uploaded image for project: 'Image Builder'
  1. Image Builder
  2. COMPOSER-2356

Image Builder CY24Q4 backend CI hackathon

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • CY24Q4
    • None
    • None
    • None
    • Image Builder CY24Q4 backend CI hackathon
    • False
    • None
    • False
    • Testable
    • To Do
    • RHIN-1483 - Improve Image Builder's developer experience

      Let's organize a hackathon to close some gaps identified in COMPOSER-2013 and COMPOSER-2014.

      Goals:

      • Improve runtime and coverage of images produced by osbuild-composer:
        • images CI uses every customization and build option at least once.
        • osbuild-composer CI reuses the artifacts built by images CI instead of rebuilding them.
        • Every build customization is tested at least once.
        • The intended effect of each customization is verified.

      Acceptance criteria:

      • A hackathon was organized.
      • Outcomes are documented in this epic.
      • Missed goals are documented as well (possibly in a new epic).

      Proposed steps:

      1. On successful build, upload the image to the appropriate cloud platform and boot it.
      2. In osbuild-composer CI, instead of rebuilding images, download them from the images CI store.

      For step 2, we could use an osbuild wrapper that finds the appropriate image by the manifest ID and downloads it to return to osbuild-composer. This way, end-to-end tests can be set up the same way they are now, but would run faster as they wouldn't need to build every image.

            obudai@redhat.com Ondrej Budai
            obudai@redhat.com Ondrej Budai
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: