Final Steps

[jmcc0nn3ll]

As we are heading into the deployment of the jetty.org site, I wanted to open this issue to identify and track the final steps we need to take. AFAICT

• Resolve Add router extension to redirect inbound requests from old URL #21 with the rewrite handler on jetty.org
• Check in with Eclipse IP about repo transfer
• Migrate this jetty.website to the jetty GitHub organization
• Sort out where to publish a ui-bundle artifact
• Find and wire up contribution guide
• api.jetty.org -> javadoc.jetty.org (update cert, fix jetty setup, populate with @olamy javadoc repo)
• Set up a Github Action to build this repository with Maven and jenkins.webtide.net. #45
• Push the build results into the jetty.org static site on our amazon webtide.com property
• Notify Eclipse to place a 301 redirect on eclipse.dev/jetty

Anything else?

[jmcc0nn3ll]

@olamy @sbordet We need to decide once and for all how the build results from this repository are going to be pulled or pushed to jetty.org

1. cron job on jetty.org pulls the _ghpages branch from here where we use the Actions @mojavelinux setup
2. jenkins build job that is triggered via action
3. ??

[jmcc0nn3ll]

Issue for coordinating with Eclipse on the redirect: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4602

[mojavelinux]

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

The command you need to run can be found in the current GitHub Actions workflow. See

https://github.com/webtide/jetty.website/blob/main/.github/workflows/publish-site.yml#L47-L52

Note that the ANTORA_CACHE_DIR environment variable is required for the time being.

[mojavelinux]

There is something missing from the list. You will need a build to produce and publish the UI bundle. An alternative is to build the UI bundle in the same job that generates the site. In other words, produce the UI bundle from source each time the site is generated. There's nothing wrong with that, though it makes it harder to test the site locally since there is no UI bundle at a publicly accessible URL.

[jmcc0nn3ll]

Eclipse IP issue to make sure they are fine with transferring this over. https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/14595

[jmcc0nn3ll]

Well, It would appear that transferring the repository is a non-starter, we can not give eclipsewebmaster access to our company organization. @mojavelinux are you ok with my just hooking up a remote to a repo in the jetty organization and transferring repo content over? We'll lose the issue history.

[joakime]

couldn't we (webtide) transfer this to github.com/jetty-project/ and then do the Eclipse IP from there to github.com/jetty/

[jmcc0nn3ll]

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4620#note_2245138

looks like we might get away with just rights to the repo itself.

[jmcc0nn3ll]

This repository has been moved to the jetty organization.

[jmcc0nn3ll]

Trying to sort out how to have the UI artifact published here now.

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4627

[mojavelinux]

This repository was set up with the understanding that we would be using GitHub. Switching to GitLab requires that the CI workflows be redeveloped. This is not a quick fix.

[jmcc0nn3ll]

Gitlab is not my intention at all; that is just where I have to interact with the Eclipse webmasters. The linked issue is my trying to sort out the organization secret deal/otterdog goop with them so we can publish the UI artifact here.

[mojavelinux]

My mistake. When you said "published here now" then linked to GitLab, my mind jumped to the fact that you were trying to do it on GitLab. I get it now.

[mojavelinux]

Are we still waiting on anything to merge the PRs with the migrated content?

[jmcc0nn3ll]

@sbordet ?

We just had to stage a release for 10 and 11 for a client, but I am personally not aware of anything else pending.

[jmcc0nn3ll]

@olamy pls populate /var/www/javadoc.jetty.org with the content you were working on

[olamy]

we might need more space on disk :)

[jmcc0nn3ll]

some back and forth on the #23 but good to close out this issue, finally!

[mojavelinux]

Hooray! 🎉 Congratulations on a successful migration!