[FOLIO-1481] Move CI job lint-raml to before maven Created: 11/Sep/18  Updated: 24/Dec/18  Resolved: 23/Dec/18

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

Type: Task Priority: P3
Reporter: David Crossley Assignee: David Crossley
Resolution: Done Votes: 0
Labels: ci, raml
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-1410 Use dedicated Sonarqube Github user f... Closed
Relates
relates to FOLIO-1027 Integrate RAML linting for all raml-b... Closed
relates to FOLIO-1447 FOLIO policy for RAML and JSON descri... Blocked
Sprint:

 Description   

The "lint-raml" stage ( FOLIO-1027 Closed ) would be better placed before the "Maven Build" stage in the Jenkins Pipeline. There it can help to explain related build problems.

However, the SonarQube stage is wiping out the messages from previous stages. So await FOLIO-1410 Closed .



 Comments   
Comment by David Crossley [ 23/Dec/18 ]

Done in https://github.com/folio-org/jenkins-pipeline-libs/pull/56

Comment by David Crossley [ 24/Dec/18 ]

That also split the lint-raml job into two stages:

First do "Lint raml-cop" early before "Maven build" to assess the RAML and examples against schema.

At the end of pipeline do "Lint raml schema" to assess the RAML Schema descriptions FOLIO-1447 Blocked .

Reduces potential to overlook RAML errors.

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