Migrate drone-builder from Drone to DK CI/CD

[dk-cicd]

Automatic PR to migrate drone-builder steps to DK CI/CD pipelines

This PR marks the initial step in the process of migrating pipelines from Drone to DK CI/CD or self-hosted GitHub Action. It migrates all the drone-builder steps from the Drone configuration file to drone-builder pipelines in the DK CI/CD configuration file. Please check the announcement.

The drone-builder step is responsible for building, pushing, and deploying applications, particularly on Kubernetes.

If you have doubts about configuring the pipelines or whether the project requires the use of self-hosted GitHub Actions, you can reach us in the drone-0 channel via Slack.

The Drone configuration can match the following cases:

1. If it only has pipelines with drone-builder steps, the DK CI/CD configuration should work with few or no adjustments required;
2. If it has pipelines with drone-builder steps and others (e.g., run-node-tests), in this case, you should observe whether there are dependencies between steps. If there are no dependencies, feel free to merge the PR. However, if dependencies exist, reach us in the drone-0 channel via Slack. We will analyze how to resolve your case.

Before merging this PR, it is recommended that you follow these steps:

1. Review the DK CI/CD pipeline configuration, comparing it with the current Drone configuration;
2. Test the pipeline while considering the application's testing environment.

Usage

1. The Drone's promote event is not supported in DK CI/CD. Instead, it has been replaced by pushing tags in the new configuration;
2. The Drone's rollback event is not supported on DK CI/CD. If your project truly requires this event, reach us in the drone-0 channel via Slack;
3. If the Drone pipeline doesn't have the trigger configuration, the DK CI/CD pipeline will be triggered when pushing tags;
4. If your Drone pipeline includes variables in the value definitions, please replace them with actual values. For example, in a Drone configuration, if you have an environment variable ENVIRONMENT: $_{DRONE_DEPLOY_TO}-us, in the DK-CICD configuration, replace $_{DRONE_DEPLOY_TO} with an actual value.

Logs and Results

The results will continue to be delivered as GitHub checks.

To see the logs, click on details and on View more details on DK CI/CD.

You will be redirected to the DK CI/CD Dashboard, and you need to be connected to the VTEX VPN to access it.

To view all the builds from your project, please go to: DK CI/CD Dashboard.