[cle-release-team] Release failures via Jenkins - please release sitestats

[Steve Swinsburg]

Ok the release now works via Jenkins.

cheers.


On Fri, Mar 8, 2013 at 12:54 PM, Matthew Jones <matthew at longsight.com>wrote:

> I remember installing svn from source because it the version in the
> repositories was old (1.6) and missing some tools that I needed for the
> release scripts.  Though, wonder why it's .bash_rc and .bashrc, I'm pretty
> sure this worked.
>
> I renamed to .bashrc, no luck. There's a project "cle-release-sample" that
> I release often and use to test.
>
> "When Jenkins connects to a computer, it goes to the sh shell, and not
> the bash shell (at least this is what I have noticed - I may be wrong).
> So any changes you make to $PATH in your bashrc file are not considered."
> -
> http://stackoverflow.com/questions/5818403/jenkins-hudson-environment-variables
> I added path as an environment variable in Jenkins and looks to be
> working. Could have sworn I did this last time though as this link was
> highlighted already.
>
> You have to wipe out your workspace or it gives the error
>
> "svn: E155036: Working copy '/var/lib/jenkins/jobs/cle-release-sample/workspace/trunk' is too old (format 10, created by Subversion 1.6)"
>
>
> I ran this script to just wipe out all workspaces. (
> https://wiki.jenkins-ci.org/display/JENKINS/Wipe+out+workspaces+of+all+jobs)
> So it should be good to go. At least the sample released.
>
> Anyway: If you want to try to write up something to do the release of an
> individual or all tools VIA the command line, please add it to confluence
> (either as new steps or a new page!
> https://confluence.sakaiproject.org/display/REL/Sakai+CLE+release+guide )
> I'm in agreement that Jenkins currently adds to the complexity.
>
>
>
> On Thu, Mar 7, 2013 at 8:10 AM, Matthew Buckett <
> matthew.buckett at it.ox.ac.uk> wrote:
>
>> On Thu, Mar 7, 2013 at 12:29 PM, Steve Swinsburg
>> <steve.swinsburg at gmail.com> wrote:
>> > Still no good:
>>
>> Jenkins has it's path set to:
>>
>>
>> PATH=/home/hudson/maven-2.2.1/bin:/usr/java/jdk1.6.0_24//bin:/usr/java/jdk1.6.0_24//bin:/sbin:/usr/sbin:/bin:/usr/bin
>>
>> svn is in:
>>
>> [mbuckett at builds ~]$ which svn
>> /usr/local/bin/svn
>>
>> which looks to have been installed on the 8th of Feb:
>>
>> -bash-3.2$ ls -l /usr/local/bin/svn
>> -rwxr-xr-x 1 root root 662571 Feb  8 18:10 /usr/local/bin/svn
>>
>> and in /root there's /root/subversion-1.7.8 which has matching dates.
>>
>> Looking back at old successful releases you can see svn command working:
>>
>> http://builds.sakaiproject.org:8080/job/sitestats%202.3.x/40/consoleFull
>>
>> and /usr/local/bin/svn wasn't on the path.
>>
>> I think what's probably happened is that the subversion rpm has been
>> removed and a local install has been made to /usr/local but jenkins
>> doesn't have that on it's path. I noticed there's:
>>
>> -bash-3.2$ ls -l ~jenkins/.bash_rc
>> -rw-r--r-- 1 jenkins jenkins 336 Mar  6 12:08 /var/lib/jenkins/.bash_rc
>>
>> and that set's the path to include /usr/local/bin
>>
>> which I think should probably be .bashrc instead.
>>
>> --
>>   Matthew Buckett, VLE Developer, IT Services, University of Oxford
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130310/06543df8/attachment-0006.html