I have set up a basic hudson server on [1]. Expect changes to the setup, but initially it does give som small benefits.
[2] should be the current trunk version of dhis.war, [3] should list the pdf versions of current documentation. I´m not sure how useful it is, but snapshot builds of all service jar artifacts is also published to [4]. When I get it going, I will also try out auto-deploying the current trunk version build to [5].
While I´m at it, I might as well mention that the plan is for [6] to run a demo of the currently released version and [7] to work as a staging server for release candidates. But we would like to create a better demo data set before we officially announce those.
On Tue, Nov 17, 2009 at 9:55 PM, Jo Størset storset@gmail.com wrote:
Hi,
I have set up a basic hudson server on [1]. Expect changes to the setup, but initially it does give som small benefits.
[2] should be the current trunk version of dhis.war, [3] should list the pdf versions of current documentation. I´m not sure how useful it is, but snapshot builds of all service jar artifacts is also published to [4]. When I get it going, I will also try out auto-deploying the current trunk version build to [5].
While I´m at it, I might as well mention that the plan is for [6] to run a demo of the currently released version and [7] to work as a staging server for release candidates. But we would like to create a better demo data set before we officially announce those.
The auto-built .war file and documentation could then be linked from dhis2.org downloads site under a “Nightly builds” section or something, that would be very useful.
I have set up a basic hudson server on [1]. Expect changes to the setup, but initially it does give som small benefits.
[2] should be the current trunk version of dhis.war, [3] should list the pdf versions of current documentation. I´m not sure how useful it is, but snapshot builds of all service jar artifacts is also published to [4]. When I get it going, I will also try out auto-deploying the current trunk version build to [5].
While I´m at it, I might as well mention that the plan is for [6] to run a demo of the currently released version and [7] to work as a staging server for release candidates. But we would like to create a better demo data set before we officially announce those.
I have set up a basic hudson server on [1]. Expect changes to the setup, but initially it does give som small benefits.
[2] should be the current trunk version of dhis.war, [3] should list the pdf versions of current documentation. I´m not sure how useful it is, but snapshot builds of all service jar artifacts is also published to [4]. When I get it going, I will also try out auto-deploying the current trunk version build to [5].
While I´m at it, I might as well mention that the plan is for [6] to run a demo of the currently released version and [7] to work as a staging server for release candidates. But we would like to create a better demo data set before we officially announce those.
The auto-built .war file and documentation could then be linked from dhis2.org downloads site under a “Nightly builds” section or something, that would be very useful.
I have set up a basic hudson server on [1]. Expect changes to the setup, but initially it does give som small benefits.
[2] should be the current trunk version of dhis.war, [3] should list the pdf versions of current documentation. I´m not sure how useful it is, but snapshot builds of all service jar artifacts is also published to [4]. When I get it going, I will also try out auto-deploying the current trunk version build to [5].
While I´m at it, I might as well mention that the plan is for [6] to run a demo of the currently released version and [7] to work as a staging server for release candidates. But we would like to create a better demo data set before we officially announce those.
The auto-built .war file and documentation could then be linked from dhis2.org downloads site under a “Nightly builds” section or something, that would be very useful.
It seems like a great resource, especially for the documentation. I
will revert to the devs for how often the app should be built, but I
think it would be fantastic to have the documentation being built
continuously, with links to the dhis2.com (and various other sites) as
appropriate.
···
On Wed, Nov 18, 2009 at 12:50 AM, Jo Størset <storset@gmail.com> wrote:
Den 17. nov. 2009 kl. 23.38 skrev Knut Staring:
DHIS2 App Hub does not work yet, otherwise the links are fine.