Operations | Monitoring | ITSM | DevOps | Cloud

CI CD

The latest News and Information on Continuous Integration and Development, and related technologies.

Achieving CI Velocity at Tigera using Semaphore

Tigera serves the networking and policy enforcement needs of more than 150,000 Kubernetes clusters across the globe and supports two product lines: open source Calico, and Calico Enterprise. Our development team is constantly running smoke, system, unit, and functional verification tests, as well as all our E2Es for these products. Our CI pipelines form an extremely important aspect of the overall IT infrastructure and enable us to test our products and catch bugs before release.

Implementing infrastructure as code with Ansible

If you’re here, it means that your application is a hit, coming through a long way of development and deployments. Your application is finally in a stage where you or your team need to set up more servers than you can handle manually, and you have to provision them fast. There’s also the need to make sure that all of them have the same configuration, packages, and versions in order for your application to have the same behavior in all of them.

Are you on top of newly introduced errors in your CI/CD releases?

Log files are infamous for being “noisy”. Without the right management solution, trying to find a specific piece of information or using them to reproduce a critical error is a complex undertaking. If you’re working with CI/CD, how do you attribute new errors to a particular release? How do you investigate those errors and make sure that your customers aren’t being impacted? Faster releases mean shorter development and testing cycles before new code reaches production.

Track, Debug, and Fix Errors with Sleuth and Sentry

Developer teams shipping software frequently are in a constant state of change. Understanding the state of their code at a given point of time is sometimes clear as mud. The Sentry | Sleuth integration is focused on helping developers automate the annoyances of deploying software, tracking the health of a release, and providing clarity on how to resolve critical code issues.

How FireHydrant's CI/CD infrastructure fixes bugs faster

Almost everyone knows that working with third-party APIs can be challenging. Sometimes the errors happen unexpectedly. Sometimes the error information that you receive is inaccurate. While most people feel these pains acutely, I’d like to share how we answer these challenges at FireHydrant and how it’s helped us avoid headaches and stress.