Il giorno sab 29 set 2018 alle ore 22:15 Stefan Schmidt < ste...@datenfreihafen.org> ha scritto:
> Hello. > > On 29/09/2018 08:19, Davide Andreoli wrote: > > Il giorno mer 26 set 2018 alle ore 10:17 Stefan Schmidt > > <ste...@datenfreihafen.org <mailto:ste...@datenfreihafen.org>> ha > scritto: > > > > Hello Dave. > > > > I have recently disabled all builds on Jenkins. The only job I left > > enabled is your base_pyefl_build job. > > > > > > Disabling the jobs was only the first step towards shutting down > Jenkins > > on our server completely. > > > > That leaves the question open what do do with the pyefl job. Is this > > something you are still actively using? Something that produces > tarballs > > or artifacts you need? > > > > > > Yes, the pyefl build is actively used for 3 main tasks: > > 1. Tests after each commit that everything build and unit-tests pass on > > various python version > > 2. Artifacts: the build create tarball and documentation that are public > > (and linked in various places) > > for in-development snapshot release. > > 3. I use the final artifacts to roll-up each stable release > > So its used and needed. Fair enough. We will have a place for it. > > > > > > > If it is something actively used and needed we need to find a new > home > > for it. If it is just a left over we can simply drop it. > > > > > > well, I'm quite surprised that we are shutting down our CI infra without > > an alternative > > ready to migrate to. Do the efl project can live without CI? I don't > > think any decent project can. > > Where did you jump to the conclusion that we will not have any CI? I did > not wrote that at all. > > Together with Mike and Marcel I have been working on using TravisCI as > our new system for many, many months. The config and scripts are even in > the main efl repo under .ci/. Not sure how you could have been able to > miss these with all the commits going into that. But be assured we want > to keep CI going and even improve it (we have mac os builds going on on > Travis and I am working on mingw cross builds for windows as well right > now). > Ugh, sorry then. I'm not actively reading the commit list lately > > > Of course it doesn't make sense to keep up jenkins only for pyefl, so if > > you are going to trash it > > just do it, I will remove any link around, change the release procedure > > and everything else needed. > > > > But we really need a new CI infra, I don't know how can I decently > > manage the python-efl project without a working CI. > > We will get something working for you. For now your Jenkins python efl > job stays as it is. > ok, good to hear, let me know if you need some help from my side :) > > regards > Stefan Schmidt > _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
