Ivan, sorry, it seems PMCs forgot to add your account to Committer group.
I've changed rights settings.
чт, 20 июн. 2019 г. в 08:42, Павлухин Иван :
> Dmitriy,
>
> It is a very important topic for Ignite CI. I think it would be great
> if all significant changes in a build configuration goes with
One more blog I found today related to this topic
https://blog.jetbrains.com/teamcity/2019/03/configuration-as-code-part-1-getting-started-with-kotlin-dsl/
If DSL may bring conditional steps, it may be used for various
optimizations in suites. Moreover, it is a git-based change management
opport
For curious ones I copied a RunAll DSL configuration to gist [1].
[1] https://gist.github.com/pavlukhin/e788bbebafe69ce9d9a3c9e9871ab8c4
чт, 20 июн. 2019 г. в 08:42, Павлухин Иван :
>
> Dmitriy,
>
> It is a very important topic for Ignite CI. I think it would be great
> if all significant changes
Dmitriy,
It is a very important topic for Ignite CI. I think it would be great
if all significant changes in a build configuration goes with a
meaningful description (a commit message). As for me, DSL sounds
promising.
BTW, a special rights are needed to view
https://ci.ignite.apache.org/admin/ed
Hello, Dmitriy.
Thanks, for starting this discussion.
I think almost all of community members don't know the difference between two
options.
I vote for the simplest solution with the human readable format.
В Пн, 17/06/2019 в 21:07 +0300, Dmitriy Pavlov пишет:
> Hi Igniters,
>
> During prepari
Hi Igniters,
During preparing of the release I've faced with lack of information related
to required steps. This was one reason of too long release preparation.
This process was automated by several Ignite contributors (thank you, BTW).
Now, these valued automation results are more or less stored
