TheGuidewire Cloud Platform (GWCP)development lifecycle is built around a modern CI/CD (Continuous Integration/Continuous Delivery) pipeline. This process moves code from a developer's local workstation through various "Planets" (environments) using integrated tools like Bitbucket, TeamCity, and Guidewire Home.
The first step in moving a local change toward production is committing andpushing the code to Bitbucket (Option C). Bitbucket serves as the centralized Git-based source code repository. This action triggers the
"Build" phase of the lifecycle. Once the code is in Bitbucket, the next step involves the CI server,TeamCity.
TeamCity is responsible for compiling the Gosu code, running automated GUnit tests, and performing static code analysis (Quality Gates). While TeamCity is often configured to trigger automatically upon a push, a developer may need to manuallytrigger or monitor the build via Guidewire Home(Option D) if they need immediate feedback or if the automation is set to a specific schedule.
Options such as "Deploying directly to pre-production" (Option A) are impossible in the GWCP model, as code must first pass through the "Dev" planet and satisfy quality gates before being promoted. "Scheduling automated builds" (Option B) is an administrative task, not an initial step for a developer's specific change.
Finally, "creating a star system" (Option E) refers to the infrastructure setup usually handled by Guidewire Cloud operations, not a part of the standard code-change lifecycle. Following the C and D sequence ensures that the code is properly versioned, tested, and validated before it ever reaches a runtime environment.