]
Mickael Istria edited comment on JBIDE-20148 at 6/30/15 12:11 PM:
------------------------------------------------------------------
Log says
{quote}[INFO] jbosstools-releng-publish-4.3.0.Beta2-SNAPSHOT.zip already unpacked.{quote}
So I believe we have to put a "-DoverWrite=true" flag to the command fetching
the zip.
Also, the "unpack" Maven command is using the common m2 repo, not the private
one for the job, which can drives to some confusion.
was (Author: mickael_istria):
Log says
{quote}[INFO] jbosstools-releng-publish-4.3.0.Beta2-SNAPSHOT.zip already unpacked.{quote}
So I believe we have to put a "-DoverWrite=true" flag to the command fetching
the zip.
releng scripts is an outdated version; jobs are not seeing latest
from Nexus
----------------------------------------------------------------------------
Key: JBIDE-20148
URL:
https://issues.jboss.org/browse/JBIDE-20148
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Beta2
Reporter: Nick Boldt
Assignee: Mickael Istria
Labels: needinfo, nexus
Fix For: 4.3.0.Beta2
I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should
echo more details into the log.
[0]
https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x
And the latest commits ARE built and available in Nexus [1], [2]:
[1]
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
[2]
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
Yet, no such output appears when the job is run, which makes me think that the -d and
--del flags are NOT being passed to the script.
Here's a snippet from
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
:
{code}
+ /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org
-Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository
-B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips
-Djbosstools_site_stream=master
...
[INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @
org.jboss.tools.site.core ---
...
rsync -arzq --protocol=28
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/*
tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
{code}
Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want:
{code}
+ .
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh
-s
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo
-t mars/snapshots/updates/core/master --del
...
[DEBUG] RSYNCFLAGS = --del
...
[INFO] rsync -arzq --protocol=28 --del
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/*
tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
++ rsync -arzq --protocol=28 --del ...
tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/
{code}
So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync
script, but it's IN the workspace [3] ?
[3]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...