[
https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18772:
------------------------------------
What you're asking is currently possible, and is being done today.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
-> invokes the pom [1] to perform the deployment to
devstudio.redhat.com by passing in
different parameters to the rsync.sh script.
You can also disable deploying to JBoss Nexus [2] at the same time and only push to an
rsync location. Not sure if you can enable publishing to a DIFFERENT Nexus. Perhaps using
an override in your settings.xml?
[1]
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
[2]
https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
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)