You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sylwester Lachiewicz (Jira)" <ji...@apache.org> on 2021/01/25 22:54:00 UTC
[jira] [Updated] (MENFORCER-377) Remove reference to travis or
switch to travis.com
[ https://issues.apache.org/jira/browse/MENFORCER-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylwester Lachiewicz updated MENFORCER-377:
-------------------------------------------
Fix Version/s: 3.0.0-M4
> Remove reference to travis or switch to travis.com
> --------------------------------------------------
>
> Key: MENFORCER-377
> URL: https://issues.apache.org/jira/browse/MENFORCER-377
> Project: Maven Enforcer Plugin
> Issue Type: Task
> Reporter: Krosheninnikov Artem
> Priority: Minor
> Fix For: 3.0.0-M4
>
>
> This is not completely related to enforcer but to the CI process it uses.
> As of [1], travis.org won't work after 31 dec, 2020. It's possible to switch to travis.com (not sure it will provide needed capacity for OSS projects) or to eliminate it completely. As far as I can see, github actions cover the same functionality (running `mvn verify -Prun-its` for different java/os versions)
> [1] https://devops.stackexchange.com/questions/1201/whats-the-difference-between-travis-ci-org-and-travis-ci-com
--
This message was sent by Atlassian Jira
(v8.3.4#803005)