[FOLIO-3005] Create ui-export-manager repository and add to CI Created: 09/Feb/21  Updated: 10/Feb/21  Resolved: 10/Feb/21

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

Sprint: DevOps Sprint 107
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 [ 10/Feb/21 ]

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

So it is ready for you to add initial code.
Then the 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 Mikita Siadykh [ 10/Feb/21 ]

David Crossley
initial set up (including Jenkins file) is done

Comment by David Crossley [ 10/Feb/21 ]

Hmmm, it seems that i need to wait for another pull-request to happen, before the branch protection setting can be finalised. Not sure why.

Comment by Mikita Siadykh [ 10/Feb/21 ]

David Crossley unfortunately I don't have anything to commit for now, I'll comment when smth is merged

Comment by David Crossley [ 10/Feb/21 ]

There is the boilerplate text of the README.

You are not alone. There are many UI module READMEs in this state.

Comment by Mikita Siadykh [ 10/Feb/21 ]

David Crossley merge one more PR, please try again

Comment by David Crossley [ 10/Feb/21 ]

I was now able to finalise the branch protection.

Gee, an "Introduction" to explain the purpose of the module would seem to be essential.

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