[FOLIO-3928] Jenkins: all automatic UI builds fail Created: 27/Nov/23  Updated: 28/Nov/23  Resolved: 28/Nov/23

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

Type: Bug Priority: TBD
Reporter: Zak Burke Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Requests
Development Team: FOLIO DevOps
RCA Group: TBD

 Description   

Summary: All automatic UI builds for our reference envs are presently broken:

  • folio-snapshot (daily): this job was disabled after a “successful” build on Saturday, 2023-11-25. 
    • I don’t know who disabled it, or why.
    • I say “successful” because although the build technically succeeded, the stripes-core build referenced in the log (v10.1.1000001544) wasn’t built from the master branch, it was from an early commit on our RTR/Poppy testing branch. IOW, A) it’s the wrong branch, and B) even if it was the right branch it would still be the wrong commit on that branch.
  • folio-snapshot-2 (daily): the yarn install portion of job began failing yesterday with errors like ‘An unexpected error occurred: “https://repository.folio.org/repository/npm-ci-all/typescript/-/typescript-4.9.5.tgz: Request failed “500 Internal Server Error”“’ and indeed, that URL returns a 500 for me, too. But that URL had to get into our yarn.lock file somehow, which means it must have been resolvable at some point. 
  • platform-complete (hourly): These builds began failing yesterday after the 05:19 UTC build with messages like “info There appears to be trouble with the npm registry (returned undefined). Retrying...” Some googling suggests this may be resolvable by changing yarn install to yarn install --network-timeout 1000000. It may be worth trying, but even if it works I’d still like to know what changed that installs are suddenly taking longer. 


 Comments   
Comment by Zak Burke [ 27/Nov/23 ]

Possibly related, as reported on Slack#devops: Nexus repo appears to be in read-only mode according to error messages some build logs: "503 Nexus Repository Manager is in read-only mode".

Comment by John Malconian [ 28/Nov/23 ]

There are a couple of issues.

1. Storage capacity on the Nexus repository was maxed out. This issue has been resolved. I've added additional storage capacity.

2. Fixing #1 results in a successful build, but the FOLIO Login Page is blank. The version of stripes-core currently configured on platform-complete is 10.1.1000001544. However, after examining the Github Actions build history, version 10.1.1000001544 was built from a non-master/main branch called 'test-build'. Typically, only builds on master or main branches publish NPMs and MDs, however, the workflow was modified on this branch to remove the branch checks.

https://github.com/folio-org/stripes-core/commit/3004fb50cf7723d0f54013693dcac8ed42251adb.

The last legit snapshot version is 10.1.1000001504

I would recommend making a trivial commit to master to increment the snapshot release.

Comment by John Malconian [ 28/Nov/23 ]

New NPM package and MD generated from master branch of stripes-core, new version added to platform-complete@snapshot, and rebuild of folio-snapshot underway.

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