Dropping Security. It is unrelated to the security breach.
We have indeed hit a limit, I'll reach out to Travis and see what we can do. On Thu, Sep 16, 2021 at 11:24 PM Jarek Potiuk <ja...@potiuk.com> wrote: > Maybe the user licence exceed is somewhat related and someone is exploiting > the leakage ? Remote possibility, but who knows. > > On Thu, Sep 16, 2021 at 11:22 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > > Just learned something (not using Travis CI but I have not seen this > > posted here). Several days ago Travis CI had a serious security breach. > > In short - for about 1 hr anyone could get access to any secrets stored > in > > any public project. > > > > https://www.infoq.com/news/2021/09/travis-ci-secrets-leak/ > > > > "If you have a Public Repository that was forked, then there was a > > possibility that someone from the forked (copied) project might have been > > able to have seen the original project’s Secret ONLY for a short time > while > > doing a build." > > > > J. > > > > > > > > On Thu, Sep 16, 2021 at 11:00 PM Stephen Mallette <spmalle...@gmail.com> > > wrote: > > > >> I was alerted to the Travis error message of "Owner apache user license > >> exceeded" by someone trying to submit a pull request to Apache > TinkerPop. > >> Here was that pull request where the person was good enough to include a > >> screenshot of the issue as well as links to Travis request: > >> > >> https://github.com/apache/tinkerpop/pull/1476 > >> > >> As you can see, the Travis job simply won't start for that PR, yet afaik > >> others builds have executed without error in the day (as recent as 4 > hours > >> ago). Does anyone know what might be happening here? > >> > >> Thanks, > >> > >> Stephen > >> > > > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
