CI/CD Industry Workshop (CCIW) 2021
Continuous Integration (CI) and Continuous Delivery (CD) are increasingly widespread throughout the technology sector. As large engineering organizations adopt CI/CD they are often met with scalability challenges. What works for small teams has not proven to work for large teams. This workshop invites practitioners and academics to come together and informally discuss the challenges and opportunities in build, test, and release automation.
This workshop is held as part of ICST 2021 and will be a virtual event. For details see the main ICST website: https://icst2021.icmc.usp.br/
Presentations (20 minutes + 5 minutes for questions)
Panel Discussion
Abstracts for 20 minutes presentations. Abstracts must not exceed 1000 words.
Submission via Easy Chair: https://easychair.org/conferences/?conf=cciw2021
See also: https://conf.researchr.org/track/cciw-2021/cciw-2021-ci-cd-industry-workshop
Large Scale Continuous Integration and/or Continuous Delivery
Flaky Tests and Non-Determinism
Managing Flaky Tests in CI/CD
CI/CD for Machine Learning Systems
CI/CD for hybrid and multi-cloud
Key Metrics for CI
CI Dashboard
Test Selection for CI
Mutation Testing for CI
Test Result Prediction
CI/CD Maturity Models
Security Measures for CI/CD
CI/CD for Kubernetes
Future Evolution of CI/CD
Move beyond PASS or FAIL (in the context of CI)
Optimization Techniques for CI/CD
Automatic Recovery for Build and Test Breakages
Multi Environment Deployment with CI/CD
Culprit Finding and Fault Localization (in the context of CI)
Prevention of Breakages in the trunk/main branch
Emergency Response using CI/CD
Using CI/CD with a Monorepo
Using CI/CD with Many Small Collaborating Repositories
Version Management in CI/CD
Dependency Management and Upgrades with CI/CD
Submission of Abstracts: March 20, 2021 (by midnight AOE)
Notification of Acceptance: Apr 02, 2021
Workshop date: Apr 16, 2021
A small Program Committee (PC) will be assembled to review the submitted abstracts. The review process will be a single blind process as we expect that abstracts may reveal the presenter’s corporation, industry, or organization. Each abstract will be reviewed by 3 PC members and rated. The chairs of the PC will then make a final determination on the program for the workshop. The submitters of the rejected abstracts will be strongly encouraged to attend the workshop. All abstracts will receive written feedback and an overall rating along with the committee’s decision.
Given the brevity of the abstracts, the PC may feel it needs more details during the selection process. If so, a PC Chair will contact the author asking for clarifications or elaborations and provide those back to the reviewers.
Tim A. D. Henderson, Google (Build, Test, Release), Sunnyvale, California, tim DOT tadh AT google's email service
John Micco, VMWare, Palo Alto, California, john DOT micco AT google's email service
Raja Balusamy, Samsung R&D Institute India, rajasamsung2021 AT google's email service