Hello Richard, we're currently evaluating a proper approach with the Packit team, to deduplicate (and optimize) the work, as I've written a set of tools for such automation: https://github.com/pvalena/theprototype https://www.youtube.com/watch?v=gUjwSj6iypw&ab_channel=DevConf Currently does not have wide adoption, and some tools are still domain-specific (rubygems). So it's in the "testing" phase (please, do file issues if you find something does not work!). After some iterations (~months), it should be quite suitable for automating various packaging tasks. Should I keep you in the loop? Regards, Pavel On Thu, Dec 31, 2020 at 2:58 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > > I maintain a suite of ham radio related packages. The developer is very active and often creates test versions adding and incrementing the "tweak" part of the version which is removed for the full releases and the patch level incremented. > > Currently I'm just trying to keep up with them by hand using pagure forks of the official repos so I don't accidentally pollute SCM with the changes and build them in COPR. > > Things I need to manage automagically: > 1. Monitor the test URLs to look for new versions. > > I could write a bash script for this and add a cron or systemd timer but I was hoping for something that took less time as I don't have a lot of that :) > > Would it be permissible to create a <package>-testing entry in release-monitoring.org? > > > 2. Trigger a "fedpkg clone" and add a tweak version. > > This could probably be managed with macros easy enough, %{?tweak}, or something like that. And then use a script to substitute into "%global tweak ..." > > > 3. I need to download the files from a different location. > > %if %{?tweak} > ... use difference Source0? > > > 4. Build the packages in COPR. > > Easy enough using a bash script but is there a better way? > > Thanks, > Richard > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
