Are your CI/CD pipelines at risk? They might be if you use long-lived, static credentials and tokens. Long-lived, static credentials and tokens are one of the most common causes of data breaches in cloud environments. CI/CD tools need access to cloud services to publish artifacts, deploy software, and access resources on their cloud provider. So, they need credentials. It's tempting to hard-code them. But that's a bad idea.
To excel in embedded development in 2023, it is essential to have a solid understanding of build systems, continuous integration, and deployment strategies. This workshop by Percepio training partner Jacob Beningo aims to provide a comprehensive primer on these practices, equipping participants with the knowledge and skills necessary to tackle complex firmware projects with confidence.
Software development, the evolution of DevOps has been nothing short of revolutionary. What began as a simple concept has transformed into a best practice that is reshaping the way organisations develop, deploy, and maintain their software. In this blog post, we will take a journey through the evolution of DevOps, from its humble beginnings to its current status as an indispensable part of modern software development.
The benefits of automating deployments for your Java Spring Boot application are undoubtable. Not only is it possible to set up images and run tests or compatibility checks before updating the production environment, but CI/CD providers like CircleCI take a step further by streamlining the entire delivery process from code changes to deployment. Many teams assume that the specifics of their development stack or deployment process will make automation difficult to achieve.
Continuous integration (CI) is the process of integrating changes from multiple contributors to create a single software project. A key component for a smooth CI pipeline is testing. Tests prove that the code does exactly what it says on the tin and that it’s safe to merge the code into the central repository. Tests also anticipate edge cases and ensure that the code handles such cases in a deterministic manner.
DevOps practices in software development have revolutionized the way updates are released. However, many companies entrenched in ITIL practices find it challenging to seamlessly integrate with the DevOps practice of Continuous Integration and Continuous Delivery/Deployment (CI/CD). This is because ITIL focuses on stability, which suits older systems, while DevOps is ideal for modern setups with its agile, automated practices.
When a headhunter reached out to me about the CEO role at Cloudsmith (where I started in August!), one of the first things I did was sign up for a trial account. The product's depth and sophistication really impressed me, and contributed to my decision to go ahead with the interviews. (Glad I did.) They were right; our web interface is still largely a Django web app, tightly coupled to the back end, and you can see the Bootstrap showing everywhere.
Last year we launched the Codefresh delivery platform powered by Argo. After the initial launch we started collecting feedback from all companies that tried it (as well as existing customers) and cataloged all feature requests and implementation ideas. The main goal is always to iterate quickly and address the most common issues in the most efficient way possible.
In the previous article of the series, we explained how to use Configmap generators in order to use Progressive Delivery for your configuration (and not just the container images). In this post, we will also cover another popular question: how to use Argo Rollouts with multiple services. Argo Rollouts is a Kubernetes controller that allows you to perform advanced deployment methods in a Kubernetes cluster. By default, it only supports a single service/application.
