And now it works :-) , but intermittently :-(. Jon
On 21 June 2015 at 06:59, Jon Wolfers <[email protected]> wrote: > Hi Rene, > > I am also really impressed and hope that we can find people who can > contribute machine time. > > This morning the build.netrexx.org link brings up a Jenkins dashboard > (with both netrexx and ooRexx builds), but the build.ooRexx.org link > returns "An internal server error occurred. Please try again later." > though with the Jenkins favIcon. > > hopefully a temporary glitch. > > Jon > > On 20 June 2015 at 23:47, Erich Steinböck <[email protected]> > wrote: > >> René, seeing the Jenkins stuff on build.oorexx.org, I can only say: what >> you have done is absolutely amazing! Thanks!! >> >> Regarding the built images: where would we find those? >> >> Erich >> >> On Sat, Jun 20, 2015 at 7:57 PM, René Jansen <[email protected]> wrote: >> >>> In the past few weeks there have been some improvements in the automatic >>> building of Rexx source. There is a Jenkins instance, reachable via >>> build.netrexx.org and build.oorexx.org, which coordinates the activity. >>> Jenkins is a tool for Continuous Integration, which can run build and test >>> jobs, preserve the output and make it visible, and act upon the results. We >>> distinguish two types of activity, which is a rebuild of the system >>> (netrexx or oorexx) on every commit, on the various platforms, and a >>> once-a-day rebuild from scratch, which includes making a distribution >>> package and running all tests, and rebuilding the documentation. In the >>> near future, we will also keep performance baselines, so we can see if a >>> change has regressed these for a specific platform. >>> >>> In this manner, the “build machine” has become a distributed process in >>> which one coordinating image farms out work to build nodes. This is visible >>> at the above mentioned locations. At the moment, we have six nodes, which >>> all have their own role and can build different parts of our products. >>> >>> I want to invite you to have a look and to think about whether you, or a >>> company you are affiliated to, can contribute to this setup, or not. What >>> we need at the moment are (machines that are up and running, and reachable, >>> or at least up at a predictable timeframe for us to schedule the jobs). If >>> you have such a machine, and can make a separate userid for RexxLA, we can >>> schedule building activity on it. At the moment, the most urgent need is >>> for the various types of MS-Windows, and the current Linux versions. Dave >>> Woodman has come forward to contribute the first Linux with OpenJDK image, >>> and we are very thankful for this. >>> >>> Also, I have setup a push message facility so a committer (and other >>> interested parties) can be informed of breaking builds or failing tests, by >>> email or phone alerts. >>> >>> There is enough work to be done. If you want to participate, for example >>> by donating machine time, or help to set up the right testing jobs, please >>> be in touch. I will follow up with detailed requirements for work to be >>> done for different platforms, and I will be revisiting the oorexx.org (and >>> netrexx.org) websites to contain the results of the jobs fired off by >>> the build machine, so both products will have nightly builds and fresh >>> documentation. >>> >>> We have a small group focusing on building oorexx already, so only >>> donating machine time on platforms we need is fine. Send me a private email >>> to discuss the details. >>> >>> best regards, >>> >>> René Jansen. >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> >>> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Oorexx-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> >> >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
