Operations | Monitoring | ITSM | DevOps | Cloud

Managing reusable pipeline configuration with object parameters

CircleCI pipelines are defined in configuration files using the YAML syntax, which has been widely adopted by many software tools and solutions. YAML is a human-readable declarative data structure commonly used in configuration files and in applications where data is being stored or transmitted. The data in pipeline configuration files specifies and controls how workflows and jobs are executed when triggered on the platform.

Become a CI/CD expert with live DevOps training courses

At CircleCI, we’ve worked hard to build on-demand training to help our users get the most out of our platform and its capabilities. Historically, we created CircleCI Academy courses to ensure that all our customers know how to effectively use the features on our platform. Today, we’re taking a proactive approach to enhance your DevOps skills.

The Confident Commit | Episode 6: Architecture meets delivery with Chris Richardson

Rob interviews Chris Richardson on how engineering metrics can help teams evaluate the effectiveness of their architecture. The two discuss how a team's architecture can enable or inhibit their ability to make changes quickly and confidently. How do you balance rapid delivery and finding product-market fit with getting to a stable, workable system over time? Tune in today!

Securing pipelines through secret management

Secrets management plays a critical role in keeping your pipelines and applications secure. While secrets management tools help, you need to implement best practices and processes to successfully manage secrets in a DevOps environment. Standardizing, automating and integrating these processes also helps secure secrets by reducing the chance of human error.

Reducing microservice overhead with shared libraries

It’s a common story: the product team gets early success and grows into a large monolithic code base. While everything is in a single code base, features can be added quickly. This is partly due to the ability to leverage shared code across each feature in the codebase. When your team is adding a new feature, a developer can leverage the existing codebase for needs such as logging or special error handling.