JDK 12 both Oracle and Open + JDK 13 Open early access builds.
May be suites require additional configuration — I can do this quick.
> On 14 May 2019, at 23:43, Dmitriy Pavlov wrote:
>
> Is Java 12 available on all TeamCity agents?
>
> вт, 14 мая 2019 г. в 23:21, Petr Ivanov :
>
>> How
Is Java 12 available on all TeamCity agents?
вт, 14 мая 2019 г. в 23:21, Petr Ivanov :
> How about adding JDK 12 to this list?
> Or it is a bit prematurely for now?
>
> > On 14 May 2019, at 21:02, Dmitriy Pavlov wrote:
> >
> > Hi Petr,
> >
> > Thank you for your reply. Almost the same term
How about adding JDK 12 to this list?
Or it is a bit prematurely for now?
> On 14 May 2019, at 21:02, Dmitriy Pavlov wrote:
>
> Hi Petr,
>
> Thank you for your reply. Almost the same term (tag) is used by Bot
> internally when the Java version is displayed. So from point of view of
> Bot's
Hi Petr,
Thank you for your reply. Almost the same term (tag) is used by Bot
internally when the Java version is displayed. So from point of view of
Bot's usability tags are not necessary. From the point of view of main TC
UI - may be.
About selection options, it is configured at TC Bot server
I can make builds autotag itself with used JDK.
Also - from what JDKs does randomiser choose?
> On 9 May 2019, at 12:56, Dmitriy Pavlov wrote:
>
> Hi Igniters,
>
> For your information, Apache Ignite TeamCity bot now triggers run all
> (nightly) using some available JDK version (random each
Hi Igniters,
For your information, Apache Ignite TeamCity bot now triggers run all
(nightly) using some available JDK version (random each time). Used JDK is
saved in the Bot DB and is shown at UI (see below).
Next step could be changing the flakyness detection algorithm in the Bot to
analyze
