]
Nick Boldt commented on JBIDE-22586:
------------------------------------
Should mention too that the base build is using the correct SHA
a86fe511763b04d7f43059082ad49aa96bed1bc5 when building [1], and the aggregate fetches the
correct json too [2]. So no idea why the org.jboss.tools.common plugin itself has a
different SHA in its MANIFEST.MF 's Eclipse-SourceReferences =
971627a3892e034feee31845f7a01d1cb45cf585.
[1]
JBT agg site build fetches sources from master instead of 4.4.0.x
branch, resulting in SHA conflict.
----------------------------------------------------------------------------------------------------
Key: JBIDE-22586
URL:
https://issues.jboss.org/browse/JBIDE-22586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, updatesite
Affects Versions: 4.4.0.Final
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.4.x
Attachments: base-wrong-sources-in-src.zip.png,
base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png
For some reason the current JBT agg site build is attempting to fetch sources from master
branch instead of 4.4.0.x branch, resulting in this SHA conflict.
{code}
[ERROR] Failed to execute goal
org.jboss.tools.tycho-plugins:repository-utils:0.25.0-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_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json
[ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base
project's MANIFEST.MF has Eclipse-SourceReferences
[ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585.
[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.{code}
--
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...