Operations | Monitoring | ITSM | DevOps | Cloud

After getting a taste of DevOps’ benefits, enterprises naturally seek to widen its adoption. However, the tooling and processes that work for small-scale use cases often fall short when teams try to scale DevOps efforts. You must support all your different teams, toolsets, applications, processes, workflows, release cycles and pipelines — both legacy and cloud native.

Choosing a software solution means checking the right boxes, and being “cloud native” has bubbled to the top of most lists. But cloud native is a box built of boxes of its own. For a CI/CD solution like JFrog Pipelines, cloud native starts by being “born in the cloud” to natively execute in, build for, test in, and deploy to cloud computing environments. But what boxes does a CI/CD solution really need to tick to complete that larger cloud native box?

The npm Registry is vulnerable for supply chain impersonation attacks. Make sure you create npm scoped packages and force exclude patterns.

For a complete JFrog DevOps SaaS solution hosted on Azure, the puzzle is now complete. JFrog DevOps Pipelines CI/CD is now available for all JFrog Cloud plan levels hosted on the Microsoft Azure cloud service. With Pipelines automation, now all the key elements of the JFrog DevOps Platform can be hosted on Azure as a SaaS subscription. That includes the Artifactory universal binary repository manager, and Xray software component analysis.

JFrog is making some important changes that will impact users of Bintray, JCenter (part of Bintray), GoCenter, and ChartCenter. Bintray has provided the open source community a free, universal cloud platform for publishing and distributing binaries. Bintray helped JFrog support the Java community as the host of the JCenter repository for Java OSS libraries, packages and components. We launched GoCenter and ChartCenter to extend similar services to the Go and cloud-native communities.

When it comes to securing your software development against open source vulnerabilities, the earlier action occurs — by the right person — the safer you and your enterprise will be. Many IT departments rely on the PagerDuty incident response platform to improve visibility and agility across the organization.

With so many esteemed adversaries competing in the same DevSecOps space, winning the “Best DevSecOps Solution” award feels even more special. We’re very grateful to the community and the DevOps Dozen2 judges who voted for JFrog Xray in this extremely tough category.

Jenkins is the most popular open source CI tool on the market today. Being an early entry into the marketplace, Jenkins popularized CI. Like other CI tools Jenkins empowers developers to automatically build, integrate, and test code as soon as they commit it to the source repository. This allows developers to catch bugs quickly and ultimately deploy much faster.

The path between two clouds ought to be a speedy two-way street. That’s the DevOps pipeline principle behind the JFrog Artifactory App for Jira, which forges a traceable link between your issues in Jira Cloud and your builds in Artifactory on the JFrog DevOps Platform for cloud. Once the app for Jira has been installed you can: The JFrog Artifactory app, now available in Atlassian Marketplace, currently works with JFrog Platform cloud accounts and Atlassian cloud accounts.

Today we’re announcing a big move that will yield substantial, concrete benefits for our customers and for the entire DevOps community: A groundbreaking partnership with Docker that exempts Cloud users of the JFrog Platform from Docker Hub’s image-pull rate limits. This agreement further boosts JFrog’s vibrant ecosystem of integration partners, built on the “too integrated to fail” principle that’s been a pillar of our company since its founding.