ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aleksey Chetaev <alex.chet...@gmail.com>
Subject Re: Check Ignite build for different Java before VOTE
Date Wed, 06 Sep 2017 19:29:31 GMT
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 Run configs:
> You do not have enough permissions to access build type with id:
> IgniteRelease_427CheckBuildIgniteFabricOpenJDK8
> 
> What should I do to see new builds?
> 
> Sincerely,
> Dmitriy Pavlov
> 
> ср, 6 сент. 2017 г. в 15:57, Aleksey Chetaev &lt;

> alex.chetaev@

> &gt;:
> 
>> 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 for
>> release candidate using params and start build on downloaded source. (now
>> 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=IgniteRelease_41CheckLicenseHeadersInFiles
>> 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=IgniteRelease_421CheckBuildIgniteFabricOracleJava7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_423CheckBuildIgniteFabricOracleJava8
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_425CheckBuildIgniteFabricOpenJDK7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_427CheckBuildIgniteFabricOpenJDK8
>> 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=811586&tab=buildResultsDiv&buildTypeId=IgniteRelease_422CheckBuildIgniteHadoopOracleJava7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_424CheckBuildIgniteHadoopOracleJava8
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_426CheckBuildIgniteHadoopOpenJDK7
>>    *
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_428CheckBuildIgniteHadoopOpenJDK8
>>
>> I think we should change release process and release developer should run
>> 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/

Mime
View raw message