Community
Participate
Working Groups
Please provide JIPP for 'codewind' and grant write access to the download area and code repositories.
FYI, initial contribution CQ's are opened. 1. Initial Contribution of Codewind's Eclipse plugin https://dev.eclipse.org/ipzilla/show_bug.cgi?id=19843 2. Initial Contribution of Codewind's VSCode extension https://dev.eclipse.org/ipzilla/show_bug.cgi?id=19886
We've our initial contribution now for codewind-vscode and would like to build- can you provision our JIPP or let us know what else might be required from us in order to set it up? https://github.com/eclipse/codewind-vscode Thanks!
I had some issues provisioning it this morning. Thanks for your patience, I'll get this done soon.
Thanks Denis!
Please also install the NodeJS and GitHub Branch Source plugins onto the new instance. https://plugins.jenkins.io/nodejs https://plugins.jenkins.io/github-branch-source
We'll have this here for you shortly, thanks for your patience: https://ci.eclipse.org/codewind
The Packager JIPP on Jiro is available here now: => https://ci.eclipse.org/codewind Publishing to download.eclipse.org requires access via SCP. We've added the credentials to the JIPP. Please see https://wiki.eclipse.org/Jenkins#How_do_I_deploy_artifacts_to_download.eclipse.org.3F for more info. To simplify setting up jobs on our cluster-based infra, we provide a "migration" pod template that can also be used with Freestyle jobs. The pod template has the label "migration" which can be specified in the job configuration under "Restrict where this project can be run". The image should contain most of the dependencies that were available on the hipp machines on the old infra. It's set up in your new JIPP, please test it, if necessary. Requested plugins have been installed.
(In reply to Mikaël Barbero from comment #7) > The Packager JIPP on Jiro is available here now: My bad, I meant the Codewind JIPP
(In reply to Mikaël Barbero from comment #8) > (In reply to Mikaël Barbero from comment #7) > > The Packager JIPP on Jiro is available here now: > > My bad, I meant the Codewind JIPP We tried it out and unable to build with the JIPP due to build executors for codewind are offline/suspended and halt with 'Waiting for next available executor' - we opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=548074. Something we've not configured or set up properly?