Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update website publication job #3759

Closed
monperrus opened this issue Jan 18, 2021 · 12 comments
Closed

update website publication job #3759

monperrus opened this issue Jan 18, 2021 · 12 comments
Labels

Comments

@monperrus
Copy link
Collaborator

Until today our website http://spoon.gforge.inria.fr was hosted on the INRIA GForge. Yes, this service will be discontinued, see https://intranet.inria.fr/Actualite/Report-a-l-ete-2021-et-plan-d-action-Arret-de-la-forge

As alternative solution, @seintur and myself have worked to move it to Github.io.

Now, the HTML pages are hosted on https://github.com/SpoonLabs/SpoonLabs.github.io/

Yet, we need to update the cron task for publishing the website, which is a Jenkins job:

@monperrus
Copy link
Collaborator Author

The job must handle both the Jekyll site in docs and the Javadoc, see #3762

@slarse
Copy link
Collaborator

slarse commented Mar 24, 2021

I'm doing some infrastructure work at the moment so I'll pick up this one, too.

@slarse
Copy link
Collaborator

slarse commented Mar 24, 2021

It took me a while to familiarize myself with Jenkins Jekyll, but now I've got it all mostly figured out. I've adapted the current deployment script to generate the new site, but I haven't written the deployment part yet.

@monperrus Should we deploy automatically to SpoonLabs/spoonlabs.github.io, or should we open pull requests (automatically) whenever the website changes?

Also, I can't find that the Javadocs for previous (stable) versions are hosted anywhere, are they? Should we to set it up such that we host the docs for, let's say, every stable release from Spoon 8 and up? Plus snapshots?

@monperrus
Copy link
Collaborator Author

that's great.

@monperrus Should we deploy automatically to SpoonLabs/spoonlabs.github.io

yes!

@slarse
Copy link
Collaborator

slarse commented Mar 25, 2021

@monperrus I've got everything working now in a simple GitHub Action workflow (simpler than Jenkins as we have the credentials at hand). Here's an automatic update example on my own fork. Note that the diff is quite large due to the switch in markdown processor (see #3859).

As the move from Travis to GHA was kind of painful, I've written the deployment script to be relatively agnostic of where it is executed. In case we need to move again. For the final revision, I'll configure the action to update the website once a day.

Before I can make the final preparations for this to work on the actual Spoon website, I need #3859, #3862 and #3863 to be merged.

@monperrus
Copy link
Collaborator Author

Thanks for the progress.

I need #3859, #3862 and #3863 to be merged.

Done

@slarse
Copy link
Collaborator

slarse commented Mar 26, 2021

FYI the new automation is ready for merge over at SpoonLabs/SpoonLabs.github.io#2

@monperrus
Copy link
Collaborator Author

Closing then!

@monperrus
Copy link
Collaborator Author

@slarse what about deleting the Jenkins job https://ci.inria.fr/sos/job/Website%20Deployer/?

@slarse
Copy link
Collaborator

slarse commented May 17, 2021

@monperrus Yep, I think we're comfortable enough with the GHA one now that the old deployer is just baggage. Will delete tomorrow morning.

@slarse
Copy link
Collaborator

slarse commented May 18, 2021

Job deleted.

@monperrus
Copy link
Collaborator Author

monperrus commented May 18, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants