CI/CD Ecosystem

This Self-Service in Port enables automated creation of new Deployment IDs, environments, and environment variables for deployments in Cloudbees (Jenkins). Through a form, users can configure the Deployment ID, create the environment, and define the required variables, eliminating the need to hardcode data in the code or pipeline.

The implementation centralizes deployment management, offering full visibility into the configurations used, organized by team and project, facilitating centralized control and effective tracking. It also integrates real-time metrics that allow monitoring and optimizing the deployment process.

This solution streamlines and standardizes the deployment process, reducing configuration times and minimizing errors, while ensuring compliance with security and governance standards in the cloud.

To understand how variable configuration works, it should be clarified that we have 3 entities:

info

• Resource Deployment ID
  Unique identifier associated with an IT Element. An IT Element can have more than one.
• Environments
  By default DEV / GLOBAL / CERT / INTG / PROD exist, but developers can create more custom environments to have different ephemeral environments and run their tests.
  Since environments are ephemeral, they can be created or deleted at any time by developers.
• Variables
  Variables associated with the pipeline being executed. E.g.: project_id, endpoint.url, cluster_name.