Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13672

could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.1.0.Alpha2
    • 4.1.0.Alpha1
    • build, updatesite
    • None
    • N/A
    • Not Required

      Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published.

      May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate).

      Sample files to check:

      http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/logs/GIT_REVISION.txt
      http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-sites.aggregate.site_41/logs/ALL_REVISIONS.txt

        1. jbide13672-proposed-markup_v2_2.png
          20 kB
          Nick Boldt
        2. jbide13672-proposed-markup_v2.png
          33 kB
          Nick Boldt
        3. jbide13672-proposed-markup.png
          23 kB
          Nick Boldt
        4. jbide13672-proposed-markup2.png
          19 kB
          Nick Boldt

              nickboldt Nick Boldt
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: