[OPENAM-10114] Verify docs builds Created: 29/Nov/16  Updated: 03/Dec/16  Resolved: 03/Dec/16

Status: Resolved
Project: OpenAM
Component/s: documentation
Affects Version/s: 12.0.4, 13.0.0, 13.5.0, 14.0.0
Fix Version/s: 12.0.4, 13.0.0, 13.5.0, 14.0.0

Type: Task Priority: Major
Reporter: David Goldsmith Assignee: David Goldsmith
Resolution: Fixed Votes: 0
Labels: AME, SHAKESPEARE
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Due to access changes for the releases and snapshots repos, it may be that doc builds fail trying to download artifacts.

The task is to make sure that the branches we are sustaining continue to build correctly:

  • Check that repo IDs are aligned with the settings.xml IDs. This ensures appropriate credentials are used to connect to the repo when downloading artifacts. (Make sure settings.xml is obtained per https://wikis.forgerock.org/confluence/display/REPLAN/Artifactory+FAQ.)
  • Remove the directories under ~/.m2/repository/ that hold artifacts required for the doc build.
  • Build as for a release.

Once everything is working locally and any PRs are resolved, also run a test release build to be sure that the release build also works on Jenkins.



 Comments   
Comment by Mark Craig [ 30/Nov/16 ]

In fact, maybe we were right and the settings.xml file was wrong.
As per the engineering chat:

[9:42 AM] Bruno Lavit: So the settings.xml we are using on the build machines wasn't correct regarding the snapshots et releases repo.
[9:42 AM] Bruno Lavit: These repos were using a wrong repo ID.
[9:42 AM] Bruno Lavit:
forgerock-snapshots instead of forgerock-snapshots-repository
[9:43 AM] Bruno Lavit: I've updated the .m2/settings.xml file on the CoreOS boxes.
[9:43 AM] Bruno Lavit: All the next Maven builds should be OK.

Comment by David Goldsmith [ 03/Dec/16 ]

Built the docs locally for 12.0.4, 13, 13.5, and 14 with no issues.

Performed QA doc releases for 12.0.4, 13, and 13.5 with no issues.

Generated at Wed Nov 25 07:44:18 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.