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

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

Build is now blue. But the problem remains:

* unified.target points to a remote location, which is expected to be built and as current as the latest copy of unified.target in github. 
* if the remote location is not up to date (missing IUs awaiting a build), then your local copy of the unified.target file will try to resolve against an incomplete site
* therefore there's a lag between "publish an update to unified.target version 4.50.-Beta1-SNAPSHOT in github" and update http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1-SNAPSHOT/REPO/ so the .target file can be resolved.

Not sure what we can do about this. [~dgolovin] any ideas? If not I'll close this again until a problem re-appears.

> 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
>            Priority: Minor
>             Fix For: 4.3.x
>
>
> 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.3.15#6346)