Stable version 2.6.0 (Compatible with OutSystems 11)

Other versions available for 10

Uploaded

on 23 October 2023

OutSystems Lab

5.0

(7 ratings)

Details

LifeTime plugin that triggers a CI/CD pipeline whenever a new changeset is available.

Trigger Pipeline plugin enables you to trigger a CI/CD pipeline hosted in an external server (such as Jenkins) whenever new versions (i.e. tags) are available for your OutSystems applications.

When configuring a new pipeline trigger, you'll need to specify the list of OutSystems applications that will trigger a given CI/CD pipeline whenever new application versions are created in LifeTime.

Main Features:

Configure multiple triggers with different application scopes based on the list of available OutSystems applications;
Applications can be marked as 'Test Applications' (i.e. containing your test code) in the trigger configuration;
CI/CD pipelines can be triggered manually (through the plugin UI) or automatically in a background process;
Dashboard screen shows the current status for each configured pipeline trigger;
Supports triggers for Jenkins and Azure DevOps pipelines.

Notes:

To install a LifeTime plugin please refer to the following guide;
This component is part of a set of resources to accelerate the creation of CI/CD pipelines for OutSystems applications, as described in this Knowledge Base article;
Additional step-by-step documentation explaining how to configure these pipelines from scratch is available in the outsystems-pipeline GitHub repository.

Release notes (2.6.0)

It is now possible to trigger CI/CD pipelines hosted in other pipeline servers besides Jenkins or Azure DevOps by leveraging the new Connector API. To use this feature, a custom connector module must be created by cloning the provided template module 'TriggerPipelineConnector'. To know more about integrating with other pipeline servers, check here;
When configuring a pipeline trigger, it is now possible to specify if the CI/CD pipeline is triggered on a predefined schedule (implemented using timer 'CheckNewVersionsForPipeline'), whenever changes are available;
A new Site Property 'MaxNumberOfApplicationVersions' was created to specify how many versions are shown in each dropdown of the Application Versions table in the 'Trigger Manifest' screen;
Fixed timeout issue when checking user access control permissions in the 'OnSessionStart' action.

License (2.6.0)

BSD-3 license (https://opensource.org/licenses/BSD-3-Clause)

Reviews (6)

2023-09-01

in version 2.5.0

Great job. Please considering new trigger features for GitHub Actions.

2023-05-21

in version 2.5.0

Dear Developers,

I am currently using the Trigger Pipeline plugin for OutSystems and have come across a potential inconsistency I'd like to discuss with you. I have observed that the version value displayed on the Trigger Dashboard differs from the one shown in the Service Center for the same application.

To ensure I understand and can track application modifications effectively, I would appreciate your guidance on how I can associate the Trigger Pipeline data with the metadata from the same application or module within the Service Center.

Looking at the main features of the Trigger Pipeline plugin, it's clear it's designed to trigger a CI/CD pipeline in an external server when new versions or tags become available for the OutSystems applications. This functionality, in theory, should align the data of the trigger pipeline and the Service Center. However, it appears there might be a discrepancy, as noted above.

Could you please advise on the possible reasons for this discrepancy and how I might resolve it? Also, I would appreciate your insight into where and how the data viewed by the Trigger Pipeline is stored.

Thank you in advance for your time and support.

2023-03-29

in version 2.5.0

This is really a nice component. Maybe a little more documentation on how often the "automatically in background process" checks for new versions and how it is possible (should you wish to) disable the automatic deployment and only do it from ADO when the ADO trigger runs.

Team