Adobe’s Web Engineering consists of multiple teams which all have an individual release process. Now a version of a Continuous Integration and Continuous Delivery (CI/CD) pipeline was introduced that should unify the release process across all teams. Some teams already onboarded onto the pipeline and have given feedback. Some issues that surfaced with the current pipeline are content synchronization between environments, lack of research on best approaches to solving issues for all teams, and not all requirements were gathered or taken into consideration when designing the current pipeline.

Different research methods were used to solve the research questions. First best practices regarding CI/CD were conducted along with lessons learned from other research projects that investigated CI/CD pipelines. The internal documentation was summarized and compared to what teams are following and where potential improvement points lay. Then interviews were conducted with internal specialists of CI/CD pipeline implementation and with teams that already were using the CI/CD pipeline implementation investigated.

The research on how internal teams follow best practices regarding CI/CD showed some pain points that the teams have. Based on the pain points some actions were already taken to release those during this paper. The current pipeline implementation was compared to an ideal CI/CD pipeline that was based on recommendations and best practices. The result showed some improvement areas that were taken into consideration when designing the potential next CI/CD pipeline version for Adobe’s web Engineering team. In addition to that, CI/CD tools were compared to each other to find a fitting alternative to the current implementation. To support the current pipeline a tutorial was written where teams can see what steps and preconditions, they need to fulfil to onboard to the pipeline successfully and who the contact persons are for the implementation and support.