On Mon, Oct 10, 2011 at 4:41 PM, Dave Martin <dave.mar...@linaro.org> 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 of the information. Personally, I'd > recommend not putting the ID in too many places -- we would just end > having to many different mechanisms for querying it, instead of having > just one, robust, mechanism. > > Thoughts? > Right. All this is for convenience only! Personally I would like to be able to find the hwpack for a build easily by going to http://ci.linaro.org/kernel_hwpack/ and eyeballing the filenames/directories there. Currently you don't have a way to find out which job/tree the hwpack is coming from nor do you get any hint which build ID in that job to look at. So given all this, how about this scheme: http://ci.linaro.org/kernel_hwpack/$CI_JOBNAME/hwpack_linaro-panda_YYYYMMDD-HHMM.b$BUILD_NUMBER.tar.gz Example: http://ci.linaro.org/kernel_hwpack/linux-next_beagle-omap2plus<https://ci.linaro.org/jenkins/view/Linux%20Next%20CI%20Builds/job/linux-next_beagle-omap2plus/> /hwpack_linaro-panda_20110927-0545.b160.tar.gz would refer to the hwpack coming out of this build: -> https://ci.linaro.org/jenkins/view/Linux%20Next%20CI%20Builds/job/linux-next_beagle-omap2plus/160/ Sounds good? -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
