Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

JBIDE-17536 add note about moving to updates/staging/luna/ instead of updates/staging; add script to regen metadata in a folder full of update sites >> master #101

Merged
merged 1 commit into from
Jul 23, 2014
Merged

JBIDE-17536 add note about moving to updates/staging/luna/ instead of updates/staging; add script to regen metadata in a folder full of update sites >> master #101

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
12 changes: 12 additions & 0 deletions release_guide/8.0/JBT_4.2.0.Beta3_Release_Milestone.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,8 @@ These steps happens on filemgmt.jboss.org, in the jbosstools download area.

=== If publishing a respin, remove respin suffix from sites

# TODO: for CR1, put content into staging/luna/ instead of just staging/

The goal of this task is to make latest respin is available in the 'updates/staging/${version}' location, without respin attribute.

Via sftp, remove older respins and rename the latest respin to remove its respin (a, b) suffix.
Expand Down Expand Up @@ -172,6 +174,8 @@ The principle is to keep only the latest respin and make it the actual release.
echo "rename development/jbosstools-${version}-build-hibernatetools development/jbosstools-${version}-build-hibernatetools.DELETEME" | sftp ${TOOLS}/builds
echo "rename development/jbosstools-${versionWithRespin}-build-hibernatetools development/jbosstools-${version}-build-hibernatetools" | sftp ${TOOLS}/builds

# TODO: for CR1, put content into staging/luna/ instead of just staging/

# rename the update site
echo "rename updates/staging/jbosstools-${version}-updatesite-core updates/staging/jbosstools-${version}-updatesite-core.DELETEME" | sftp ${TOOLS}
echo "rename updates/staging/jbosstools-${versionWithRespin}-updatesite-core static/releases/jbosstools-${version}-updatesite-core" | sftp ${TOOLS}
Expand All @@ -189,6 +193,8 @@ The principle is to keep only the latest respin and make it the actual release.
echo "rename updates/staging/jbosstools-${version}-updatesite-hibernatetools updates/staging/jbosstools-${version}-updatesite-hibernatetools.DELETEME" | sftp ${TOOLS}
echo "rename updates/staging/jbosstools-${versionWithRespin}-updatesite-hibernatetools static/releases/jbosstools-${version}-updatesite-hibernatetools" | sftp ${TOOLS}
else
# TODO: for CR1, put content into staging/luna/ instead of just staging/

# if there were no respins, then version = versionWithRespin
echo "rename updates/staging/jbosstools-${version}-updatesite-core static/releases/jbosstools-${version}-updatesite-core" | sftp ${TOOLS}
echo "rename updates/staging/jbosstools-${version}-updatesite-coretests static/releases/jbosstools-${version}-updatesite-coretests" | sftp ${TOOLS}
Expand All @@ -215,6 +221,8 @@ A graphical sftp client such as FileZilla or FireFTP (plugin for Firefox) is the

Webtools site is expected to be found in +http://download.jboss.org/tools/updates/webtools/${eclipseTrain}+ (where eclipseTrain is for example "luna"). So, with a sftp client, on filemgmt.jboss.org

# TODO: for CR1, put content into staging/luna/ instead of just staging/

1. Rename +/downloads_htdocs/tools/updates/webtools/${eclipseTrain}+ into +/downloads_htdocs/tools/updates/webtools/${eclipseTrain}_${previousVersion}+, with ${previous} being the name of previous release (for example 4.2.0.Alpha1 when releasing 4.2.0.Beta3)
1. Move last build in +/downloads_htdocs/tools/updates/staging/jbosstools-${version}-updatesite-webtools+ to +/downloads_htdocs/tools/updates/webtools/${eclipseTrain}+

Expand All @@ -226,6 +234,8 @@ versionWithRespin=4.2.0.Beta3b
eclipseTrain=luna
TOOLS=tools@filemgmt.jboss.org:/downloads_htdocs/tools

# TODO: for CR1, put content into staging/luna/ instead of just staging/

echo "rename webtools/${eclipseTrain} webtools/${eclipseTrain}_${previous}" | sftp ${TOOLS}/updates/
echo "rename staging/jbosstools-${versionWithRespin}-updatesite-webtools webtools/${eclipseTrain}" | sftp ${TOOLS}/updates/
----
Expand Down Expand Up @@ -453,6 +463,8 @@ fi

----

# TODO: for CR1, put content into staging/luna/ instead of just staging/

* Check the following URLs show the right versions and reference content under the 'static/releases' directory (not 'updates/${version}' nor 'updates/staging/*'

[source,bash]
Expand Down
24 changes: 24 additions & 0 deletions release_guide/8.0/JBT_4.2.0.Beta3_Staging_For_QE.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,8 @@ Then verify sites are correctly populated with build metadata. To do so, you can

p2 repositories are expected to be under the +http://download.jboss.org/jbosstools/updates+ directory. Similarly to the build sites, we move them there.

# TODO: JBIDE-17536 - for CR1, put content into staging/luna/ instead of just staging/

[source,bash]
----
stream=4.2.luna
Expand All @@ -96,6 +98,20 @@ echo " >> http://download.jboss.org/jbosstools/updates/staging/jbosstools-${vers

Then verify those 4 sites are correctly populated.

=== Regenerate composite site metadata for staged updates

# TODO: JBIDE-17536 - for CR1, put content into staging/luna/ instead of just staging/

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
firefox "view-source:http://download.jboss.org/jbosstools/updates/staging/compositeContent.xml"

----

== Update Discovery sites

Because Central and Early Access target platforms contain parts of JBoss Tools which have not yet been released, you need to rebuild the target platform using the new JBT
Expand Down Expand Up @@ -123,6 +139,8 @@ Update the *stable branch* discovery job [1] to publish to the right URL, accord
* Update property +JBTCENTRALTARGET_VERSION+ to 4.40.0.Beta4b-SNAPSHOT
* Update property +JBTEARLYACCESSTARGET_VERSION+ to 4.40.0.Beta4b-SNAPSHOT

# TODO: for CR1, put content into staging/luna/ instead of just staging/

* Update property +JBT_UPDATE_SITE+ to http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Beta3c-updatesite-core/
* Update property +JBDS_UPDATE_SITE+ to http://www.qa.jboss.com/binaries/RHDS/updates/development/8.0.0.Beta3c-updatesite-core/

Expand Down Expand Up @@ -167,6 +185,8 @@ dev01$ . /home/hudson/config_repository/scripts/jbds/prompt.sh

# can run 5 steps these in parallel

# TODO: for CR1, put content into staging/luna/ instead of just staging/

version=4.2.0.Beta3c # a, b, c...
branch=core/4.2.luna
scpr tools@filemgmt.jboss.org:/downloads_htdocs/tools/updates/staging/jbosstools-${version}-updatesite-core/* /tmp/jbosstools-${version}-updatesite-core/
Expand Down Expand Up @@ -272,6 +292,8 @@ As always, these are not FINAL bits, but preliminary results for QE & community

Update site:

# TODO: for CR1, put content into staging/luna/ instead of just staging/

* http://download.jboss.org/jbosstools/updates/staging/jbosstools-${version}-updatesite-core/

Target platforms:
Expand Down Expand Up @@ -299,6 +321,8 @@ https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.syst

Additional update sites & builds:

# TODO: for CR1, put content into staging/luna/ instead of just staging/

* http://download.jboss.org/jbosstools/updates/staging/jbosstools-${version}-updatesite-coretests/
* http://download.jboss.org/jbosstools/updates/staging/jbosstools-${version}-updatesite-hibernatetools/
* http://download.jboss.org/jbosstools/updates/staging/jbosstools-${version}-updatesite-webtools/
Expand Down