[sane-devel] daily git snapshots

[Rolf Bensch]

Hi Olaf,

The cron job seems running. I can download the daily git snapshots.

I just pushed some commits to gitlab. But I cannot find the immediately
builds on the website.

Cheers,
Rolf

Am 06.03.2018 um 13:20 schrieb Olaf Meeuwissen:
> Hi Rolf,
> 
> Rolf Bensch writes:
> 
>> Hi Olaf
>>
>> Am 04.03.2018 um 02:52 schrieb Olaf Meeuwissen:
>>> ...
>>>
>>> Sorry about that.  Should be fixed now.
>>
>> The last file on the website is from 28-Feb-2018 00:05
> 
> Should be fixed now.  Looks like something is wrong with the changes I
> made to the script and/or permission issues with me running the script
> manually and Allan's cron job running it.  Will have a look.
> 
>>> # Not quite sure why that happened but I suspect I made a mistake with
>>> # the ln command.  It doesn't seem to be caused by the update-htdocs.sh
>>> # script.  IIUC, that script runs daily.
>>>
>>> Anyway, given the (in)frequency with which our repositories are pushed
>>> to I wonder if it makes sense to drop the daily git snapshots in favour
>>> of the source tarballs created by our CI setup on every push.
>>>
>>> # Sometimes weeks go by without a commit ;-)
>>>
>>> The git snapshots are *not* the same as the source tarballs.  The former
>>> are the result of
>>>
>>>   git archive --format=tar --prefix=sane-backends-$(date +%Y%m%d) master
>>>
>>> whereas the latter are the result of
>>>
>>>   make dist
>>
>> This is exactly what I need.
> 
> If that's the case, you may want to take a look at changing the URL you
> fetch your source tarballs from.  The details[1] are on GitLab, but you
> basically want to grab
> 
>  https://gitlab.com/sane-project/$project/builds/artifacts/master/download?job=archive
> 
> and use the sane-$project-*.tar.gz that's in the zip'd archive that that
> URL provides.  This works for $project values of backends and frontends.
> There may be other files in the zip'd archive but those are intended for
> the website so you can safely ignore those.
> 
>  [1]: https://docs.gitlab.com/ce/user/project/pipelines/job_artifacts.html
> 
> You can also take a peek at
> 
>  alioth.debian.org:/home/groups/sane/bin/make-git-snapshots.sh
> 
> which does something similar for the Alioth hosted website.
> 
>>> So the latter are equivalent to what we eventually release.
>>>
>>> How easy/hard would it be to change things on your end to use the CI
>>> source tarballs?  Should I submit an issue for that on GitLab?
>>>
>>> ...
>>
>> On my point of view, daily git snapshots without any changes make no sense.
> 
> That's exactly why I asked.  We now have CI builds with every push.
> These are guaranteed to have a change.  It doesn't really matter how
> often they happen, once a month or every five minutes ;-)
> A new source tarball will be created for *every* push unless the build
> fails.  Even so, the last successfull source tarball will be available
> from the URL above.
> 
> Hope this helps,
> --
> Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
>  GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
>  Support Free Software                        https://my.fsf.org/donate
>  Join the Free Software Foundation              https://my.fsf.org/join
>