A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://docs.oracle.com/en-us/iaas/Content/devops/using/run_pipeline.htm below:

Deploying Applications

  1. Open the navigation menu and click Developer Services. Under DevOps, click Projects.
  2. On the DevOps Projects page, select a project and a pipeline associated with that project.
  3. Click Run pipeline.
  4. Accept the default name entered for the deployment, or change it.
  5. (Optional) Select the Enable Dry Run checkbox to preview the difference between Helm chart's current version and the upgrade before deploying.

    With this option, you can see the difference between the upgraded Helm chart and the deployed chart before running the deployment, allowing you to make any changes before deploying the Helm chart. The dry run might pass or fail, the outcome of which is available in the log.

    Note

    This checkbox is applicable only for Helm chart deployment.

  6. Review the defined parameters for the pipeline. You can update the parameter values. For more information, see Configuring Parameters.

    Pipeline parameters can be overridden by stage parameters.

    Note

    The deployment occurs only when the Helm chart is deployed for the first time, or if any updates are detected in the artifact and any other Helm stage parameter. To deploy the Helm chart irrespective of the updates, set the ENFORCE_HELM_DEPLOYMENT parameter to true.

    For a specific Helm deployment stage, you have the option to use OCI_DEVOPS_DEPLOY_USE_CREATE_NAMESPACE_FLAG as a stage parameter override. The parameter can be set to true or false to control the --create-namespace flag when using the helm upgrade command for deploying Helm charts. This parameter operates at the stage level, offering enhanced granularity in the deployment configurations.

  7. (Optional) Define parameters for the specific stages in the pipeline.

    You can override pipeline parameters by stage parameters or add new stage parameters.

  8. Click Start Manual Run.

Deployment progress and status are displayed in the Deployments tab. You can stop a deployment in progress before it completes, by clicking Stop Run. Note the reason for canceling the deployment. Only one deployment can run at a time for a pipeline.

During deployment of the Install Helm chart to Kubernetes cluster orĂ‚ run Helm commands on Kubernetes cluster stage, you have option to cancel the deployment that results in rollback of the stage to the previous state. See Deploying a Helm Artifact.

If the deployment pipeline has an Approval stage, then the deployment waits for the manual approval before completion. Approver can approve or reject the deployment. Reason for approval or rejection must be mentioned. You can rerun completed deployments, see Deployment Rerun. After the deployment completes, you can manually roll back individual stages in the pipeline. For more information, see Rolling Back a Deployment.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4