The content history is now in tomee-site-pub.  I added an .asf.yaml file:

```
notifications:
  commits: [email protected]
  issues: [email protected]
  pullrequests: [email protected]
  jira_options: link label link label

# this staging config will publish any commits to 
https://tomee-beta.staged.apache.org
#staging:
#  profile: beta
#  whoami: master
```

that directs mail to [email protected].

Mail notifications are turned back on.

For reference, here’s how far I’ve got with publishing the Aries site:

```
#!/bin/bash

npm run clean-install

rm -rf build
mkdir -p build/site
# clone the aries-site-pub repo
(
cd build/site
git clone --depth 1 [email protected]:apache/aries-site-pub.git .
git rm -r .
)

npm run build-noclean

(
cd build/site
git add .
git commit -m "site build"
git push origin master
)
```

This is for an Antora-only site; the site build is actually `npm run 
build-noclean`.  So far I only know how to run this locally, buildbot and 
jenkins remain mysteries to me.  I don’t see why this couldn’t be run on GitHub 
using GitHub actions, but it might be against infra policy.

David Jencks

> On Aug 27, 2020, at 9:51 PM, David Jencks <[email protected]> wrote:
> 
> Maybe my memory’s just a bit slow.
> 
> svn log https://svn.apache.org/repos/infra/websites/production/tomee/content 
> <https://svn.apache.org/repos/infra/websites/production/tomee/content> shows 
> that I’ve found the last commit.
> 
> David Jencks
> 
>> On Aug 27, 2020, at 9:47 PM, David Jencks <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> I’m afraid I no longer understand how svn works or how to see what’s in it.  
>> I can’t find the published site on viewvc.
>> 
>> The last imported-to-git revision I got was 
>> 
>> commit d971bdc415a5aacedad7a73bfc59a72abe0ddc09 (HEAD -> master, svn/trunk)
>> Author: Daniel Gruno <[email protected] <mailto:[email protected]>>
>> Date:   Mon Aug 10 17:53:26 2020 +0000
>> 
>>     Publishing svnmucc operation to tomee site by humbedooh
>>     
>>     git-svn-id: 
>> https://svn.apache.org/repos/infra/websites/production/tomee/content@1064188 
>> <https://svn.apache.org/repos/infra/websites/production/tomee/content@1064188>
>>  90ea9780-b833-de11-8433-001ec94261de
>> 
>> 
>> however there appeared to be a git gc error after that.  I can’t figure out 
>> how to confirm that this is indeed the last site commit, although running 
>> the svn2git command again doesn’t find anything more.
>> 
>> What I can find in https://svn.apache.org/viewvc/tomee/site/trunk/?view=log 
>> <https://svn.apache.org/viewvc/tomee/site/trunk/?view=log> is
>> 
>> Revision 1880750 
>> <https://svn.apache.org/viewvc?view=revision&revision=1880750> - Directory 
>> Listing <https://svn.apache.org/viewvc/tomee/site/trunk/?pathrev=1880750> 
>> Modified Mon Aug 10 17:17:31 2020 UTC (2 weeks, 3 days ago) by dblevins
>> force cms to update
>> so the time frame seems approximately right.
>> 
>> Can anyone confirm I’ve got the whole history?
>> 
>> Thanks
>> David Jencks
>> 
>>> On Aug 27, 2020, at 7:44 PM, David Jencks <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> tomee-site-pub created
>>> [email protected] <mailto:[email protected]> requested
>>> INFRA-20781 <https://issues.apache.org/jira/browse/INFRA-20781> (disable 
>>> commit emails) opened
>>> svn2git still in process.
>>> 
>>> If things go really quickly I might be able to push tomorrow.
>>> 
>>> David Jencks
>>> 
>>>> On Aug 27, 2020, at 4:42 PM, David Blevins <[email protected] 
>>>> <mailto:[email protected]>> wrote:
>>>> 
>>>>> On Aug 27, 2020, at 1:58 PM, David Jencks <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> I’ve been “warming up” with the Aries website and did this recently for 
>>>>> them.  I think I can do this easily.  What do we want the TomEE repo to 
>>>>> be named? I’d suggest tomee-site-pub.
>>>> 
>>>> I was struggling to think of a good name.  `tomee-site-pub` is great!
>>>> 
>>>>> On Aug 27, 2020, at 2:11 PM, David Jencks <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> I started…. should be done in a few hours.  Next step is to create the 
>>>>> apache git repo using self-serve and ask infra to turn off commit emails 
>>>>> for the push (which may take a day or so).
>>>>> 
>>>>> Where should commit emails for this repo go?  For aries I created a 
>>>>> [email protected] <mailto:[email protected]> list since I 
>>>>> don’t think anyone is interested in looking at the html changes directly. 
>>>>>  Should I ask for such a list for TomEE?  Sending the emails there is 
>>>>> configured with the .asf.yaml file in the root of the repo.
>>>> 
>>>> I think site-pub@ is another very good suggestion.
>>>> 
>>>> Thank you so much for taking this one up, David!
>>>> 
>>>> I'm pretty excited to ditch the CMS!  The last publish I did took hours of 
>>>> checking/poking and prodding just to get the updates to go live as the 
>>>> commit size was so large and there are 2 repos to go through.  It'll be 
>>>> wonderful to be done with that.
>>>> 
>>>> 
>>>> -David
>>>> 
>>> 
>> 
> 

Reply via email to