[jbosstools-issues] [JBoss JIRA] (JBIDE-18594) Create a consistent /staging/ URL for JBT

Nick Boldt (JIRA) issues at jboss.org
Wed Oct 15 09:32:35 EDT 2014


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

Nick Boldt commented on JBIDE-18594:
------------------------------------

Old way was to run a script to regen those two files. Your new approach requires manually updating this file, so we can just update this section of the rel guide:

{code:title=https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBT_4.2.0_Staging_For_QE.adoc#regenerate-composite-site-metadata-for-staged-updates}
=== Regenerate composite site metadata for staged updates
Update files __http://download.jboss.org/jbosstools/updates/staging/luna/composite*.xml__ , with SFTP/SCP via command-line or your 
favourite SFTP GUI client (such as Eclipse RSE).

Optionally, run this script, then verify the resulting composite site:

[source,bash]
----
~/tru/buildci/util/cleanup/jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --dirs-to-scan updates/staging/luna
firefox "view-source:http://download.jboss.org/jbosstools/updates/staging/luna/compositeContent.xml"
----
{code}

> Create a consistent /staging/ URL for JBT
> -----------------------------------------
>
>                 Key: JBIDE-18594
>                 URL: https://issues.jboss.org/browse/JBIDE-18594
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.2.0.CR2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Critical
>              Labels: respin-a
>             Fix For: 4.2.0.CR2
>
>
> Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
> We need to rework the staging process so that its output is similar to what will be the output of a release:
> * updates/staging/luna , compositing
> ** target-platform
> ** JBT core
> ** Central TP
> * earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.CR1-SNAPSHOT/REPO/
> Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
> Then the process of releasing to development isn't much more than a _cp -r_ and some _sed /staging/development/_



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list