We requested Drew Piland, product supervisor at CloudBees, how the corporate’s answer helps organizations facilitate duties that must be achieved contained in the CI/CD pipeline. That is what he needed to say:
There are a number of completely different activity varieties: integrations with different instruments, scripts, deployments, and handbook duties. Integration steps will work together with the third-party providers utilizing API calls. Scripts, however, will run on an agent. You may goal a selected agent or a pool of brokers with the required dependencies put in.
Deployment duties will typically run on the goal deployment surroundings, optionally utilizing a utility agent to dump any heavy lifting. And handbook duties will notify the assigned individual of their activity, optionally together with a set of directions. When a activity is run, the info from the occasion is saved and may be referenced from any activity additional within the pipeline. This lets you construct automated workflows based mostly on knowledge between completely different providers.
RELATED CONTENT:
CI/CD pipelines getting wider
A information to CI/CD instruments
You group the duties into levels with entry and exit gates figuring out when the pipeline can run the duties throughout the stage. The gate guidelines can consider knowledge from any activity, such because the outcomes from a safety scan. Or it may be a handbook approval the place a specific individual or group is tasked with approving it.
When you construct your perfect pipeline, it could actually simply be shared and reused by exporting it into DSL code and including it to the self-service catalog. With a service catalog filled with content material, you may present the group with a set of compliant workflows the place anybody with permissions can generate their occasion of a workflow.
