You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2020/04/03 10:41:31 UTC

FYI, community.a.o site with Hugo/Git (mostly) works

Hi,

Thank you very much Roy for this work (details below),  I just tested
the new website build and it looks good to me!

I added a link to https://github.com/apache/comdev-site to the footer
of http://community.apache.org/

The README of https://github.com/apache/comdev-site has all the
information and links on how to edit and publish the website, so from
now on that URL is the only thing one needs to know to update the
website.

The only thing that didn't work for me is the automatic trigger of the
Jenkins build after pushing my changes to
https://github.com/apache/comdev-site - not sure why but manually
triggering the build job worked.

Thanks again Roy for your great work!

-Bertrand

On Tue, Mar 31, 2020 at 6:07 PM Roy Lenferink <rl...@apache.org> wrote:
>
> I agree the PR [1] is ready to be merged (no conflicts anymore and minor differences are resolved as
> well now). Also, merging the pull requests doesn't automatically switch over serving of community.a.o
> from svn to git. It will only be served from git after [2] is merged.
>
> So what I'd suggest:
> - merge [1],
> - create a Jenkins job which updates the asf-site branch after changes to the 'master' branch are
> made (I'll do this)
> - then merge [2] and start serving community.a.o from git :)
>
> [1] https://github.com/apache/comdev-site/pull/5
> [2] https://github.com/apache/infrastructure-puppet/pull/1753 ...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Re: FYI, community.a.o site with Hugo/Git (mostly) works

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Tue, Apr 7, 2020 at 1:44 PM Rich Bowen <rb...@rcbowen.com> wrote:
>... +1. It is no longer needed.

ok, I have created https://issues.apache.org/jira/browse/INFRA-20087
to have it deleted.

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Re: FYI, community.a.o site with Hugo/Git (mostly) works

Posted by Rich Bowen <rb...@rcbowen.com>.
On Mon, Apr 6, 2020, 05:11 Bertrand Delacretaz <bd...@apache.org>
wrote:

> Hi,
>
> On Sun, Apr 5, 2020 at 5:13 PM Roy Lenferink <rl...@apache.org>
> wrote:
> > ...Another thing I noticed on this topic is the comdev-wwwsite [1]
> repository. It seems it was once
> > requested as playground for converting the site to Pelican.Is this
> repository still needed otherwise we
> > might as well delete it (to prevent possible confusions like this [2])...
>
> +1 - Rich I think you created that repository, do you agree with deleting
> it?
>
> As per https://gitbox.apache.org/ we have to create a jira ticket to do
> that.
>

+1. It is no longer needed.

>

Re: FYI, community.a.o site with Hugo/Git (mostly) works

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Sun, Apr 5, 2020 at 5:13 PM Roy Lenferink <rl...@apache.org> wrote:
> ...Another thing I noticed on this topic is the comdev-wwwsite [1] repository. It seems it was once
> requested as playground for converting the site to Pelican.Is this repository still needed otherwise we
> might as well delete it (to prevent possible confusions like this [2])...

+1 - Rich I think you created that repository, do you agree with deleting it?

As per https://gitbox.apache.org/ we have to create a jira ticket to do that.

-Bertrand

>
> [1] https://github.com/apache/comdev-wwwsite
> [2] https://issues.apache.org/jira/browse/INFRA-20009?focusedCommentId=17065576&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17065576

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


RE: FYI, community.a.o site with Hugo/Git (mostly) works

Posted by Roy Lenferink <rl...@apache.org>.
Thanks for verifying the taken steps Bertrand :)
The community.a.o entry has been removed from cms.a.o as well now.

Another thing I noticed on this topic is the comdev-wwwsite [1] repository. It seems it was once 
requested as playground for converting the site to Pelican.Is this repository still needed otherwise we 
might as well delete it (to prevent possible confusions like this [2]).

[1] https://github.com/apache/comdev-wwwsite
[2] https://issues.apache.org/jira/browse/INFRA-20009?focusedCommentId=17065576&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17065576

On 2020/04/03 10:41:31, Bertrand Delacretaz <bd...@apache.org> wrote: 
> Hi,
> 
> Thank you very much Roy for this work (details below),  I just tested
> the new website build and it looks good to me!
> 
> I added a link to https://github.com/apache/comdev-site to the footer
> of http://community.apache.org/
> 
> The README of https://github.com/apache/comdev-site has all the
> information and links on how to edit and publish the website, so from
> now on that URL is the only thing one needs to know to update the
> website.
> 
> The only thing that didn't work for me is the automatic trigger of the
> Jenkins build after pushing my changes to
> https://github.com/apache/comdev-site - not sure why but manually
> triggering the build job worked.
> 
> Thanks again Roy for your great work!
> 
> -Bertrand
> 
> On Tue, Mar 31, 2020 at 6:07 PM Roy Lenferink <rl...@apache.org> wrote:
> >
> > I agree the PR [1] is ready to be merged (no conflicts anymore and minor differences are resolved as
> > well now). Also, merging the pull requests doesn't automatically switch over serving of community.a.o
> > from svn to git. It will only be served from git after [2] is merged.
> >
> > So what I'd suggest:
> > - merge [1],
> > - create a Jenkins job which updates the asf-site branch after changes to the 'master' branch are
> > made (I'll do this)
> > - then merge [2] and start serving community.a.o from git :)
> >
> > [1] https://github.com/apache/comdev-site/pull/5
> > [2] https://github.com/apache/infrastructure-puppet/pull/1753 ...
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org


Re: FYI, community.a.o site with Hugo/Git (mostly) works

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Apr 3, 2020 at 12:41 PM Bertrand Delacretaz
<bd...@apache.org> wrote:
> ...The only thing that didn't work for me is the automatic trigger of the
> Jenkins build after pushing my changes to
> https://github.com/apache/comdev-site ...

I tried again and that works, but with a lag of about 10 minutes.

The Impatient with Sufficient Karma can still trigger the build
manually, the Hugo build is very fast!

-Bertrand

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org