Automating Your Way to Greatness by Combining OutSystems CI/CD with the Power of Jenkins and Azure
•Download as PPTX, PDF•
3 likes•406 views
Having built-in CI/CD capabilities has always been a core tenet of the OutSystems platform. As customer factories have grown and CI/CD pipelines have become more complex, OutSystems has developed an integration with some of the leading CI/CD DevOps tools in the market, Jenkins, and Azure DevOps to tackle some of the challenges of managing enterprise-grade CI/CD pipelines.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Automating Your Way to Greatness by Combining OutSystems CI/CD with the Power of Jenkins and Azure
Similar to Automating Your Way to Greatness by Combining OutSystems CI/CD with the Power of Jenkins and Azure (20)
More from OutSystems
More from OutSystems (20)
Recently uploaded
Recently uploaded (20)
Automating Your Way to Greatness by Combining OutSystems CI/CD with the Power of Jenkins and Azure
- 1. | Combining OutSystems CI/CD with the power of Jenkins and Azure Automating Your Way to Greatness Combining OutSystems CI/CD with the power of Jenkins and Azure
- 2. | Measure Customer Experience of Your OutSystems Web and Mobile Applications| Measure Customer Experience of Your OutSystems Web and Mobile Applications Mark Burns Director Product Management | OutSystems @ in mark.burns@outsystems.com https://www.linkedin.com/in/mark-burns-b2272b3/
- 3. | Combining OutSystems CI/CD with the power of Jenkins and Azure Goals of Today’s Session ● How to set up a fully automated OutSystems pipeline with Jenkins and/or Azure DevOps ● Benefits for Developers and DevOps Engineers
- 4. | Combining OutSystems CI/CD with the power of Jenkins and Azure An open platform with No Limits!
- 5. | Combining OutSystems CI/CD with the power of Jenkins and Azure Open to be extended to other CI/CD platforms Jenkins, Azure DevOps, TeamCity...
- 6. | Combining OutSystems CI/CD with the power of Jenkins and Azure Combine the best of both worlds...
- 7. | Combining OutSystems CI/CD with the power of Jenkins and Azure Hi, I completed a story before and tagged and triggered the pipeline. Let’s see how it went in Jenkins.
- 8. | Measure Customer Experience of Your OutSystems Web and Mobile Applications What tools do you use for CI/CD automation? ● Jenkins ● Azure DevOps ● Bamboo ● GoCD ● TeamCity ● Travis CI ● CircleCI ● Other
- 9. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Combining OutSystems CI/CD with the power of Jenkins and Azure How it works
- 10. | Combining OutSystems CI/CD with the power of Jenkins and Azure OutSystems LifeTime LifeTime APIs Jenkins / Azure DevOps pipeline Python package Git Pipeline as Code Dev Regression Acceptance Pre-Prod Production Trigger Pipeline CI/CD probe
- 11. | Combining OutSystems CI/CD with the power of Jenkins and Azure Developer’s day in life... Responsible for: ● Cases application ● Write automated tests ● Tests passing in regression ● Fix code
- 12. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Change session name in master slide Demo
- 13. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Combining OutSystems CI/CD with the power of Jenkins and Azure Behind the scenes
- 14. | Combining OutSystems CI/CD with the power of Jenkins and Azure OutSystems LifeTime LifeTime APIs Jenkins pipeline Python package Git “Cases” Pipeline as Code Dev Reg Acc PPrd Prd Trigger Pipeline “Cases” Pipeline CI/CD probe
- 15. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Combining OutSystems CI/CD with the power of Jenkins and Azure How to set up
- 16. | Combining OutSystems CI/CD with the power of Jenkins and Azure DevOps Engineer day in life... Responsibilities: ● Enables the CI/CD process ● Ensure delivery process is followed and so automated ● Approve new versions to production
- 17. | Combining OutSystems CI/CD with the power of Jenkins and Azure Hi! Let me show you how to set up a new pipeline using Jenkins!
- 18. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Combining OutSystems CI/CD with the power of Jenkins and Azure Set up a Jenkins pipeline
- 19. | Combining OutSystems CI/CD with the power of Jenkins and Azure Building an OutSystems pipeline with Jenkins All the steps and resources available in github.com/OutSystems/out systems-pipeline/
- 20. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Change session name in master slide Demo
- 21. | Combining OutSystems CI/CD with the power of Jenkins and Azure Hi, Seems that I have a new version of Cases app to approve...
- 22. | Combining OutSystems CI/CD with the power of Jenkins and Azure Hi again! Let me show you how you can do it with Azure DevOps...
- 23. | Combining OutSystems CI/CD with the power of Jenkins and Azure| Combining OutSystems CI/CD with the power of Jenkins and Azure Set up an Azure DevOps pipeline
- 24. | Combining OutSystems CI/CD with the power of Jenkins and Azure Building an OutSystems pipeline with Azure DevOps All the steps and resources available in github.com/OutSystems/ outsystems-pipeline/
- 25. | Combining OutSystems CI/CD with the power of Jenkins and Azure OutSystems setup for Azure DevOps ● LifeTime Service Account ● CI/CD probe in regression ● LifeTime Trigger pipeline plugin
- 26. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps setup ● Azure Pipelines self- hosted agent in default pool
- 27. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps setup ● Create a Variable Group
- 28. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Build Pipeline Dev Reg Acc PPrd Prd CI/CD probe Build
- 29. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Build Pipeline ● Get the Pipeline from a repository
- 30. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Build Pipeline ● Use YAML file ● Example provided in github.com/OutSystems/ outsystems-pipeline/
- 31. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Build Pipeline ● Link to the variables group
- 32. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline Dev Reg Acc PPrd Prd CI/CD probe Build Release
- 33. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline ● Import a task group ● Available in github.com/OutSyst ems/outsystems- pipeline/ (used later in each release stage)
- 34. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline ● Artifact from each build of “Cases-Build- Pipeline”
- 35. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline ● Create the Acceptance stage ● Use and configure the imported task group
- 36. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline ● Clone the “Acceptance” stage for Pre- Production and Production ● Set the configurations for the new stages.
- 37. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline Add an approver after the Acceptance stage
- 38. | Combining OutSystems CI/CD with the power of Jenkins and Azure Azure DevOps: Create the Release Pipeline Done!
- 39. | Combining OutSystems CI/CD with the power of Jenkins and Azure OutSystems + Azure DevOps: Some Runs...
- 40. | Combining OutSystems CI/CD with the power of Jenkins and Azure Does the Cases new version reached Production?
- 41. | Combining OutSystems CI/CD with the power of Jenkins and Azure Summary ● How to integrate the OutSystems CI/CD with Jenkins and Azure DevOps ● Benefits for a Developer and DevOps Engineer
- 42. | Combining OutSystems CI/CD with the power of Jenkins and Azure Try It Give Feedback Contribute
- 43. | Combining OutSystems CI/CD with the power of Jenkins and Azure Thank You! @ injoao.bento@outsystems.com /joaofernandesbento
- 44. | Combining OutSystems CI/CD with the power of Jenkins and Azure Automating Your Way to Greatness Combining OutSystems CI/CD with the power of Jenkins and Azure
Editor's Notes
- [2min]
- [2 min] Introduce yourself
- [2min]
- (1min) It is open to be extended to any CI/CD platform. Today, you will see how to integrate it with Jenkins and Azure DevOps, but can be with TeamCity or other.
- [5 min] Before this presentation, as a developer, I completed a new user story, created the automated tests, and triggered the automatic deployment to the regression environment for testing. Let me check the status of the pipeline, oh God, it failed. Let me fix it in development. Open cases app and fix the code to change the status to Discarded instead of Closed. Click 1-click publish and return to LifeTime to tag; than trigger the pipeline (for demo purpose I am triggering manually but you can set up a timer to run it automatically after a tag)
- [5 min] Here you’re seeing the typical stages of a CI/CD pipeline. I will explain later what happens on each stage. click All of these stages are managed by LifeTime. LifeTime has a set of APIs which enables you to integrate with any CI/CD tool. click On top of those APIs we are promoting and open-source package in Python which accelerates this integration. So you don’t have to start learning how to call and orchestrate those LifeTime APIs. click Since it is in python, it can be used in any Operating System and any CI/CD automation tool as Jenkins, Azure, TeamCity, Bamboo, GoCD... click We are also providing some pipeline templates for Jenkins and Azure, so you can easily import them. Not only saves you time to set up but also you will be following a good practice by having the pipeline in a source control as code. So far so good? Two extra things you should know before I jump into the demo. click 1) How to trigger the pipeline? In the traditional development you have a commit or a pull request that triggers the pipeline. In OutSystems, the developers implement story of the backlog in the development environment, and click 1-CP everytime then want to see if it is ok. In moment that a developer believes the story is done, he goes to the LifeTime and tags the application with the version number. That procedure will trigger the pipeline. How? We have a “Trigger pipeline” plugin which you install in LifeTime, it will trigger the Jenkins or Azure Devops pipeline after the tagging. click 2) Last thing you should know, for CI purpose the developer needs to automate tests. Here we recommend you to do Behaviour-Driven Development tests. It can be done with the BDD framework available on forge <To understand how you can create those tests, there is a lab about “Testing With OutSystems” at 3:30pm> In order to dynamically find the tests to run for your pipeline you need to install the CI/CD probe in the regression environment, this component is also available on forge.
- [2 min] Let’s move to the demo I’m a developer now and I’m responsible for the application “Cases”. I implement also the automated test which should run in regression phase. So I also keep the regression step green and fix code if needed.
- 25 min so far
- [4 min] As a developer I fixed the code and published it in Dev. Then I went to Lifetime and I tagged cases app and triggered the pipeline Now, what is happening: The trigger pipeline plugin triggers the cases pipeline Since it have it define as code in Git, the Jenkins will fetch this pipeline template The pipeline is installed and will run the step defined using the python package as support to orchestrate the LifeTime API So the first step will be deploying the new cases version in Regression Then run the regression suite and get the results If it is ok, it will deploy in Acceptance (also called QA). Here your testers, PO or a Biz representative will validate the new features and will eventually accept this new release If that happens this new version will reach production but first a deployment dry-run happens in Pre-Production, an environment which mimics the production environment And that’s it
- 30min so far
- [2 min] Now I’m a DevOps Engineer, and I’m responsible for: Enable a CI/CD process Ensure the delivery process is followed, so the best way to do it is by automating it. Approve new versions to be deployed in production according to Product Owner instruction (it can be the Product Owner or other Biz Representative directly)
- [10 min] Switch to Live configuration and have back up slides: The components required: 1. I need to install the CI/CD probe in the regression environment. This component is responsible for interacting with Jenkins to execute the tests and return the results. 2. I need to install the Trigger Pipeline component from Forge which allows you to set up the triggers which each unique pipeline that exists in your factory. 3. I will configure the Cases pipeline. 4. I will create a LifeTime service account. 5. Now, I am ready for Jenkins. I install pre-reqs, set up credentials to interact with LifeTime and I am ready to start creating my pipelines. 6. Here’s an example for my demo setup……. Continue, continue.
- 30min so far
- All the steps and resources are available in this GitHub repository. (It is currently available as read-only but you can leave your feedback and we will later open it for contributions.)
- [3 min] My Product Owner told me there is a new version of cases app to be promoted to Production…. (go to Jenkins) Yes the the regression tests have passed, the PO might have checked this version in acceptance environment and it is ready to be deployed to prod. All looks good and I am going to deploy to Prod.
- [4 min] Let me now briefly show you how you can set up the same pipeline in Azure DevOps.
- 30min so far
- Again, all the steps and resources are available in this GitHub repository.
- The steps in OutSystems side are similar to Jenkins The service account be used by Azure DevOps The CI/CD probe in regression environment Configure the Trigger Pipeline
- In Azure side, you need to have a self-hosted agent to run each pipeline command. Please follow the Microsoft documentation.
- Create a Variable Group with the list of variables to be used in the context of the pipelines. I named it as “CiCdVarGroup” here. We have here defined the LifeTime Service Account Token for instance and also the environment names.
- In Azure DevOps you need to define the Build part of you pipeline which will create the artifact to be released to production. We defined here the build part as the CI part, so the area that the Developer should be most focused on.
- The build pipeline can be defined as code.
- We provide you an example in YAML that you can use which has the build definition (deploy to regression and run the regression) Put it in your repository and change it to your scenario and then link it here.
- Link the Variable group you defined before to this pipeline.
- Build part is configured now let’s move to release pipeline part which will be trigger every time we have a new artifact passing from the build side.
- Currently the YAML feature is not available for this release pipeline. We hope all that Microsoft will deliver this feature in the future. Meanwhile you can use a task group available in our repository. Import it. It has all the tasks to call the python script to do the deploy on each release stage.
- Define that the release pipeline part will be trigger with the output of Build (if passed in regression tests).
- Create the Acceptance stage using the task group you imported before.
- Clone the Acceptance stage, and configure it for Pre-Production and Production Deploy
- Define the approval step after the Acceptance stage.
- The service account be used by Azure DevOps
- The trigger pipeline
- [3 min] I now return to see that my application has successfully been traversed the pipeline from development to production in 20 min. Summary the progression using a pre-staged set up pipeline results in Jenkins. A failed pipeline in regressions A pipeline which I reject in acceptance before reach production A green pipeline
- 2 min
- 55 min so far