www.eclipse.org/jetty.git Migration to GitLab

Looks like you are taking requests to migrate services over to this from git.eclipse.org so if you are moving website repositories we would be happy to participate.

Unless you support moving that repo to Github of course but I don't think that was an option.

We're still unsure of the direction for web content -- we're tracking that planning via issue #1 (closed). We're also contemplating the usage of GitLab pages (via #2 (closed))

marked this issue as related to #2 (closed)

removed the relation with #2 (closed)

marked this issue as related to #2 (closed)

It's currently possible to use Gitlab for the source code of your website. We recently migrated the eclipse.org/dash website to Eclipse GitLab a few months ago: https://gitlab.eclipse.org/eclipse/dash/dash-website

That project was built using our hugo-eclipsefdn-website-boilerplate project which aims to help our projects build a Hugo website using Eclipse Infrastructure.

This is how it works:

The website source code repo has a Jenkins file that defines how to build the website. Once the website is built, we use Jenkins to push the build to the www.eclipse.org/${PROJECT_NAME} repo. For Jetty, that would be www.eclipse.org/jetty.git

added Migration label

At this point our jetty.git repo is fine to deploy straight over. We used to have another repo that built and site and update the jetty.git repo, but we fairly recently switched to just use your solstice setup directly.

My workflow just needs to be commit into this repo and have it deploy within a reasonable timeframe.

Also, I really don't need the history for this repository, it would be best if we could just take the latest version and dump it into a fresh repository.

assigned to @mward

Appologies as this clearly got lost somewhere in the past year.

Is Jetty still interested in moving to Gitlab or would you prefer to remain on Github?

We are at github now so might as well stay there. thanks!

closed