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

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-18876:
---------------------------------------

We should do that step by step with these facts in mind:
1. Builds might be running at the same time while we deploying new tp over current one;
2. Even tp p2 repo synchronization is over it is still no available for public and time to sync it with public server may vary;
3. Before new TP published in nexus it should be verified against public url and it should not be published until it is valid (see point 2);
4. compositeArtifacts.xml should be updated first with new uploaded tp and then compositeContent.xml to prevent "missing artifact" errors;
5. before deleting child tp repo from composite repo compositeContent.xml should be updated first and then compositeArtifacts.xml;
6. Some builds can have slow connection so we have to keep previously published TP for some time and then run clean up script and remove child repos that are not referenced in xml files.



> 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)