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

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

Problem was an unresolved variable (I was trying to resolve the version of the target platform dynamically from the value in the root pom, but assumed it could be parsed the same as the poms for central/EA) when publishing the updated target platform. So instead of pushing the update site ref'd by unified.target into 

http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.0.Beta1-SNAPSHOT/REPO/

it went into

http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/REPO/

I've added a more verbose check & failure to the job config. However, since unified.target depends on a successful publish, and it needs to be in github in order to be built, we retain this (somewhat) circular workflow.

Here's what we do today:

1. push change to github for multiple.target and unified.target
2. deploy multiple.target to Nexus
3. rebuild target site
4. publish into http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/$\{VERSION}/REPO/
5. deploy unified.target to Nexus (depends on the above URL being populated correctly & being up to date)

Anyway, respinning:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatforms-matrix >=410

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