The +request-builds page doesn't use the default build configuration

[Sebastien Bacher]

We needed a rebuild for https://launchpad.net/~ubuntu-desktop/+snap/gnome-3-26-1604 my first reaction was to hit 'Request builds' on the web UI and validate the subpage. Ken warned me to be careful editing the configuration or for safety maybe just push a no change commit to the vcs that would trigger the build with the right parameters...

Indeed https://launchpad.net/~ubuntu-desktop/+snap/gnome-3-26-1604/+edit has its automatic builds set up to use a ppa and the backport pocket, which +request-builds doesn't.

It's somewhat confusing that different means to trigger a rebuild don't lead to the same result. If they are technically different action it's not really obvious as an user. If use the same default configuration is wrong one way to reduce the confusing could be to add an option to +request-builds 'use the same configuration than automatic builds' (even selected by default if possible)

[Dimitri John Ledkov (xnox)]

this affects me too very badly.

Imho the defaults preset on /+request-builds should be the same as automated builds sources if those are set on the snap. For source archive, pocket, and source snap channels

[Dimitri John Ledkov (xnox)]

snap=lp.load('/~xnox/+snap/xnox-pc-kernel')
In [3]: snap.auto_build_pocket
Out[3]: 'Security'

In [7]: snap.auto_build_archive_link
Out[7]: 'https://api.launchpad.net/devel/~xnox/+archive/ubuntu/nonvirt'

And yet https://launchpad.net/~xnox/+snap/xnox-pc-kernel/+request-builds has source archive set to primary archive for ubuntu; pocket updates.