[ https://issues.jboss.org/browse/JBIDE-21392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21392: --------------------------------------------- [~nickboldt] since there is very little awareness about how/when these jobs should be enabled and as you say - they might result in interfering with ongoing release works - I think jira is the best option. i.e. if we had templatized jobs we could just do a single update with a commit noticing why a job is disabled - but now when jobs are just inside jenkins with no history tracking/info it is really difficult to know if/why things are like they are. Until this is done - could you not ensure that these jobs does get enabled, or that at least others than you are aware it is okey to enable ? i.e. Mickael, Denis, Martin or jbosstools-dev ? i.e. for me I constantly gets "surprised" to learn jobs were disabled since there is no communication on jbosstools-dev about it happening and I think that explains why both devs and QE are opening jiras since they have no feedback or way to find out when and why big changes like this is done to toe build system. -- This message was sent by Atlassian JIRA (v6.4.11#64026)