Re: Linaro CI hwpack name improvements

2011-10-12 Thread Deepak Saxena
On 12 October 2011 09:25, Dave Martin wrote: > On Wed, Oct 12, 2011 at 03:10:59PM +0530, Deepti Kalakeri wrote: >> On Tue, Oct 11, 2011 at 7:23 PM, Alexander Sack wrote: >> >> > On Tue, Oct 11, 2011 at 3:42 PM, Dave Martin wrote: >> > >> >> >> >> Also, what timezone is used to determine the date

Re: Linaro CI hwpack name improvements

2011-10-12 Thread Dave Martin
On Wed, Oct 12, 2011 at 03:10:59PM +0530, Deepti Kalakeri wrote: > On Tue, Oct 11, 2011 at 7:23 PM, Alexander Sack wrote: > > > On Tue, Oct 11, 2011 at 3:42 PM, Dave Martin wrote: > > > >> > >> Also, what timezone is used to determine the date and time? I think we > >> should use UTC, not any lo

Re: Linaro CI hwpack name improvements

2011-10-12 Thread Deepti Kalakeri
On Tue, Oct 11, 2011 at 7:23 PM, Alexander Sack wrote: > On Tue, Oct 11, 2011 at 3:42 PM, Dave Martin wrote: > >> >> Also, what timezone is used to determine the date and time? I think we >> should use UTC, not any local timezone. >> >> > agreed on the UTC time. > Yup its UTC time. > > > -- >

Re: Linaro CI hwpack name improvements

2011-10-11 Thread Alexander Sack
On Tue, Oct 11, 2011 at 3:42 PM, Dave Martin wrote: > > Also, what timezone is used to determine the date and time? I think we > should use UTC, not any local timezone. > > agreed on the UTC time. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source

Re: Linaro CI hwpack name improvements

2011-10-11 Thread Dave Martin
On Tue, Oct 11, 2011 at 06:57:53PM +0530, Deepti Kalakeri wrote: > On Tue, Oct 11, 2011 at 5:32 PM, Alexander Sack wrote: [...] > > Example: > > > > http://ci.linaro.org/kernel_hwpack/linux-next_beagle-omap2plus

Re: Linaro CI hwpack name improvements

2011-10-11 Thread Deepti Kalakeri
On Tue, Oct 11, 2011 at 5:32 PM, Alexander Sack wrote: > On Mon, Oct 10, 2011 at 4:41 PM, Dave Martin wrote: > >> For convenience only, we can put the job name and build ID into the >> > URL and/or the hwpack filename, and possibly in the hwpack metadata, >> but it's important to remember that th

Re: Linaro CI hwpack name improvements

2011-10-11 Thread Alexander Sack
On Mon, Oct 10, 2011 at 4:41 PM, Dave Martin wrote: > For convenience only, we can put the job name and build ID into the > URL and/or the hwpack filename, and possibly in the hwpack metadata, > but it's important to remember that this is only a convenience and is > not the authoritative source o

Re: Linaro CI hwpack name improvements

2011-10-10 Thread Dave Martin
On Mon, Oct 10, 2011 at 02:22:05PM +0200, Alexander Sack wrote: > On Mon, Oct 10, 2011 at 2:08 PM, Loïc Minier wrote: > > > On Mon, Oct 10, 2011, Deepti Kalakeri wrote: > > > 1) The board on which the hwpack can be booted > > > 2) The hwpack creation timestamp includes the date in mmdd format

Re: Linaro CI hwpack name improvements

2011-10-10 Thread Deepti Kalakeri
Hello Alexander, Oops! I am sorry if I have misunderstood the BP https://blueprints.launchpad.net/linaro-ci/+spec/improve-hwpack-names. If we check the Acceptance criteria, it says "Acceptance: The new name of hwpack generated by the linaro-hwpack-replace contains the defconfig information." If

Re: Linaro CI hwpack name improvements

2011-10-10 Thread Alexander Sack
On Mon, Oct 10, 2011 at 2:08 PM, Loïc Minier wrote: > On Mon, Oct 10, 2011, Deepti Kalakeri wrote: > > 1) The board on which the hwpack can be booted > > 2) The hwpack creation timestamp includes the date in mmdd format > along > > with the time in hhmm format. > > > > The hwpack name does no

Re: Linaro CI hwpack name improvements

2011-10-10 Thread Loïc Minier
On Mon, Oct 10, 2011, Deepti Kalakeri wrote: > 1) The board on which the hwpack can be booted > 2) The hwpack creation timestamp includes the date in mmdd format along > with the time in hhmm format. > > The hwpack name does not include any defconfig related information, which > was used to bu

Linaro CI hwpack name improvements

2011-10-10 Thread Deepti Kalakeri
Hello, I am working on improving the hwpack names delivered by the Linaro Kernel Continuous Integration. To start on this I needed inputs from the kernel team. currently the hwpack containing the newly built kernel debian package is named for example as hwpack_linaro-panda_20111004-1126_armel_sup