[FOLIO-551] FOLIO release artifacts via Jenkins Created: 07/Apr/17  Updated: 12/Nov/18  Resolved: 24/May/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: None
Remaining Estimate: Not Specified
Time Spent: 3 hours
Original estimate: Not Specified

Issue links:
Relates
relates to OKAPI-287 Document release procedure Closed
Sprint:

 Description   

I propose that all release artifacts for FOLIO "releases" created by the core FOLIO development team are created and deployed by FOLIO Jenkins. Artifacts include (but are not limited necessarily to) the following:

  • Maven artifacts and NPM packages uploaded to the FOLIO Nexus repository.
  • Docker images uploaded to the Docker Hub repository.
  • Debian or RPM packages uploaded to a package repository.

The advantage to this approach includes the following:

  • Developers will not require special access or custom configurations to the different repositories.
  • All artifacts are created in a clean and repeatable environment.
  • All relevant artifacts for a project release are produced and distributed consistently.

To implement this, special "release" jobs will be created in Jenkins for all GitHub projects. The release jobs will be initiated manually and will take a single parameter - the Git release tag specifying the version of the release.



 Comments   
Comment by John Malconian [ 28/Apr/17 ]

I've set up release jobs in Jenkins for most backend modules and okapi. The names of the jobs have a '-release' suffix. The jobs are parameterized (git release tag) and run manually. Building a Debian package via this job for Okapi is a bit tricky since I need Pipeline to do it. Also haven't started anything on frontend stuff yet.

Comment by John Malconian [ 24/May/17 ]

Marking this as complete for now. All backend FOLIO components have a Jenkin's release job associated with it and release procedure documentation has been updated. Will leave UI release process alone for now as it seems to be working. We can revisit later if needed.

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