#22 add a canary file for fedfind to know when make-updates is done with a compose
Closed 5 years ago by ausil. Opened 5 years ago by maxamillion.
maxamillion/releng make-updates-canary  into  master

file modified
+2
@@ -106,3 +106,5 @@ 

  for type in Cloud_Atomic Docker Cloud-Images Cloud-Images-Untested; do sg releng "rsync -avhH $FINALDEST/$type/ /pub/alt/stage/$VERSION-$DATE/$type/"; done

  sg releng "chmod 755 /pub/alt/stage/$VERSION-$DATE/"

  

+ sg releng "printf \"make-updates finished at $(date)\n\" > /pub/alt/stage/$VERSION-$DATE/finish"
ausil commented 5 years ago

normally we would put a file like this in the logs/ dir but that is not public. we really need to rethink the whole compose process. and just make sure everything is always public.

ausil commented 5 years ago

This path has changed.

+ 

no initial comment

+1 - I requested this and it would be very useful for fedfind.

Note: so far as I can tell, this script doesn't produce the Cloud_Atomic tree. But it does seem to run after whatever produces Cloud_Atomic, so it should be safe to say that once this script is done, the compose is done.

Note: so far as I can tell, this script doesn't produce the Cloud_Atomic tree. But it does seem to run after whatever produces Cloud_Atomic, so it should be safe to say that once this script is done, the compose is done.

It produces it by running lorax in mock near the top of the script

normally we would put a file like this in the logs/ dir but that is not public. we really need to rethink the whole compose process. and just make sure everything is always public.

This path has changed.

This never seems to have been merged; we get fedmsg's, which is nice, but I could still use the canary file for fedfind (right now it uses a nasty hack of just checking if the Cloud-Images directory exists).

Metadata