CI changes for main

14 views
Skip to first unread message

Guillaume Smet

unread,
Feb 18, 2026, 11:48:52 AM (11 days ago) Feb 18
to Quarkus Development mailing list
Hi,

We used to try building main for each push. "Try" because I think a lot of builds were cancelled when another push was coming resulting in a lot of useless work (a lot of partial builds not giving us any useful status info).

This was quite counter productive and used some significant CI resources. We will now build the main branch twice a day - if changes were made (we publish an artifact with the sha for each workflow run, and we compare current with previous one before starting the full build).

I was already working on it when Holly suggested it but she pushed me to try harder :).

If you see something odd, you know where to find me :).

-- 
Guillaume

George Gastaldi

unread,
Feb 18, 2026, 12:03:57 PM (11 days ago) Feb 18
to Quarkus Development mailing list
Perhaps we can also trigger QE tests + quickstart build workflows in this job? 

That would at least somehow give the QE test a faster feedback on upstream changes (provided it could notify the people that introduced the change accordingly).

Trying to find a solution before I lose my mind investigating broken tests in the same repository every week.

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo9A17cT9TAxOWk%3Dwhp9WiVchjbBThvVS7ajOqYZGajSeg%40mail.gmail.com.

Guillaume Smet

unread,
Feb 18, 2026, 12:20:59 PM (11 days ago) Feb 18
to quark...@googlegroups.com
I'm not sure I understand how this would help. Maybe we should do a call to discuss this?

You can pick a slot in my calendar tomorrow, provided it's in my working hours :).

George Gastaldi

unread,
Feb 18, 2026, 12:31:16 PM (11 days ago) Feb 18
to Quarkus Development mailing list
Thanks, again, this is just an idea aiming to catch impacted changes early. I am still investigating potential improvements on this process.

I'm trying some things locally and I've already added it as a topic for our F2F anyway, but we can discuss in a call sometime next week (still busy finishing some pending QE tasks and reviewing Agroal PRs).

Thanks! 

Guillaume Smet

unread,
Feb 18, 2026, 12:39:01 PM (11 days ago) Feb 18
to quark...@googlegroups.com
Yeah, I think it would help if I could think about it a bit before the F2F.

Reply all
Reply to author
Forward
0 new messages