Hi, > What if we used git-publish to always push to gitlab when submitting > patches, and have it include the gitlab ref in the cover letter.
Well, when pushing to gitlab anyway for CI runs this should be done *before* publishing the patch series on the list ... > That would trigger CI jobs in the user's fork, and patchew would not > have to run anything itself. It would merely monitor the user's fork > and report back to the list if the job failed. That part would still work (when posting patches after CI run finished). Right now running CI in my user account fails though, with this: 95608:45:05 INFO | Fetching https://apt.armbian.com/pool/main/l/linux-4.20.7-sunxi/linux-image-dev-sunxi_5.75_armhf.deb -> /builds/kraxel/qemu/avocado-cache/by_location/9b421efcfd044bf444a901be12757a1d9484ccbd/linux-image-dev-sunxi_5.75_armhf.deb.x38o9x5f 95708:45:05 INFO | Temporary asset file unavailable due to failed download attempt. 95808:45:05 ERROR| URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1056)> Probably happens to work with the qemu project account due to the file being in the avocado cache already. Shouldn't avocado be able to handle this better btw, now that it supports a separate "download assets" step? take care, Gerd
