On 11 July 2011 19:53, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Great, thank you,
what about to create wiki page with configuration descriptions?
what you meant by configuration descriptions? you mean job descriptions? Like: "This job runs a, b then c" ?
What exact VM version does the CI server use?
pretty old one: ./squeak -version 4.4.7-2357 #1 XShm Sun Jan 23 18:17:31 PST 2011 gcc 4.3.2 Linux vps2.piumarta.com 2.6.18-028stab053.10-ent #1 SMP Thu Feb 28 20:34:08 MSK 2008 i686 GNU/Linux plugin path: /builds/vm/lib/squeak/4.4.7-2357 [default: /builds/vm/lib/squeak/4.4.7-2357/]
-- Pavel
On Mon, Jul 11, 2011 at 7:19 PM, Igor Stasenko <siguctua@gmail.com> wrote:
Hello,
i put an initial version of build scripts which used by hudson/jenkins to gitorious:
git://gitorious.org/pharo-build/pharo-build.git
I modified build.sh script to work well with this set up. So, instead of locating scripts on slave, a job takes them from "Scripts download" job, which just takes them from git. (https://ci.lille.inria.fr/pharo/job/Scripts%20download/)
The rest is as usual - run scripts and see what happens. I added a job to build Pharo 1.4 using new set up.. after couple bugs, it seems to be working well: https://ci.lille.inria.fr/pharo/job/new%20scripts%20Pharo%201.4/
so, we should migrate all jobs to use these scripts , which is publicly available through git.. so, we don't need to manually manage these files on server anymore.
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.