Re: The future of Gump

[Mark Thomas]

On 09/03/2020 08:49, Martin Grigorov wrote:
> Hi Mark,
> 
> On Sat, Mar 7, 2020 at 10:11 PM Mark Thomas  > wrote:
> 
> Hi all,
> 
> The Gump project has reached the point where Tomcat is the only ASF
> project using it. The Gump community is currently discussing options for
> the future.
> 
> One of those options is status quo which would have no impact on us.
> 
> Another option is the attic. If that were to happen, the vmgump service
> would potentially go away. vmgump has been very useful to the Tomcat
> community. It seems to have a knack of finding concurrency bugs. It
> also, recently, found a regression in OpenSSL master enabling us to get
> that fixed.
> 
> If gump heads to the attic is the Tomcat community prepared to:
> 
> a) take over the management of the vmgump service?
> 
> b) take over the maintenance of the gump code (occasionally code changes
>    are required like when Maven Central started to require https)
> 
> In reality I do most of a) and b) already and I would continue doing so
> if they moved to Tomcat.
> 
> Note that all of this is hypothetical at this point. The Gump PMC has
> not made a decision yet.
> 
> Thoughts?
> 
> 
> For testing ARM64 on TravisCI
> (https://github.com/apache/tomcat/blob/34a855f844091bcdbac6205c6343f7bf6764806f/.travis.yml
>  & 
> https://github.com/apache/tomcat-connectors/blob/9750da36d3c6a30d44d8374c7f6c5182e34fd5cf/.travis.yml)
> I've rolled custom scripts (YAML, actually) which build trunk/master of
> APR, APR Util, libtcnative and HTTPD projects to be able to build and
> test Tomcat and Tomcat Connectors projects.
> I have zero experience with Gump and I've never seen its Tomcat build
> configuration, but I guess it does something similar.

It does a little more than that. It aims to build Tomcat, and all its
dependencies (and the dependencies of the dependencies etc.), from source.

There are a some components that are pulled in as packages rather than
built from source.

For an idea of what is built, take a look at:
http://vmgump.apache.org/

> If the setup is similar then maybe we can extend the usage of TravisCI
> by adding whatever is missing and enabling AMD64 (this is one line change) ?

I don't know TravisCI well enough to know if it can replicate what Gump
is doing for us.

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: The future of Gump

[Martin Grigorov]

Hi Mark,

On Sat, Mar 7, 2020 at 10:11 PM Mark Thomas  wrote:

> Hi all,
>
> The Gump project has reached the point where Tomcat is the only ASF
> project using it. The Gump community is currently discussing options for
> the future.
>
> One of those options is status quo which would have no impact on us.
>
> Another option is the attic. If that were to happen, the vmgump service
> would potentially go away. vmgump has been very useful to the Tomcat
> community. It seems to have a knack of finding concurrency bugs. It
> also, recently, found a regression in OpenSSL master enabling us to get
> that fixed.
>
> If gump heads to the attic is the Tomcat community prepared to:
>
> a) take over the management of the vmgump service?
>
> b) take over the maintenance of the gump code (occasionally code changes
>are required like when Maven Central started to require https)
>
> In reality I do most of a) and b) already and I would continue doing so
> if they moved to Tomcat.
>
> Note that all of this is hypothetical at this point. The Gump PMC has
> not made a decision yet.
>
> Thoughts?
>

For testing ARM64 on TravisCI (
https://github.com/apache/tomcat/blob/34a855f844091bcdbac6205c6343f7bf6764806f/.travis.yml
 &
https://github.com/apache/tomcat-connectors/blob/9750da36d3c6a30d44d8374c7f6c5182e34fd5cf/.travis.yml
)
I've rolled custom scripts (YAML, actually) which build trunk/master of
APR, APR Util, libtcnative and HTTPD projects to be able to build and test
Tomcat and Tomcat Connectors projects.
I have zero experience with Gump and I've never seen its Tomcat build
configuration, but I guess it does something similar.
If the setup is similar then maybe we can extend the usage of TravisCI by
adding whatever is missing and enabling AMD64 (this is one line change) ?

Martin


>
> Mark
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>
>

Re: The future of Gump

[Mark Thomas]

On 07/03/2020 22:33, Michael Osipov wrote:
> Am 2020-03-07 um 21:11 schrieb Mark Thomas:
>> Hi all,
>>
>> The Gump project has reached the point where Tomcat is the only ASF
>> project using it. The Gump community is currently discussing options for
>> the future.
>>
>> One of those options is status quo which would have no impact on us.
>>
>> Another option is the attic. If that were to happen, the vmgump service
>> would potentially go away. vmgump has been very useful to the Tomcat
>> community. It seems to have a knack of finding concurrency bugs. It
>> also, recently, found a regression in OpenSSL master enabling us to get
>> that fixed.
>>
>> If gump heads to the attic is the Tomcat community prepared to:
>>
>> a) take over the management of the vmgump service?
>>
>> b) take over the maintenance of the gump code (occasionally code changes
>>     are required like when Maven Central started to require https)
>>
>> In reality I do most of a) and b) already and I would continue doing so
>> if they moved to Tomcat.
>>
>> Note that all of this is hypothetical at this point. The Gump PMC has
>> not made a decision yet.
>>
>> Thoughts?
> 
> Counter question: Why not go to https://builds.apache.org/?

Infra is unlikely to take it on.

> How much of your time does a) and b) consume?

Very little. Most of my time is spent on Tomcat's configuration files
(which is a project responsibility at the moment anyway).

> What if even more burden
> is put on you, is that acceptable for you?

That is always going to depend on how much effort for how much return.
At the moment I'd say we are no where near the tipping point.

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Re: The future of Gump

[Michael Osipov]

Am 2020-03-07 um 21:11 schrieb Mark Thomas:

Hi all,

The Gump project has reached the point where Tomcat is the only ASF
project using it. The Gump community is currently discussing options for
the future.

One of those options is status quo which would have no impact on us.

Another option is the attic. If that were to happen, the vmgump service
would potentially go away. vmgump has been very useful to the Tomcat
community. It seems to have a knack of finding concurrency bugs. It
also, recently, found a regression in OpenSSL master enabling us to get
that fixed.

If gump heads to the attic is the Tomcat community prepared to:

a) take over the management of the vmgump service?

b) take over the maintenance of the gump code (occasionally code changes
are required like when Maven Central started to require https)

In reality I do most of a) and b) already and I would continue doing so
if they moved to Tomcat.

Note that all of this is hypothetical at this point. The Gump PMC has
not made a decision yet.

Thoughts?


Counter question: Why not go to https://builds.apache.org/?

How much of your time does a) and b) consume? What if even more burden 
is put on you, is that acceptable for you?


Michael

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

The future of Gump

[Mark Thomas]

Hi all,

The Gump project has reached the point where Tomcat is the only ASF
project using it. The Gump community is currently discussing options for
the future.

One of those options is status quo which would have no impact on us.

Another option is the attic. If that were to happen, the vmgump service
would potentially go away. vmgump has been very useful to the Tomcat
community. It seems to have a knack of finding concurrency bugs. It
also, recently, found a regression in OpenSSL master enabling us to get
that fixed.

If gump heads to the attic is the Tomcat community prepared to:

a) take over the management of the vmgump service?

b) take over the maintenance of the gump code (occasionally code changes
   are required like when Maven Central started to require https)

In reality I do most of a) and b) already and I would continue doing so
if they moved to Tomcat.

Note that all of this is hypothetical at this point. The Gump PMC has
not made a decision yet.

Thoughts?

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org