Re: TC hell
On Thu, Aug 27, 2015 at 2:24 PM, Sergi Vladykin sergi.vlady...@gmail.com wrote: I think we have to switch to manual TC runs, this will solve the problem. Guest account should not be able to run anything in my view anyways, it must be allowed only for registered contributors. Just to be clear, I said committer in my email meaning ASF committers, not any Github contributor. BTW - I found the plugin I was on about: https://github.com/janinko/ghprb. However, it's for Jenkins. I've seen it in action and it's pretty cool. Raúl.
How to fix build failure Check License Headers (by RAT) (Maven
I got below error in the TC, how to fix such issue? [12:27:35]Step 4/8: Check License Headers (by RAT) (Maven) (7s) [12:27:41][Step 4/8] org.apache.ignite:ignite-platform [12:27:41][org.apache.ignite:ignite-platform] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project ignite-platform: Too many files with unapproved license: 1 See RAT report in: /home/teamcity/agent/work/cf2353597844dbf3/modules/platform/target/rat.txt [12:27:43][Step 4/8] Step Check License Headers (by RAT) (Maven) failed [12:27:43]Step 7/8: Build and run tests (Maven) [12:27:44][Step 7/8] Step Build and run tests (Maven) failed Thanks, kcheng
Re: TC hell
Definitely we have to change something here. I would use a manual triggering granting access through a special account available only to contributors and commiters. -- Denis On 8/27/2015 9:51 AM, Valentin Kulichenko wrote: Igniters, We currently have 200 builds in TC queue and it will take around 15 hours to run everything. This is becoming unusable. It seems to me that it got worse after we switched to pull requests, because builds are triggered each time someone pushes to the branch that is tied up with existing PR. I'm sure that not all of these builds are really needed, so I suggest to disable automatic trigger and always start builds manually (we already have 'Run All' configuration in case you need all suites). The only issue - right now manual run is not possible under Guest account. So we will have to either change Guest permissions or add special account for this. Thoughts? -Val
[jira] [Created] (IGNITE-1310) Platforms: move cluster group to Ignite.
Vladimir Ozerov created IGNITE-1310: --- Summary: Platforms: move cluster group to Ignite. Key: IGNITE-1310 URL: https://issues.apache.org/jira/browse/IGNITE-1310 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov Priority: Critical Fix For: ignite-1.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
