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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18876:
----------------------------------------

Marking bug as minor as it would affect very few users in very rare circumstances.

{quote} IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. {quote}
If you look at configuration of https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/configure , you'll notice that the unified TP is deployed to Maven after the binaries are changed. The unified target-platfrom validation step does require that the p2 repositories referenced by the .target file (in such case the unified site and TP) are available, or validation would fail.

So it seems to me that the issue is that binaries content changed remotely, and that the initial resolution of TP, which happens early in the build, referenced older THyM artifacts that moved.
I don't think we can/need to do anything better on the publish part for this issue.


> 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
>            Priority: Minor
>
> 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.8#6338)