Website

[Jonathan Gallimore <jo...@gmail.com>]

Could I get some pointers on publishing the website? I guess its changed as
we don't have the CMS any more.

I have some updates I'd like to get on there, including new download links
and updating documentation. I've pushed some updates to SVN, if that helps.
:)

Jon

Re: Website

[Jonathan Gallimore <jo...@gmail.com>]

Awesome, thanks! I'll give that a shot now.

> The convenience code that does the copy and svn update needs to get
updated, but short of that there's nothing stopping a manual copy of the
generated files into a git clone and doing an add/commit/push.

We had convenience code that did that? I've been manually copying stuff
across to SVN for years!

Jon

On Wed, Oct 21, 2020 at 2:12 AM David Blevins <da...@gmail.com>
wrote:

> > On Oct 20, 2020, at 7:11 AM, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
> >
> > Could I get some pointers on publishing the website? I guess its changed
> as
> > we don't have the CMS any more.
> >
> > I have some updates I'd like to get on there, including new download
> links
> > and updating documentation. I've pushed some updates to SVN, if that
> helps.
> > :)
>
> If you can help with the documentation that'd be great.  The short version
> is everything is the same except now we publish to this git repo instead of
> SVN.
>
>  - https://github.com/apache/tomee-site-pub
>
> The convenience code that does the copy and svn update needs to get
> updated, but short of that there's nothing stopping a manual copy of the
> generated files into a git clone and doing an add/commit/push.
>
> After the push, you're done.  Just wait a bit and changes will show up.
> No need to visit https://cms.apache.org/tomee/publish anymore.
>
> Long term, Apache has a special Jenkins node that has permissions to
> publish.  Eventually we should set that up to run the generator and check
> in the new content automatically.
>
>
> -David
>
>

Re: Website

[Jonathan Gallimore <jo...@gmail.com>]

I personally have issues with all of them. GitHub actions is the one I have
the least knowledge of. If someone specifically wants to work on setting
this up on GitHub actions, there's certainly no objections from me. While I
appreciate the information in the ticket, I don't have enough knowledge to
take that and apply it. I'm happy to learn, but have a lot on the todo list
at the moment. A manual copy to the git repo is fine for now.

Jon

On Wed, Oct 21, 2020 at 5:37 AM David Jencks <da...@gmail.com>
wrote:

>
>
> > On Oct 20, 2020, at 6:11 PM, David Blevins <da...@gmail.com>
> wrote:
> >
> >> On Oct 20, 2020, at 7:11 AM, Jonathan Gallimore <
> jonathan.gallimore@gmail.com> wrote:
> >>
> >> Could I get some pointers on publishing the website? I guess its
> changed as
> >> we don't have the CMS any more.
> >>
> >> I have some updates I'd like to get on there, including new download
> links
> >> and updating documentation. I've pushed some updates to SVN, if that
> helps.
> >> :)
> >
> > If you can help with the documentation that'd be great.  The short
> version is everything is the same except now we publish to this git repo
> instead of SVN.
> >
> > - https://github.com/apache/tomee-site-pub
> >
> > The convenience code that does the copy and svn update needs to get
> updated, but short of that there's nothing stopping a manual copy of the
> generated files into a git clone and doing an add/commit/push.
> >
> > After the push, you're done.  Just wait a bit and changes will show up.
> No need to visit https://cms.apache.org/tomee/publish anymore.
> >
> > Long term, Apache has a special Jenkins node that has permissions to
> publish.  Eventually we should set that up to run the generator and check
> in the new content automatically.
> >
>
> Personally I find both jenkins and buildbot 100% incomprehensible.  It
> looks like it may be possible to use GitHub actions to publish websites;
>
>    [
> https://issues.apache.org/jira/browse/INFRA-20633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217967#comment-17217967
> <
> https://issues.apache.org/jira/browse/INFRA-20633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217967#comment-17217967>
> ]
>
> Gavin McDonald commented on INFRA-20633:
> ----------------------------------------
>
> in combination with Github Actions committing to the same repository as
> the action, to the asf-site branch, then this is possible with a built in
> GHA token. asf-site branch would then be published by configuring a
> .asf.yaml file accordingly.
>
> Example code to use for a built in GHA token:
>
> with:
>        repo-token: ${{ secrets.GITHUB_TOKEN }}
>
> Would you like to give that a try?
>
> David Jencks

Re: Website

[David Jencks <da...@gmail.com>]

> On Oct 20, 2020, at 6:11 PM, David Blevins <da...@gmail.com> wrote:
> 
>> On Oct 20, 2020, at 7:11 AM, Jonathan Gallimore <jo...@gmail.com> wrote:
>> 
>> Could I get some pointers on publishing the website? I guess its changed as
>> we don't have the CMS any more.
>> 
>> I have some updates I'd like to get on there, including new download links
>> and updating documentation. I've pushed some updates to SVN, if that helps.
>> :)
> 
> If you can help with the documentation that'd be great.  The short version is everything is the same except now we publish to this git repo instead of SVN.
> 
> - https://github.com/apache/tomee-site-pub
> 
> The convenience code that does the copy and svn update needs to get updated, but short of that there's nothing stopping a manual copy of the generated files into a git clone and doing an add/commit/push.
> 
> After the push, you're done.  Just wait a bit and changes will show up.  No need to visit https://cms.apache.org/tomee/publish anymore.
> 
> Long term, Apache has a special Jenkins node that has permissions to publish.  Eventually we should set that up to run the generator and check in the new content automatically.
> 

Personally I find both jenkins and buildbot 100% incomprehensible.  It looks like it may be possible to use GitHub actions to publish websites; 

   [ https://issues.apache.org/jira/browse/INFRA-20633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217967#comment-17217967 <https://issues.apache.org/jira/browse/INFRA-20633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217967#comment-17217967> ] 

Gavin McDonald commented on INFRA-20633:
----------------------------------------

in combination with Github Actions committing to the same repository as the action, to the asf-site branch, then this is possible with a built in GHA token. asf-site branch would then be published by configuring a .asf.yaml file accordingly.

Example code to use for a built in GHA token:

with:
       repo-token: ${{ secrets.GITHUB_TOKEN }}

Would you like to give that a try?

David Jencks

Re: Website

[David Blevins <da...@gmail.com>]

> On Oct 20, 2020, at 7:11 AM, Jonathan Gallimore <jo...@gmail.com> wrote:
> 
> Could I get some pointers on publishing the website? I guess its changed as
> we don't have the CMS any more.
> 
> I have some updates I'd like to get on there, including new download links
> and updating documentation. I've pushed some updates to SVN, if that helps.
> :)

If you can help with the documentation that'd be great.  The short version is everything is the same except now we publish to this git repo instead of SVN.

 - https://github.com/apache/tomee-site-pub

The convenience code that does the copy and svn update needs to get updated, but short of that there's nothing stopping a manual copy of the generated files into a git clone and doing an add/commit/push.

After the push, you're done.  Just wait a bit and changes will show up.  No need to visit https://cms.apache.org/tomee/publish anymore.

Long term, Apache has a special Jenkins node that has permissions to publish.  Eventually we should set that up to run the generator and check in the new content automatically.


-David