bzr-eclipse team mailing list archive

[Piotr Piastucki <piastucki@xxxxxxxxx>]

Hi,

I added some comments in LP as I see a couple of (rather minor) issues
in the patch yet I like the idea of automating over documenting very
much :)
BTW, there is no need to create a symlink, just make sure
bzr-xmloutput is checked out into xmloutput folder inside plugins
folder and BZR_PLUGIN_PATH points to plugins folder. Bazaar should be
able to look up xmloutput automatically in this case.

Regarding the CI server, I set it up the way it exposes all the
interesting build artifacts - see Last Successful Artifacts:
1) bzr-java-lib.jar
http://185-5-96-190.greendata.pl/job/bzr-java-lib/
2) bzr-eclipse update site  - "Latest bzr-eclipse build" in left menu or
http://185-5-96-190.greendata.pl/job/bzr-eclipse/lastSuccessfulBuild/artifact/org.vcs.bazaar.eclipse.site/target/site/

Both jar & Eclipse update site available on Ci server should be fully
functional, the only difference between the CI server and the builds I
make manually from time to time is the JDK used to create them. CI
server uses OpenJDK while I use Oracle JDK on my machine. However, it
is not a problem to install Oracle JDK on the CI server too.

Should you have any further questions or want to play with the Jenkins
server please let me know.

Cheers,
Piotr


On Mon, May 20, 2013 at 6:20 AM, Alexander Taler <alex@xxxxxxxxxxxxx> wrote:
>
> Hi Piotr, thanks for the feedback,
>
>   > 1) When I remove bzr-java-lib from .classpath in ui plugin I get no errors
>
> Hmm, looks like you're right. I'll try it out for a bit and then
> commit it.
>
>   > 2) Do we really need the changes in bzr-java-lib?  BZR_PLUGIN_PATH is yet
>   > anothr environment variable you can set before running maven build e.g.:
>   > export BZR_PLUGIN_PATH=/xxxxx. I use this approach both on my local machine
>   > and on CI server (http://185-5-96-190.greendata.pl/). This way I can easily
>   > run bzr-java-lib tests against various xmloutput versions stored in
>   > different folders just by changing a single env variable.
>
> My goal was to make the setup as straightforward as possible.
>
> Using the environment requires a few extra manual steps: create
> "plugins" directory, create symlink xmloutput -> bzr-xmloutput,
> and export variable BZR_PLUGIN_PATH.
>
> Perhaps we should discuss how it's packaged (my other mail) and
> then use the same solution here.
>
> Can I add a link to the CI server on the wiki page?  Can we use
> it for doing installs of the trunk?
>
> Alex
>
> --
> idereal | deliver                       http://idereal.co.nz/
> Get your software to market sooner      022 659 0282