I think I asked the wrong question. I’d like to understand:
- where the human-edited website source is,
- where the generated source is and what it’s generated from and how
- the process by which this eventually gets to the asf-site branch of the
openwebbeans-site repo.
> On Aug 5, 2021, at 1:26 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote:
>
> Le jeu. 5 août 2021 à 20:54, David Jencks <david.a.jen...@gmail.com> a
> écrit :
>
>> What process updates the content?
>>
>
> We have an asf.yaml but didnt see it used fast enough so pushed directly in
> main branch the html files.
>
>
>
>> Personally I think it’s weird to have a site repo that combines html and
>> markdown with some process that builds the markdown to html.
>>
>
> We dont need the md to html part i think.
>
>
>> Would cloning at depth 1 alleviate your concerns?
>>
>
> Can i push after? Got trouble with that years ago.
This Jenkinsfile script seems to be working great for Aries and Felix with an
Antora build:
stages {
stage('build') {
steps {
sh 'rm -rf build'
// clone the felix-site-pub repo
sh 'git clone --depth 1 --branch asf-staging
https://gitbox.apache.org/repos/asf/felix-site-pub.git build/site'
dir('build/site') {
sh 'git rm -r .'
}
sh 'npm run clean-install'
sh 'npm run build-noclean'
dir('build/site') {
sh 'git add .'
sh 'echo `git commit -m "site build"`'
sh 'git push
https://gitbox.apache.org/repos/asf/felix-site-pub.git asf-staging'
}
}
}
}
What I like about this approach is that the website is built complete each time
from some kind of source and the initial ‘git rm -r’ makes sure there is no
leftover outdated content that is no longer being generated.
>
> If publishing is done by CI what’s the problem with cloning the whole repo?
>>
>
> Does not scale and blocks/slows down too much publishing after some time,
> must stay straight forward IMHO since we dont do it often and should be
> locally reproducable.
I don’t understand. If you clone with depth 1 then you are only fetching the
last version of the site, which is likely to be approximately the same size as
the new version of the site.
AFAICT the only way to get a predictable result is to have a process to build
the entire website from sources, in which case there’s no need to locally clone
the site repo since only CI should be actually updating it.
I might be biased from my Antora experiences.
David Jencks
>
>
>
>> David Jencks
>>
>>> On Aug 5, 2021, at 6:31 AM, Romain Manni-Bucau <rmannibu...@gmail.com>
>> wrote:
>>>
>>> Hi all,
>>>
>>> AFAIK we migrated our site to
>> https://github.com/apache/openwebbeans-site
>>>
>>> It is ok until we want to publish the content. Until now we were
>> publishing
>>> it to subfolders directly (like meecrowave one) but now it is on git i'm
>>> not sure how to setup the publish-scm or other plugin.
>>> What i'd like to avoid is to clone the full git repo to modify meecrowave
>>> folder and then commit/push it.
>>>
>>> Any idea?
>>>
>>> Side note: worse case we can go back on svn if there is no clean
>> solution,
>>> it does not impact the dev process so the simplest is the best here IMHO.
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>>> <
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>>>
>>
>>
