We're starting to use mozreview more and more for https://hg.m.o/build/buildbot-configs, and buildbotcustom. Would it be possible to set those up for autoland?
dminor: do we need to do anything on the Autoland server to configure new repos? Or is this just adding some settings in the MozReview admin UI?
You need to make a local clone of the repositories on the autoland server under /repos. You will also have to add an "upstream" path to the .hg/hgrc file which points to the repository to which changes will be landed. This is separate from the destination received from MozReview because the destination could be try and we don't want to pull from try. If MozReview passed both the "try" and "landing" repositories we could probably get rid of local configuration on the autoland server completely, but making autoland smart enough to do a clone of an unrecognized repo from the "landing" repo url. I think that is it. There is a "version-control-tools" path defined in the v-c-t repo hgrc on autoland, but I think that is cruft left over from when we didn't pass full destination urls into Autoland from MozReview.
I /think/ I've enabled autoland for buildbot-configs and buildbotcustom. Please give it a try and let me know if it works.
Doesn't seem to work. From https://reviewboard.mozilla.org/r/49467/#review46311: There was an error executing the Autoland request on buildbot-configs Requested by catlee hg error in cmd: hg pull buildbot-configs -r ec946c9cea7671faca05aeef9522349bd864520b: pulling from buildbot-configs abort: repository buildbot-configs not found!
Please try again.
Same problem: hg error in cmd: hg pull buildbot-configs -r ec946c9cea7671faca05aeef9522349bd864520b: pulling from buildbot-configs abort: repository buildbot-configs not found!
I friggin fat fingered the path name in the hgrc. Try again.
Works now, thanks!
Doesn't land on the correct branch. Will need autoland and mozreview changes to make this work correctly. I'll file a new bug.