Hi Ruddraksh,

Many of your questions are answered in the official OutSystems documentation:

• https://success.outsystems.com/documentation/how_to_guides/devops/how_to_build_an_outsystems_continuous_delivery_pipeline/
• https://success.outsystems.com/documentation/best_practices/lifecycle/application_lifecycle_management_in_outsystems_ci/cd/

The link on the first bullet also points to a Jenkins Github repository called: Building an OutSystems pipeline with Jenkins with the templates you can use as a starting point.

If you use BDD Framework for unit testing, it contains an API that you can call from the Jenkins pipeline.

If you google you find multiple recorded sessions of expert explaining how you can implement CI/CD for OutSystems using Jenkins.

-- Daniel

Hello Daniel,
For the first and the third questions, I am still not clear from the documentation. Can you please guide me on that also Can you please refer some of the recorded session which i can refer ?
Thanks in advance.

1. How can we include Dependency Modules/Applications in the Jenkins Pipeline?

2. What are the different ways for Acceptance testing before going to the STAGING environment?

3. How can we set the site properties in the Jenkins pipeline, as it is required to set them after each environment deployment?

Hi Rudraksh,

1. We use https://www.outsystems.com/forge/component-overview/5670/trigger-pipeline-o11, the documentation of this forge component has some useful information and links.
   
   
2. Acceptance testing is normally done by end-user/key-user or customer and a manual process. Only after a formal acceptance of the new version of your apps in Acceptance, you want to continue the pipeline to deploy to Pre-production and then Production. You can include this decision in your Jenkins pipeline, by asking letting the responsible person to confirm that the acceptance testing is completed successfully.
   
   
3. Normally you set the site properties for an environment only once, on the first publish. Site properties related data is stored in the following OutSystems system's entities:
   
   SiteProperty_Shared is for non multi-tenant site properties, and Site_Property is for multi-tenant values. You could create an OnPublish timer, that would update the site properties once when it is deployed the first time to a target environment.
   The OutSystems LifeTime API unfortunately has no feature to set site property values on deploy.

-- Daniel