[FOLIO-3186] Investigate infrastructure configuration and scripts to handle Git default branch name Created: 03/Jun/21  Updated: 23/Jul/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   

Various infrastructure and Jenkins configurations explicitly use "master" for deciding whether the operation is for a feature branch or the mainline branch. Handle the transition to new default branch.

This is a basic overview and investigation of the steps that will be required. Scanned some main repositories to find mentions of "master". Trying to added separate tickets for each.

 


jenkins-pipeline-libs

About 12 Groovy files, mostly in the "vars" directory.

Every backend repo Jenkinsfile has "publishMaster" parameter in "doDocker"
(Publish image to Docker repo (master branch only): Default: true)
Need to handle another parameter in vars/build*Docker.groovy and get every back-end repo to transition.

Also some non-standard Jenkinsfile (e.g. raml-util mod-licenses) refers to "master"


folio-ansible

About 20 files, mostly in roles, a couple in group_vars, and a few in docs

Also need to consider release branches which are still in use.


folio-infrastructure

About 60 files:
mostly in CI/jenkins and CI/terraform
CI/packer/Jenkinsfile
some in CI/vagrant/vagrant-nodes.yml and CI/ansible and CI/eks/apps
serverless-devdoc-pipeline

Also need to consider branches which are still in use.

Update git submodule at CI/ansible/folio-ansible


platform-complete and platform-core

Jenkinsfile.build
renovate.json

Also need to consider snapshot and release branches which are still in use.


folio-tools

packaging/docker-build.sh

These refer to hard-coded "master" for folio-ansible:
kubernetes-utilities/folio-ansible-runner/Dockerfile
kubernetes-utilities/folio-ansible-runner/entrypoint.sh

These deprecated tools refer to "master" of the old configuration file
generate-api-docs
lint-raml


Jenkins

Most pipelines have explicit configuration for "master" branch of the relevant repos.


dev.folio.org repo

Apart from much documentation FOLIO-2813 Open , there is hard-coded "master" for documentation-related links in the Liquid code for source-code/map and reference/api which can only be altered after FOLIO-2811 Open .

The GitHub Actions workflows (daily automation) will need various code changes.


GitHub Actions workflow-templates need to handle master or the new name.


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