Trigger Pipeline

Stable Version 2.2.1 (O11)
Also available for 10
Published on 21 Jun by 
OutSystems Pipeline Team
OutSystems Pipeline Team
Created on 12 April 2019

Trigger Pipeline

Available in OutSystems versions:
OutSystems 11

Version 2.2.1

Stable
Current
Application Package
Published on 21 Jun by Rui Mendes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
.NET
What's new
  • Fixed issue when creating triggers for Azure DevOps pipelines.

Version 2.2.0

Stable
Application Package
Published on 18 December 2019 by Rui Mendes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
.NET
What's new

Upgrade to OutSystems 11 based on version 1.2.0

Version 2.1.1

Stable
Application Package
Published on 07 October 2019 by Rui Mendes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
.NET
What's new

Upgrade to OutSystems 11 based on version 1.1.1


IMPORTANT NOTE: From Jenkins version 2.176.3 onward, authentication of requests to Jenkins Remote API using username/password credentials is no longer supported. Instead of the user password you should provide an API token when configuring the 'Pipeline Server Credentials' field.

Version 2.1.0

Stable
Application Package
Published on 03 October 2019 by Rui Mendes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
.NET
What's new

Upgrade to OutSystems 11 based on version 1.1.0

Version 2.0.0

Stable
Application Package
Published on 15 April 2019 by Rui Mendes
Requirements
Platform:
11.0.0.200
Database:
All
Stack:
.NET
What's new

Upgrade to OutSystems 11 based on version 1.0.0

OutSystems 10

Version 1.2.0

Stable
Application Package
Published on 18 December 2019 by Rui Mendes
Requirements
Platform:
10.0.0.402
Database:
All
Stack:
.NET
What's new
  • Modified applications can now be tagged automatically (i.e. on-the-fly) when triggering a pipeline. To activate this feature, Site Property 'Feature_AutoTagging' must be enabled;
  • It is now possible to re-trigger a pipeline by bypassing the check for new application versions. To activate this feature, Site Property 'Feature_ForceTriggerPipeline' must be enabled;
  • Revamped UX in 'Trigger Details' screen and general UI improvements (Kudos to Pedro Cardoso);
  • Improved error messages when invoking the configured pipeline server to trigger a pipeline;
  • Added version number to plugin name label in top-right corner of plugin screens.


NOTE: Since the AutoTagging feature relies on the LifeTime Deployment API, a valid service account token must be provided (as a Site Property) and the correct API endpoint must be specified in the 'Integrations' tab in Service Center.

Version 1.1.1

Stable
Application Package
Published on 07 October 2019 by Rui Mendes
Requirements
Platform:
10.0.0.402
Database:
All
Stack:
.NET
What's new
  • Added Site Property to control if a Jenkins Crumb (i.e. CSRF protection token) should be requested prior to triggering a Jenkins pipeline.


IMPORTANT NOTE: From Jenkins version 2.176.3 onward, authentication of requests to Jenkins Remote API using username/password credentials is no longer supported. Instead of the user password you should provide an API token when configuring the 'Pipeline Server Credentials' field.

Version 1.1.0

Stable
Application Package
Published on 03 October 2019 by Rui Mendes
Requirements
Platform:
10.0.0.402
Database:
All
Stack:
.NET
What's new
  • Support for triggering pipelines in Azure DevOps (including both 'Build' and 'Release' pipeline types);
  • It is now possible to define a default pipeline server configuration, which can be overridden for each trigger configuration.

Version 1.0.1

Stable
Application Package
Published on 27 June 2019 by Rui Mendes
Requirements
Platform:
10.0.0.402
Database:
All
Stack:
.NET
What's new

Re-upload of version 1.0.0 to address IPP issue

Version 1.0.0

Stable
Application Package
Published on 12 April 2019 by Rui Mendes
Requirements
Platform:
10.0.0.402
Database:
All
Stack:
.NET