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

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121521#comment-13121521 ] 

Nick Boldt commented on JBIDE-20992:
------------------------------------

The actual error was reported in the linked log file:

{code}org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project freemarker.site: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.freemarker:freemarker.site:zip:1.5.1 from/to jboss-staging-repository (https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/): Failed to transfer file: https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/org/jboss/tools/freemarker/freemarker.site/1.5.1/freemarker.site-1.5.1.zip. Return code is: 401, ReasonPhrase: Unauthorized.{code}

I've opened JBIDE-21012 to discuss not deploying snapshots to nexus at all.

Since JBIDE-20908 is fixed again, we can now close this. 

> 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
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.3.1.Beta1
>
>         Attachments: deployment.fail.txt
>
>
> Freemarker build is failing to deploy the site to nexus. 
> Log snippet: [^deployment.fail.txt], taken from 
> * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/22/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/qa04-rhel6-x86_64 ) and 
> * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-freemarker_4.3.mars/21/console (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev180-rhel6-x86_64 )
> vs.
> * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/54/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev127-virt1 )
> * http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-openshift_4.3.mars/52/consoleFull (on http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev181-rhel6-x86_64 ) 
> 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)