[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18772:
------------------------------------
As PR 185 is applied, I've closed it.
Also applied
https://github.com/jbosstools/jbosstools-build-sites/pull/187 which supports
publishing all JBT agg sites w/ deploy (2 pushes for site, coretests, webtools; 4 pushes
for central, earlyaccess); also fix references to obsolete
jbosstools-nightly-staging-composite and instead uses upstream jbosstools-site from parent
pom, so it's easier to override at build time
Verified by building webtools and central locally against local upstream local JBT site:
mvn clean install
-Djbosstools-site=file:///home/nboldt/tru/jbosstools-build-sites/aggregate/site/target/repository/
I've updated the _master and _4.3.mars jobs to use this shiny new `deploy` step and
remove the duplicate step(s) invoked by shell. Also added to the profiles for central and
earlyaccess so they publish to both servers (dl.jb.o and ds.rh.c).
https://github.com/jbdevstudio/jbdevstudio-ci/commit/d4f26761495860e86e63...
Unfortunately, Jenkins is being insanely slow today so I haven't had time to run the
jobs to verify.
Include publish steps in pom files
----------------------------------
Key: JBIDE-18772
URL:
https://issues.jboss.org/browse/JBIDE-18772
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: build
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.3.0.Beta1
Attachments: jbds-publish-to-snapshots.png
instead of relying to publish.sh being on master, we should use a versioned publish.sh
(or maybe even mojo) that the build then uses.
suggestion:
publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform
publishing.
What this helps with is:
a) can do changes to publish mechanism without affecting every past builds.
b) more movable build system
c) isolated testing possible
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)