[FOLIO-3261] Transition master: project-related repos rename primary branch Created: 03/Aug/21  Updated: 03/Aug/21

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: David Crossley Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-2858 Transition to 'main' as the new defau... In Progress
Sprint:
Development Team: FOLIO DevOps

 Description   

Rename the primary branch of project-related repositories (mod-* and ui-* and stripes-* and folio-* repos).

The current plan is to do this on a dedicated day ( FOLIO-3225 Open ).

(The infrastructure-related repositories will already be switched and tested FOLIO-3244 Open .)

As soon as each project-related repository is switched, people will need to repair their clones. See GitHub documentation updating-a-local-clone.

On the day (TODO: Planning of these steps is not yet complete):

  • Send another reminder notice, asking people to be ready to test their repo.
  • Commence with two test repositories (e.g. mod-tags and ui-tags). For these test repos only, add a special property to their Jenkinsfile (defaultBranch = 'main'). Do a PR and merge. Ensure success of each build stage.
  • After success with those test repos, then set the general property (defaultBranch = 'main') in the jenkins-pipeline-libs files "vars/buildMvn.groovy" and "vars/buildNPM.groovy".
  • Switch the remainder (see the lists in "Source-code map").
  • Ask developers to verify their repos with a test PR and merge (do a minor change, e.g. set the README date to 2021). Raise separate Jira tickets if problems are encountered.

Generated at Thu Feb 08 23:26:48 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.