Operations | Monitoring | ITSM | DevOps | Cloud

CI CD

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

GitOps 2.0 hands-on workshop: Setting up your repositories with ArgoCD and Codefresh

Follow along with Anais as she takes you from setting-up an active ArgoCD installation in your cluster to connecting it with the GitOps Dashboard in Codefresh. We will: By the end of the session, you will have a Codefresh pipeline that will use a standard Git trigger to monitor the GitOps repository for updates using the Codefresh ArgoCD step. Throughout the workshop, we will also highlight GitOps best practices and how you can make the most out of the ArgoCD Codefresh integration.

Code Coverage Analysis Using Codecov and Codefresh

Codecov is a code analysis tool with which users can group, merge, archive, and compare coverage reports. Code coverage describes which lines of code were executed by the test suite and which ones were not. However, this is not to be confused with a testing tool. Codecov does not run your tests, that is the job of your testing tools. The analysis that Codecov provides will classify code in either of the following states: Additionally, In this tutorial, we will.

JFrog CLI Plugin: rt-fs

JFrog CLI Plugins allow enhancing the functionality of JFrog CLI to meet the specific user and organization needs. All public plugins are registered in JFrog CLI's Plugins Registry. The source code of a plugin is maintained as an open source Go project on GitHub. Anyone can develop their own plugin, in Go. This rt-fs plugin runs file system commands in Artifactory. It is designed to mimic the functionality of the Linux/Unix 'ls' and 'cat' commands. Watch this video to see how.

JFrog ChartCenter: How to Include Helm Charts from Source

Learn how you can add your Helm chart to ChartCenter directly from its Git-stored source. ChartCenter will host your Helm repository for you to share it with the world. Until the release of Helm v3, you might have submitted your Helm chart to the official `stable` or `incubator` chart repository to share it with the community. But this Helm chart archive is no longer actively maintained, and is not accepting new charts. Now all Helm charts must be in a hosted repository elsewhere.

All That Developers Need Is a Browser (or How to Be More Productive by Having Less)

What would you say if I would tell you that you can be as productive with the cheapest laptop as with the one you already have? Would you believe me if I would say that there is no need for you to install an IDE, compilers, CLIs, Docker, and whatever else you might have on your laptop? How about having a full development environment created whenever you need it instead of dealing with virtual machines and whatever else might be fulfilling your development needs?

Achieving Continuous Deployment with Artifactory Webhooks & Docker

Continuous Deployment (CD) requires setting up your infrastructure and automation to update your solution with the latest code change from the main branch. That’s what we call “Liquid Software”. Full automation makes your deployment seamless, less error prone, faster and it makes the feedback loop shorter because you can now deploy after each change. Achieving continuous deployment requires the following elements.

DevOps 101: Introduction to CI/CD

When you’re new to an industry, you encounter a lot of new concepts. We tend to use a lot of jargon, the documentation may be written with someone more experienced in mind or rely on contextual knowledge of the rest of the space, and it often doesn’t explain the “why” for the tool. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers.

Manual steps in parallel groups available for Pipelines

Bitbucket Pipelines now allows steps with a manual trigger to be used in parallel groups, satisfying one of the highest voted feature requests. This feature provides more flexibility in Pipelines, allowing teams to configure pipelines with multiple options and then only run the steps they actually need to run, at the time they want. For example you can choose which environments should be deployed for individual developers, giving them different environments to test and do their work.