Eclipse Github organisation move for technology.lsp4e

As part of our ongoing efforts to improve security and allow more self service for projects, we are moving project repositories from the Github Eclipse organisation to individual per-project organisations[1].

We will use pre-existing project organisations when available, otherwise new ones will be created with the eclipse-projectshortname(ie: eclipse-babel) format.

Github provides redirects for moves like this, so the process should be fairly smooth. That said, committers will need to update any local repositories and build jobs to point at the new remote URL locations once the move is done.

If your project needs to adjust the timing, or has another organisation it would like to use, we can discuss that here.

If we have not heard from the project by the due date, Webmaster will simply complete the move and refer the project to the EMO team who will confirm that the project is still active.

[1]#3571

/cc @rmisingnameu3r /cc @mistria

changed due date to January 20, 2025

added IT-prioritymedium IT-severitylow Migration team:infra + 1 deleted label

assigned to @chills2023

changed the description

Moving ASAP is fine by me, not even waiting for the due date.

Moving is fine for me as well.

added service:GitHub label and removed 1 deleted label

@mistria @rmisingnameu3r Repo has been moved to the new organization https://github.com/eclipse-lsp4e commiters will gain access once our sync tools run (~3-4 hours). @heurtemattes can you please enable Otterdog?

assigned to @heurtemattes

CI integration with GitHub is currently broken:

FATAL: Failed to recompute children of lsp4e-github
org.kohsuke.github.HttpException: {"message":"Must have push access to view collaborator permission.","documentation_url":"https://docs.github.com/rest/collaborators/collaborators#get-repository-permissions-for-a-user","status":"403"}
	at PluginClassLoader for github-api//org.kohsuke.github.GitHubConnectorResponseErrorHandler$1.onError(GitHubConnectorResponseErrorHandler.java:72)
	at PluginClassLoader for github-api//org.kohsuke.github.GitHubClient.detectKnownErrors(GitHubClient.java:504)
	at PluginClassLoader for github-api//org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:464)
	at PluginClassLoader for github-api//org.kohsuke.github.GitHubClient.sendRequest(GitHubClient.java:427)
	at PluginClassLoader for github-api//org.kohsuke.github.Requester.fetch(Requester.java:85)
	at PluginClassLoader for github-api//org.kohsuke.github.GHRepository.getPermission(GHRepository.java:1118)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$1.fetch(GitHubSCMSource.java:1052)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceRequest.getPermissions(GitHubSCMSourceRequest.java:460)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.ForkPullRequestDiscoveryTrait$TrustPermission.checkTrusted(ForkPullRequestDiscoveryTrait.java:327)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.ForkPullRequestDiscoveryTrait$TrustPermission.checkTrusted(ForkPullRequestDiscoveryTrait.java:316)
	at PluginClassLoader for scm-api//jenkins.scm.api.trait.SCMHeadAuthority.isTrusted(SCMHeadAuthority.java:101)
	at PluginClassLoader for scm-api//jenkins.scm.api.trait.SCMSourceRequest.isTrusted(SCMSourceRequest.java:213)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$4.create(GitHubSCMSource.java:1282)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$4.create(GitHubSCMSource.java:1276)
	at PluginClassLoader for scm-api//jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:339)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrievePullRequest(GitHubSCMSource.java:1273)
	at PluginClassLoader for github-branch-source//org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:1113)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMSource._retrieve(SCMSource.java:372)
	at PluginClassLoader for scm-api//jenkins.scm.api.SCMSource.fetch(SCMSource.java:282)
	at PluginClassLoader for branch-api//jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:662)
	at PluginClassLoader for cloudbees-folder//com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:269)
	at PluginClassLoader for cloudbees-folder//com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:167)
	at PluginClassLoader for branch-api//jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1065)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:446)
Finished: FAILURE

and this is blocking development. Anything we need to do on project end?

@fgurr @heurtemattes any idea?

eclipse-lsp4e-bot was not invited to the new GH org yet.

This is usually done as part of the otterdog setup, but since this has not happened yet, it was missing.

I've invited the bot. Otterdog setup will follow soon.

@mistria where did you see the error message?

In the "Scan repository log"

Nut this is all working now, thank you!

@heurtemattes is Otterdog enabled for this org?

Otterdog has been enabled for the eclipse-lsp4e organization.

The following repo has been created: https://github.com/eclipse-lsp4e/.eclipsefdn

You can find the current configuration at https://github.com/eclipse-lsp4e/.eclipsefdn/blob/main/otterdog/eclipse-lsp4e.jsonnet

A dashboard UI of the configuration can also be accessed at https://eclipse-lsp4e.github.io/.eclipsefdn/ which also provides a playground to test snippets before making a PR. When you want to suggest changes, fork the repo, make changes and create a PR. A workflow will automatically run and show you the changes that will be applied and validate that the configuration is correctly formatted and composed.

The documentation of all supported settings can be found here: https://otterdog.readthedocs.io/en/latest/reference/resource-format/

A list of all Eclipse projects that have it also enabled can be accessed here: https://eclipsefdn.github.io/otterdog-configs/ That is often quite helpful to get ideas about how others do their configurations.

You can also navigate to https://otterdog.eclipse.org/projects/technology.lsp4e to get more insights for your project in a dashboard like view.

If you have any problems, let us know.

closed