Eclipse.org Simultaneous Release Releng Jobs

The process of promoting a SimRel staging repository for each milestone, release candidate, and release involves manually triggering the following jobs:

• The simrel.releng.promoteToReleases job promotes the staging area's current SimRel repository to the releases area's current SimRel repository.
  It's good to check that committed changes have all been built and appear in the simrel.buids's main changes.
  The resulting repository location is announced to cross-project-issues-dev@eclipse.org and is consumed by EPP.
• The simrel.releng.makeVisible job makes visible the temporary resources compositeContent${checkpoint}.jar and compositeArtifacts${checkpoint}.jar located in the SimRel repository https://download.eclipse.org/releases/${trainname} as produced by the simrel.releng.promoteToReleases job by copying them to compositeContent.jar and compositeArtifacts.jar.
  This job should be reconfigured to ensure that it runs at the correct time on the correct day according to the release train schedule for the milestone, release candidate, or release.
• The simrel.sbom should be run after EPP's promote-a-build job has promoted a corresponding repository for the EPP IDEs. This can be done before simrel.releng.makeVisible runs.

The process of completing a release and starting a new release involves manually triggering the following jobs after the simrel.releng.makeVisible job has completed:

• The simrel.releng.clean_up_old_builds job removes all child repository subfolders of the current release, except for the actual final release repository's subfolder.
• The simrel.releng.update_latest_repo job updates the https://download.eclipse.org/releases/latest composite to point to current release repository.
• The simrel.releng.setup_next_release job creates the p2 repository for the next release, pre-populating new composite repository to point to the current release.
• The simrel.releng.update_latest_repo job also updates the https://download.eclipse.org/releases/milestone composite to point to the just-created next/upcoming release repository.
• Also update the Simultaneous Release wiki table, the wikipedia's Eclipse_(software) Releases table (including version metadata), as well as other steps from the Release Checklist.
• To start a new cycle, run update_build_configuration.sh. There is a launch configuration Update Build Configuration whose parameters must be changed with the new values.

In all cases, after the simrel.releng.makeVisible job has executed on schedule, and the EPP downloads are available, announce this to simrel-dev@eclipse.org.