Mastering the power of Git and VS Code on IBM i – A Candid Interview with an Industry Expert
Interview with Sébastien Julliand, full-stack Software Engineer at Arcad Software
Interview with Sébastien Julliand, full-stack Software Engineer at Arcad Software
Discover the hidden potential of RPG Free Form and why it's time to upgrade to modern features and tools for creating cutting-edge business applications!
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.
Whether you are a current Arcad Customer or one just looking to move from your current or nonexistent source control process to one that makes use of Git, then you have found the right blog.
Merlin is a joint solution from IBM and ARCAD to help streamline new next-generation application development on IBM i and automate modernization of existing ones.
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 CodeChecker can step in.
"90% of CIOs have experienced failed or disrupted migration projects, for many and diverse reasons. There is a better way to approach migration of your legacy applications, don’t do it!"
IBM i was born over thirty years ago and has seen many innovations that have kept the platform ahead of the field. With looming staffing changes comes the inherent challenge of closing the knowledge gap and keeping the legacy of IBM i alive and well...
In this article, you'll discover how Arcad dashboards give managers both visibility to their value stream, and the tools to ensure real Application Intelligence.
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.
As databases begin to age, so does their source code, and their purpose may also change. Refitting a database to meet the current needs of business often requires modification to the database at the field level, which can have all kinds of undesirable consequences if it is not executed with the greatest of care.
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 constant challenge for a Chief Information Officer in a transactional, data-heavy industry is leveraging the legacy of their IBM i platform to adapt to current needs, essentially using it to its fullest potential. Keeping that potential tapped translates into a flexible and agile platform, driving growth for your business, an important aspect to keep in mind when approaching the demands of IT.
First let’s answer the question: why modernize your IBM i applications anyway? Well, many IBM i modernization projects don’t start until after a major production failure, so getting out ahead of problems saves you time, pain and resources. Secondly, many IBM i specific skills like RPG or 4GL development are becoming more and more scarce, meaning time could be running out.
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.
A personal and sympathetic view of taking a traditional AS/400 development team to an Agile POD using a fully automated CI/CT/CD DevOps pipeline with Agile methodology on the IBM i, by Adrian Tully
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.
Why test data can be hard to manage, what are the best practices and which tangible benefits you stand to gain from a consistent set of test data?
Similar to GitHub’s relationship with the open source project Git, CloudBees is the company built around the open source project Jenkins.
With the major economic crisis we will face for at least the next twelve months, it is high time to take a fresh look at our existing application assets.
In this article we will examine the importance of unit testing in general and assess how relevant the technique is on IBM i.
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.
Git is still generating an enormous amount of buzz. What are the reasons behind its poularity? Is it really justified? And how relevant is Git in the world of IBM i development?
SonarQube is the de-facto standard code review tool for many modern languages today. But do you need to automate the same continuous quality checking for your RPG code and CL?