ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
systwi_ has joined #freedesktop
systwi has quit [Ping timeout: 480 seconds]
Seirdy has quit [Ping timeout: 480 seconds]
Seirdy has joined #freedesktop
ximion has quit []
Rainer_Bielefeld has joined #freedesktop
mvlad has joined #freedesktop
<emersion>
we were talking about FDO_DISTRIBUTION_TAG the other day
<emersion>
i can easily imagine the hair-pulling when the CI manifest is slightly more complicated
danvet has joined #freedesktop
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #freedesktop
chomwitt has joined #freedesktop
AbleBacon has quit [Read error: Connection reset by peer]
AbleBacon has joined #freedesktop
<jadahl>
emersion: if a specific commit of a tool is needed, you can explicitly build it into the image instead of relying on the distro giving you whatever version they have, but how is that related to FDO_DISTRO_TAG?
<emersion>
jadahl: this is exactly what the manifest is doing
<emersion>
the issue is that the version of the tool in the container got out of sync with the version specified in the manifest
<emersion>
because i forgot to bump FDO_DISTRIBUTION_TAG during a force-push in a MR, presumably
dri-logg1r has quit [Remote host closed the connection]
rektide has quit [Remote host closed the connection]
rektide has joined #freedesktop
dri-logger has joined #freedesktop
<jadahl>
sure, when one wants to update the image, one have to bump the tag
<jadahl>
causing the image to be rebuilt when a MR iterates while having changed the tag, without having to update the tag over and over in the mr, would be nice though
<emersion>
yup -- just giving a real-world illustration that desync can happen to people saying that bumping the tag is easy enough :P
GNUmoon has quit [Remote host closed the connection]
<emersion>
(and no, i didn't forgot to bump on purpose!)
<jadahl>
doesn't sound impossible to add, e.g. always rebuild if the tag is different from the tag in the target branch... that is assuming one can some how extract thet tag from the target branch
agd5f has quit [Remote host closed the connection]
agd5f has joined #freedesktop
Satan has quit [Quit: Ping timeout (120 seconds)]
Satan has joined #freedesktop
ceyusa has quit [Remote host closed the connection]
ceyusa has joined #freedesktop
GNUmoon has joined #freedesktop
ximion has joined #freedesktop
<pq>
I thought there *is* a way to force re-building of the image even without bumping the tag, exactly for re-iterating on MR?
<MrCooper>
yeah, there's a separate variable for that
<MrCooper>
that has its own risks though, in particular forgetting to remove it again before merging :)
<pq>
wait, it's not a 'git push' argument?
<pq>
like -o ci.skip
Rainer_Bielefeld has quit []
<MrCooper>
another alternative to repeatedly bumping the tag is to delete the tag in the registry
<MrCooper>
though unfortunately GitLab's UI for the registry seems to keep getting worse
<pq>
hmm...
<pq>
git push -o ci.variable=FDO_FORCE_REBUILD=1
<pq>
doesn that woork? If not, it should.
<MrCooper>
it might
<MrCooper>
it's a pretty big hammer for something like Mesa with lots of images though
<pq>
luckily this is not about Mesa this time
<pq>
for simpler projects it would be nice
<MrCooper>
indeed
<MrCooper>
it's worth keeping in mind though that the ci-templates were largely influenced by the needs of Mesa, some of which don't apply to simpler projects
ximion has quit []
vbenes has quit []
vbenes has joined #freedesktop
<pq>
and libinput, I believe
<MrCooper>
and gstreamer, all large projects with very heavy CI
<bentiss>
I think networkManager has a tag based on the sha of the DISTRIBUTION_EXEC script, so they never forget to bump the sha