Ignite TC Bot created IGNITE-28732:
--------------------------------------

             Summary: [TCBot] Auto-trigger TeamCity builds for PRs from trusted 
bot accounts
                 Key: IGNITE-28732
                 URL: https://issues.apache.org/jira/browse/IGNITE-28732
             Project: Ignite
          Issue Type: Task
            Reporter: Ignite TC Bot


Dependency update bots can open many small PRs. Most of these changes are 
simple dependency bumps and usually only need the regular TeamCity validation. 
Today a human still has to trigger the build and then publish the result 
comment.

Implement an automated TCBot path for PRs created by configured trusted GitHub 
accounts, for example dependabot[bot].

Scope:
* Add configuration for trusted GitHub PR authors that are allowed to trigger 
automatic TeamCity validation.
* Periodically inspect open PRs for the configured GitHub repository and detect 
PRs from trusted authors that do not have a recent/active TCBot validation for 
the current head commit.
* Automatically trigger the configured TeamCity build chain for such PRs.
* Publish a GitHub PR comment in all cases: build successfully queued, build 
was skipped because a matching run already exists, or trigger failed.
* After the observed build finishes, publish the regular TCBot analysis comment 
to the PR regardless of whether blockers were found.
* Avoid duplicate triggers/comments for the same PR head commit and make the 
duplicate marker stable enough for retries.

Acceptance criteria:
* Trusted accounts are configurable, disabled by default unless the config 
explicitly lists accounts.
* A PR by a trusted account can be validated without a human pressing the 
trigger button.
* The PR receives a visible TCBot comment even when the bot decides not to 
trigger or cannot trigger the build.
* The final test analysis is commented back to the PR with the same GitHub 
comment flow used by manual trigger-and-comment runs.
* Non-trusted PR authors keep the existing manual behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to