I copied the SqueakTrunk workspace over to the new server at:
To the best of my knowledge, that job is ready to go.
I'll copy over the UpdateFromLastRelease material once I get a confirmation that the SqueakTrunk is working as expected. Unless David wants otherwise, I'll leave the LinuxInterpreterVM job to him.
The last thing would be to point squeakci.org to the new server.
Chris
On 19 October 2012 19:16, Chris Cunnington smalltalktelevision@gmail.com wrote:
I copied the SqueakTrunk workspace over to the new server at:
To the best of my knowledge, that job is ready to go.
The server needs git. If you crawl through the stack trace at http://173.246.101.237:8080/job/SqueakTrunk/1/console you'll see "Caused by: java.io.IOException: Cannot run program "git": java.io.IOException: error=2, No such file or directory".
Thanks very much for doing the heavy lifting, Chris!
frank
I'll copy over the UpdateFromLastRelease material once I get a confirmation that the SqueakTrunk is working as expected. Unless David wants otherwise, I'll leave the LinuxInterpreterVM job to him.
The last thing would be to point squeakci.org to the new server.
Chris
On 12-10-19 2:29 PM, Frank Shearar wrote:
On 19 October 2012 19:16, Chris Cunnington smalltalktelevision@gmail.com wrote:
I copied the SqueakTrunk workspace over to the new server at:
To the best of my knowledge, that job is ready to go.
The server needs git. If you crawl through the stack trace at http://173.246.101.237:8080/job/SqueakTrunk/1/console you'll see "Caused by: java.io.IOException: Cannot run program "git": java.io.IOException: error=2, No such file or directory".
Thanks very much for doing the heavy lifting, Chris!
frank
OK, I think that means I missed a plugin it needs. There are about four with the word "git" in the old server and I must have missed adding one in the new. That should be easy to fix. By your leave, I'll leave this to my next session playing with Jenkins. I have to turn to some other things at the moment. It sounds like it is nearly there, so that's great news.
Chris
On 19 October 2012 19:35, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:29 PM, Frank Shearar wrote:
On 19 October 2012 19:16, Chris Cunnington smalltalktelevision@gmail.com wrote:
I copied the SqueakTrunk workspace over to the new server at:
To the best of my knowledge, that job is ready to go.
The server needs git. If you crawl through the stack trace at http://173.246.101.237:8080/job/SqueakTrunk/1/console you'll see "Caused by: java.io.IOException: Cannot run program "git": java.io.IOException: error=2, No such file or directory".
Thanks very much for doing the heavy lifting, Chris!
frank
OK, I think that means I missed a plugin it needs. There are about four with the word "git" in the old server and I must have missed adding one in the new. That should be easy to fix. By your leave, I'll leave this to my next session playing with Jenkins. I have to turn to some other things at the moment. It sounds like it is nearly there, so that's great news.
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
Chris
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Chris
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
On 12-10-19 5:18 PM, Frank Shearar wrote:
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
OK, /var/lib/jenkins/workspace/SqueakTrunk is now a writable directory.
Chris
On 22 October 2012 17:27, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 5:18 PM, Frank Shearar wrote:
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
OK, /var/lib/jenkins/workspace/SqueakTrunk is now a writable directory.
Cool. We now get one step further. I think we're reworking through the setup of the first CI: we now fail when checking out the repository (in the sense that we have successfully cloned the repo, and are setting up the working contents to HEAD):
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied)
frank
Chris
On 12-10-22 12:41 PM, Frank Shearar wrote:
On 22 October 2012 17:27, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 5:18 PM, Frank Shearar wrote:
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
OK, /var/lib/jenkins/workspace/SqueakTrunk is now a writable directory.
Cool. We now get one step further. I think we're reworking through the setup of the first CI: we now fail when checking out the repository (in the sense that we have successfully cloned the repo, and are setting up the working contents to HEAD):
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied)
frank
Chris
Right. I went into Cog.app and opened some permissions for files and directories.
Chris
On 22 October 2012 17:52, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-22 12:41 PM, Frank Shearar wrote:
On 22 October 2012 17:27, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 5:18 PM, Frank Shearar wrote:
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote:
Er yes, the plugin too. (It's called "Git Plugin", but the old build server also has the "GitHub API Plugin".) I meant you probably need to "apt-get install git" on the Jenkins box because git's not installed.
frank
That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
OK, /var/lib/jenkins/workspace/SqueakTrunk is now a writable directory.
Cool. We now get one step further. I think we're reworking through the setup of the first CI: we now fail when checking out the repository (in the sense that we have successfully cloned the repo, and are setting up the working contents to HEAD):
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied)
frank
Chris
Right. I went into Cog.app and opened some permissions for files and directories.
You'd need to do so for the whole of /var/lib/jenkins/workspace/SqueakTrunk, because we're now failing because of file permissions on other files:
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied) error: unable to unlink old 'Cog.app/Contents/MacOS/Croquet' (Permission denied) error: unable to unlink old 'Cog.app/Contents/PkgInfo' (Permission denied)
frank
Chris
On 12-10-22 12:59 PM, Frank Shearar wrote:
On 22 October 2012 17:52, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-22 12:41 PM, Frank Shearar wrote:
On 22 October 2012 17:27, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 5:18 PM, Frank Shearar wrote:
On 19 October 2012 20:09, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 12-10-19 2:45 PM, Frank Shearar wrote: > Er yes, the plugin too. (It's called "Git Plugin", but the old build > server also has the "GitHub API Plugin".) I meant you probably need to > "apt-get install git" on the Jenkins box because git's not installed. > > frank > That made me laugh. Right. Actual Git.
I've apt-get'd git-core, so maybe you could try it again?
Mm, progress! I think we now have a permissions problem, in that git tries to write to somewhere/.git/FETCH_HEAD. I guess "somewhere" is the workspace Jenkins uses? http://173.246.101.237:8080/job/SqueakTrunk/5/console makes it look like it's /var/lib/jenkins/workspace/SqueakTrunk/ that needs adjusting.
frank
Chris
OK, /var/lib/jenkins/workspace/SqueakTrunk is now a writable directory.
Cool. We now get one step further. I think we're reworking through the setup of the first CI: we now fail when checking out the repository (in the sense that we have successfully cloned the repo, and are setting up the working contents to HEAD):
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied)
frank
Chris
Right. I went into Cog.app and opened some permissions for files and directories.
You'd need to do so for the whole of /var/lib/jenkins/workspace/SqueakTrunk, because we're now failing because of file permissions on other files:
Caused by: hudson.plugins.git.GitException: Command "git checkout -f 2f48b219d00362c1201db0eab1467562f8a77c1f" returned status code 1: stdout: stderr: error: unable to unlink old 'Cog.app/Contents/Info.plist' (Permission denied) error: unable to unlink old 'Cog.app/Contents/MacOS/Croquet' (Permission denied) error: unable to unlink old 'Cog.app/Contents/PkgInfo' (Permission denied)
frank
Chris
Right. I'd cleared permissions for SqueakTrunk and sundries inside that directory. I did not do it for the enclosing directory, workspace:
/var/lib/jenkins/workspace/SqueakTrunk
Chris
On Fri, Oct 19, 2012 at 02:16:10PM -0400, Chris Cunnington wrote:
I copied the SqueakTrunk workspace over to the new server at:
To the best of my knowledge, that job is ready to go.
I'll copy over the UpdateFromLastRelease material once I get a confirmation that the SqueakTrunk is working as expected. Unless David wants otherwise, I'll leave the LinuxInterpreterVM job to him.
Thanks, that sounds fine. I know zero about Jenkins at this point, so I may need to ask some dumb questions.
Meanwhile, I'm not sure what is permitted on this server, but to do the VM build we would need a Subversion client (svn), the CMake build system, and the normal Linux development tools (gcc and friends).
Are these things that can be installed on box3?
Dave
On 12-10-19 3:26 PM, David T. Lewis wrote:
Thanks, that sounds fine. I know zero about Jenkins at this point, so I may need to ask some dumb questions.
Meanwhile, I'm not sure what is permitted on this server, but to do the VM build we would need a Subversion client (svn), the CMake build system, and the normal Linux development tools (gcc and friends).
Are these things that can be installed on box3?
Dave
I wasn't sure, so I checked the rule book. I think I found a listing:
Rule #22.2.12
If the VM Team leader needs anything at anytime for any purpose on a server that is the process of being configured, he may forthwith load any and all such tools, libraries, and appurtenances with expediency.
The book was dusty, but I'm willing to bet the rule still stands.
I'm quite sure you have the confidence of myself, Ken, and every member of the Squeak Board. Please proceed.
Chris
On Fri, Oct 19, 2012 at 03:33:42PM -0400, Chris Cunnington wrote:
On 12-10-19 3:26 PM, David T. Lewis wrote:
Thanks, that sounds fine. I know zero about Jenkins at this point, so I may need to ask some dumb questions.
Meanwhile, I'm not sure what is permitted on this server, but to do the VM build we would need a Subversion client (svn), the CMake build system, and the normal Linux development tools (gcc and friends).
Are these things that can be installed on box3?
Dave
I wasn't sure, so I checked the rule book. I think I found a listing:
Rule #22.2.12
If the VM Team leader needs anything at anytime for any purpose on a server that is the process of being configured, he may forthwith load any and all such tools, libraries, and appurtenances with expediency.
ha! ;-)
Thanks for that, it made my day.
The book was dusty, but I'm willing to bet the rule still stands.
I'm quite sure you have the confidence of myself, Ken, and every member of the Squeak Board. Please proceed.
I'll try setting things up within the next few days. I will need sudo for installing packages, can someone please add me to /etc/sudoers?
Thanks again, Dave
On 10/19/2012 02:45 PM, David T. Lewis wrote:
I'll try setting things up within the next few days. I will need sudo for installing packages, can someone please add me to /etc/sudoers?
Thanks again, Dave
Oops, I missed a step. You now should have sudo rights. By the way I'm doing this on the new server (box3) by add the relevant users to the sudo group rather than modifying /etc/sudoers. This is meant to be one of the 3 steps when adding a user, I guess I should really wrap it in in a shell script.
Also, regarding installing packages. Always think twice but ultimately if it is needed then it is needed and you should install. In general I would suggest always doing what needs to be done while giving a bit of thought to how much trouble it will be to fix or undo if anyone has a complaint.
BUT, please record all changes to the system at some reasonable level of detail in the file /root/admin-log.txt. You can find existing entries for examples. This is a continuation of a long time habit within the box-admins team and an often useful one when you forget how you did something the last time (like forgetting to add you to the sudo group). Or if you need to figure out who to blame and when they did it. :)
Ken
On Fri, Oct 19, 2012 at 04:13:09PM -0500, Ken Causey wrote:
On 10/19/2012 02:45 PM, David T. Lewis wrote:
I'll try setting things up within the next few days. I will need sudo for installing packages, can someone please add me to /etc/sudoers?
Thanks again, Dave
Oops, I missed a step. You now should have sudo rights. By the way I'm doing this on the new server (box3) by add the relevant users to the sudo group rather than modifying /etc/sudoers. This is meant to be one of the 3 steps when adding a user, I guess I should really wrap it in in a shell script.
Also, regarding installing packages. Always think twice but ultimately if it is needed then it is needed and you should install. In general I would suggest always doing what needs to be done while giving a bit of thought to how much trouble it will be to fix or undo if anyone has a complaint.
BUT, please record all changes to the system at some reasonable level of detail in the file /root/admin-log.txt. You can find existing entries for examples. This is a continuation of a long time habit within the box-admins team and an often useful one when you forget how you did something the last time (like forgetting to add you to the sudo group). Or if you need to figure out who to blame and when they did it. :)
Thanks Ken,
I've installed enough packages to support a basic VM build, details in /root/admin-log.txt. Progress so far: here is the output from a VM regenerating itself from a Squeak image on box3:
lewis@box3-squeak:~/VMUnixBuild$ squeak -nodisplay Squeak4.3.image VMUnixBuild.st CHECKING squeakvm 2012-10-20T04:49:48.494+02:00: starting VM builder image 2012-10-20T04:49:48.494000001+02:00: begin install OSProcess 2012-10-20T04:49:58.923+02:00: install OSProcess complete 2012-10-20T04:49:58.923000001+02:00: begin install CommandShell 2012-10-20T04:50:08.735+02:00: install CommandShell complete 2012-10-20T04:50:08.941+02:00: Subversion is installed on this system 2012-10-20T04:50:08.941000001+02:00: save ./src directory if it exists 2012-10-20T04:50:09.431+02:00: update ./platforms from repository 2012-10-20T04:50:10.072+02:00: platforms source update complete 2012-10-20T04:50:10.072000001+02:00: begin install VMMaker (trunk) 2012-10-20T04:52:45.562+02:00: install VMMaker complete 2012-10-20T04:52:46.121+02:00: generate all sources 2012-10-20T04:53:36.601+02:00: source generation complete 2012-10-20T04:53:36.601000001+02:00: create build directory ./build 2012-10-20T04:53:37.262+02:00: cd to build, then run ../platforms/unix/cmake/configure --src=../src 2012-10-20T04:53:46.91+02:00: configure completed successfully 2012-10-20T04:53:46.910000001+02:00: begin make 2012-10-20T04:55:05.302+02:00: make completed with successful VM build 2012-10-20T04:55:05.302000001+02:00: to install, cd to ./build and do "make install" 2012-10-20T04:55:05.401+02:00: create build directory ./build64 2012-10-20T04:55:05.981+02:00: cd to build64, then run ../platforms/unix/cmake/configure --src=../src --image64 2012-10-20T04:55:14.521+02:00: configure completed successfully 2012-10-20T04:55:14.521000001+02:00: begin make 2012-10-20T04:56:38.422+02:00: make completed with successful VM build 2012-10-20T04:56:38.422000001+02:00: to install, cd to ./build and do "make install" 2012-10-20T04:56:38.519+02:00: platform sources are in ./platforms 2012-10-20T04:56:38.519000001+02:00: generated sources are in ./src 2012-10-20T04:56:38.519000002+02:00: VM build is in ./build 2012-10-20T04:56:38.519000003+02:00: to install the VM, cd to ./build and type make install 2012-10-20T04:56:38.519000004+02:00: VM for 64-bit images is is in ./build 2012-10-20T04:56:38.519000005+02:00: to install the VM for 64-bit images, cd to ./build64 and type make install 2012-10-20T04:56:38.52+02:00: both versions of the VM can be installed on the same machine 2012-10-20T04:56:38.520000001+02:00: the squeak script (normally /usr/local/bin/squeak) determines the VM to use 2012-10-20T04:56:39.691000001+02:00: VM builder image complete after 0:00:06:51.198 2012-10-20T04:56:39.691000002+02:00: source generation and VM build complete 2012-10-20T04:56:39.691000003+02:00: exiting image lewis@box3-squeak:~/VMUnixBuild$
box-admins@lists.squeakfoundation.org