Additional Build-Node for Windows on ARM
Hello.
I'd like to help getting Eclipse and SWT ported to Windows on ARM by providing a build node for the project for a few months until a more permanent solution is available.
server description: Windows 11 22H2 22621, aarch64, 200 GB of available storage space, 10GB of memory
user name: runnerPlease add it to https://ci.eclipse.org/releng/job/eclipse.platform.swt/
I'll leave the name up do maintainers here. In GIMP, when I was helping that project in the past. They called it "Hernan's ARM runner"
Since this is not a beefy machine, I think we should let it do only one concurrent build for now.
See discussion at https://github.com/eclipse-platform/eclipse.platform.swt/issues/1019
Where can I download agent.jar?
Activity
What's the version of Java that the master node is running? I don't have access to https://ci.eclipse.org/releng/job/eclipse.platform.swt/ to be able to look at that information myself.
@hmartinez82 many thanks, the agent jar will be usually copied automatically by the Jenkins master if the connection is setup. For Java versions Java 17 will be needed.
If you want to do some preliminary tests, you can look here https://github.com/eclipse-platform/eclipse.platform.swt/blob/master/.github/workflows/maven.yml how a build is running currently on the additional Github nodes.
Edited by Christoph Laeubrich@claeubrich Sorry then I'm very lost here. I thought that this whole thing started by me downloading agent.jar and running it locally with the master node parameters. I have no knowledge of starting a Jenkins agent any other way
Do you have instructions how to connect to the master node? I already installed Java 17. That video with instructions also begins with downloading agent.jar from the master node.
Also, is there an IRC or Slack channel for SWT?
Edited by Hernan Martinez-
I created a user + added the master Jenkins SSH key and IT staff did the rest but as it was a linux machine the setup is probably different for windows, I'm sure you will soon receive some additional information about that from @fgurr .
added IT-prioritylow IT-severitylow service:jenkins statetodo team:releng labels
@hmartinez82, thank you for your willingness to support the SWT project. Your generosity and eagerness to contribute are greatly appreciated.
However, we must decline the offer to connect external machines to our production systems. As much as we value community contributions, the security of our projects and infrastructure is our top priority. Connecting an external machine, regardless of intent, poses significant security risks. This situation would not be very different from connecting a USB stick found in a coffee shop to a company laptop—a practice fraught with potential security vulnerabilities.
That said, your enthusiasm and readiness to help are truly appreciated. We encourage you to assist in making the necessary changes to build SWT on the Windows ARM architecture. Your contributions in this area would be beneficial to the project.
Meanwhile, @claeubrich, I suggest exploring the possibility of obtaining a Windows ARM agent by leveraging resources through an Eclipse Foundation member: https://github.com/eclipse-cbi/cbi/wiki#additional-resources.
Thank you all for your understanding.
No hard feelings. I understand.
https://www.eclipse.org/membership/showMember.php?member_id=1196 or https://www.eclipse.org/membership/showMember.php?member_id=823 should be able to get the project two or three Windows DevKits.
The GIMP project which is a much smaller project than Eclipse was able to get some :)
Edited by Hernan Martinez
-
@mbarbero I must confess I'm really confused here... adding a build node does not "connects" something to "the infrastructure", in fact it is the other way round, you give quite much control to the one you donate this as the Jenkins master is able to execute arbitrary commands on this machine while the reverse is not possible in any way. So @hmartinez82 should be concerned that EF is maybe burning is CPU for mining bitcoins...
Also please note that this was done before here:
Furthermore we are waiting literally for years but the EF is not capable of providing a single ARM node see:
- https://github.com/adoptium/adoptium-support/issues/616
- https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/issues/597
On the other hand there is now a FORK(!) of the whole Eclipse platform driven by an individual to supply with (unofficial) Eclipse for Windows ARM:
so who should "donate" us such runner then even if we found any strategic member? Even worse as per your document
Those resources are assigned as a whole to a single project (i.e., we can’t split resources across multiple projects).
So it would mean we need a total of at least (if not more) 5 dedicated contributions from strategic members (SWT, Platform, Equinox, aggregator, adoptium)... this completely blocks adoption of Windows ARM platform for Eclipse IDE!
In any case if there are concerns, please then consider to take @hmartinez82 gentle offer and take the required actions to connect his machine as a Github self-hosted runner:
so we can at least compile the code so if we can't test and ship it at least we don't need to handle this by single persons and missing valuable discussions and improvements like this one:
The GIMP project which is a much smaller project than Eclipse was able to get some
So true I'm really stunned...
FYI @jograham the Eclipse IDE WG FYI @akurtakov as project lead of SWT project
Edited by Christoph Laeubrich
