Ignite Teamcity at Apache side

[Anton Vinogradov]

Hello,

As you may know we already have Ignite Teamcity server where contributors
can check it's patches. But, as Cos said before, this test environment
should be runned under apache hardware.

Apache test environment based on Jenkins, but it is not so simple to
migrate from TeamCity to Jenkins.

Is it possible to make Ignite test environment at Apache side using
TeamCity, not Jenkins?
TeamCity can be used under opensource license (
https://www.jetbrains.com/teamcity/buy/opensource.html).

[Branko Čibej]

On 03.09.2015 15:11, Anton Vinogradov wrote:

> Hello,
>
> As you may know we already have Ignite Teamcity server where contributors
> can check it's patches. But, as Cos said before, this test environment
> should be runned under apache hardware.
>
> Apache test environment based on Jenkins, but it is not so simple to
> migrate from TeamCity to Jenkins.
>
> Is it possible to make Ignite test environment at Apache side using
> TeamCity, not Jenkins?
> TeamCity can be used under opensource license (
> https://www.jetbrains.com/teamcity/buy/opensource.html).

There are two ways to do this:

  * Ask Infra (in JIRA or mail) to provide a TeamCity instance on our
    infrastructure. This is far more likely to succeed if several PMCs
    make the request.
  * Ask Infra to set up a VM for Ignite and manage a dedicated instance.

The first option is by far preferred, but be aware that Infra has very
limited resources.

-- Brane

[Konstantin Boudnik-2]

On Thu, Sep 03, 2015 at 04:11PM, Anton Vinogradov wrote:
>    Hello,
>    As you may know we already have Ignite Teamcity server where contributors
>    can check it's patches. But, as Cos said before, this test environment
>    should be runned under apache hardware.

It isn't like test env. _should_ be running on Apache infra, but that's what
most
projects do and it takes away a bunch of chores of maintenance. The part that
_should_ be on Apache infra is where you build and deploy project's artifacts
and/or building releases. The main reason is trust: with Infra you know where
your bits are coming from and can be relatively sure there's no malware and
other nasty things on it.

Say, in Bigtop we are running all the CI on our own infra, but all the
deployable artifacts are created by builds.a.o. Same goes with Ignite already.
So I am not particularly married to an idea that CI just _has_ to be moved
over.

Cos

>    Apache test environment based on Jenkins, but it is not so simple to
>    migrate from TeamCity to Jenkins.
>    Is it possible to make Ignite test environment at Apache side using
>    TeamCity, not Jenkins?
>    TeamCity can be used under opensource license
>    (https://www.jetbrains.com/teamcity/buy/opensource.html).

[Branko Čibej]

On 03.09.2015 20:31, Konstantin Boudnik wrote:

> On Thu, Sep 03, 2015 at 04:11PM, Anton Vinogradov wrote:
>>    Hello,
>>    As you may know we already have Ignite Teamcity server where contributors
>>    can check it's patches. But, as Cos said before, this test environment
>>    should be runned under apache hardware.
> It isn't like test env. _should_ be running on Apache infra, but that's what
> most
> projects do and it takes away a bunch of chores of maintenance. The part that
> _should_ be on Apache infra is where you build and deploy project's artifacts
> and/or building releases. The main reason is trust: with Infra you know where
> your bits are coming from and can be relatively sure there's no malware and
> other nasty things on it.
>
> Say, in Bigtop we are running all the CI on our own infra, but all the
> deployable artifacts are created by builds.a.o. Same goes with Ignite already.
> So I am not particularly married to an idea that CI just _has_ to be moved
> over.

Yeah, there's that. For example, many projects that use buildbot instead
of jenkins have buildslaves peppered all over the place. There's nothing
wrong with having a complete test environment outside ASF the ASF, but
of course it does cause additional sysadmin work for someone.

-- Brane