K-T > The user would initiate a web-based 'Forced-build' and provide, as > web-form > > input, the series of branches to be used during the build. In general > this > > would be the set of 'tickets/DM-#' on which the modifications were made. > > The users would need to note the *next* Buildbot build # in sequence to > > provide as the certificate. Alternately, the user would need to examine > the > > end of the run's Buildbot log to provide the lsst_build build number -- > if > > the build was successful. > > Presumably we could automate that last step. > Yes. > At the moment, Buildbot only > notifies on error and even for errors it was planned to send the > notification only, but more globally, to [lsst-data]. Ticket builds should *not* error to lsst-data. Only master/next > builds should, I would think. > > That would be reasonable. I'll write up a Jira Issue in due course. Robyn ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1