www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From shath...@e-z.net
Subject Re: Fwd: Migrate to svnpubsub and buildbot - what's possible?
Date Thu, 13 Sep 2012 16:07:03 GMT
> L.S.,
>
> Forwarding these questions to the builds@ mailing list - perhaps
> someone here can help us out with the build related questions about
> what is possible with buildbot with regards to getting our
> documentation/website builds automated?
>
> Thanks,
>
> Gert
>
>
>
> ---------- Forwarded message ----------
> From: Gert Vanthienen <gert.vanthienen@gmail.com>
> Date: Fri, Sep 7, 2012 at 5:22 PM
> Subject: Migrate to svnpubsub and buildbot - what's possible?
> To: infrastructure <infrastructure@apache.org>
>
>
> L.S.,
>
> At the Apache ServiceMix project, we're preparing to migrate our
> website and documentation to svnpubsub.  Both the contents for the
> website and documentation are being generated using Maven and we can
> change our builds to allow our committers to deploy the site to an SVN
> location.
>
> However, during the discussion, Dan Kulp also pointed out another
> solution that would avoid the deploy step, by using buildbot to
> rebuild the contents automatically for us on checkin.  Before we setup
> our builds to generate contents in an external directory for use in
> buildbot, we have a few more questions.
>
> We are using two external tools for building our documentation pages:
> Pygments to generate CSS markup for code highlighting and Prince XML
> to generate PDF documents.  Is either one of these already supported
> on the buildbot machines or should we look into using pure
> Maven/Java-based alternatives for them?
>
> Also, the documentation project contains two branches (for
> version-based documentation) and the website main contents is coming
> from another project.  Can buildbot be set up to run those build
> separately and publish into another subdirectory of the website or
> would it be better to try and create a unified build for everything?
>
>
> Thanks,
>
> Gert
>
>

Hi,

We at Apache Xalan have recently implemented "svnpubsub" for publishing
our website content.

Any website construction tools can be used to edit your website
content.  You should do your website edits outside of the "svnpubsub"
so you can review your work, and then publish the reviewed
artifacts to the "svnpubsub" directory when satisfied with your
website appearance and functionality.

Initial website setup:

Copy the website artifacts to any subversion directory under your TLP.
Notify INFRA that you are ready to have that directory become the
"svnpubsub" publishing repository for your Apache TLP website.

Website Maintenance:

Your sub-projects can separately publish their website artifacts
to sub-directories under your "svnpubsub" TLP website registry.

It is important to edit, build, and generate your website artifacts
outside of the "svnpubsub" directory.  This allows for content
and functionality review.  When the artifacts are complete, then
copy them to the appropriate path in your website "svnpubsub"
repository tree.

Any svn check-in to your "svnpubsub" will trigger an Apache website
update to the public facing pages.

--

As for buildbot issues:  I am reasonably ignorant of their
configuration.

Sincerely,
Steven J. Hathaway
Xalan Documentation Project



Mime
View raw message