Regarding security - we should make sure that we don't run scripts changed
in PRs from external contributors.
If a non-committer changes a TC script in their fork, then we should not
start a TC build automatically.
I think this can be done in GitHub with workflow approvals.
On Fri, Dec 20, 2024 a
Mikhail, thank you for taking the initiative.
I agree with the Kotlin DSL direction.
> slowdown in indexing in the developers' projects
IDEA can exclude a folder from indexing [1] - should be an easy workaround.
[1] https://www.jetbrains.com/help/idea/indexing.html
On Fri, Dec 20, 2024 at 2:22
I fully support the proposal regarding the transition to the code base
approach. As Peter said, we may have problems with testing the build from
branches, but as far as I see in the TC documentation [1] it is stated that
this is a fully working feature, if we encounter bugs, then this is not an
blo
That is a great idea if you understand what you are doing. And awful if not.
Currently - settings for all Apache Ignite build projects on TeamCity are
ALREADY stored as code in GitHub, as a PMC member you have access to
https://github.com/apache-ignite-teamcity/configuration.
Though the initial co
