It would be useful and beneficial to the Yocto community to add support on the Autobuilder for building and publishing eSDK package artifacts.
I'm not quite sure what you mean here. We build the eSDK installer itself; as far as things you can install using devtool sdk-install, that's simply done from the shared state cache (or more precisely, a mirror set up via SSTATE_MIRRORS).
Yes, when I said packages earlier that was incorrect. What we want to create are SSTATE objects, as Paul indicated.
The goal is to provide publicly usable sstate objects for consumption both by users of the project (eSDK and general builds) and for use by our automated QA.
Brain dumping some thoughts: We need to publish not only sstate objects generated by the build, but also sstate objects used by the build. A slightly hacky approach would be that when the custom_release_me property is set we set up a separate, empty, SSTATE_DIR and set up an http mirror of the cluster's shared sstate directory. Then when any hits in the mirror are found they will be fetched to the new SSTATE_DIR and we can then publish the entire contents of that directory for the build. The reason we would set up a http mirror, instead of using a file mirror, is because in the case of file mirrors files in the mirror aren't fetched/copied. It might be worth investigating file mirrors as a slightly cleaner approach.
Implementation has begun on an approach which uses the autobuilders published sstate mirror with a per-release sstate directory.
http://git.yoctoproject.org/clean/cgit.cgi/yocto-autobuilder/commit/?id=c8e7a8ce382139dde534b533134a4445c25f0d98
http://sstate.yoctoproject.org/dev/2.3/