Open AccessUsing Continous Deployment techniques to manage software change at a WLCG Tier-2
Author(s) -
G. Roy,
E. Simili,
Gavin Stewart,
Samuel Cadellin Skipsey,
D. Britton
Publication year - 2020
Publication title -
journal of physics. conference series
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.21
H-Index - 85
eISSN - 1742-6596
pISSN - 1742-6588
DOI - 10.1088/1742-6596/1525/1/012066
Subject(s) - software deployment , computer science , software , automation , grid , software engineering , software development , downtime , process (computing) , configuration management (itsm) , resource (disambiguation) , systems engineering , operating system , engineering , mechanical engineering , computer network , geometry , mathematics
Continuous Integration (CI) and Continuous Development (CD) are common techniques in software development. Continuous Integration is the practice of bringing together code from multiple developers into a single repository, while Continuous Development is the process by which new releases are automatically created and tested. CI/CD pipelines are available in popular automation tools such as GitLab, and act to enhance and accelerate the software development process. Continuous Deployment, in which automation is employed to push new software releases into the production environment, follows naturally from CI/CD, but is not as well established due to business and legal requirements. Such requirements do not exist in the Worldwide LHC Compute Gird (WLCG), making the use of continuous deployment to simplify the management of grid resources an attractive proposition. We have developed work presented previously on containerised worker node environments by introducing continuous deployment techniques and tooling, and show how these, in conjunction with CI/CD, can reduce the management burden at a WLCG Tier-2 resource. In particular, benefits include reduced downtime as a result of code changes and middleware updates.