tcWebHookTrigger v1.3.1

Add warning in log when queue permission is missing
Don't stop the triggers from running, as it would stop them all, and we can still trigger the build, we just can't move it to the top of the queue, so add a warning to the log to indicate as such.

Full Changelog: v1.3.0...v1.3.1

tcWebHookTrigger v1.3.0

Adds a new checkbox in the UI which enables requesting the build to move to the top of the queue when triggered.
If using an access token to trigger builds, make sure the token has "Re-order build queue" permission. Token permissions can't be modified, so it's best to generate a new token.

See #14 for details about this change.

Full Changelog: v.1.2.0...v1.3.0

tcWebHookTrigger v1.2.0

Contains the following improvements

• Allow rewrite of branch name
• Only process the trigger when the trigger is enabled
• Change logging to log to teamcity-triggers.log (was previously teamcity-activities.log for some crazy reason).
• Catch and log a failed processing (that would previously have returned a 500) as WARN in teamcity-triggers.log
• Don't define regex interim variable when group match value returns null
• Don't process filters if one or more of the required path mappings was not found

More details can be found on issue #13

Full Changelog: v.1.0.6...v.1.2.0

Bugfix: "Include Payload" would prevent other Build Parameters from being defined

Any parameters found/resolved would previously be overwritten by setting the "payload" option in the UI.
This release now fixes this issue.

Now checking the payload checkbox adds the payload variable to any existing variables resolved rather than clearing them.
These variables are saved into the build as Parameters.

tcWebHookTrigger v1.0.5

Add support for building a specific commit - #1

Defining a variable named commit will request the build to trigger against a specific commit.
eg. name=commit::path=$.project.commit::required=true

When the trigger runs, the value of commit will be searched for in Teamcity's list of known commits.

⚠️ If the commit is not found in TeamCity's list, the build will not run. The commit might not have been discovered by teamcity yet. The plugin does not force teamcity to query the VCS source.

When the build trigger executes, the following will appear in the teamcity-activities.log file.

DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Found specific modifcation in VCS for commit '24e1154728b4c55b8d864c47c1c56377ce612dd2'. Build will be triggered against this commit.

Here is the log entry in context:

DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Starting Webhook Trigger processing. buildType='TcPlugins_TcWebHookTriggerOnQuimby', triggerName='webhookBuildTrigger', triggerId='TRIGGER_3'
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Parameter is resolved. Parameter will be passed to the build. name='branch', value='main'
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Parameter is resolved. Parameter will be passed to the build. name='commit', value='24e1154728b4c55b8d864c47c1c56377ce612dd2'
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: No filters defined. Skipping regex validation.
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Found parameter named 'branch'. Build will be requested against branch 'main'. buildType='TcPlugins_TcWebHookTriggerOnQuimby', triggerName='webhookBuildTrigger', branchName='main', triggerId='TRIGGER_3'
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Found specific modifcation in VCS for commit '24e1154728b4c55b8d864c47c1c56377ce612dd2'. Build will be triggered against this commit. buildType='TcPlugins_TcWebHookTriggerOnQuimby', triggerName='webhookBuildTrigger', triggerId='TRIGGER_3'
INFO - tcWebHookTrigger-BuildTriggerHandlerService: Build queued by Webhook Trigger processing. buildType='TcPlugins_TcWebHookTriggerOnQuimby', triggerName='webhookBuildTrigger', triggerId='TRIGGER_3', buildId='1221'
DEBUG - tcWebHookTrigger-BuildTriggerHandlerService: Completed Webhook Trigger processing. buildType='TcPlugins_TcWebHookTriggerOnQuimby', triggerName='webhookBuildTrigger', triggerId='TRIGGER_3'

tcWebHookTrigger v1.0.4

Displays the webhook URL in the UI when editing a trigger configuration

This fixes issue #3

tcWebHookTrigger v1.0.3

Validate token permissions before executing #7

Now checks that the user or token used to authenticate the request has the correct permission (RUN_BUILD) allocated to it.

tcWebHookTrigger v1.0.2

This release adds support for Bearer Authentication and fixes the version number presented in the TeamCity UI

Add support for Bearer Authentication (issue #5)

⚠️ Breaking Change

Adding support for Bearer Authenication requires that the endpoint is located in the /app/rest URL namespace.
Existing webhooks need to be updated to point to the new URL <teamcity_root_url>/app/rest/webhook-trigger/BuildConfigId

Note: The httpAuth is no longer required because the rest endpoints support Basic and Bearer Authentication.

Fix versioning (issue #6 )

Version in this release page, the maven POM file, and the UI are now all in sync.

tcWebHookTrigger v1.0.1

Fixes two issues:

Support non-text path values in json (issue #4)

Number and boolean values now resolve to the String equivalent so that they can be passed to the build as parameters.

   {
       "my_number" : 12345,
       "my_boolean" : true
   }

Support including whole payload as a build parameter (issue #2)

Enables the checkbox in the UI to pass the original webhook payload as build parameter.

tcWebHookTrigger v1.0

Initial version for testing