I have been doing a POC on a new publishing method using the Budget
website. We are able to build the site and need to do some CSS cleanup
I believe that we will be able to publish in AsciiDoc if we so desire,
On Thu, Apr 6, 2017, at 01:23 AM, Jeff Fearn wrote:
> On 6/4/17 02:07, Kevin Fenzi wrote:
> > On 03/06/2017 05:17 AM, Petr Kovar wrote:
> >> I'm afraid we don't have the same Publican web site data in
> >> https://pagure.io
/docs-fp-o/ that used to be in
> >> https://git.fedorahosted.org/cgit/docs/web.git/log/
(which is no longer
> >> available).
> >> Unless we get the data back from the old web.git repo, we won't
> >> be able to publish any new Publican content to
> >> http://docs.fedoraproject.org/
, as documented in
> >> http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
> > I can get the data back if you like. We still have it available.
> >> I guess we should set up a temporary web.git repo in pagure and update the
> >> publish scripts for http://docs.fedoraproject.org/
> > ok. If someone does this, please let me know so I can change the pull
> > location in infrastructure.
> > It just seems bad to me that we currently don't have any way of updating
> > that content and don't seem to have the new setup ready yet.
> If the system replacing publican isn't ready then it might be worth
> considering a less cumbersome way of using publican for fdocs.
> I think it'd be reasonably easy to get jenkins  to build the books,
> say using a git trigger, rebuild the site, and push the site out to the
> web head ... assuming ACLs can be set up to grant jenkins rights to scp
> to the right place (assumes using  there are plenty of other plugins
> for publishing artifacts).
> This way you just push/tag the right way in the books/brands source
> repos and some time later it appears on the site without the
> intermediate git repo even existing. If it all goes pear shaped and you
> need to regenerate the site from scratch for some reason, you just
> manually trigger the scp or the builds as required.
> Extra bonus is that Jenkins has EL7/F25 hosts, so you can switch to a
> newer publican without affecting the infra team as the generated site is
> OS agnostic, so no changes need to occur on the docs web hosts.
> There maybe some effort required to fix books though as there are some
> incompatibilities between older XML and publican major versions.
> Cheers, Jeff.
> 1: https://jenkins.fedorainfracloud.org/
> 2: https://wiki.jenkins-ci.org/display/JENKINS/SCP+plugin
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
> Email had 1 attachment:
> + signature.asc
> 1k (application/pgp-signature)