Re: Check Ignite build for different Java before VOTE

Alexey Thanks for contributing! The idea is good for the improving of product quality. Could you explain which values the release engineer should put in the parameters section? On Wed, Sep 6, 2017 at 10:29 PM, Aleksey Chetaev wrote: > Dmitriy, > Sorry, we had problem

Re: Check Ignite build for different Java before VOTE

Dmitriy, Sorry, we had problem on Ignite TeamCity, I fixed it, now project available for all developers. Dmitry Pavlov wrote > Hi Aleksey, > > I think all types of release automation is very good for improving our > processes and provide stable product. > > Currently I am not able to view new

Re: Check Ignite build for different Java before VOTE

Hi Aleksey, I think all types of release automation is very good for improving our processes and provide stable product. Currently I am not able to view new Run configs: You do not have enough permissions to access build type with id: IgniteRelease_427CheckBuildIgniteFabricOpenJDK8 What should

Re: Check Ignite build for different Java before VOTE

FYI: I founded some issues with build failed in our JIRA: 1. https://issues.apache.org/jira/browse/IGNITE-2149 2. https://issues.apache.org/jira/browse/IGNITE-4721 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Check Ignite build for different Java before VOTE

Igniters, In Ignite DEVNOTES we have full instruction how we can build Ignite, but we have a lot of different options with which Ignite can be builded: 1. Ignite Fabric without Scala modules 2. Ignite Fabric with Scala modules 3. Ignite Fabric LGPL without Scala 4. Ignite Fabric LGPL with