Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-20168 create buildinfo.json files for old project builds which predate buildinfo.json generator
  3. JBIDE-20171

buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 4.3.0.Beta2
    • 4.3.0.Beta2
    • build
    • None

      Since the addition of a check that verifies exactly this condition:

      https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6cd546def43ad11ff02d9c5468c156

      I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json.

      https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console
      [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files!
[ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json
[ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences
[ERROR] commitId .
[ERROR] If you have locally built projects which are aggregated here,
[ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
[ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
[ERROR] -> [Help 1]

      This happened after I put a buildinfo.json file here:

      http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo.json

      I've since moved the file here to temporarily work around the build failure:

      http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo_2012-11-26_18-50-16-B155.json

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

              Created:
              Updated:
              Resolved: