The Open Source ABAP Continuous Integration (abapCI) plugin for Eclipse is now available in Plug and Play mode (since version 0.4.0). That means, after installation over the Eclipse marketplace there is no configuration needed anymore to get the plugin up and running.
This Plug and Play mode is made possible by reusing the existing connectivity and CI functions of the ABAP Development Tools for SAP NetWeaver. A short summary and description for the AbapCI Plugin can be found in the Github repository – readme.md. (this will be extended and improved continuously – hopefully 🙂 )
Also there are some improvements in the usability of the plugin that hopefully meet the two main purposes of the plugin: save development time and provide immediate feedback.
Some time ago I was also asked to expand the functionality of the ABAP CI plugin to support more than one development project. Starting with the version released today, this feature is finally available.
Unit Testruns for more than one development project
By adding this feature to the plugin the introduction of a completely different data persistence model was necessary. I skipped the implementation of a migration from the old model to the new one and instead invested more time into the usability, especially the management of the Unit Testrun packages. Hopefully this new features outweight the lack of the migration.
Now there are three methods available to add ABAP packages to the Continuous Unit Testrun:
- manually within the view ABAP Continuous Integration
- with the Projects Explorer context menu item “Add to CI run”
- or automatically when an ABAP class of a not yet configured package is activated
More details can be found in the documentation.
There are some further features like a hyperlink to the failed Unit Tests in the ABAP CI Dashboard. This link opens automatically the corresponding ABAP class for the failed test by calling an ADT feature.