• 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.

• Added new 'Pipeline Parameters' section to configure custom parameters on different scopes (i.e. global, pipeline or run). When configured, these parameters are sent as key-value pairs in the trigger manifest artifact;
• It is now possible to specify pre-deployment configuration items (alongside post-deployment ones) in the 'Trigger Manifest' screen. To activate this feature, Site Property 'Feature_EnablePreDeploymentConfigurations' must be enabled;
• In order to send information in the trigger manifest about the LifeTime user who triggered the pipeline (instead of using pipeline input parameter 'TriggeredBy'), Site Property 'SendTriggeredByParameterInManifest' must be enabled;
• Fixed issue when specifying configuration items in the 'Trigger Manifest' screen, and environment labels were defined for the corresponding trigger;
• Refreshed dependencies to version 1.2.5 of ardoHTTP component.

• 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.

• 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.