From 63f30a11c691b043075e19a3ebe12c0b257deb74 Mon Sep 17 00:00:00 2001 From: James Denyer Date: Thu, 3 Oct 2024 14:26:18 -0700 Subject: [PATCH] adding bitbucket logo to hub page, fixing some new url paths --- .../continuous-delivery/_index.md | 48 ++++++++++--------- static/logos/tech/ci-cd/bitbucket.svg | 26 ++++++++++ 2 files changed, 52 insertions(+), 22 deletions(-) create mode 100644 static/logos/tech/ci-cd/bitbucket.svg diff --git a/content/docs/iac/packages-and-automation/continuous-delivery/_index.md b/content/docs/iac/packages-and-automation/continuous-delivery/_index.md index 4ac67adb703a..ce99a81626f0 100644 --- a/content/docs/iac/packages-and-automation/continuous-delivery/_index.md +++ b/content/docs/iac/packages-and-automation/continuous-delivery/_index.md @@ -27,44 +27,44 @@ process that you have today. For example, doing code reviews via Pull Requests, analysis tools, and running unit and integration tests as appropriate. It all "just works" for your cloud infrastructure the same way it would for your application code. -Pulumi can easily integrate into any continuous integration/continuous delivery (CI/CD) system. If your CI/CD system isn't listed below or you are testing something new, see [adding support for CI/CD systems](/docs/using-pulumi/continuous-delivery/add-support-for-cicd-systems). +Pulumi can easily integrate into any continuous integration/continuous delivery (CI/CD) system. If your CI/CD system isn't listed below, or you are testing something new, see [adding support for CI/CD systems](/docs/iac/packages-and-automation/add-support-for-cicd-systems). -> Looking to troubleshoot failures related to running Pulumi in CI/CD? Check out our [CI/CD troubleshooting guide](/docs/using-pulumi/continuous-delivery/troubleshooting-guide). +> Looking to troubleshoot failures related to running Pulumi in CI/CD? Check out our [CI/CD troubleshooting guide](/docs/iac/packages-and-automation/troubleshooting-guide).
- + AWS Code Services

AWS Code Services

 - + Azure DevOps

Azure DevOps

 - + CircleCI

CircleCI

 - + Codefresh

Codefresh

 - + GitHub Actions

GitHub Actions

 - + GitLab CI

GitLab CI

 - + Google Cloud Build

Google Cloud Build

 - + Jenkins

Jenkins

 - + Octopus Deploy

Octopus Deploy

 @@ -72,28 +72,32 @@ Pulumi can easily integrate into any continuous integration/continuous delivery Pulumi Deployments

Pulumi Deployments

- + Pulumi Kubernetes Operator

Pulumi Kubernetes Operator

 - + JetBrains TeamCity

JetBrains TeamCity

 - }}"> + }}"> Spinnaker

Spinnaker

 - + TravisCI

TravisCI

 + + Bitbucket +

Bitbucket

+
> Pulumi can also bridge results from your CI/CD system with GitHub, surfacing the results of stack updates -> on GitHub pull requests. See the [Pulumi GitHub App](/docs/using-pulumi/continuous-delivery/github-app/) for more information. +> on GitHub pull requests. See the [Pulumi GitHub App](/docs/iac/packages-and-automation/continuous-delivery/github-app/) for more information. -### Configuration and Secrets +### Configuration and secrets Pulumi is designed to be entirely code-centric, including the way in which configuration and secrets are managed. Configuration values and secrets are stored safely inside of `Pulumi.yaml` files, which you will commit. @@ -103,18 +107,18 @@ Secret configuration values are encrypted on [app.pulumi.com](https://app.pulumi source code repository. But you can use your own secrets provider, ensuring that only you have access to your sensitive information. See [Managing Secrets with Pulumi](/blog/managing-secrets-with-pulumi/) for more information. -### Managing Complex Environments +### Managing complex environments Most real-world environments are complex. Perhaps you have a networking stack that's independent from your data -and application stacks. Pulumi [supports "stack references"](/docs/guides/organizing-projects-stacks), which +and application stacks. Pulumi [supports "stack references"](/docs/iac/guides/organizing-projects-stacks), which permit one stack to depend upon another. This facilitates continuous delivery and integration at scale. -### Using Branches for Environments +### Using branches for environments Pulumi is agnostic to what sort of branching strategy you take. Most customers use Git-based flows; the most common is -to use one branch-per-[stack](/docs/concepts/stack/). This allows you to control deployments to environments +to use one branch-per-[stack](/docs/iac/concepts/stack/). This allows you to control deployments to environments using your usual commit, code review, and approval process, such as GitHub pull requests. If you are using GitHub pull requests to trigger updates, you will likely want to use the -[Pulumi GitHub App](/docs/using-pulumi/continuous-delivery/github-app/). This gives you interactive infrastructure change previews +[Pulumi GitHub App](/docs/iac/packages-and-automation/github-app/). This gives you interactive infrastructure change previews inside of your Pull Request, making it easier to see, review, and comment on any changes before a deployment occurs. diff --git a/static/logos/tech/ci-cd/bitbucket.svg b/static/logos/tech/ci-cd/bitbucket.svg new file mode 100644 index 000000000000..f179fa7ee596 --- /dev/null +++ b/static/logos/tech/ci-cd/bitbucket.svg @@ -0,0 +1,26 @@ + + + + + + + + + + + + + + + + + + + + + + + + + +