[jbosstools-issues] [JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18876:
------------------------------------

So, you want me to publish TPs like we do component jobs, using rysnc.sh and publishing 1+ build folders into this location:

http://download.jboss.org/jbosstools/neon/snapshots/builds/

That would certainly be doable for the bits on dl.jb.org/ds.rh.c but I'm not sure that would help w/ the lag between "new bits on dl server" and "new entity in nexus". But if the nexus entity just points to the .target which points to builds/TP-job/latest/composite*.xml then the change seen by the dl server would be much smaller than a full 1G republish, and would (hopefully) appear faster.

Anyway, I'm good to try migrating the TP publishing to use the rsync.sh system, since it appears that that would solve at least MOST of your issues here. 

Would you agree that our current solution for everything in /builds/<JOB_NAME>/latest/ works for you most of the time, and the only thing still prone to failure is the /targetplatforms/ content?

> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18876
>                 URL: https://issues.jboss.org/browse/JBIDE-18876
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>             Fix For: 4.4.0.Alpha1
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. 
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)