May I ask why "netbeans-vm"? This name makes no sense to me.

On Mon, Nov 12, 2018 at 1:12 PM Antonio <[email protected]> wrote:

> Hi,
>
> So infra suggested using ci.apache.org.
>
> Do we want to use that or not? Maybe we would build the artifacts using
> our current jenkins setup and them transfer those to
> netbeans-vm.apache.org?
>
> Now that the domains are operated within the ASF we could redirect
> bits.netbeans.org to a virtual server inside netbeans-vm.apache.org.
>
> Thoughts?
>
> Cheers,
> Antonio
>
> El 12/11/2018 a las 11:47, Eric Barboni escribió:
> > Thanks for the work Antonio
> >
> >   Where should we help and what we can do now?
> >
> > Regards
> > Eric
> > -----Message d'origine-----
> > De : Antonio <[email protected]>
> > Envoyé : mercredi 7 novembre 2018 14:13
> > À : [email protected]
> > Objet : Re: bits.netbeans.org / javadocs / mavenutils
> >
> > Hi Eric,
> >
> > I think the point is that javadoc is published automatically. For
> instance, for the apex-core project, see
> >
> >
> https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.4/index.html
> >
> > Anyway feel free to ask whatever questions you consider to the JIRA
> ticket with Infra. They know more than I do :-)
> >
> > Cheers,
> > Antonio
> >
> >
> > El 07/11/2018 a las 11:54, Eric Barboni escribió:
> >> Hi Antonio
> >>    I did not get the point here. What is the difference using between
> build.apache.org vs buildbot.apache ? Why do we need another type of ci ?
> >>
> >> Regards
> >> Eric
> >>
> >> -----Message d'origine-----
> >> De : Antonio <[email protected]>
> >> Envoyé : mercredi 7 novembre 2018 01:26 À :
> >> [email protected] Objet : Re: bits.netbeans.org /
> >> javadocs / mavenutils
> >>
> >> Hi all,
> >>
> >> Gavin from infra is suggesting [1] that we use the Apache buildbot [2]
> to generate javadocs and other stuff (JNLP/Maven).
> >>
> >> I think it's a great idea, is it ok if I request one of these for us
> and we give it a go?
> >>
> >> Cheers,
> >> Antonio
> >>
> >> [1]
> >> https://issues.apache.org/jira/browse/INFRA-17202
> >>
> >> [2]
> >> https://ci.apache.org/projects/
> >>
> >> El 2/11/18 a las 18:48, Antonio escribió:
> >>> Hi,
> >>>
> >>> javadoc.tgz is just an example binary, probably not very
> representative.
> >>>
> >>> The real problem arises when we want to host _development_ maven
> >>> artifacts or JNLP binaries. That is big, and we just can't do that
> >>> each eight hours using a git branch, I think.
> >>>
> >>> For releases I'd suggest:
> >>>
> >>> - Creating javadoc.tgz and distributing it along the rest of release
> >>> binaries through the mirror system, as sources are. This may require
> >>> chaning the release process.
> >>> - Publishing the javadoc at netbeans.apache.org under an appropriate
> >>> 9.0/10.0 subdirectory.
> >>> - Linking from bits.netbeans.org back to netbeans.apache.org for
> >>> these javadoc.
> >>>
> >>> Thoughts?
> >>>
> >>> Thanks,
> >>> Antonio
> >>>
> >>>
> >>> El 2/11/18 a las 18:19, Neil C Smith escribió:
> >>>> On Fri, 2 Nov 2018 at 16:52, Antonio <[email protected]> wrote:
> >>>>> Generating a 51Mb. binary file and hosting it in a git branch each
> >>>>> eight hours simply won't scale.
> >>>>
> >>>> No kidding! :-)
> >>>>
> >>>> This is meant to be a short term fix for hosting release Javadocs,
> >>>> and possibly dev Javadocs with your date fix, and will proxy back to
> >>>> Oracle hosting for anything not there.  Of course, that's not
> >>>> necessarily useful here.
> >>>>
> >>>> But do we need that .tgz generated anyway?  Maybe a .tgz of the
> >>>> release docs on the mirror system alongside the release, which was
> >>>> discussed previously, is enough?
> >>>>
> >>>> Incidentally, speaking of release Javadoc, we should work out how to
> >>>> build those for NB10.  I had to manually edit some files for the
> >>>> NB9.0 ones.
> >>>>
> >>>> Best wishes,
> >>>>
> >>>> Neil
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> - To unsubscribe, e-mail:
> >>>> [email protected]
> >>>> For additional commands, e-mail:
> >>>> [email protected]
> >>>>
> >>>> For further information about the NetBeans mailing lists, visit:
> >>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>>
> >>>>
> >>>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail:
> >> [email protected]
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail:
> >> [email protected]
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Reply via email to