[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18772:
------------------------------------

Do we really want *two* different ways to call rsync? This change would mean:

1. For simple jbosstools-* projects, just use mvn deploy -Pdeploy-to-jboss.org, but

2. For every other job, call shell directly, because...
* the params are different
* multiple calls to rsync are needed to push files to /builds/, /updates/
* pushing files to devstudio.redhat.com requires more calls

What benefit does this get us? Is it simply that "doing things with maven is better than calling shell directly" ? Or is the idea that component leads could deploy from their own Jenkins instead of the JBQA one?

As long as we accept that this solution only works for the 17 projects, and none of the aggregates, discovery, target platorms, etc. then +1. But really I'm +0 because having different ways to call the same script seems... questionable.


> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
>                 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
>
>
> 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)