infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-17763) Enable Travis on Maven github repositories
Date Sun, 27 Jan 2019 04:33:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-17763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-17763:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

I'm going to have to say no on this, at least initially. Travis is a limited resource that
we pay for, and adding 100+ repos for a single project isn't going to work very well. You'll
need to provide us with very specific reasons why you need travis builds for 100+ repos, and
explain why you can't perform these builds on our existing CI, then infra admin [~gstein]
will evaluate if the ask is viable, and what resources need to be allocated, and where that
allocation comes from.


> Enable Travis on Maven github repositories
> ------------------------------------------
>
>                 Key: INFRA-17763
>                 URL: https://issues.apache.org/jira/browse/INFRA-17763
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Enrico Olivelli
>            Priority: Major
>
> I would like to enable Travis-CI on all (100!!) github repositories related to Maven
project.
> We (Maven committers) have already tried with maven-scripting-plugin and it is working
as expected.
> Next step is to enable to the whole group of repositories.
> If you prefer I can file X issues and batch repositories. No problem from my side.
> Initially I will push the Travis configuration file to most active repositories, not
to every 100.
> cc [~stephenc] [~rfscholte]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message