CASA Software Engineering Project: Build a CASA Package Deployment Pipeline

Develop a CASA deployment pipeline to

• deliver CASA packages on a consistent schedule to all users, on all supported platforms,
• improve consistency and quality of delivered packages,
• reduce manual work required to deliver packages.

Depends on project Standardize CASA Package Contents

Status: See CAS-5389.

---

Team

• ScottRankin - project lead

Customers

• ESO Network Admins
• JAO Network Admins
• NAOJ Network Admins
• NRAO Network Admins
• CASA Testers
• CASA Users

Collaborators

• TBD

Plan

(Note: replace this note with an outline of the plan to complete this project. Do not list detailed steps. These will be tracked in Jira as necessary.)

Deliverables

• Design: CASA Package Contents

Requirements

The CASA deployment pipeline must deliver native packages for all supported platforms.

• Distributing CASA To Users
• CAS-5173

Based on known requirements, we must use the following package management systems:

• Debian
  • Basics
  • Debian Package Management
• Redhat
  • How to create an RPM package

Based on known requirements, we must use one of the following package management systems:

• Homebrew
  • Try Homebrew!
• Macports
  • Guide

Design

(Note: replace this note with a one paragraph summary of the design for this project, a short bullet list of design details, or link(s) other pages documenting the design for this project.)

Implementation

(Note: replace this note with a one paragraph summary of the implementation for this project, a short bullet list of implementation details, or link(s) other pages documenting the implementation for this project. Often, this will be a bullet list including the location for any source code in change control and any user accounts or computers required by this project.)

Tasks

Project tasks are tracked with Jira sub-tasks under this project's master task. See CAS-5389.

-- ScottRankin - 2013-07-16