[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [babel-dev] Build configuration for babel plugins
|
Hi Martin,
That is great news. You guys are moving very fast!
The next steps would be to:
a) sign your plugins using the Foundation's signing infrastructure. The
Foundation provides an internal web service for easy signing [1]
however, as I understand it, a maven plugin is available to facilitate
this step from within Hudson. Signing is entirely optional at this
time; however, signing plugins is a Goog Thing, and if we (Babel) wish
to join the annual release train, signing becomes mandatory. If you'd
like to investigate signing, perhaps a quick question on the cbi-dev
mailing list [2] can save you a ton of time here. I personally don't
know the best way to sign from within Hudson.
b) create a p2 repository. This can likely be done from within your
Hudson job, or you could request another job for packaging/assembly.
Again, as I am not a developer, I don't know the best way to do this
from maven artifacts, but the folks on the cbi-dev (or the
cross-project-issues-dev) mailing lists are always happy to help.
c) copying the p2 repo onto the downloads area
(http://download.eclipse.org). Eclipse Webmasters don't encourage the
practice of allowing Hudson to publish build output directly to the
downloads area, but some projects go this route anyway for simplicity.
Most projects maintain a cron job on build.eclipse.org that will monitor
Hudson and copy build output to the appropriate place, depending on a
nightly build, or a formal release.
This download location for Babel is:
build.eclipse.org:/home/data/httpd/download.eclipse.org/technology/babel
Our translation p2 repos are in update-site/ -- feel free to create a
directory there for your tapiji repos. I notice you have a valid SSH
shell on build.eclipse.org, so please feel free to look around
d) once the p2 repo is in place, we'll edit the Babel project download
page (http://eclipse.org/babel/downloads.php) to include the plugins.
That page is quite heavy, so we can examine options for making the
plugins very visible. I'll work with you and Kit when you get there.
I hope most of this makes sense :) As usual, I'm here to assist if
you need help.
[1]
http://wiki.eclipse.org/IT_Infrastructure_Doc#JAR_files_from_a_web_service_.28Instant.29
[2] https://dev.eclipse.org/mailman/listinfo/cbi-dev
On 11/28/2012 05:52 AM, Martin Reiterer wrote:
Hi Denis,
configuring the tycho build was much easier than working with PDE
Build. Moreover, it allows to configure a target platform without the
need of downloading delta-packs. Great!
Now I've configured our new tycho based build at hudson:
https://hudson.eclipse.org/hudson/job/babel-tools-indigo/
Please, can you guide me through the process of publishing our
artifacts on the build server?
thx,
Martin
On 11/19/2012 10:25 PM, Denis Roy wrote:
Hi Martin,
Tycho is the technology used by the Common Build initiative at
eclipse.org (http://wiki.eclipse.org/CBI). CBI will soon be used to
build the Eclipse Platform, the backbone of our community downloads.
If you're going to start fresh, I would suggest Tycho.
You can also use the Eclipse Hudson CI environment
(https://hudson.eclipse.org) to run your builds. To request a new
job, simply file a bug against Eclipse Foundation > Community > Hudson.
If you need pointers on using tycho or running builds, the cbi-dev
mailing list is a great resource, as is the cross-project-issues-dev
mailing list. I don't know much about builds other than running the
servers.
https://dev.eclipse.org/mailman/listinfo/cbi-dev
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Once your builds are up and running, downloadable plugins must be put
on the build server. I can guide you through that process -- its
very easy.
Denis
On 11/19/2012 12:35 PM, Martin Reiterer wrote:
Hi,
I'm currently working on creating build scripts for the babel
messages editor and the I18N tool suite. Therefore, I defined a
headless build by making use of PDE Build [0]. For fetching the
build sources from GIT, I installed the EGIT pde extension [1] into
my target platform.
This way seems to me a little bit complex and assumes that we have
installed the EGIT pde fetchfactory and an appropriate target
platform. Moreover, I explored the Eclipse Buckminster [2] and Tycho
project [3]. Both provide an alternative approach for building
Eclipse features. Tycho also provides integration with maven. Is
there a recommended way for eclipse (especially for babel) projects,
how to setup a headless build?
[0] http://www.eclipse.org/pde/pde-build
[1] https://github.com/eclipse/egit-pde
[2] http://www.eclipse.org/buckminster
[3] http://eclipse.org/tycho
thanks,
Martin
