Oracle Cloud Infrastructure (OCI) DevOps is a continuous integration and continuous delivery (CI/CD) service for development teams building on OCI.
While the CI/CD process streamlines coding development and delivery, it also comes with areas of complexity. When implementing a CI/CD architecture, technology diversity, quality requirements, team skills, cost-benefit of adoption, and product strategy should all influence your decision.
How do you keep consistency across multiple clouds without giving the build system direct access to OCI Kubernetes Engine? Learn how to connect OCI DevOps deployment pipelines to a continuous integration system, such as GitHub Actions, to achieve build consistency despite IaC inconsistencies between clouds.
A deployment strategy should be chosen by considering the trade-offs between the risk of deploying a new release, the impact of the release on users, and the implementation investment. This guide introduces and contrasts canary and blue-green deployment strategies.
Create private code repositories or connect to external code repositories such as GitHub, GitLab, Bitbucket Cloud, Visual Builder Studio, Bitbucket Server, and GitLab Server.
Use pull requests to trigger a build run to deploy the code changes. Merge checks configured in the repository help ensure that the build succeeds without any conflicts.
Create and manage a build pipeline containing the stages that define the build process for successfully compiling, testing, and running software applications before deployment.
Start a deployment pipeline containing different stages for automated deployment based on blue-green, canary, or rolling strategies; each stage is associated with certain actions.
Since OCI DevOps is an OCI native service, identity, security, logging, and more are consistent across Oracle Cloud’s infrastructure, along with preconfigured secure deploys to OCI Compute services.
OCI DevOps works with your existing workflows and tools, such as GitHub, GitLab, and Jenkins. You can also leverage DevOps native code repositories to collaborate and merge code changes using pull requests.
Focus on your code and workflows with concurrent builds that scale to keep developer teams focused on development—and no servers to operate or maintain as you scale.
We’re thrilled to announce the release of the new pull request features with the Oracle Cloud Infrastructure (OCI) DevOps Code Repository. This significant update introduces several critical developer collaboration features, including pull requests, repository forks, and repository insights. Whether you’re developing new application code, enhancing an existing application, or managing infrastructure-as-code (IaC) repositories, having a workflow that allows teams to review new code changes and enforce code quality controls through mandatory approvals is critical for all enterprise customers.
Read the full postSee what’s getting better and more powerful in shipping software in the OCI DevOps release notes.
OCI services are always evolving and improving. We summarize everything that’s new in one place, so you can see how we’re enhancing OCI.
One of the fastest ways to try OCI DevOps—along with Kubernetes or compute instances—is to implement a deployable reference architecture into your trial, pay-as-you-go, or universal credit OCI tenancy.
Interested in learning more about Oracle Cloud Infrastructure? Let one of our experts help.
Oracle offers a Free Tier with no time limits on a selection of services, such as Autonomous Database, Compute, and Storage, as well as US$300 in free credits to try additional cloud services. Get the details and sign up for your free account today.