[FOLIO-932] refactor maven and Nodjs-based CI build pipeline Created: 10/Nov/17  Updated: 12/Nov/18  Resolved: 22/Nov/17

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

Type: Task Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: ci, sprint26, sprint27
Remaining Estimate: Not Specified
Time Spent: 1 day, 3 hours
Original estimate: Not Specified

Sprint:

 Description   

refactor maven-based CI docker builds to use a smaller, generic image with custom configuration and credentials stored in Jenkins.



 Comments   
Comment by John Malconian [ 22/Nov/17 ]

This round of refactoring complete.

  • Removed 'secrets' from Docker images used for all FOLIO builds and reconfigured Jenkins and pipeline scripts to inject them during build time. Now the images can be stored publicly in the 'folioci' repository on Docker Hub. Useful for when we will need to scale to a distributed Jenkins environment.
  • Use 'yarn' instead of 'npm' for Nodejs-based builds with the exception of 'publish'. Using yarn means we can honor project yarn.lock files in builds.
  • 'publishModDescriptor' is now more generic.
  • Move smaller, useful functions to a class called 'foliociCommands'. More work could probably be done here.
  • Make some of the functions more generic so that we can more easily expand to non-Nodejs or non-Maven based projects in the future.
  • Add some user documentation to jenkins-pipeline-libs repo.
  • Some other smaller things that I'm forgetting right now.
Generated at Thu Feb 08 23:09:22 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.