...
# | Assumption | Notes |
|---|---|---|
| 1 |
Open Issues & Decisions
...
| # |
|---|
| Issue | Answer/Resolution | Notes/Images | |
|---|---|---|---|
| 1 | After adding files there are 2,300 checkstyle violation | After conversation with Toine Siebelinkwe are to ignore violations and proceed to see if it is a viable option |
|
| 2 | Was using latest codebase from GitHub but should be aligned with Andrew Fenner | I am in contact with Andrew Fennerto ensure that we are both testing with the same release version |
.
Approaches
...
- Explore option to automatically copy an build using a Nordix Repo and C/I job. Some technical and legal issues to be examined. Will the delivered artifact(s) be available to non-Nordix users ie. what repo will be used?
- Create CPS sub-repo with copy of sources from https://github.com/liquibase/liquibase (legal option, but not easy to share with others) Later even a new shared stand-alone repo? (two-step approach) (Appears to be the quickest and most efficient way to add liquibase to code base)
- Consider DB-Migrator tool already used and part of ONAP: https://docs.onap.org/projects/onap-policy-parent/en/guilin/drools/pdpdEngine.html#data-migration
- Consider FlyWay https://dzone.com/articles/flyway-vs-liquibase
Point #1
Andrew Fenneris investigating this.
Point #2
- Clone liquibase code from GitHub: https://github.com/liquibase/liquibase
- Create new module in CPS (e.g. cps-liquibase)
- Add necessary code to new module (After adding files there are 2,300 checkstyle violations)
...
- Build liquibase with CPS & ensure DB steps are carried out
Point #3
Point #4
Former user (Deleted)is investigating this.