All the code has been factorized in a Jenkins Shared Library and can be reused in all your pipelines.To help the Jenkins Pipeline writer, the community around Red Hat Integration came up with a Jenkins Shared Library named 3scale-toolbox-jenkins. Introducing the Toolbox Jenkins Shared Library There is nothing hard or complicated with those improvements that's the daily bread of every Jenkins Pipeline writer! The "runToolbox" helper method has not been designed to handle multiple parallel runs of the 3scale toolbox.To match most companies' security policies, we would need to generate those test credentials dynamically. A "manifest" would separate the code from the configuration. Everything is hardcoded: if we need to change some API metadata, the Pipeline code needs to be updated.There are several delays used in the "runToolbox" method and tuning those delays proved to be tricky.The "runToolbox" helper method was duplicated in each pipeline.To support production workloads, however, some minor aspects need to be improved: What needs to be improvedĪlthough it was not perfect, the pipeline we designed in the previous article was simple and self-contained. In this article, we will improve the pipeline from the previous article to make it more robust, less verbose, and also offer more features by using the 3scale toolbox Jenkins Shared Library. In the previous article of this series, Deploy your API from a Jenkins Pipeline, we discovered how the 3scale toolbox can help you deploy your API from a Jenkins Pipeline on Red Hat OpenShift/Kubernetes.
0 kommentar(er)
