[jbosstools-issues] [JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-25138 at 10/3/17 1:49 PM:
-------------------------------------------------------------

The fix is threefold:

a) when publishing a new milestone [3], regen the composite metadata in the /updates/rhamt/ folder. cc: [~manaRH]

{code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45}
# regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /updates/rhamt/composite/ !
rm -f jbosstools-cleanup.sh 
curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/util/cleanup/jbosstools-cleanup.sh > jbosstools-cleanup.sh
chmod +x jbosstools-cleanup.sh
./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite
{code}

[3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release

b) change the RHAMT updates/rhamt/composite/ folder so it reuses the ../ folder (/updates/rhamt/) instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! 

[4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e455be56a1c49d9163bdb80e9e0143feeb46

c) update the discovery plugins to use the new ../ folder's composite site too [5]

[5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec95a5eaba729b517cd4599f1b81



was (Author: nickboldt):
The fix is threefold:

a) when publishing a new milestone [3], regen the composite metadata in the rhamt folder. cc: [~manaRH]

{code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45}
# regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /rhamt/composite/ !
rm -f jbosstools-cleanup.sh 
curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/util/cleanup/jbosstools-cleanup.sh > jbosstools-cleanup.sh
chmod +x jbosstools-cleanup.sh
./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite
{code}

[3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release

b) change the RHAMT /composite/ folder so it reuses the ../ folder instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! 

[4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e455be56a1c49d9163bdb80e9e0143feeb46

c) update the discovery plugins to use the new ../ folder [5]

[5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec95a5eaba729b517cd4599f1b81


> RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-25138
>                 URL: https://issues.jboss.org/browse/JBIDE-25138
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: central-update
>    Affects Versions: 4.5.1.AM3
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.5.1.AM3
>
>
> Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site:
> {code}
> 15:15:09    [p2.dir] !MESSAGE Only one of the following can be installed at once: 
> 15:15:09    [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0)
> 15:15:09    [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1)
> {code}
> [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstools-install-p2director.install-tests.matrix_master/PROJECT=jbosstools,SET=earlyaccess,eclipseID=eclipse_downloads_drops4_R-4.7.1-201709061700_eclipse-platform-4.7.1-linux-gtk.tar.gz,jdk=openjdk-1.8,label_exp=rhel7-devstudio-releng/1173/console
> [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/composite/
> [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)