[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16140: ------------------------------------ Requirements: * Each job has a unique name, github repo & branch, SCM check schedule. * Many jobs override defaults in parent pom to pass in different URLs for composite sites, or parameters for testing. Not all jobs use the same params. * Many jobs use the same target platform versions/URLs. But not all -- discovery build may be generating based on a newer TP than what the rest of the stack is using because it links to the Central TP as well as the JBT/JBDS TP. That job in particular gets updated and respun as part of the release process, so it probably shouldn't be generated from a template. * Links between jobs must exist correctly. Generating a job referencing a downstream job which doesn't yet exist may break the job links. * Buildflow job changes periodically as new component projects are added to or removed from the stack. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira