INFRA requests more insight on this topic and if we want to enable all of
the repositories we have to create a script.
I think the best option is to enable Travis only on repositories which
satisfy these criteria:
- tests finish within 50 minutes
- the repository ia receiving pull requests from no
Go for it. Nobody said no (and forgiveness is sometimes easier than
permission)
Ask infra which they prefer, all in one go or one at a time
On Tue 15 Jan 2019 at 20:36, Enrico Olivelli wrote:
> ping
>
> Il giorno gio 10 gen 2019 alle ore 20:29 Enrico Olivelli
> ha scritto:
> >
> > I would like
ping
Il giorno gio 10 gen 2019 alle ore 20:29 Enrico Olivelli
ha scritto:
>
> I would like to enable Travis on other plugins, maybe I can do it on plugins
> which have active prs
>
> Okay?
> Enrico
>
> Il lun 7 gen 2019, 02:46 Manfred Moser ha scritto:
>>
>> Fair enough. If its just for outside
I would like to enable Travis on other plugins, maybe I can do it on
plugins which have active prs
Okay?
Enrico
Il lun 7 gen 2019, 02:46 Manfred Moser ha
scritto:
> Fair enough. If its just for outside contributor PRs I am agree with not
> owning the risk ;-)
>
> Stephen Connolly wrote on 2019-
Fair enough. If its just for outside contributor PRs I am agree with not owning
the risk ;-)
Stephen Connolly wrote on 2019-01-04 16:06:
> On Fri 4 Jan 2019 at 22:00, Tibor Digana wrote:
>
>> @Stephen Connolly
>> After such a big investment, especially made on your side, in Jenkins
>> plugi
Il dom 6 gen 2019, 21:04 Sylwester Lachiewicz ha
scritto:
> In Maven Resolver we have a sample Travis configuration, so someone can
> test with the forked repo.
> If we go with Travis CI I would be good to have a common configuration for
> all projects (ie to run run-it etc and have .travis.yml e
I believe my employer also offers free build services for OSS projects via
our CodeShip offering. If people are concerned about tying PR validation
exclusively to one vendor we should inspect the CloudBees CodeShip
capabilities (includes Docker build agents, which can be very nice...
though I confe
In Maven Resolver we have a sample Travis configuration, so someone can
test with the forked repo.
If we go with Travis CI I would be good to have a common configuration for
all projects (ie to run run-it etc and have .travis.yml excluded from RAT).
I saw in one Apache project (don't remember now n
Il dom 6 gen 2019, 18:03 Hervé BOUTEMY ha scritto:
> you mean this directory is not involved in the seed job [2]?
>
I meant only that the name of such directory was not special, it works as
you described
when I look into this job, I see a "Process Job DSLs" step that looks on
> filesystem ".tes
you mean this directory is not involved in the seed job [2]?
when I look into this job, I see a "Process Job DSLs" step that looks on
filesystem ".test-infra/jenkins/job_*.groovy"
in Maven, the "maven-box" seed job [3] is created with the ASF's Gitpubsub
Jenkins plugin that creates the mutlibran
Enrico> limited to linux and osx, not windows.
Windows can be tested via AppVeyor.
The configuration is the same: one adds appveyor.yml (e.g.
https://github.com/apache/calcite/blob/master/appveyor.yml ) and asks
Infra team to enable AppVeyo-GitHub integration.
Vladimir
--
It is not a special directory, we are using Je kins DSL, and there is a
'seed job' which parses these files and creates/updates the jobs.
This way committers without direct access to Jenkins can operate on
configuration and we can work with review then commit.
Therefore it is easy to reconstruct ev
Il dom 6 gen 2019, 10:32 Hervé BOUTEMY ha scritto:
> Le samedi 5 janvier 2019, 12:34:30 CET Enrico Olivelli a écrit :
> > Travis up and running on Maven Scripting Plugin
> > this is the first build with integration tests
> >
> > mvn verify -Prun-its
> > https://travis-ci.org/apache/maven-scriptin
Le samedi 5 janvier 2019, 12:34:30 CET Enrico Olivelli a écrit :
> Travis up and running on Maven Scripting Plugin
> this is the first build with integration tests
>
> mvn verify -Prun-its
> https://travis-ci.org/apache/maven-scripting-plugin/builds/475666300
>
> This is how the PR looks like:
>
interesting
I suppose this is enabled by the content of .test-infra/jenkins directory [1]
even if I don't really understand the content and how we could add something
like this in our configuration
Regards,
Hervé
[1] https://github.com/apache/bookkeeper/tree/master/.test-infra/jenkins
Le same
On Sat, Jan 5, 2019 at 8:11 AM Olivier Lamy wrote:
> No way. Apache Infrastructure is a shared infrastructure. There are NO
> dedicated machine for any projects.
>
I guess you mean physical machines here, don't you?
I don't think physical machines are what matters, but having an infra that
can p
Travis up and running on Maven Scripting Plugin
this is the first build with integration tests
mvn verify -Prun-its
https://travis-ci.org/apache/maven-scripting-plugin/builds/475666300
This is how the PR looks like:
https://github.com/apache/maven-scripting-plugin/pull/2
I think it is a great st
Il sab 5 gen 2019, 08:48 Hervé BOUTEMY ha scritto:
> Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> > On Sat, 5 Jan 2019 at 12:39, Tibor Digana
> wrote:
> > > Manfred, did you see my comment on Slack?
> > > Shortly, let's have dedicated machines just only for Maven project with
Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> On Sat, 5 Jan 2019 at 12:39, Tibor Digana wrote:
> > Manfred, did you see my comment on Slack?
> > Shortly, let's have dedicated machines just only for Maven project with
> > Infra support and one person from our team with Infra permi
On Sat, 5 Jan 2019 at 12:39, Tibor Digana wrote:
> Manfred, did you see my comment on Slack?
> Shortly, let's have dedicated machines just only for Maven project with
> Infra support and one person from our team with Infra permissions just on
> these machines. There are 6 Windows machine. So 4 Wi
On Fri 4 Jan 2019 at 22:00, Tibor Digana wrote:
> @Stephen Connolly
> After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHub PRs and you just
> let be to go with TravisCI just like that? I do not think so!
I want to a
Manfred, did you see my comment on Slack?
Shortly, let's have dedicated machines just only for Maven project with
Infra support and one person from our team with Infra permissions just on
these machines. There are 6 Windows machine. So 4 Win/Ubuntu for us.
all: WDYT?
Cheers
Tibor
On Sat, Jan 5, 2
I agree with Tibor. I would rather not have to deal with two different CI
systems...
Manfred
Tibor Digana wrote on 2019-01-04 14:00:
> @Stephen Connolly
> After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHub PRs and
Thanks
I am asking INFRA to enable Travis, let's see how it works
https://issues.apache.org/jira/browse/INFRA-17554
Enrico
Il giorno ven 4 gen 2019 alle ore 23:00 Tibor Digana
ha scritto:
>
> @Stephen Connolly
> After such a big investment, especially made on your side, in Jenkins
> plugin you
@Stephen Connolly
After such a big investment, especially made on your side, in Jenkins
plugin you developed you do not want to support the GitHub PRs and you just
let be to go with TravisCI just like that? I do not think so!
T
On Fri, Jan 4, 2019 at 7:22 PM Stephen Connolly <
stephen.alan.conn
+1 from me
On Fri 4 Jan 2019 at 18:21, Enrico Olivelli wrote:
> Hi,
> I would like to try out Travis on this small plugin:
> https://github.com/apache/maven-scripting-plugin
>
> I have pushed a minimal configuration file
> I need to ask to Infra, but I need approval from the community and PMCs..
Hi,
I would like to try out Travis on this small plugin:
https://github.com/apache/maven-scripting-plugin
I have pushed a minimal configuration file
I need to ask to Infra, but I need approval from the community and PMCs...
Can I proceed ?
Enrico
27 matches
Mail list logo
