[chirp_devel] Could we please get a "latest" symlink to the most recent daily build?
Wanting a URL like:
https://trac.chirp.danplanet.com/chirp_daily/latest/chirp-daily-latest.tar.g...
The exact format doesn't matter, the key is that there's a reliable permalink to the latest daily build.
I'm putting together a Flatpak distribution channel. Flatpaks are cross-distribution, containerized, desktop packages for Linux. I'm much of the way toward having this automated via GitLab CI, but I still have to change the URL *and* the SHA256 checksum between daily builds. What would be better is if the URL remained constant and I only trigger a build if the checksum changes, because calculating that is easy. Harder would be scraping the site to determine the latest daily build, constructing the download URL *and* updating the checksum. :)
Thanks.
I'm putting together a Flatpak distribution channel. Flatpaks are cross-distribution, containerized, desktop packages for Linux. I'm much of the way toward having this automated via GitLab CI, but I still have to change the URL *and* the SHA256 checksum between daily builds. What would be better is if the URL remained constant and I only trigger a build if the checksum changes, because calculating that is easy. Harder would be scraping the site to determine the latest daily build, constructing the download URL *and* updating the checksum. :)
You could pull this reliably, and when the checksum of the .tar.gz changes, pull the real file (which you have the filename for in the manifest):
https://trac.chirp.danplanet.com/chirp_daily/LATEST/SHA1SUM
That would mean you're polling a single URL, and pulling down a tiny file instead of the whole tarball periodically just to see if it has changed.
--Dan
That's fair. Didn't know about the LATEST directory. Even so, having a chirp-daily-latest.tar.gz would be one less moving part in the CI manifest.
On 03/30/2018 12:04 PM, Dan Smith via chirp_devel wrote:
I'm putting together a Flatpak distribution channel. Flatpaks are cross-distribution, containerized, desktop packages for Linux. I'm much of the way toward having this automated via GitLab CI, but I still have to change the URL *and* the SHA256 checksum between daily builds. What would be better is if the URL remained constant and I only trigger a build if the checksum changes, because calculating that is easy. Harder would be scraping the site to determine the latest daily build, constructing the download URL *and* updating the checksum. :)
You could pull this reliably, and when the checksum of the .tar.gz changes, pull the real file (which you have the filename for in the manifest):
https://trac.chirp.danplanet.com/chirp_daily/LATEST/SHA1SUM
That would mean you're polling a single URL, and pulling down a tiny file instead of the whole tarball periodically just to see if it has changed.
--Dan _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
participants (2)
-
Dan Smith -
Nolan Darilek