Operations | Monitoring | ITSM | DevOps | Cloud

At JFrog, we’ve seen DevOps and DevSecOps adoption growing robustly in Asia-Pacific (APAC), as the region’s large enterprises recognize the competitive advantage and importance of DevOps and digital transformation. In fact, by 2025, up to 25% of Asia’s 500 largest companies will become software producers to digitally transform and maintain their A500 status, IDC predicts1.

These days many setups have a lot of redundancy and you may not want to send notifications during the night, just because one of multiple http servers has a problem. This blog post will show you how to setup a single service with a state combining multiple other services.

On April 15th Moogsoft’s VP Marketing, John Haley, welcomed Datadog Product Manager, Alex Vetras, along with DevOps Institute Chief Ambassador, Helen Beal, and Moogsoft’s CTO, Dave Casper, for an informal roundtable exploring how users can now see rich-context incidents from across the full stack in minutes, and the opportunities this presents to organizations.

While PR analysis within Code Insights and Snyk Pipes are available to use right now, we're rolling out a native Security tab in Bitbucket Cloud. This will be a gradual rollout through the month of May so watch out for it in the left nav. We look forward to your feedback. Even small vulnerabilities can cost a team a lot. All too frequently we see news reports of organisations that mishandled their code & build level security, causing customer data to be exposed.

JFrog and PagerDuty have deepened their technology integration to further boost IT operators’ and developers’ visibility into the software development lifecycle and accelerate incident resolution. The latest integration, which involves the JFrog Pipelines DevOps pipeline automation solution, simplifies and streamlines how to identify faulty builds that impact production environments.

Creating robust, manageable, and reusable functionality is a big part of my job as a CI/CD engineer. Recently, I wrote about managing reusable pipeline configuration by adopting and implementing pipeline variables within pipeline configuration files. As I showed in that tutorial, pipeline variables and orbs have added some flexibility to this process, but they are still a bit limited.

With the new release of dynamic config via setup workflows, CircleCI customers can now use jobs and workflows, not only to execute work but to determine the work they want to run. We built dynamic config because we know our users want more dynamism in the CircleCI build process. Historically, our platform has been very deterministic: the config is pre-set in a file based on the revision for a given pipeline.