Setting up Jenkins is outside of the direct scope of this Integration Guide, and should be seen as a prerequisite for using this integration.

Please refer to this 3rd Party Documentation for information on the installation of a Jenkins pipeline.

Triggering Jenkins builds from ActiveControl

Basis Technologies do not think it is practical to trigger Jenkins builds on pull request in an abapGit environment. However, Jenkins pipelines can be triggered via an URL, as show in below diagram:

Figure: Triggering a Jenkins Build remotely

ActiveControl can call that URL when a task reaches a certain status, triggering an automated build. This is accomplished by our integration framework, using class /BTI/TE_INTEGRATION_CI using a parameter to store the trigger URL within table /BTI/TE_TVARV. More information on this configuration can be found later in this Integration Guide.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment