[jbosstools-issues] [JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-16128:
------------------------------------

[~maxandersen]:

Tweaking our job configs to drop SNAPSHOT zips to Nexus is easy. Compositing them is also easy. We can follow the process that JBT IS uses for this, including PRs for requests to add new versions of zips to the composite.

Training devs to do so, and convincing them of the value as it outweighs the overhead incurred in having to do so, that's not so easy. 

I'm all for the idea of having the various projects (components) releasing independently (at least for the ones that aren't closely interdependent), even though it may initially feel like we're moving away from a synchronized release train (JBT, Eclipse) and more toward a cat-herding exercise (JBT IS).

But before that can happen, you need to convince the team that this is a Good Idea. Mickael and I can support them in what they'll need to do to adopt the new workflow. But if they don't buy into the concept, they won't do it. 

Proof of this is the fact that back in February 2013, I implemented a suggestion that all component nightlies would be automatically promoted to "integration" once a week [1], so that devs could then choose to promote their integration builds at some interval to stable milestone or even do an early release. Even the dev who'd specifically asked for this capability never ended up using it.

[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-integration-matrix_master/

Replacing that process
  - run automatically to create integration builds 
  - permit devs to selectively take the latest weekly integration build to promote to milestone or release 
with a process that
  -  run automatically to drop builds into the Nexus staging repo
  - permit devs to perform the release from staging to release repo

Achieves the same goal. Will it be perceived as "better?" Maybe.

Bottom line: if you can lead them to the water, I'll make sure the water is potable when they get there. But it's up to you to convince them to actually DRINK.
                
> Publish component sites to Nexus
> --------------------------------
>
>                 Key: JBIDE-16128
>                 URL: https://issues.jboss.org/browse/JBIDE-16128
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.0.Alpha1
>
>
> In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus.
> Then we'll see what are the pros/cons of this approach.
> Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira