Issues

Select view

Select search mode

 

Detect common mistakes with module configuration early in CI stages

Description

Some mistakes with module configuration will cause disruption for subsequent build systems, and so hinder further services and development, and cost devops time.

Detect such during the early phases of a module project repository branch build continuous integration.

Some grief situations and some notes:

  • Incomplete release process not updating mainline POM version ready for next development (e.g. , and another a few weeks ago)

  • Must use a proper complete SemVer (e.g. FOLIO-3015 used only major.minor (follow the link to FOLIO-3001 comment and subsequent discussion).

  • Must use appended "-SNAPSHOT"

  • Mismatch of port numbers (ModuleDescriptor, Dockerfile, and in program code and configuration).

  • https://dev.folio.org/guides/install-backend-module/#avoid-typical-mistakes

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

FOLIO DevOps

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 13, 2022 at 11:01 AM
Updated November 13, 2024 at 9:00 PM

Activity

Show:

Marc Johnson January 13, 2022 at 11:28 AM

Must use appended "-SNAPSOT"

Given that our mainline builds are used to seed our pre-release artefacts, I like the idea of failing mainline builds that are not considered a pre-release.

TestRail: Cases
TestRail: Runs
Loading...