This is automated by build_and_deploy_adapter Jenkins job. Once the Jenkins job is successfully completed, MF deployment can be seen from the ICP deployments dashboard, as shown in the screenshot.Īfter MF is deployed on ICP, adapters can be built and deployed on MF for testing the changes. The complete script is available in the attachment. The script uses the helm commands to deploy MF Server and Analytics Server on ICP. The screenshot of the script that perform the deployment of MF on ICP is shown below. The parameters are used internally in the scripts that automate the job. The scripts for deploying MF on ICP requires details of the ICP cluster and DB credentials (in this pipeline we use DB2 as the database), which can be provided as parameters for the Jenkins jobs. The source code for apps and adapters is publically available in the git repo. If you don’t require to test the app and adapter changes on a new deployment of MF on ICP, you can skip this job from the pipeline. You can choose to test the changes on a fresh MF deployment by configuring the deploy_mfp_on_ICP job to listen to the changes in the source repository. You can configure Jenkins jobs in such a way that whenever an app or adapter change is committed to the git repository, a job can be kicked-off. The jobs can be linked together to create an end-to-end devops pipeline. Once the build machine is set up, which is a one-time activity, the other jobs can be run. A snapshot of the script for the same is shown below The scripts for setting up the build machine can be found in the attachment. These command line tools are needed for running the rest of the jobs in the pipeline such as building apps and adapters and testing them. The jobs install IBM Cloud CLI (Bluemix CLI), IBM Cloud Private Command Line, Helm Command Line, NodeJS, Maven, MFP Dev CLI, and Android SDK. The job needs to be run only once on the build machine. These jobs install all the prerequisite software required to run the Jenkins jobs. Setting up the Jenkins build machineĪs mentioned earlier, we will be using Jenkins that is installed locally for running Jenkins job. We will now discuss each of these jobs in detail. The Jenkins job that is used for creating DevOps pipeline for MF on ICP is shown below. It is hence recommended to have locally installed Jenkins server and client, which can connect to the ICP running on your data center. This may have a performance impact on the execution of jobs. ICP provides helm charts for Jenkins deployments that you could use to build the DevOps pipeline, but ICP may run the Jenkins job on a new pod each time a job is run, and that would require every job to have the scripts to install the prerequisite software such as mfpdev command line, maven, helm etc., which is required to run the job. This blog post assumes that Jenkins is installed locally within the organization’s intranet. The DevOps pipeline that is described in this blog is built by using Jenkins. This blog post assumes that you have already set up IBM Cloud Private and loaded the IBM Mobile Foundation Passport Advantage Archive on ICP. In a continuous build and test automation pipeline, the job execution can start with a fresh deployment of Mobile Foundation on ICP and then do the building of apps and adapter and subsequently register it with Mobile Foundation Server running on ICP followed by testing both apps and adapter and finally tearing down the Mobile Foundation deployment on ICP. The jobs can be configured in such a way that whenever developers commit a code change to a git repository, the pipeline automatically gets triggered to execute some of the Jenkins jobs. The Jenkins jobs use the combination of ICP, Helm and mfpdev command line to automate the different stages/jobs in the pipeline. In this blog post, we will walk you through the steps of creating a DevOps pipeline for Mobile Foundation on ICP using Jenkins. For Mobile Foundation on ICP, the tasks such as deploying Mobile Foundation (MF) on ICP, building and deploying apps and adapters to MF on ICP, testing apps and adapters, and deleting and updating the Mobile Foundation deployments on ICP needs to be automated. The DevOps pipeline for Mobile Foundation on IBM Cloud Private helps in automating tasks that are required to set up a continuous delivery of mobile apps. DevOps is a practice used by enterprises for faster delivery of software and to improve the time taken for go to market.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |