Le dimanche 11 février 2018, 11:51:25 CET sebb a écrit :
> On 11 February 2018 at 09:47, Hervé BOUTEMY wrote:
> > Le dimanche 11 février 2018, 01:42:30 CET sebb a écrit :
> >> On 10 February 2018 at 21:46, Hervé BOUTEMY
wrote:
> >> > Hi,
> >> >
> >> > Is is possible to add notes on publishing t
On 11 February 2018 at 09:47, Hervé BOUTEMY wrote:
> Le dimanche 11 février 2018, 01:42:30 CET sebb a écrit :
>> On 10 February 2018 at 21:46, Hervé BOUTEMY wrote:
>> > Hi,
>> >
>> > Is is possible to add notes on publishing to svnpubsub from Jenkins,
>> > please?
>> >
>> > Gitpubsub is perfect f
Le dimanche 11 février 2018, 01:42:30 CET sebb a écrit :
> On 10 February 2018 at 21:46, Hervé BOUTEMY wrote:
> > Hi,
> >
> > Is is possible to add notes on publishing to svnpubsub from Jenkins,
> > please?
> >
> > Gitpubsub is perfect for sites that are build from only one Git repo.
> > But whe
What we do for the OpenWhisk website is the following:
We use jekyll [1] to generate the site out of markdown files
We use github repo [2] with two branches master and asf-site
We follow normal flow of using PRs, when they get merged to master a
Jenkins job that is configure with "Poll SCM" on g
On 10 February 2018 at 21:46, Hervé BOUTEMY wrote:
> Hi,
>
> Is is possible to add notes on publishing to svnpubsub from Jenkins, please?
>
> Gitpubsub is perfect for sites that are build from only one Git repo.
> But when a site mixes content from many repositories (like a main site + one
> site
Hi,
Is is possible to add notes on publishing to svnpubsub from Jenkins, please?
Gitpubsub is perfect for sites that are build from only one Git repo.
But when a site mixes content from many repositories (like a main site + one
site per component release), svnpubsub is more suited
This is for e
Notice for those using Maven to build their site that I added similar feature
in Maven Fluido Skin 1.7
you can see an example in Maven site itself, with the little edit icon in the
breadcrumb:
https://maven.apache.org/
Regards,
Hervé
Le mardi 6 février 2018, 11:31:51 CET Bertrand Delacretaz a
On Tue, Feb 6, 2018 at 10:49 AM, Lukasz Lenart wrote:
> ...The most
> important thing is a button "Edit on GitHub" [2] which can be easily
> used by everyone to create a PR with proposed changes...
Cool stuff, thanks for mentioning it!
-Bertrand
..
> [2] http://struts.apache.org/getting-started
Struts is also using Jekyll to build its website [1] (but we are still
in a process of transitioning pages from Confluence). The most
important thing is a button "Edit on GitHub" [2] which can be easily
used by everyone to create a PR with proposed changes (yes, we are
using Gitbox [3]). All the ch
Hi Chris,
my 2c, at JSPWiki we use JBake for the site generation [#1]; we started the
site adapting it from Apache Guacamole's site [#2], so if you wish to link
to a couple of examples there they are. I think it would be nice to
highlight the fact than the push must be done from some specific labe
On Feb 3, 2018 08:40, "Chris Lambertus" wrote:
... If anyone has created internal documentation for their own work with
markdown+gitpubsub, I’d love to have a link.
The internal website maintenance/build docs for Guacamole, which uses
Jekyll and gitpubsub:
https://github.com/apache/guacamole-w
Whimsy's pubsub implementation:
https://github.com/apache/whimsy/blob/master/tools/pubsub.rb
Should be easy to adapt to Jekyll
On Sat, Feb 3, 2018, 11:40 AM Chris Lambertus wrote:
> Hi folks,
>
> There has been a lot of interest lately in creating and deploying project
> sites with gitpubsub a
Hi,
PLC4X have gone down slight different path (asciidoc and maven to compile) but
it uses gitpubsub and is documented here. [1] The jenkins job is here [2].
Thanks,
Justin
1. http://plc4x.incubator.apache.org/developers/website.html
2. https://builds.apache.org/view/M-R/job/PLC4X/job/PLC4X%20S
Hi folks,
There has been a lot of interest lately in creating and deploying project sites
with gitpubsub and markdown builders like Pelican, Jekyll, etc. To date, we
have very little documentation or guidance on this approach. I’d like to fix
that by developing some documentation as a starting
14 matches
Mail list logo
