Community
Participate
Working Groups
The projects SAT and DeviceKit have been moved from OHF to the Equinox runtime under /cvsroot/rt/org.eclipse.equinox/incubator/soda, please refer to the bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=297405 So can you include SAT and DK in the equinox download site under http://download.eclipse.org/equinox/? Thanks
What bundles are to be added to our build? How are they to be built - standalone bundles, feature, product build? (I just briefly looked at the RT equinox incubator soda bundles).
The DeviceKit is built with an update site in the workspace. When DeviceKit was under OHF, we built the DeviceKit update site in a local workspace, then ftpe the update site to the folder "/home/data/httpd/download.eclipse.org/technology/ohf/soda/dk/update-site/weekly35" on host "download1.eclipse.org". I expect we can do the similar things under the new location, right?
We may need to rethink how we build incubator stuff (and other things in Equinox in general that are not a part of the eclipse SDK). For example, we may want to consider a separate build that can do incubator stuff. We plan to discuss this at the Equinox call tomorrow. Ruibin and Simon, could you attend the meeting to discuss? http://wiki.eclipse.org/Equinox/Meeting_Minutes
Yes, I will join the call, thank. Ruibin
At the equinox call we decided not to include the SAT/DeviceKit content in the current Equinox/Eclipse build. Here is a summary of the reasons: * We noted that adding more and more to the overall Eclipse project SDK build only increases our failure rate for producing Eclipse SDK builds on time. The recent failures caused by equinox weaving is a good example. * It is not right to add everything into one build if the built content of the project really has no relationship with the Eclipse project SDK. We think it would be much better to set such projects up as independent builds. * The DeviceKit builds currently have a rather complicated and manual build process and it does not sound like it will easily integrate into the overall Eclipse Build. We want to investigate setting put separate builds for SAT and DeviceKit. This may be an ideal opportunity to investigate setting up a Hudson build so we can start separating out builds of the different content from Equinox. Ruibin and Simon from DeviceKit and SAT should investigate setting up automated builds on Hudson and publishing the builds under their respective folders under http://download.eclipse.org/equinox/ Kim, Can you help point to some instructions for Hudson at Eclipse and hopefully provide some guidance to Ruibin and Simon for setting a Hudson build for DeviceKit and SAT. I suggest starting with SAT since I think that is a relatively simple set of bundles to build. I am hoping such guidance would be less of an impact to the Eclipse releng team than trying to integrate more and more stuff from Equinox into the overall Eclipse build.
Well, this sounds like a good approach. It makes sense to have Equinox incubator bundles in a separate build that is small and fast. SAT and DeviceKit teams, I would suggest looking at using the templates in the Dash Athena common builder to build your bundles as it includes Hudson support. Basically, Athena provides templates that you could fill out with the location of your bundles, build options etc. Here's the getting started guide for Athena http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started Here's the getting started guide for Athena with Hudson. http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson I have admin rights on build.eclipse.org's Hudson so I can create your job when you are ready. After this is working, we'll need to create cron jobs to copy the results of your build to the appropriate location on the equinox portion of download.eclipse.org. Hudson can't write to download.eclipse.org for security reasons. I assume that you will have a separate p2 repository from that of the Equinox/Eclipse build. Tom, is this a correct assumption? SAT and DeviceKit teams, let me know if you need help at any time during this process. Also, I have commit right on Dash Athena if there are use cases in your build that aren't currently supported, I might be able to help in this area too. Good luck!
(In reply to comment #6) > After this is working, we'll need to create cron jobs to copy the results of > your build to the appropriate location on the equinox portion of > download.eclipse.org. Hudson can't write to download.eclipse.org for security > reasons. I assume that you will have a separate p2 repository from that of the > Equinox/Eclipse build. Tom, is this a correct assumption? That is my assumption. Perhaps we will want a single p2 repository for all incubator things we build with Hudson. Do you think that is possible?
Yes, I think this would be possible. I think it would be a good idea to move other incubator bundles out once we have the SAT and DeviceKit build working.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
