Transcript
This here is gear set pipelines, the evolution of the compare and deploy process. And this is what's used by our larger teams. But it's still underpinned by the same comparison engine, meaning that this is where teams who start with compare and deploy can simply evolve to at a suitable time.
Pipelines provides a visual automated CICD workflow for the deployment of user stories through a Git based release process, providing one single interface for all team members irrespective of their skill set or experience.
Straight away, you'll notice a few things.
Blue boxes represent a user's developer org, and the green boxes represent CICD jobs that will support the automated deployment processes.
I'm sure at Accenture you're working with a mixture of greenfield and brownfield implementation, each on their own DevOps journey with different pipelines configuration.
So Pipelines is totally flexible to match the required environment structure.
So this means then you can use Gearset on a new project where you'll stay involved post delivery or with a brownfield environment where Accenture have been brought in to maybe support or help drive best practices, meeting the customer where they are.
Additionally, especially for larger teams, perhaps with forty, fifty, or a hundred plus users, sandbox groupings enable you to group together particular work streams or projects. And, of course, all of these environments that we can see here are controlled with permissions to control exactly who can do and see what within each environment.
In larger teams and especially with consultancies like yourself, we often hear that you may be working on a project for three, six, nine months, or any extended period. And you might wanna keep this work totally isolated from the main pipeline, but also want to continually iterate on this work until it's ready to release.
Of course then, once that is ready to release, you want to push these stories through the pipeline en masse simultaneously as an immutable block.
So you'll also notice these gray boxes. These are the long term projects where you can create a project or a pipeline within the pipeline.
And this enables you to develop longer term work without the needing to push those changes to production immediately, while also staying on the latest code base.
And this also enables you to track all tickets related to a project in one place and keep this tracking once it's ready for release.
