The new, native Jenkins plugin should lower the barrier to start with Continuous Integration and ABAP but is not a replacement for the existing tools. But I think to get started with Jenkins, ABAP and CI practices, fully scripted or entire based on “Infrastructure as a Code” approaches are not easy start – although they have indiscussable advantages. Related to Jenkins I want to point out two projects – which served also as base for the creation of the native Jenkins plugin – thanks for them to Christian Lechner and Chairat (Par) Onyaem.Īnd of course there is already a Project “Piper” implementation to connect to an ABAP Cloud instance and not to forget the future will bring us with gCTS hopefully a full CI/CD system for the ABAP ecosystem.Īll these tools are more powerful than the actual version of the native abap-ci Jenkins plugin. There are plenty of working solutions to enable Continuous Integration for ABAP. What is the intention of yet another plugin? And here is the link to the actual documentation : Ībap-ci – A native Jenkins Plugin to enable Continuous Integration for ABAP.The installation into an existing Jenkins instance can be done with the integrated plugin manager in the web UI of the Jenkins server or by using the Jenkins CLI install-plugin command.As introduced in my presentation of the SAP Online Track an Open Source native Jenkins Plugin is now also available for ABAP to apply Continuous Integration or Daily/Nighly Build components easily on an ABAP development system. Jenkins is one of the standard tools for Continuous Integration.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |