[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=12926834#comment-12926834 ] 

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

If you're not going to consume the sites, when why bother? How will you know what the performance pros/cons are if we don't stress-test the system?

Is the point of this to publish just milestones and .Final bits? Or every single nightly build? If the former, that's semi-reasonable, especially if we are planning to move toward the IS model of "components can release their Final earlier than the rest of the stack".

Thus instead of these sites:

http://download.jboss.org/jbosstools/updates/stable/kepler/core/
http://download.jboss.org/jbosstools/builds/staging/

we'd have the equivalent bits in Nexus:

https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/

What exactly does moving to nexus get us? Automated cleanup of snapshots? We have that already. Fast downloads of both sites and zips? We have that already. Seems like all we'd be getting is another checkpoint process (deploy to staging then release from staging to public) which in a sense we already have [1], except the existing job can publish a nightly to release or a milestone to stable, not just a staged build to public.

[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/

Also, are you assuming that component owners will be responsible for doing their own promotes from nexus-staging to nexus-public? If that is your assumption, I challenge it. Chances are good the real person who'll be performing that step is YOU. Because realistically, many component leads don't even know how (or want to know how) to kick their own BUILD JOBS, much less play with Nexus to promote bits.


                
> 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