Presentation used in Hyderabad

1. [ 11th July 2020]: [CI/CD pipeline for Mule Application]
Meetup #14 (Virtual #1)
[Hyderabad-India]

2. All contents © MuleSoft Inc.
Introduction : Organizer, Speaker and You
2We love to hear about you in Meetup

3. All contents © MuleSoft Inc.
Agenda
3
• Introductions
• CI/CD
• Q&A
• What’s next
• Networking time

4. Using Jenkins, GitHub
CI/CD

5. All contents © MuleSoft Inc. 5
• Continuous Integration (CI) is a development practice that requires
developers to integrate code into a shared repository several times
a day. Each check-in is then verified by an automated build,
allowing teams to detect problems early.
• Continuous Delivery (CD) ,which sits on top of Continuous
Integration adds the practice of automating the entire software
release process.
What is CI/CD ?

6. All contents © MuleSoft Inc. 6
• Traditionally, integration is performed in preparation of the
deployment of a new release. This approach can lead to problems, as
integrating multiple or large changes in one go may result in last-
minute conflicts and bugs.
• Continuous Integration (CI) is a solution to the traditional format.
• Detect errors quickly, and locate them more easily.
• Build a solid foundation.
• Stop waiting to find out if your code’s going to work
• Reduce integration problems allowing you to deliver software more
rapidly
Need for CI?

7. All contents © MuleSoft Inc.
Elements in CI/CD
7
Source
(Git)
Build Test Deploy
• Source Stage
• Pipeline run is triggered by a source code repository.
• A change in code triggers a notification to the CI/CD tool, which runs the corresponding
pipeline.
• Automatically scheduled or user-initiated workflows, as well as results of other
pipelines.

8. All contents © MuleSoft Inc. 8
Elements in CI/CD
Source
(Git)
Build Test Deploy
• Build Stage
• Combine the source code and its dependencies to build a runnable instance of our
product that we can potentially ship to our end users.
• All the dependencies are downloaded and packaged into a single deployable artifact in
this stage.
• For Mule it is the Mule Package generated.

9. All contents © MuleSoft Inc.
Elements in CI/CD
Source
(Git)
Build Test Deploy
• Test Stage
• Run automated tests to validate the correctness of our code and the behavior of
product.
• Acts as a safety net that prevents easily reproducible bugs from reaching the end users.
• Essential for this stage to produce feedback to developers quickly, while the problem
space is still fresh in their minds
• Tests can be unit and then integration testing.
• Munit Test cases can be run here for the testing stage.

10. All contents © MuleSoft Inc.
Elements in CI/CD
Source
(Git)
Build Test Deploy
• Deploy Stage
• Once we have a built a runnable instance of our code that has passed all predefined
tests, we’re ready to deploy it.
• Deployment can be done to a Cloudhub or on premise mule runtime.
• The environment depends on the development model.
• For example : Agile: Sprint end QA and Dev build can be triggered.

11. All contents © MuleSoft Inc. 11
A good CI/CD pipeline is fast, reliable and accurate.
• Speed
– How quickly do we get feedback on the correctness of our work?
– How long does it take us to build, test and deploy a simple code commit?
– How quickly can we set up a new pipeline?
• Reliability
– A reliable pipeline always produces the same output for a given input, and with
no oscillations in runtime.
• Accuracy
– Any degree of automation is a positive change. However, the job is not fully
complete until the CI/CD pipeline accurately runs and visualizes the entire
software delivery process.
A good pipeline?

12. All contents © MuleSoft Inc. 12
• Jenkins - an open source Continuous Integration server capable of
orchestrating a chain of actions that help to achieve the Continuous
Integration process (and not only) in an automated fashion.
• GitHub - a Git repository hosting service
• Maven - a powerful project management tool that is based on POM.
It is used for projects build, dependency and documentation.
Demo

13. Open forum discussion
( Demo, Q&A, Quiz )

14. Quiz Time ?

15. All contents © MuleSoft Inc.
What’s next
15
• Share:
– Invite your network to join: https://meetups.mulesoft.com/Hyderabad/
• Feedback:
– Contact your organizers to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
– Your Feedback is catalyst for us
• Our next meetup:
– Date: TBD
– Location: Hyderabad
– Topic: TBD

16. All contents © MuleSoft Inc.
Take a stand !
16
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

17. See you next time
Please send topic suggestions to the organizer

18. Thank You