[jbosstools-issues] [JBoss JIRA] (JBIDE-20992) Why is freemarker build failing to deploy to nexus?

[Nick Boldt (JIRA)]

Nick Boldt created JBIDE-20992:
----------------------------------

             Summary: Why is freemarker build failing to deploy to nexus?
                 Key: JBIDE-20992
                 URL: https://issues.jboss.org/browse/JBIDE-20992
             Project: Tools (JBoss Tools)
          Issue Type: Bug
          Components: build, freemarker
    Affects Versions: 4.3.1.Beta1
            Reporter: Nick Boldt
            Priority: Critical
         Attachments: deployment.fail.txt

Freemarker build is failing to deploy the site to nexus. 

Log snippet: [^deployment.fail.txt]

Far as I can tell (?) there's:

*  no significant change to job config (I tried re-adding the `-gs /home/hudson/.m2/settings.xml` instruction to the maven tasks, but it made no difference at deployment time), 

* no difference between /home/hudson/.m2/settings.xml on dev180 (freemarker fails to deploy) vs. dev181 (where openshift is deploying fine [1])

* no significant difference when comparing root poms [2], [3]

[1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/openshift/openshift.site/

[2] https://github.com/jbosstools/jbosstools-freemarker/blob/jbosstools-4.3.x/pom.xml#L29-L40 

[3] https://github.com/jbosstools/jbosstools-jst/blob/jbosstools-4.3.x/pom.xml#L53-L64

Seems that the inclusion of `jboss-public-repository-group` is not even needed since for openshift's build it's omitted:

[4] https://github.com/jbosstools/jbosstools-openshift/blob/jbosstools-4.3.x/pom.xml#L36

--

Only place I can see where the wrong (?) deployment URL is configured is in the code for the build-ci/pom, which was changed when we went from version 4.3.0.CR1-SNAPSHOT to 4.3.0.Final (see lines 120-134) [5].

[5] https://github.com/jbosstools/jbosstools-build-ci/commit/05103d96c923e1fc8ecabcb7c8572940b190d4ed#diff-600376dffeb79835ede4a0b285078036R120

Yet the openshift job uses the same version: `artifact=org.jboss.tools.releng:jbosstools-releng-publish:4.3.0.Final:zip`.

So... what other reason could there be for one job failing to deploy to `jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/)`, and another successfully deploying to https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/ ?

--

(Aside to [~mickael_istria]: Why do we deploy site zips to nexus? We never use them in the aggregates. Can we simply disable this? Should we?)





--
This message was sent by Atlassian JIRA
(v6.4.11#64026)