Trigger Quarkus Deploy Snapshots in the middle of the night #48054
Conversation
quarkus-bot
bot
added
the
area/infra-automation
Looking forward to it and thanks! |
|
@michalvavrik so the good news is that I think the snapshot deployment is fixed. The bad news is that it takes 1h20 instead of 30 minutes... I sent an email to Central support but I wouldn't hold my breath. Does it change something for you? |
Great!
There is randomness in how long we wait for a runner machine, so maybe I'll have to tweak timing, but in general, I scheduled everything most of the things in GH and Jenkins after 2 AM, so it may work. We don't have space to run everything later, I think we will just keep it and watch times. |
|
OK, feel free to ping me if we have to tweak things more. |
2 participants
I have tests running against Quarkus daily snapshots and ideally I'd like to test whatever was merged yesterday so that I can detect & investigate & report issues early. I use
999-SNAPSHOTartifacts deployed by https://github.com/quarkusio/quarkus/actions/workflows/deploy-snapshots.yml (currently the deployment is not working, but that's irrelevant). In theory, you can see that the deployment is scheduled for 2 AM and it runs roughly 30 minutes, plus it takes little while until the artifacts are available. However, if you look at the runs properly, they most often starts like 2:30 GMT+0. I suppose that is due to the fact that runners (busy running other jobs).Due to the fact that me and my colleagues work in GMT+2, it means that on average we have artifacts available around 5 AM. Our tests are running roughly 8 hours and takes all the executors we could use for PR CIs.
TL;DR; I'd appreciate if the deployment could be scheduled at 0:00 so that the new snapshot is available little sooner. It kinda makes sense considering it is supposed to be a build for previous day, right?