Last build is from yesterday.
But it looks like jenkins doesn't properly calculate "last stable build"
or it is not properly synced when build is published from internal jenkins.
In short it looks like this is jenkins bug, that we cannot do much about it.
We are working on new public CI infrastructure for WildFly that will fix all this problems for good.
But it will take few more weeks before it is done.
Thanks Tomaz, we get this kind of thing from time to time on Narayana and I agree, it seems like a jenkins issue. What we tend do is "Manage Jenkins" -> "Reload Configuration from Disk" Seems to sort it out usually.
The danger with the link you provided is I am guessing lastBuild/ can sometimes be to a failed build?
it should always be valid build as failed builds are not synced from internal to public instance.
So you always see only successful builds there.
you can notice that from time to time build number is missing, that are ones that failed on internal instance.
Ah, great. Thanks for clarifying. I will just use that link then.