johnzon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Louis Monteiro <jlmonte...@tomitribe.com>
Subject Re: Travis or not travis?
Date Tue, 01 Oct 2019 07:58:52 GMT
I may have enough permissions on Jenkins to help
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Mon, Sep 30, 2019 at 8:46 AM Romain Manni-Bucau <rmannibucau@gmail.com>
wrote:

> Just to clarified, it is not my decision ;).
>
> Now the point of this thread is that contributors dont use travis - it is
> broken since months and we didnt get any report before your PR and seems
> you dont use it too (or I misunderstood the answer in the PR), this is why
> I'm enclined to just drop it and it does not prevent contributors to use
> travisci/circileci/semaphoreci/... if desired in their fork anyway.
>
> Le lun. 30 sept. 2019 à 08:39, Markus Karg <karg@quipsy.de> a écrit :
>
> > Romain,
> > I do respect your decision not to put credentials (even encrypted) on
> > Travis.
> > Certainly you then loose a great Travis feature: Every contributor (not
> > just registered Jenkins users) can have automatic build of each build of
> > their fork using Travis. 😊
> > A nightly snapshot using Jenkins would be fine, at least. 😊
> > -Markus
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Romain Manni-Bucau <rmannibucau@gmail.com>
> > Gesendet: Montag, 30. September 2019 08:35
> > An: dev@johnzon.apache.org
> > Betreff: Re: Travis or not travis?
> >
> > Hi Markus
> >
> > If "nightly" = snapshot deployment then no cause we dont put credentials
> > on travis I think but we can set up sucha job on our jenkins I think.
> >
> > @Mark: think you still have more karma than me on that so if you can have
> > a look and worse case let me know if i should open an INFRA ticket ;)
> >
> >
> > Now, i will likely start the release this morning so you should be able
> to
> > catch up a staging repo within 2h.
> >
> >
> > Le lun. 30 sept. 2019 à 08:31, Markus Karg <karg@quipsy.de> a écrit :
> >
> > > Instead of droppping it, it could be used for nightly builds. We are
> > > currently switching our application to Johnzon which implies producing
> > > several fixes to make it work, and it would be a good thing to have
> > > nightly builds. We can setup that on our server, but I wonder if Team
> > > Johnzon wouldn't like to simply use Travis for that, so everybody has
> > > that benefit, not just us?
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Romain Manni-Bucau <rmannibucau@gmail.com>
> > > Gesendet: Freitag, 27. September 2019 10:00
> > > An: dev@johnzon.apache.org
> > > Betreff: Re: Travis or not travis?
> > >
> > > up?
> > >
> > > any issue to drop it?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog <
> > > https://rmannibucau.metawerx.net/> | Old Blog <
> > > http://rmannibucau.wordpress.com> | Github
> > > <https://github.com/rmannibucau>
> > > | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <
> > > https://www.packtpub.com/application-development/java-ee-8-high-perfor
> > > mance
> > > >
> > >
> > >
> > > Le mar. 24 sept. 2019 à 10:40, Romain Manni-Bucau
> > > <rmannibucau@gmail.com> a écrit :
> > >
> > > > Hi everyone,
> > > >
> > > > we have an old travis.yml in johnzon source code base we don't
> > maintain.
> > > > Markus started to work to fix it but the question of the usage
> > > > popped
> > > out.
> > > >
> > > > AFAIK, nobody uses travis so we could drop it but before pushing
> > > > that way I'd like to ensure it is actually the case (but since the
> > > > setup was broken since months I guess so ;)) and if it is ok to drop
> > > > that file
> > > for everybody.
> > > >
> > > > Side note: don't hesitate to stop and shout you are interested in
> > > > using it and we'll make it back ready to work, I just don't want to
> > > > keep a maintenance on something which is useless for the community.
> > > >
> > > > Hope it makes sense
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > > > <https://rmannibucau.metawerx.net/> | Old Blog
> > > > <http://rmannibucau.wordpress.com> | Github
> > > > <https://github.com/rmannibucau> | LinkedIn
> > > > <https://www.linkedin.com/in/rmannibucau> | Book
> > > > <https://www.packtpub.com/application-development/java-ee-8-high-per
> > > > fo
> > > > rmance>
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message