110 likes | 123 Views
Learn about the continuous delivery process for CS-Studio, including local copy setup, compilation and testing on development repositories, delivery on production repositories, and integration into the ESS Development Environment.
E N D
CS-Studio & ESS Continuous Delivery Process Claudio Rosati, Software Engineerclaudio.rosati@esss.se Leandro Fernandez, Software Engineerleandro.fernandez@esss.se EPICS Collaboration Meeting 19-23 September 2016, Oak Ridge National Laboratory
Objectives • Having a local copy of CS-Studio. CS-Studio & ESS Continuous Delivery Process
Objectives • Having a local copy of CS-Studio. • Continuous delivery process for: • Compilation and testing on changes in development repositories; • Compilation, testing and delivery on changes in production repositories; • Compilation and testing on changes in community edition repositories before synchronisation. CS-Studio & ESS Continuous Delivery Process
Objectives • Having a local copy of CS-Studio. • Continuous delivery process for: • Compilation and testing on changes in development repositories; • Compilation, testing and delivery on changes in production repositories; • Compilation and testing on changes in community edition repositories before synchronisation. • Integration into the ESS Development Environment CS-Studio & ESS Continuous Delivery Process
Future Developments • Moving to Jenkins 2 • Pipeline DSL (domain-specific language) based on the Groovy programming language. • A pipeline script can be committed on GitHub and shared. • Using docker containers to setup the testing environment. • Adding Unit tests to the pipeline. • Adding UI tests to the pipeline. CS-Studio & ESS Continuous Delivery Process
Thank you CS-Studio & ESS Continuous Delivery Process