If you are testing an EPP package, you need the Simultaneous Release repository *and* an EPP repository. The EPP repositories can be found on our build server and are located next to the packages in a separate directory. An example:
- Juno build output from Hudson: http://build.eclipse.org/technology/epp/epp_build/juno/download/ - Build 20130205-0630: http://build.eclipse.org/technology/epp/epp_build/juno/download/20130205-0630/ - p2 repository: http://build.eclipse.org/technology/epp/epp_build/juno/download/20130205-0630/repository/ The same works for Kepler ( http://build.eclipse.org/technology/epp/epp_build/kepler/download/) Regards, Markus On Tue, Feb 5, 2013 at 10:36 PM, Beth Tibbitts <[email protected]> wrote: > Remind me, is there a way we can test "Check for Updates" before the > updates are actually in the spot that folks installed from to begin with? > That is, how do I take e.g. an EPP package (e.g. our Parallel Package) and > test what will happen for Help > Test for Updates > once Juno SR2 is final? > If I put > *http://download.eclipse.org/releases/maintenance/*<http://download.eclipse.org/releases/maintenance/> > in Available Software Sites, 'Check for Updates' still doesn't see anything > new. > > > > ...Beth > > Beth Tibbitts > Eclipse Parallel Tools Platform http://eclipse.org/ptp > IBM STG - High Performance Computing Tools > Mailing Address: IBM Corp., 745 West New Circle Road, Lexington, KY 40511 > > [image: Inactive hide details for David M Williams---01/17/2013 09:39:22 > AM---Sorry, fell asleep last night :) when I should have been]David M > Williams---01/17/2013 09:39:22 AM---Sorry, fell asleep last night :) when I > should have been sending out this notice. > > > > From: > > > David M Williams/Raleigh/IBM@IBMUS > > To: > > > "Cross project issues ([email protected])" < > [email protected]>, > > Date: > > > 01/17/2013 09:39 AM > > Subject: > > > [cross-project-issues-dev] Concluding SR2 RC1 warm-up repository > > Sent by: > > > [email protected] > ------------------------------ > > > > Sorry, fell asleep last night :) when I should have been sending out this > notice. > > But, we are done with SR2 RC1 warm-up repo. > > Remember its "staging" location is * > **http://download.eclipse.org/releases/maintenance/*<http://download.eclipse.org/releases/maintenance/> > > > Besides testing that repo, be sure to check the repository reports ... > looks like a few regressions for required files, signed jars, etc. * > **http://build.eclipse.org/simrel/juno/reporeports/*<http://build.eclipse.org/simrel/juno/reporeports/> > > > In addition to testing only that single repo, be sure to test it as a > "composite", since eventually it will be added to .../releases/juno > as a child repository. See * > ** > http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#Test_staging_as_a_pseudo_composite > *<http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#Test_staging_as_a_pseudo_composite> > > Don't forget to test "update" scenarios (some of which need to wait for > EPP repositories to be ready, if they are not already). > > Recall that there is no "promotion" of this repo. It will simply be "left > alone" for about a week ... until Juno SR2 RC2 +0. * > **http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#SR2*<http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#SR2> > > > As a "warm-up", we don't expect this to be a true "release candidate", but > please approach RC2, RC3, etc., with the attitude that those will be true > "release candidates" suitable for adopter acceptance testing, etc. > > Thanks, > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > >
<<graycol.gif>>
<<ecblank.gif>>
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
