adapt and attach existing gitlab pipelines to the new github repo.

details

build + test

• add new job template definitions, based on the global github templates, duplicating existing ones (the gitlab templates will be removed at a later phase)
• add new jobs, calling the newly created github templates, duplicating existing ones (the gitlab jobs will be removed at later phase)
• update project/group keys in the jobs config' project field to the github keys (or duplicate the entire definition, if possible)
• update repo URL in the OCM app landlord code-component definition (or duplicate the entire definition, if possible)
• manually create GH webhooks for initial configuration of ci-ext hosted jobs; read this guide wait! our GH repo is private, so CI should probably remain on ci-int! read this section

existing jobs to migrate:

• pr-check jobs for topic/long-lived branches (push to quay)
• build-deploy jobs for long-lived branches (push to quay)
• FedRAMP jobs (push to insights)
• cypress E2E smoke-test pipeline jobs
• cypress E2E smoke-test image builder job

deploy

• update repo URL in the deploy resource-template definition (or duplicate the entire definition, if possible)

observability

• update prometheus rules (1, 2, 3), to reference the newly created github job keys (check if this is necessary - these configs might be obsolete)

Q & A

• is there any change necessary in the OCM app config' field codeComponents.gitlabSync?
  looks like it was added to aid FedRAMP somehow, for mirroring the repo (see this revision), but the source and target are the same.. wat

  no, there's no change necessary - apparently the target refers to a separate gitlab instance, used solely for FedRAMP. tho, we may have to add the same codeComponents.gitlabSync field to the newly added codeComponent

• how can we keep the sync to the FedRAMP instance, after the migration? at the moment, github is not supported for gitlabSync.
  (would we have to keep the gitlab repo, just for the FedRAMP sync?)

  good question - it was delegated to the #sd-app-sre slack channel, as per the app-interface docs (see enable gitlab repo synchronization).

  from the answer: see https://github.com/app-sre/git-partition-sync-producer and https://github.com/app-sre/git-partition-sync-consumer?tab=readme-ov-file

• is the prometheus rules change necessary? what are they used for? what is prometheus? does it not refer to old, obsolete jobs?

references

• jenkins job-builder wrappers
• jenkins job-builder publishers
• jenkins job-builder triggers