If you believe you have found a bug or other issue with the Code for IBM i extension, you can post it to the Code for i issue tracker. The maintainers are very good about resolving issues.
Before reporting an issue, though, we recommend checking for (and applying) updates. It is very possible that your issue was already resolved.
(Co-written with Alan Seiden)
Continuous Integration (CI) ensures that every time a developer commits changes to a version control system such as Git, the code is automatically built and subjected to automated tests.
CI has been invaluable to us. As maintainers of PHP’s PDO_IBM and ibm_db2 extensions, we use CI to ensure high quality across platforms.
Platforms supported by PHP’s extensions for Db2 include IBM i, Unix/Linux, and Windows. While our focus is IBM i, we must ensure compatibility with the others. Reliance on manual testing would introduce the risk of broken builds or subtle bugs. Automation is a must.
In this post, we explain how we use CI principles when building and testing PHP’s Db2 extensions.
If recent customer requests for Git training are any indication, this popular, free, open source tool for managing source code is gaining momentum and will soon be mainstream on IBM i.
Standard Git provides source control; GitHub adds collaborative web-based tools that spark discussion and encourage team cooperation.
One of my favorite jobs here at Seiden Group is to introduce developers to the Git version control system. I’ve delivered talks, workshops, and individual Git training.
Fast, popular, and open source, Git can be hosted on varied platforms, such as cloud-based repositories (Github, Bitbucket), internal servers (GitLab), and on our trusty IBM i servers.