Productization requirements:

• Upstream sources: https://github.com/che-dockerfiles/che-backup-server-rest
• Upstream image: quay.io/eclipse/che-backup-server-rest:eeacd92
• Downstream image: quay.io/crw/backup-rhel8 and registry.redhat.io/codeready-workspaces/backup-rhel8

• add branch creation every 3 weeks (tied to Che releases) so we can productize from a stable branch/commit, rather than tip of the main branch - see https://github.com/eclipse-che/che-release/blob/main/make-release.sh#L204

• ask Nick to add you to https://github.com/orgs/redhat-developer/teams/che-productization-collab/members (so you can see private GH repos like codeready-workspaces-productization)
• get added to https://comet.engineering.redhat.com/containers/teams/5c79a4debed8bd28d0e5bc31 via someone who's already in there (eg., Nick, Eric)
  • new comet build entry ==> pkgs.devel repo - see https://github.com/redhat-developer/codeready-workspaces-productization/blob/crw-2-rhel-8/devdoc/building/osbs-container-builds.adoc#gaining-access
    • naming convention is codeready-workspaces- prefix, then a simplified name for the container, eg., codeready-workspaces-backup
    • does not have to have the same name as upstream; often simplifies it and removes "che" from the name, eg., che-theia -> theia-rhel8
  • new comet delivery entry ==> RHEC url (make sure added to the correct errata targets/branches) - https://github.com/redhat-developer/codeready-workspaces-productization/tree/crw-2-rhel-8/devdoc/publishing#non-operator-container

• new folder in crw-images repo to contain sources transformed/synced from upstream
  • use same naming convention as for the pkgs.devel repo, eg., codeready-workspaces-backup
• new sync.sh script to handle sync logic (upstream -> midstream)
• new get-sources.sh script to handle fetching any third party deps not able to be synced (or vendored) directly in the source tree
  • to run rhpkg builds, need POSIX LDAP group devel access - request access via this form
  • to install rhpkg and brew tools locally, see https://gist.github.com/nickboldt/52d7031fab62bfab7ed15195ddfc9e7f#file-f31-sh-L141
• implement Jenkins job in https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/tree/master/jobs/CRW_CI to build in 2.11 and 2.x branches - ideally reusing the template_*.jenkinsfile so that your new crw-foo.groovy is as minimal/simple as possible. See https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins#first-time-user-setup for initial setup steps.
  • job will sync from up to midstream, then trigger a second job to sync from mid to downstream, and collect any 3rd party binaries that can't be fetched during the offline Brew container build. A third job will then allow you to run rhpkg container-build via Jenkins, using the crw bot.

• in midstream repo, create container.yaml and content_sets.yml files to define how to build in brew and from which RPM repos; these will be synced to downstream and used by Brew.

• add to build-all-images job so it can be rebuilt weekly, in the correct sequence based on dependencies (parents, children)
• include container in scripts getLatestImageTags.sh, tagRelease.sh, and manifest/get-3rd-party-deps-manifests.sh

• create image in quay https://quay.io/repository/crw/backup-rhel8 and set correct owners/creators permissions so humans and bots can push content
  • owners: admin
  • creators: write
  • crwci bot: write

• update deployment yaml in 2.11 and 2.x branches (see codeready-workspaces-operator/build/scripts/sync*.sh) to replace this:

            - name: RELATED_IMAGE_internal_rest_backup_server
              value: quay.io/eclipse/che-backup-server-rest:eeacd92

with

            - name: RELATED_IMAGE_internal_rest_backup_server
              value: registry.redhat.io/codeready-workspaces/backup-rhel8:2.11

---------------------

https://github.com/eclipse/che/issues/18703