[FOLIO-2352] Create jenkins pipeline for single module deployment to k8s Created: 14/Nov/19  Updated: 03/Jun/20

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

Type: Task Priority: TBD
Reporter: Ian Hardy Assignee: Ian Hardy
Resolution: Unresolved Votes: 0
Labels: ci, devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Core: Platform

 Description   

Instead of running the module deployment as a stage of the snapshot/release build, create a pipeline to deploy modules to kubernetes.

Requirements:

  • takes a module/version as a parameter
  • fails if module is not successfully deployed to kubernetes
  • can be triggered when a release/snapshot job is complete.

Benefits over existing kubeDeploy step in the buildMvn pipeline:

  • Increased transparency: The current deployment method deploys a job on kubernetes which in turn deploys the. module. If the job itself is deployed correctly, but the tasks in the job failed then it's hard to see the failure from jenkins (pipeline will succeed)
  • Better separation from release job. This can be triggered by release jobs, but insulates the release process itself from depending on the health of the k8 infrastructure (which isn't specifically related to releasing a module.


 Comments   
Comment by Jakub Skoczen [ 26/Nov/19 ]

Ian Hardy --has this ticket been closed?

Comment by Ian Hardy [ 26/Nov/19 ]

I'd like to keep this one open. We already are using a method to deploy modules to k8s, but IMO it's overly complicated. This is about improving/replacing that. Not urgent (as long as the old method isn't causing John Malconian any problems right now).

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