[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [jwt-dev] Documentation and build updates
|
Hi Mickael,
yes, this seems a good solution. With that not only the persons who
currently have the submissions can login and test, but maybe at another time
point we can give these credentials also to other persons to check that.
Will you ask the webmaster?
Thanks and best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 08 January 2009 17:42
An: Java Workflow Toolbox
Betreff: Re: [jwt-dev] Documentation and build updates
Hello (again),
Since build.eclipse.org runs a X server, it is now used for testing (added
"export DISPLAY=localhost:1.0" in build.sh to use this X server by default).
That means that:
* You don't require a X server on your local machine, nor to connect using
"ssh -X"
* Build now takes 4 to 8 minutes instead of 10 to 15.
Still is remaining the permissions problem. Some projects (php and wtp) have
a custom user that they use for builds (phpBuild and wtpBuild). I wonder
whether we could also have a jwtBuild user, that we could all use for
builds. If this solution seems good for you, I'll ask Denis on this topic.
Regards
Mickael
Mickael Istria a écrit :
> Hello,
>
> I've made some improvements on the build process and related
> documentations
>
> Build process update:
> * Releng folder was refactored
> * Used a new base for building (see
> http://wiki.eclipse.org/JWT_Automatic_Build#JWT_build_minimal_Eclipse_
> base
> )
> * build scripts now runs tests BUT
> ** running tests on Eclipse server requires you to have an Xserver on
> your local machine (see
> http://wiki.eclipse.org/JWT_Automatic_Build#Requirements )
> ** Build now takes around 10 minutes
> ** Still the permission problems reported by Florian on bug 259578
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=259578>
> * The build scripts creates a clone of the build base and adds to it
> newly built JWT features and plugins, then runs the test scripts
> (org.eclipse.jwt/releng/jwt-tests-plugin/test.xml)
> * A test report is published on the update site (see
> http://download.eclipse.org/technology/jwt/integration-update-site/ )
>
> Documentation about build:
> The page
> http://wiki.eclipse.org/JWT_Automatic_Build#Adding_new_plugins_to_the_
> JWT_release explains how to include new plugins into the build process
>
> Documentation about Bug fixing:
> I writed a little checklist of things that should be done in order to
> solve a bug. Since the build now handles automated testing, this
> strategy encourages Test Driven Development to ensure that we'll get
> more and more non-regression tests.
> http://wiki.eclipse.org/JWT_DeveloperFAQ#How_to_nicely_fix_a_bug.3F
>
>
> If you have any correction or precision to give to this documentation,
> do not hesitate to edit it.
>
> Regards,
> Mickael
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jwt-dev
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
