Set up a Github Action to build this repository with Maven and jenkins.webtide.net.

[jmcc0nn3ll]

@olamy can you setup a jenkins job that does a full build?

I think you can probably just setup env and run 'jetty-website.sh stage' and that ought to do it all.

bonus points it if is triggered on changes in the documentation subdir of the jetty project since I think that will be the primary source of errors that we want to suss out early.

[olamy]

where do we want to stage? https://stage.jetty.org/?
this means we need to put some keys somewhere to be able to scp/rsync from the staged location (github action or jenkins). I'm a bit cautious to put some keys which need to have sudo access to such location.
Maybe better to have jenkins copying to a local directory and then rsync/scp from this directory.

[jmcc0nn3ll]

No we can just stage it into the target directory which is the default of the script

…

On Sun, Jun 2, 2024, 18:33 Olivier Lamy ***@***.***> wrote: where do we want to stage? https://stage.jetty.org/? this means we need to put some keys somewhere to be able to scp/rsync from the staged location (github action or jenkins). I'm a bit cautious to put some keys which need to have sudo access to such location. — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACCXLY2GX2H4HJITUTLKJLZFOTTXAVCNFSM6AAAAABIVEEOPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUGA2TQNRQGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[olamy]

I was trying something to integrate pushing the generated content to a git repo.
PR draft here #47
The result is a bit surprising with gh-pages https://olamy.github.io/jetty.website/
weird because the content in the gh-pages branch looks correct.
hard to know the cause. some issues with directory starting _/?

[olamy]

ah right. I need a .nojekyll file at root directory

[olamy]

some POC PR created here #47

[jmcc0nn3ll]

I am still leery of having a Jenkins job publishing anything. At this point, we really just need a website build that raises red flags if the site can't be built because of bad documentation compilation.

[mojavelinux]

Now that the site is published somewhere other than GitHub Pages, perhaps GitHub Pages should be disabled on this repository. Also, I see no reason why GitHub Actions has to be publishing to GitHub Pages when the files aren't being served from there anymore. It seems like we are in a between state right now regarding what CI job is running.

[jmcc0nn3ll]

I still use the github pages build as a sanity check. We could still do the build but not actually deploy to Pages I suppose.