[ https://issues.jboss.org/browse/JBIDE-20833?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20833: ---------------------------------------- {code}How can we educate Devs that they need to kick their own jobs when last-minute, urgent changes happen very close to the build time? Mickael Istria WDYT? {code} In that case, it's not a last-minute urgent change. It's a planned change. I expected to buildflow to run once all "Bump to Final" Jiras were resolved, to pick the right change. So I don't remember I triggered it manually, and honestly, I don't believe we should expect devs to do that for such "requested by releng" changes. However, I believe the reason of the issue can be in the buildflow: the bundles of jbosstools-playground are consumed by other components: maven, jst, aerogear... and included in the component features. So if those comsumers weren't rebuilt after the update, the new bundles didn't make it into the consuming features so they didn't make it into aggregate neither. For JBDS 10, the plan is to move the bundles to their components as much as possible. However, the current high frequence of API changes in Easymport made it easier to keep them in a separated repo for JBDS 9. -- This message was sent by Atlassian JIRA (v6.4.11#64026)