Bug#839072: autopkgtest: Allow for GitHub-style PR urls
Package: autopkgtest
Version: 4.0.5
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
As we've been discussing, it would be nice if you could run
autopkgtest against GitHub-style pull requests. There's no direct URL
that would allow you to do this, but you can support this by doing a
git fetch after the initial clone, e.g.:
$ git clone https://github.com/CanonicalLtd/ubuntu-image.git
$ cd ubuntu-image
$ git fetch origin +refs/pull/68/merge
$ git checkout -qf FETCH_HEAD
So the idea then is to allow URLs that can additionally specify that
PR ref. Then I could run autopkgtest like so:
$ autopkgtest https://github.com/CanonicalLtd/ubuntu-image.git+refs/pull/68/merge -- schroot yakkety-amd64
Notice the '+' separating the .git URL from the PR refspec.
I'm not sure this is the best possible syntax, and I'd like to be able
to support GitLab PRs too, which apparently don't use a + or the same
refspec for their merge requests, although the same general
implementation (clone then fetch) *should* work.
I thought about maybe using a '@' or some other unexpected delimiter
to separate the .git URL from the PR specification. I'll play with a
GitLab MR to see what works best, but that would be an easy change.
I have a hack that works for GitHub, which I'll send along shortly.
- -- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages autopkgtest depends on:
ii apt-utils 1.3
ii libdpkg-perl 1.18.10
ii procps 2:3.3.12-2
ii python3 3.5.1-4
ii python3-debian 0.1.29
Versions of packages autopkgtest recommends:
ii autodep8 0.8
Versions of packages autopkgtest suggests:
pn lxc <none>
pn lxd-client <none>
pn qemu-system <none>
pn qemu-utils <none>
ii schroot 1.6.10-2+b1
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJX69L6AAoJEBJutWOnSwa/YUsQAKHzOSkuu509bpjX7tKJ4M19
4erLTGuF5yoUBgC79yNGEt0x5AvidsCuV/xeSCiyzbDXkU9sO/D48Wyq+CVUdxUr
kzDh4wORDFp0VhDo3maci8JnHu+Ng5nQ37JR+iQTk4Xd/abaiFMpADhU5DHDCO11
naHdOwsms26S+O/83zKujkxUHujOFMrv1Y+cvCc7lfuOgK4plBQh0LIc7bi3vFjn
zjFBtflyVRK1qBMROgQLJgq+Ijz6507Uf5hf317pwt5XjZk+/GBF2sRu0e7LTXxC
6GvpPgCQv4ru70OBrgzw8uj/aClb1IDg20CDEij+dwehGh97WkpqT5200V4V+OX0
4iRiMbOaMPtAzTBN1V3qlOLkIKSP1KlkRT86J6/+jYBReMZeXXDlf10WdaKjkMA/
yIQUfMIQfTPgSNl2NxGvxHF3EED9JXAGJuObHcqPiQTdI9wBkjOIlsSf5nwQkteF
Tp9BpfleTomgPVpwv1yxVDdqvoOT8OPVxVCE9tgOiSpG1Bad8y7CMmW9X4TgHA80
DWglHel6RtS0ihAol1gzeOiB79lQcpSEW3+8ill2b3I4K2s/is3iUlvqX8zRCzKS
Ckw62mCDPLGBZM19NbJxMHrjqmeVIxjlWtWrZoqoP5vqSRagcS/TpxczYJA2p4VS
xqaX2k7Kc7VB2zvnShjS
=p5rd
-----END PGP SIGNATURE-----
Reply to: