[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13835: ------------------------------------ Currently, the publish.sh script does this: 1. create metadata (now mostly replaced by mojo in JBIDE-15135); {color:green}DEPRECATED: this step can *almost* be removed{color} 2. generate a PUBLISH_STATUS and BUILD_DESCRIPTION, which can then be parsed by Jenkins into a job description in the left nav. * Includes: link to log, target platform(s) used, update site/installers folder, coverage report & jacoco file, upstream job's update site (if JBDS); {color:blue}OPTIONAL: this step is purely informative but provides great ease-of-use; and as long as the string BUILD_DESCRIPTION='...' appears in the build log, it doesn't matter WHAT produces this. Could also be the mojo in JBIDE-15135, if we wanted.{color} 3. store a copy of the Jenkins build log on download.jboss.org / www.qa; {color:blue}OPTIONAL: could be omitted if we want; the log is ALSO available from Jenkins itself{color} 4. Publish bits; {color:red}REQUIRED{color} * generate MD5 sums * push update site into /builds/staging/JOB_NAME/all/repo/ * push update zip into /builds/staging/JOB_NAME/all/ [unless JBDS] * push source zip into /builds/staging/JOB_NAME/all/ [create if not already present?] * (JBDS only) push installers into /builds/staging/JOB_NAME/installer/ [including update site if JBDS] * (JBDS only) push results page into /builds/staging/JOB_NAME/installer/ 5. purge old builds (keep last 5, if older than 5 days); {color:red}REQUIRED{color} -- This message was sent by Atlassian JIRA (v6.3.11#6341)