Hey, On Thu, Mar 15, 2012 at 11:48, Toni Menzel <t...@okidokiteam.com> wrote: > I actually like travis somewhat. Haven't really used it yet, i am also > unsure about software running the builds.
The real agent is an ubuntu 11.somewhat with openjdk6.somewhat and maven 3.somewhat. > Also looks like Heroku has problems at the moment appealingly which is one > of the drawbacks using those kinds of solutions. But yeah, its just a bad > coincidence perhaps. That's true, but as long as the build servers are running and sending notifications I can live with some small downtimes. > For an (for now) undisclosed reason i would like to keep the build pipeline > running completely in OPS4J hands. *THRILLED* :-) > If the community comes up with hosted solutions, i don't have a problem > going with it, maybe on a per project basis right now, so we can check out > the pros and cons of each solution. Personally i still favor (as it was > installed before) Hudson over Jenkins but in general i am open to anything > that improves the build pipeline of good open source software! TBH I really like travis-ci for the reasons explained above and it's simplicity. I think we definitely need (better earlier than later) a hosted solution. Nobody has the time to maintain an own solution and keep it up-to-date tbh... Nevertheless I can life with any solution the community prefers. Let's keep discussing here and then start a vote about the possible solutions. Kind regards, Andreas > > Toni > > On Thu, Mar 15, 2012 at 10:51 AM, Jimmi Dyson <jimmi.dy...@specsavers.com> > wrote: >> >> If you wanted to remain on Jenkins but move away from self-hosting, >> Cloudbees (http://www.cloudbees.com/) is a pretty good option, depending on >> your utilisation. They offer free cloud hosting of Jenkins to open source >> projects (http://www.cloudbees.com/foss/index.cb), although obviously with >> resource constraints. I have set this up with some projects I have in Github >> & all works nicely. >> >> Just an alternative, although I must say http://travis-ci.org looks pretty >> interesting. >> >> Not quite sure what you mean by: >> >> >> "compared to hudson where you need to setup a build seperately and the >> single commits are gathered together till no service is available and are >> build afterwards all together" >> >> The Git plugin for Jenkins can build all branches & can also perform >> pre-tested commits from integration branches which we've started using at >> work. You can also send post-commit hooks to trigger builds automatically. >> Maybe I've misunderstood what you mean? >> >> Thanks, >> Jimmi >> >> >> On 14 March 2012 19:49, Andreas Pieber <anpie...@gmail.com> wrote: >>> >>> Hey guys, >>> >>> Because of the current problems with our CI&T system we did some time >>> searching what we could find of hosted CI systems. After various ppl >>> thinking travis-ci.org for a good choice Achim and I invested some >>> time today to evaluate that service and setup pax-web today [1]. And >>> TBH we're pretty impressed. Anyone with owner permissions to ops4j can >>> simply setup a travis hook to an ops4j project which will >>> automatically setup a build for the project. Once this is done the >>> entire configuration is done via a ".travis.yml" file in the root of >>> the repository. [2] is the pax-web one for example. As you see this >>> one is pretty simple to create an maintain. Travis automatically >>> builds all branches and every commit (compared to hudson where you >>> need to setup a build seperately and the single commits are gathered >>> together till no service is available and are build afterwards all >>> together). This will mean you'll get the EXACT commit where you break >>> the build; even if pushing many changes in a short time frame. Another >>> advantage is that each build is started in a completely fresh VM which >>> means that also dependency problems between projects are identified. >>> >>> Nevertheless, there is also one big disadvantage. There is no >>> possibility (as far as I see) to get a key file into the system to >>> deploy snapshots to sonatype for each build. Since there is no >>> surviving .m2 repo (and no snapshots) we'll need to either deploy >>> snapshots manually or extend the install script to checkout the right >>> branch of the related projects and build them separately (without >>> tests) before we start to build/test the main repo. >>> >>> Nevertheless, after seeing all the advantages of travis-ci I would >>> almost accept this single drawback. At least this will allow us to >>> drop another self hosted service from the list... One vulnerability >>> less! >>> >>> WDYT? >>> >>> Kind regards, >>> Andreas >>> >>> [1] http://travis-ci.org/#!/ops4j/org.ops4j.pax.web >>> [2] https://github.com/ops4j/org.ops4j.pax.web/blob/master/.travis.yml >>> >>> _______________________________________________ >>> general mailing list >>> general@lists.ops4j.org >>> http://lists.ops4j.org/mailman/listinfo/general >> >> >> ________________________________ >> >> NOTICE: This message contains privileged and confidential information >> intended only for the addressee. If you have received this message in error >> you must not disseminate, copy or take action on it; please notify >> specsavers.postmas...@specsavers.com Opinions expressed in this message are >> those of the sender and do not necessarily represent those of Specsavers. >> Although this e-mail and any attachments are believed to be virus free, >> e-mail communications are not 100% secure and Specsavers makes no warranty >> that this message is secure or virus free. All references to Specsavers >> means Specsavers Optical Superstores Limited, a company limited by shares >> and registered in England under number 1721624 of Forum 6, Parkway, Solent >> Business Park, Whiteley, Fareham, Hampshire, PO15 7PA. Nothing in this >> transmission shall or shall be deemed to constitute an offer or acceptance >> of an offer or otherwise have the effect of forming a contract by electronic >> communication. Your name and address may be stored to facilitate >> communication. >> >> ________________________________ >> . >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> > > > > -- > Toni Menzel Source > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
