Chip, Ok! I thought you are automatically scheduling so asked for that time. Would it be okay for you to do builds at the end of your day instead of mornings? Reason is that most recent fixes will be included in the latest builds and team would be picking those up in IST time zone. Three times a week is fine for now.
What is the ETA for official builds?? Edison?? Install and upgrade need to be tested as well Thanks /Sudha -----Original Message----- From: Chip Childers [mailto:[email protected]] Sent: Friday, September 07, 2012 11:53 AM To: [email protected] Subject: Re: [ASFCS40] Release Candidate Staged on people.a.o On Fri, Sep 7, 2012 at 2:45 PM, Sudha Ponnaganti <[email protected]> wrote: > Thanks Chip! > > If there are no objections would like to see the build happening by 6:00 AM > IST daily. > Once official build is ready, this schedule can be replaced with > official builds So I'm in US Eastern time, and it requires me to do this manually... daily and at that time won't work. Monday, Wed, Friday in the morning ET would be fine. I would propose a slightly different approach, given your desire for daily builds. How about I schedule the jenkins builds to provide the nightly RPM and DEB package builds from the 4.0 branch. This is not the same thing as a signed package, but I assume that your focus is on the feature / function / performance of the software itself. Am I correct about this? -chip > Thanks > /Sudha > > -----Original Message----- > From: Chip Childers [mailto:[email protected]] > Sent: Friday, September 07, 2012 10:37 AM > To: [email protected] > Subject: Re: [ASFCS40] Release Candidate Staged on people.a.o > > On Fri, Sep 7, 2012 at 1:27 PM, John Kinsella <[email protected]> wrote: >> Something's not quite right - several of the hash files (.md5/.sha) >> are zero length... > > This is corrected now. Thanks for paying attention John! ;-) > >> On Sep 7, 2012, at 10:05 AM, Chip Childers >> <[email protected]<mailto:[email protected]>> >> wrote: >> >> All, >> >> First, a huge thanks to everyone that worked on the build issues >> recently! Edison, Wido, Hugo, others... I don't mean to ignore any >> contribution here! >> >> Edison got the build process working on >> http://jenkins.cloudstack.org/ for the binary distributions. I >> copied his original job, and created >> build-cloudstack-4.0-rhel6.3 and build-cloudstack-4.0-ubuntu12.04. >> These jobs are set to run manually right now. >> >> Although we certainly are not ready to call this an official release, >> I've posted our first signed sample build to >> http://people.apache.org/~chipchilders/cloudstack/4.0/ I would >> suggest that we use these copies as the current *for test* release >> candidate, since we're also hoping to be testing the overall build >> and release process along with the code itself. REMINDER: This is >> not an official project release. >> >> The process I used was: >> >> 1 - Run the two binary build jobs on jenkins, and download the >> produced tarballs >> 2 - Rename the files to >> apache-cloudstack-4.0.0.RC1-incubating-ubuntu12.04.tar.gz and >> apache-cloudstack-4.0.0.RC1-incubating-rhel6.3.tar.gz respectively >> (to fit our naming convention) >> 3 - Ran tools/build/build_asf.sh -v 4.0.0.RC1 -b 4.0 >> 4 - Copy the previously downloaded artifacts from jenkins to by build >> target folder (for me, it's ~/cs-asf-build) >> 5 - Generate the asc, md5 and sha files for the two binary artifacts >> 6 - scp'ed all of the files to my p.a.o public_html folder >> >> Honestly, the longest part of the process is waiting for the scp to >> p.a.o to complete (second longest is waiting for the jenkins jobs to >> complete). However, I can go through this process on a schedule if >> we want to. What days and times would everyone like to see the full >> process get run through? >> >> -chip >> >> >> Stratosec<http://stratosec.co> - Secure Infrastructure as a Service >> o: 415.315.9385 >> @johnlkinsella<http://twitter.com/johnlkinsella> >> >
