Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 6 Sep 2017 12:29:31 -0700 (MST)
From: Aleksey Chetaev <alex.chetaev@gmail.com>
To: dev@ignite.apache.org
Message-ID: <1504726171738-0.post@n4.nabble.com>
In-Reply-To: <CALUCNEvbq+1TJSY_hF3ECpyF7gFqgn9SfH7sG_dtx0u_3P7m8w@mail.gmail.com>
References: <1504702671323-0.post@n4.nabble.com> <CALUCNEvbq+1TJSY_hF3ECpyF7gFqgn9SfH7sG_dtx0u_3P7m8w@mail.gmail.com>
Subject: Re: Check Ignite build for different Java before VOTE
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 06 Sep 2017 19:29:41 -0000

Dmitriy,=20
Sorry, we had problem on Ignite TeamCity, I fixed it, now project available
for all developers.


Dmitry Pavlov wrote
> Hi Aleksey,
>=20
> I think all types of release automation is very good for improving our
> processes and provide stable product.
>=20
> Currently I am not able to view new Run configs:
> You do not have enough permissions to access build type with id:
> IgniteRelease_427CheckBuildIgniteFabricOpenJDK8
>=20
> What should I do to see new builds?
>=20
> Sincerely,
> Dmitriy Pavlov
>=20
> =D1=81=D1=80, 6 =D1=81=D0=B5=D0=BD=D1=82. 2017 =D0=B3. =D0=B2 15:57, Alek=
sey Chetaev &lt;

> alex.chetaev@

> &gt;:
>=20
>> 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 Scala
>>  5. Ignite Hadoop for default Hadoop release.
>>  6. Ignite Hadoop for one of last Hadoop release
>>  7. Ignite Hadoop for one of last Hadoop version and one of Spark
>> version.
>> Because we provide source code to users, success build for all this
>> options
>> should be tested with all supported Java version before release. Make it
>> manually it's really difficult.
>>
>> So that release developer can check all this build option automatically =
I
>> created 9 task on TeamCity. All task download source archive from svn fo=
r
>> release candidate using params and start build on downloaded source. (no=
w
>> source downloading from release svn for testing, because release
>> candidate
>> svn is empty)
>>
>> 1. Task check that we have license headers in all source files:
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
1CheckLicenseHeadersInFiles
>> 2. Tasks check build option 1-4 for Oracle Java 7,8 and for OpenJDK 7,8:
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
21CheckBuildIgniteFabricOracleJava7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
23CheckBuildIgniteFabricOracleJava8
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
25CheckBuildIgniteFabricOpenJDK7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
27CheckBuildIgniteFabricOpenJDK8
>> 3. Tasks check build option 5-7 for  Oracle Java 7,8 and for OpenJDK 7,8=
,
>> for Hadoop(default, 2.6.5, 2.7.3) and for Spark(2.1.1, 2.2.0)
>>    *
>>
>> https://ci.ignite.apache.org/viewLog.html?buildId=3D811586&tab=3DbuildRe=
sultsDiv&buildTypeId=3DIgniteRelease_422CheckBuildIgniteHadoopOracleJava7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
24CheckBuildIgniteHadoopOracleJava8
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
26CheckBuildIgniteHadoopOpenJDK7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgniteRelease_4=
28CheckBuildIgniteHadoopOpenJDK8
>>
>> I think we should change release process and release developer should ru=
n
>> all this task before send release to VOTE.
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>


--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/