@Jean-Louis Monteiro <jlmonte...@tomitribe.com> based on the reply from Daniel Gruno, it seems ASF Jenkins don't have limitation to build upon PR's.
Daniel Gruno > <https://jira.apache.org/jira/secure/ViewProfile.jspa?name=humbedooh> added > a comment - 2 hours ago > Why not use the ASF Jenkins with the PR builder plugin? @mawiesne @Richard Thank you much for the infra offering, let's see how INFRA-17654 evolves. El mar., 15 ene. 2019 a las 4:53, Jean-Louis Monteiro (< jlmonte...@tomitribe.com>) escribió: > https://jira.apache.org/jira/browse/INFRA-17654 > > Here we go. Let's see what infra is going to answer > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Tue, Jan 15, 2019 at 11:08 AM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > It sounds wonderful. > > > > Lemme open a ticket to #infra. > > Questions I have in mind are > > > > - possible we can set up a hook to notify and external jenkins system? > > - possible to set a status back into the github repository? > > > > We recently switched to gitbox. Maybe it offers some additional services. > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Tue, Jan 15, 2019 at 10:48 AM Richard Zowalla <rich...@zowalla.com> > > wrote: > > > >> Hi, > >> > >> we could setup the following within our university infrastructure: > >> > >> Jenkins VM with 8 vCores, 4 Build-Slots with up to 24GB Ram (exclusive). > >> > >> Disk isn't that much of a problem, as it's basically SAN storage. We > >> could also use RAM-disks but we can evaluate this later, if this might > >> be a concern. > >> > >> If you like, @mawiesne and I can proceed with the initial setup & > >> hardening of the system. > >> > >> > >> Best, > >> > >> Richard > >> > >> On 15.01.19 10:31, Jean-Louis Monteiro wrote: > >> > The build takes 2+ hours on a linux system. If it's only a build > >> machine, > >> > I'd say minimum 8GB of memory. > >> > The disk is quite important as we do a lot of start/deploy/stop cycles > >> and > >> > there is therefor a lot of files accessed. > >> > > >> > The trick here is that we can't set a github hook because we don't > have > >> > permissions. We would need to ask the #infra team for advices. > >> > > >> > But if you are willing to help, I'm happy to open a ticket for you and > >> help > >> > as much as I can. > >> > > >> > > >> > > >> > > >> > > >> > -- > >> > Jean-Louis Monteiro > >> > http://twitter.com/jlouismonteiro > >> > http://www.tomitribe.com > >> > > >> > > >> > On Tue, Jan 15, 2019 at 9:59 AM Richard Zowalla <rich...@zowalla.com> > >> wrote: > >> > > >> >> Hi, > >> >> > >> >> @mawiesne and me are having a coffee discussion on the build > >> >> infrastructure topic. > >> >> > >> >> What would be the requirements for a VM / Jenkins - CI system, i.e. > the > >> >> resources you were referring to? > >> >> > >> >> Maybe we can provide such a setup within our virtual infrastructure > at > >> >> university without any costs. > >> >> > >> >> What do you think? > >> >> > >> >> Best, > >> >> > >> >> Richard > >> >> > >> >> > >> >> On 11.01.19 10:46, Jean-Louis Monteiro wrote: > >> >>> Yes this is definitely the challenge. > >> >>> We might be able to setup something around buildbot and a system > >> polling > >> >>> github for new PR. > >> >>> > >> >>> Ideal scenario would be to have a company to donate either a machine > >> or > >> >>> build time on their CI system. > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> Le jeu. 10 janv. 2019 à 16:39, César Hernández Mendoza < > >> >> cesargu...@gmail.com> > >> >>> a écrit : > >> >>> > >> >>>> Yesterday I did a quick test trying to configure Travis on my > branch > >> >> [1], > >> >>>> but it seems travis.org have a limit of 4 MB for the maven clean > >> >> install > >> >>>> output [2] > >> >>>> > >> >>>> As Jean-Louis mentioned, even with migration from buildbot to > >> Jenkins it > >> >>>> seems we can't have auto-PR test results, I recall on another > thread > >> >>>> Jonathan mentioned that one can request committer to trigger a > build > >> in > >> >>>> Jenkins like we currently do on buildbot. > >> >>>> > >> >>>> My point of view is that if we migrate to Jenkins we will > definitely > >> >> obtain > >> >>>> better UX compared with current buildbot, but auto PR testing will > >> still > >> >>>> not be possible. > >> >>>> > >> >>>> What I haven't tested is to have the tests executed in a docker > >> >> container > >> >>>> that simulates the buildbot environment, but that will end up > being a > >> >> local > >> >>>> ("It works on my machine") test instead of a test in the "real" > >> buildbot > >> >>>> environment. > >> >>>> > >> >>>> [1] > >> https://github.com/cesarhernandezgt/tomee/blob/master/.travis.yml > >> >>>> [2] The job exceeded the maximum log length, and has been > terminated. > >> >>>> > >> >>>> El jue., 10 ene. 2019 a las 9:22, Doychin Bondzhev (< > >> >> doyc...@dsoft-bg.com > >> >>>>> ) > >> >>>> escribió: > >> >>>> > >> >>>>> I'm now running full build with all tests here to see how it will > >> work > >> >>>>> here and when I have the changes on github I'll send you the > >> details. > >> >>>>> > >> >>>>> On 10.1.2019 г. 17:12, jgallimore [via TomEE & OpenEJB] wrote: > >> >>>>> > >> >>>>> We don't have a capability on ASF infrastructure to do that. Let > us > >> >> know > >> >>>>> what your branch is here, and I'm happy to get a build run on it > for > >> >> you. > >> >>>>> Jon > >> >>>>> > >> >>>>> On Thu, Jan 10, 2019 at 2:58 PM Doychin Bondzhev <[hidden email] > >> >>>>> <http:///user/SendEmail.jtp?type=node&node=4687407&i=0>> > >> >>>>> wrote: > >> >>>>> > >> >>>>>> Hi guys, > >> >>>>>> > >> >>>>>> I have set of changes that I want to test on the buildbot before > >> they > >> >>>>>> are merged into master branch. > >> >>>>>> > >> >>>>>> Is there any way to do this? The reason I want to run on the > build > >> bot > >> >>>>>> is that here all tests pass without problem but the test we > ignored > >> >>>>>> yesterday fails on the build bot. > >> >>>>>> > >> >>>>>> I want to confirm that the changes I did do make change for that > >> test > >> >>>> on > >> >>>>>> the build bot. > >> >>>>>> > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Doychin Bondzhev > >> >>>>>> dSoft-Bulgaria Ltd. > >> >>>>>> PowerPro - billing & provisioning solution for Service providers > >> >>>>>> http://www.dsoft-bg.com/ > >> >>>>>> Mobile: +359888243116 > >> >>>>>> > >> >>>>>> > >> >>>>> ------------------------------ > >> >>>>> If you reply to this email, your message will be added to the > >> >> discussion > >> >>>>> below: > >> >>>>> > >> >>>>> > >> >> > >> > http://tomee-openejb.979440.n4.nabble.com/How-to-run-test-build-on-PR-tp4687405p4687407.html > >> >>>>> To start a new topic under TomEE Dev, email > >> >>>>> ml+s979440n982480...@n4.nabble.com > >> >>>>> To unsubscribe from TomEE Dev, click here > >> >>>>> < > >> >> > >> > http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=982480&code=ZG95Y2hpbkBkc29mdC1iZy5jb218OTgyNDgwfC0xNTI2MjM5MTA3 > >> >>>>> . > >> >>>>> NAML > >> >>>>> < > >> >> > >> > http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > >> >>>>> > >> >>>>> -- > >> >>>>> Doychin Bondzhev > >> >>>>> dSoft-Bulgaria Ltd. > >> >>>>> PowerPro - billing & provisioning solution for Service > >> providershttp:// > >> >>>> www.dsoft-bg.com/ > >> >>>>> Mobile: +359888243116 > >> >>>>> > >> >>>>> > >> >>>> -- > >> >>>> Atentamente: > >> >>>> César Hernández Mendoza. > >> >>>> > >> > > > -- Atentamente: César Hernández Mendoza.
