MuleSoft Jenkins CI-CD || Fly High Automating Your Build & Deployment

[@champak831]

I lead a team which has many mule devs and I am always on a look out how to enhance my knowledge on Mule (I was once a spring dev ) . I am loving your content . thank you so much Siva .

[@champak831]

By far the best course on Mule available on the internet !!!!! Couple it with the official free mule training course and one is all set to kick start his career in Mule :)

[@not_lightning_god2627]

crystal clear steps I have watched each & every video The thought process is clearly communicated the way it should

[@priyamagesh8750]

I am doing CICD setup using jenkins for Mulesoft applications. There are many applications within a single project. What branching strategy should be used for applications. Should i create a seperate repository for every application or a branch is enough for application. Please advice

[@Expertmusiclounge]

Your videos are clear , precise. Thanks.

[@vk2875]

Thanks Siva, excellent tutorial and detailed explanation.

[@reshmibanerjee8580]

Could you please share the project . I am following the same steps after including all plugins in pom.xml but its not working.. So I want to keep the same setting as you set in your project.

[@afrojpathan1659]

Hi Siva, when I have entered mvn command it got failed error like Deployment failed repository element was not specified in the POM inside distributionManagement element or in -DaltDepolymentRepository=Id::layout::url parameter I have configured all the things as per video but got stuck here

[@giriteja480]

Very good explanation sir...Can you please do more videos on devops tools in mule(Docker, kubernates, Ansible) it will help us.!

[@MrRafaelwars]

help me!! How do I script jenkins to run this command to deployer anypoint-cli runtime-mgr cloudhub-application deploy --bearer ${ACCESS_TOKEN} --organization and to modify anypoint-cli runtime-mgr cloudhub-application modify --bearer $ {ACCESS_TOKEN} --organization I need the command to do this in jenkinsfile

[@manmadha-rl8wz]

Hi Siva, Thanks for the Video, Could you please share the Jenkins.properties file content so that we can try it , in local machine.

[@adishak6095]

Thank you for these videos Siva. They are really helpful.

[@praveenreddy6805]

Hi siva , it was a very good explanation, I have started following your videos thanks for posting this kind of useful information. Ok here i have a query below can you help me on this please In a Continuous Integration/Deployment one of the premises is to deploy the same unmodified binary that is obtained from a repository to all the environments (DEV, QA, PROD, etc) I know that I can use properties to handle environment specific values BUT the properties file is embedded onto the deployable binary (jar file). For on-premise installations I set the to look for the file anywhere on the file system. My question is, how can I achieve the same on a cloud installation? Thanks in advance

[@sivathankamanee-channel]

Hi Praveen - Thanks for watching my videos. The deployment model is simple. "Build Once - Deploy Many" or "Build Many - Deploy Many". This means, that you can build and create Zip deployment archive and replicate it with varying configurations. Else, you need to build everytime by taking a branch and deploy. For your second question, you can define the environment property into the console such as environment=PROD or environment=QA and you can still point to env specific properties. But in CloudHub, the best practice is to configure env specific properties only in the console and not inside the deployment archive. Hope this helps.

[@sivathankamanee-channel]

Hi Praveen - Sorry for the delay in replying. Yes, you can achieve the same in cloud installation. The strategy we follow in our project is to have all properties under mule-app.properties and promote it with environment specific properties added in the console by admins (usually dev team wont have access to staging or PROD enviornments). This strategy is called "Build Once and Deploy Many". Another one is to have one branch for every environment and do the build and deployment from the branch during the deployment which is called "Build Many and Deploy Many". Each strategy has advantages and disadvantages. For example, branch helps to identify the fix and do the PROD fixes without any worries or reverse commit. On the other hand, using the binary helps assure 100% tested code goes to PROD. Hope these explanations help.

[@praveenreddy6805]

siva thankamanee thanks sir

[@rajeshs287]

Hi Siva, Thanks for putting up this tutorial, quite informative. Is the jenkins deploying mule artifact on the jenkins local server or on cloudhub? how it deployed it back to CloudHub is not very clear.

[@sivathankamanee-channel]

Hi Rajesh - Thanks. You can please note that the Jenkins server retrieves those information from the credentials setup configured in settings.xml. The deploy goal is automatically known to Maven by means of plugin mentioned in the POM file. Please let me know if it is still not clear.

[@TELUGUCOUPLE-USA]

Thanks Siva, it's simple and clear.

[@shanijaiswal]

very good explanation sir!!

[@sivathankamanee-channel]

Thanks Shani !

[@dineshbabu4919]

Excellent Sir keep teaching

[@parthasarathibaidya7540]

This is an excellent video.

[@mhsardar1288]

Can you please explain Hankins.properties file

[@mhsardar1288]

We need one video on custom connector sir please help in this

[@abhisheksinha7328]

Very good video, keep it up

[@syedazamtalat]

Quite good, I was merely wondering if you'd take online classes

[@kalyaniboyapati1785]

Thank you so much for this wonderful video.

[@thedeveloper2513]

Hello siva, could you please share the pom.xml file and the the commands you used in the command line. And thank you for the video.

[@sivathankamanee-channel]

Sure will do.

[@rangraopatil3229]

Good explanation sir...

[@chanderpalsoni8559]

good explanation, very helpful

[@janagty9062]

Hi Siva. its nice video.. Is it possible to share POM file?

[@sivathankamanee-channel]

Hi Jana - The POM file link attached in the description. Thanks for your appreciation !!

[@krishnakishore3976]

Siva Thankamanee, Simple and Sexy video with out extra baggage. Now a days very little people are ready to share the knowledge to world. I appreciate your effort. We have very less data on API Manager, Analytics and Data weave ( Basics and Advanced). Like to see series of videos on this in your style ( with out extra baggage.) of presentation. I have one question, The command you have displayed at 10:07 minutes to build and deploy job, don't we need "mule:deploy" to run the deploy job in "mule" plugin. I got build error for following command 1, command 2 it was success. can you throw some light here. 1) clean install deploy -Danypoint.username= -Danypoint.password= -Danypoint.environment [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project apdev-flights-ws: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter -> [Help 1] 2) Success command clean install mule:deploy -Danypoint.username= -Danypoint.password= -Danypoint.environment Kishore

[@skyhigh9474]

Thank you

[@saeedjilae6370]

Thanks a lot! its very helpful. keep it up! If you have an email or a forum to contact you . i appreciate that

[@saravanalinga]

Thanks u so much 😍