Mastering the DevOps Certification: CI/CD, Governance & Monitoring Made Simple
- 1. Mastering the DevOps Certification 1 Helena Lameiro Tech Expert @ Grupo Ageas Portugal OutSystems MVP /hlameiro July 19th, 2025
- 2. Agenda 1. Exam Overview 2. Governance & IT User Management 3. Release Management & CI/CD 4. Test Automation & Strategy 5. Monitoring & Logging
- 3. Exam Overview 3 Perspective of OutSystems Practical Challenges Extended concepts in the scope of Devops
- 4. Exam Tips 4 • Learning Paths and documentation are extensive, but enough. • Having a practical experience is a plus, but not enough. • Sometimes, documentation is redundant (same • Topics are described multiple times in different links). Do not skip it. Some details are only on those links and can be asked in the exam • Bear in mind the scope of what are you reading (CI/CD or standard infrastructure) • Exam English can be tricky. Read carefully your questions.
- 6. Governance 6
- 7. Governance 7 OutSystems Governance model: • Centralization of user/teams/apps permissions • Enable Cross-functional teams’ app cycle independence • Granular and specific permissions for each member of the ream • Promotes ownership and governance
- 8. IT Users Permissions 8 No Access User does not have access to the environment Access Allows logging in, but does not have access to applications List Applications User can see the information about applications(e.g. version) Monitor and Add Dependencies User can reuse public elements of applications, and monitor both applications and environment Open and Debug Applications User can open and debug the applications. Change & Deploy Applications User has all permissions for reusing and monitoring applications, and can also debug, change and deploy applications Full Control The user can create, change & deploy applications, and manage the environment settings (e.g. date format)
- 9. Role Access Definition 9 Environment Based Permissions OutSystems has two built-in roles that allow you to implement a simple security policy: • Developer - By default, this role allows deploying to the Development environment, open applications on Quality Assurance, and list applications on Production. You can change the permissions of the Developer role according to your case. • Administrator - Has full control over all environments and applications. Allows deploying applications to all environments of the infrastructure and manage IT users, security, and environments. You can’t change the permissions of the Administrator role. If these two built-in roles aren't enough to set up your security policies, you can create additional roles to define a more granular policy. Understand the permission model for IT users - OutSystems 11 Documentation
- 10. Team based permissions 10 New Team Add Users to Team Add Apps to Team Configure Role for each User in the team Each team can have: • one or more applications • one or more IT users Users can belong to multiple teams, and have a different role in each team Users in the same team can have different roles for the same application
- 12. IT Users – Fine tuning of Permissions 12
- 13. IT Users – Fine tuning of Permissions 13
- 14. Environments non connected to Lifetime (on prem) 14
- 15. Sample Test questions (I) 15
- 16. Sample Test Questions (II) 16
- 18. Devops & ALM (Application Lifecycle Management) in OutSystems 18 • Fast development with low-code • Easy integration with any external enterprise system • Integrated version control • Embedded build server • Cross-environment deployment • Access control policy • Real-time monitoring • Full extensibility through plugins and APIs https://success.outsystems.com/documentation/11/deploying_apps/devops_and_alm_in_outsystems Managing OutSystems platform and application lifecycle - OutSystems 11 Documentation
- 19. Deploy in OutSystems 19 2 Step deploy What configurations can be set during deploy Deploy zones Deploy under the hood and Impact Analysis Custom Tag Reuse or Abort Deploy Plan What configurations can be set after deploy Deploying apps - OutSystems 11 Documentation Configure application settings after deployment - OutSystems 11 Documentation Configure site properties during deployment - OutSystems 11 Documentation Applying Configurations in Service Center - OutSystems 11 Documentation
- 20. Development and Delivery at Scale in OutSystems 20 Domain Driven Design Team Structure Ownership & Governance Small Batch Approach Trunk-Based dev Patterns Quality Validations Hotfix Strategy Development and delivery at scale - OutSystems 11 Documentation
- 21. Metrics and Release Frequency 21
- 22. Continuous Integration vs Continuous Delivery 22
- 23. CI/CD Pipeline 23 • Development (DEV): primary development environment • Regression (REG): regression test environment • Acceptance (ACC): environment for manual exploratory testing. Promotion to the two environments in the automatic deployment lane requires manual approval. • Pre-Production (PRE): a dry-run environment to rehearse deployment in a production-like environment. If no problems are detected the release candidate is automatically promoted. • Production (PRD): Ready for release How to build an OutSystems continuous delivery pipeline - OutSystems How to Guide
- 24. CI/CD Pipeline – 5 environments 24
- 25. CI/CD Requirements 25 ● Small Batch Approach ● Domain Driven Design ● Develop Applications with Testability in mind (automation) ● Independent Development (Team Governance) ● Lifetime as Application Lifecycle Management ● Trunk-based development – Toggle Feature / API versioning
- 27. CI/CD – setup Jenkins 27 Trigger Pipeline component (Lifetime environment) https://www.outsystems.com/forge/component-overview/5670/trigger-pipeline CI/CD Probe (regression environment) https://www.outsystems.com/forge/component-versions/6528 https://github.com/OutSystems/outsystems-pipeline/wik i/Building-an-OutSystems-pipeline-with-Jenkins https://success.outsystems.com/documentation/11/ reference/outsystems_apis/lifetime_api_v2/
- 28. Sample Test Questions (I) 28
- 29. Sample Test Questions (II) 29
- 31. 31
- 32. Testing Strategy – A Team’s Effort 32 Why do you want to introduce automation? What is your context? What do you want to achieve? 3 Amigos
- 33. Testing Strategy – Advantages 33 ● Faster Feedback ● Reduced business expenses ● Testing efficiency improvement ● Reusability & reliability of automated tests ● Stop repeating boring, error prone manual tasks ● Quality “baked into” the software, instead of covering it at the end
- 34. AgileTesting Strategy – What to automate 34
- 35. Testing Strategy – What to automate 35 Test Suite Canvas Testing Piramid Decision Matrix
- 38. Testing Strategy vs Architecture Components 38
- 40. BDD Framework 40 A Guide To BDD Testing In the OutSystems Low-Code Platform BDD Framework ● Create test scenarios in Gherkin Language (given; when; then notation) ● Enable Test Driven Development ● Enhance Test Maintenance ● Dedicated Data Setup/ Teardown steps
- 41. BDD Framework – Component Test Best Practices 41 Test Code Isolation Reusability and Component test Design Patterns Rule #1: Test Code must be separate from Business Code. Rule #2: Test Code may only reference Business Code used in the context of the application it is testing. Rule #3: Test Code may mirror at most the existing dependencies between Business Code. Rule #4: Business Code does not reference Test Code 1. Screens are Test Suites ● They should contain multiple tests inside 2. Tests are created in isolated webblocks. 3. Do not use exception handlers ● When needed, do not abort the transaction
- 42. Component Tests Anti-Patterns 42 Develop for Testability - OutSystems 11 Documentation Anti-Pattern #1: Validations at the UI Level Only Anti-Pattern #2: Business Logic at the UI Level Anti-Pattern #3: Unsupported Cross-Domain Referencing Anti-Pattern #4: Same API Consumed in Multiple Modules
- 43. Integration Tests 43 •Parameters → Black Box Testing + Boundary Value Analysis •Output → Contract Testing + Schema Validation •Interoperability → Integration Testing + Mock Testing •Security → Penetration Testing + SAST •Errors → Negative Testing + Fault Injection •Data → Data-Driven Testing + Load Testing
- 44. Integration Tests – Mocking API 44 Automated Testing Strategy - OutSystems 11 Documentation
- 45. Sample Test questions (I) 45
- 46. Sample Test Questions (II) 46
- 47. Sample Test Questions (III) 47
- 50. Log Tables & Views 50 For each log type, the database model consists of: • A set of 10 tables, oslog_<TYPE>_0 to oslog_<TYPE>_9 • Two views, oslog_<TYPE> mapped to the current week, and oslog_<TYPE>_Previous mapped to the previous week. Each table has a detail table that stores the log trace. Types of the platform logs Top-level Logs Drill Logs • Screen – one entry in this log maps to an access to a web application or a responsive web application on a mobile device • Integration (of sub-type: exposed) – one entry in this log maps to an access to a web service (SOAP or REST) exposed by the platform • Mobile Request – one entry in this log maps to an access to server-side logic in a mobile web application • Cyclic Job – one entry in this log maps to an execution of a batch job/Timer • Error • General • Integration (of sub-type: consumed) • Extension
- 51. Monitoring in Service Center and Lifetime 51 How to set log level or activate logging in Service Center How to activate performance logs in Lifetime What Kind of logs can be monitored in Service Center What Kind of logs can be monitored in Lifetime Environment Health and Module warning / errors Analytics – Performance Reports Set up of Analytics
- 52. PerformanceMonitoring API 52 To allow you to analyze the user experience of your apps, OutSystems logs request events with valuable data for your analytics. To give you access to request events, the PerformanceMonitoring API provides REST API methods to: • Retrieve a list of request events that occurred in your application • Register your own request-related events
- 53. Sample Test questions (I) 53
- 54. Sample Test Questions (II) 54
- 56. zzzzzzz Thank You!!! 56 Helena Lameiro Tech Expert @ Grupo Ageas Portugal OutSystems MVP /hlameiro
Editor's Notes
- #2: 1. Welcome and Self-Intro 2. Activity for the day (Post Challenge) 3. Technical Session 4. Hackathon Plan 5. Problem Statement 6. Q&A 7. Wrap up & Refreshments