![]() Tip: if the URL contains smart values (variables), replace those with actual values (constants) for the time of the validation, then revert to the smart values after the configuration was successfully validated. Validate your settings in the Validate your webhook configuration section below. Check the Delay execution of subsequent rule actions until we've received a response for this webhook checkbox.Replace the placeholder with the actual Access Token created at step 2. Replace the placeholder with your actual TeamCity base URL.Īdd a header with the name "Authorization" and with the value of "Bearer ". If you are using an older TeamCity version which does not support CSRF protection (or it's disabled), skip these steps and continue with step 12.Select the trigger Changeset accepted (from the DevOps category).Login to Jira as admin, go to Administration → System → Automation rules.If your TeamCity version does not support Access Tokens, continue with step 4.Įnter a token name in the Token name field.Ĭopy the generated token, because it cannot be recovered in the future. Login to TeamCity as admin, go to your profile → My Settings & Tools → Access Tokens. It starts the build once per changeset, after all the commits in the changeset are already in the repository. It is the simplest way to integrate TeamCity to your DevOps pipeline. ![]() ![]() This automation starts a TeamCity build when a new changeset is received. Starting a TeamCity build after every changeset ![]()
0 Comments
Leave a Reply. |