We have all heard about the CI/CD pipeline in DevOps. This is the standard phrase. But what is often left out of this is the CT - the Continuous Testing aspect. Automation of the testing is vital to the success of the CI/CT/CD pipeline and with the Arcad testing suite of tools, we fit right in with the use of automation, regardless of the pipeline used.
When you begin your process to develop a new application or an enhancement to an existing application, one of the areas that is often at the bottom of the list is security. So, this is where Arcad Software’s Code Checker can step in.
With Arcad dashboards, managers can feel in control of their application, getting a full view of the flow metrics essential to understanding how value is constantly moving through the system and where things can be improved.
The twenty-first century is well underway and automation has radically changed nearly every industry across the planet. And this is just as true in the world of DevOps where automation is no longer just another handy tool, but is often the key to whether a business survives or thrives.
When speaking of the IBM i and the lifecycle of application development, it would be easy to stick to the old ways of working. But in today’s world, those old ways just do not cut it. Forward thinking enterprises have massively adopted the Agile and DevOps philosophy.
A practitioner’s guide to easy CI/CD on IBM i with Git (or, why are you waiting?).
I have a question for the IBM i shops out there. What are we waiting for?
Why aren’t we doing DevOps yet? I’m going to suggest that a lot of shops fall into the
“if it ain’t broke, don’t fix it” category. That’s pretty much been the culture of traditional IBM i shops.
Until now, the current change management (CM) tools have dominated the IBM i market providing some elementary versioning of application releases, only ONE version of the source per release. But today the term ‘source control’ - or SCM - has taken on a whole new meaning.
Learn how your IBM i shop can utilize Microsoft’s most powerful development software, aside from perhaps Windows itself. Azure DevOps has existed in some iteration since 2006, but it seems to have hit its stride with the addition of git in 2013.
Imagine being able to branch and merge IBMi code as easily as you do your PHP code. Imagine adopting agile methodologies for native development, builds and deployments. Imagine never having to “check-out” code and jump through those hoops. That’s what Git allows, and it’s really not that hard to accomplish.
Of the world’s most visited websites this month, GitHub rates 59 and climbing. Not bad considering that GitHub’s appeal is limited to software developers whereas the other popular sites like Google and Amazon have a planetary audience. Is software becoming as important as the written word?
IBM continues to encourage greater and more extensive use of open source tools on the IBM i platform. This has helped IBM i become more popular, less “proprietary” and more accessible to young generations of developers. Further, it has opened the platform to a vast software offering produced via the open source model.
I have been fortunate to attend many events and conferences throughout the years, several on an annual basis. These gatherings bring together industry leaders from all over the world to share their expertise and knowledge about the IBMi and open source ecosystems.
When we first heard the term “DevOps” and the buzz it was generating, we asked ourselves whether it was just another case of reinventing the wheel. It’s common in our business that a hot new term signifies an evolution, rather than a revolution. And DevOps is a good example.