If you happened to be in Tel Aviv, Israel last month, you probably saw the eye-catching JFrog billboards that took over the city. The JFrog logo with a solid bright green background challenged all of us to Imagine There’s No Version. The JFrog green billboards were everywhere! Decorating trains and buses and lighting up the city landmarks. The message was clear; it was an invitation to imagine a future where software updates flow like water.
Now that GitHub Actions version 2 is out of Beta and available for general use, how can you start managing your Artifactory repositories in your automated DevOps workflows? Who will save your binaries in distress? Never fear, JFrog is here! A new Action has joined the GitHub Marketplace that enables you to use the JFrog CLI in your GitHub Actions workflows to move your builds through development, test, and release.
Today we are adding native support for DigitalOcean clusters to Codefresh. You could already connect DigitalOcean Clusters as generic clusters in the past (Codefresh works with any cluster that is compliant with the Kubernetes API) but today the process becomes much easier. One of the most important advantages of Codefresh CI/CD is the ability to work with any cloud and git provider.
Today we’re announcing the first-ever solution for live debugging a CI/CD pipeline. You can now place stop/resume breakpoints and inspect live pipelines in the same way that developers debug their applications. It’s the easiest, fastest way to troubleshoot and fix bugs in complex pipelines. Live debugging is very well known to software developers and is one of the most efficient ways to find and fix bugs in application code.
Being innovative is like being handsome. It only counts when others think so. When Bank of America honors you for being innovative and improving how their 30,000 developers perform, it’s a very handsome compliment. At the 11th Bank of America Technology Innovation Summit, JFrog was recognized for industrial leadership and excellence in providing global business solutions. This year, JFrog was one of only two technology companies honored for its strong partnership with the firm.
At JFrog, we think enabling DevSecOps in the cloud should be as easy as ordering from a drive-up window. Getting the tools you need for digital transformation should only be a short stop on your long journey. And you should be able to get it your way, on the cloud services platforms you choose. That’s why we’re excited to announce the availability of JFrog Cloud Pro X on Azure Marketplace.
One of the most well-known problems when it comes to testing applications is the amount of time required by all test suites. Integration tests, in particular, are usually very slow to execute and depending on the type of application, several minutes (or even hours in extreme cases) are needed in order to get the final execution result. You can reduce the test execution time with several techniques, but one of the most effective methods is running your tests in parallel.
What is the bare minimum you need to build, test and run your Java application in Docker container? The recipe: Create a separate Docker image for each step and optimize the way you are running it. I started working with Java in 1998, and for a long time, it was my main programming language. It was a long love–hate relationship. During my work career, I wrote a lot of code in Java. Despite that fact, I don’t think Java is usually the right choice for microservices.
Yalla DevOps made a grand entrance! and for those of you who didn’t make it this time, or those of you who just want a recap, here are the highlights from the event. From an expert panel to a live broadcast by Alan Shimel (Founder, CEO & Editor-In-Chief of DevOps.com), there was a lot going on. The main themes across keynotes and talks were centered around the community, all about introducing change, shifting left and the importance of enhancing people processes.
As compliance managers, we often find ourselves in a struggle. Our responsibility is to uphold compliance standards but in order to achieve this, we need to “sell” the concept to the relevant stakeholders, inter alia the business teams and R&D. We’re put in the position of justifying required changes and processes and are thus mistakenly perceived as business “stoppers” and not enablers.
