Hi Nuno,

I don't believe that is the direction OutSystems took for fully implementing automated CI/CD.  OutSystems recognized that many enterprise companies already use tools like Jenkins, AzureDevOps, etc. for CI/CD. So OutSystems made the LifeTime API, to accomodate integration of Lifetime into these tools, which is just the opposite of what you are asking.

https://success.outsystems.com/documentation/11/reference/outsystems_apis/lifetime_api_v2/

Regards,

Daniel

Hi Daniel,

I understand OutSystems rationale, but from a client perspective it doesn't seem very practical. Having a powerful tool like Lifetime, why would I need to add extra expenses and complexity by building a CI/CD pipeline outside OutSystems? 

When evaluating a project's viability, I need to add additional costs and time associated with integrating AI Mentor or a test suite through a separate pipeline. This process can be time-consuming and less efficient compared to simply using the "add button" in Lifetime.

From a sales perspective, this could be a significant selling point. Emphasizing the ease of integration and efficiency of Lifetime's built-in tools can make it more attractive to potential clients.

Regards.

Hi Nuno,

I don't disagree with you, I actually liked your idea.

Just wanted to share my thoughts on what can be expected from OutSystems. 

Hi Nuno Fernandes 

Your suggestion may have some overhead on pipeline but it will take O11 to next level.

Also not sure if ths change will be done in O11 as more focus of OS team is on ODC.

In ODC also this feature will help.

I liked this idea very much