[FOLIO-2843] Create remote storage repository and add to CI Created: 20/Oct/20  Updated: 25/May/21  Resolved: 03/Nov/20

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

Type: Task Priority: P3
Reporter: Mikita Siadykh Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Gantt End to Start
has to be done before UIRS-4 Project Setup: ui-remote-storage Closed
Relates
relates to FOLIO-2851 Amend Jenkins Sonar config to use def... Open
relates to FOLIO-3172 Amend Jenkins Sonar config to use mai... Open
Sprint: DevOps: Sprint 100
Development Team: FOLIO DevOps

 Description   

Overview:
Please create github repo and associated CI infrastructure (Jenkins/Sonarqube/etc.):

Acceptance Criteria:

  • The repo is created and added to the respective teams
  • Members of these team can create and merge branches
  • CI has been setup for the repo, including jenkins builds and sonarqube analysis


 Comments   
Comment by David Crossley [ 20/Oct/20 ]

Created a new empty repo: https://github.com/folio-org/ui-remote-storage
and configured Team access.

So it is ready for you to add initial code.
Then a basic Jenkinsfile can be committed directly to master branch. That will do the base Sonar scan.

See some guidelines at https://dev.folio.org/guidelines/create-new-repo/

After the first pull-request, then i can finalise the branch protection settings.

Comment by David Crossley [ 20/Oct/20 ]

Also note that from here on, new repos have default branch "main".

Comment by Marc Johnson [ 20/Oct/20 ]

David Crossley

Also note that from here on, new repos have default branch "main".

Does that mean that the Jenkins builds have been tested and they work with a mainline branch other than master?

Comment by David Crossley [ 20/Oct/20 ]

Oh, good question. Will raise at DevOps meeting today. IIRC a GitHub announcement said that the transition would be seamless.

Comment by Mikita Siadykh [ 23/Oct/20 ]

David Crossley done with set up

Comment by Mikita Siadykh [ 23/Oct/20 ]

but Sonar is failed because of main branch, should we still use master?

Comment by David Crossley [ 23/Oct/20 ]

Ah we at DevOps wondered if something would break. It seems that this transition will not be seamless.

Yours is the first new repo.

Perhaps just disable Sonar in your Jenkinsfile until this is sorted.

Comment by David Crossley [ 28/Oct/20 ]

Until we handle FOLIO-2811 Open and related tickets, to generally deal with the master/main thing ...

I have created a new branch called "master" and configured that as the "Default branch".

I temporarily retained the branch "main" in case you had outstanding commits. When those are merged, then please delete the old "main" branch.

Comment by David Crossley [ 02/Nov/20 ]

Mikita Siadykh Please follow-up on the previous Jira comment regarding the old "main" branch.

Comment by Alex Mozolev [ 03/Nov/20 ]

David Crossley I've deleted "main"

Comment by David Crossley [ 03/Nov/20 ]

Thanks

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