[FOLIO-2427] Do initial repository configuration mod-ncip Created: 20/Jan/20  Updated: 03/Jun/20  Resolved: 23/Feb/20

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

Type: Task Priority: P2
Reporter: David Crossley Assignee: David Crossley
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-2441 Add NCIP2-Toolkit jars to FOLIO maven... Closed
Sprint: DevOps: sprint 82
Story Points: 2
Development Team: FOLIO DevOps

 Description   

Follow setup documentation and related documents.

Some initial files are already in place, however there are changes needed. For example:
ModuleDescriptor and POM automated version handling
LaunchDescriptor
Dockerfile
Jenkinsfile



 Comments   
Comment by David Crossley [ 23/Feb/20 ]

This is ready now. The Jenkinsfile is in place, and our CI is deploying artifacts when a PR is merged to master.

There are not yet any RAML files and schemas, so those jobs (runLintRamlCop, publishAPI) are disabled in Jenkinsfile.

The module does not yet have a "health" endpoint, so that is disabled in Jenkinsfile.

Comment by David Crossley [ 23/Feb/20 ]

There are various "getting started" and procedure notes at dev.folio.org to assist with further development (e.g. "Naming conventions" and "Release procedures" and "SonarCloud code analysis"). Use its Search system. Ask for further assistance via Slack.

Comment by David Crossley [ 25/Feb/20 ]

Michelle Suranofsky Most modules are using a default port 8081, and that is what is set in the default LaunchDescriptor and Dockerfile for mod-ncip.

Its README says that the module default is 8082. That is okay, it can be whatever. Would you please align those to be consistent.

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