Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

15000 users, one update site

863 views

Published on

This talk focus on how we automatically create a p2 repository aggregating over 30 external repos, describe the wide variety of technologies being used (b3 aggregator, artifactory, jenkins, tycho, p2 tools, etc.) and talks about the challenges encountered.

Published in: Software
  • Be the first to comment

15000 users, one update site

  1. 1. 15000 users, one update site Pascal Rapicault Emilio Palmiero
  2. 2. Ericsson Internal | 2014-03-07 | Page 2 Problem Statement › Stand-alone repository › Accumulate versions › Pre-validated for a given stream › Categorized for our users ? External repos Ericsson repo
  3. 3. Ericsson Internal | 2014-03-07 | Page 3 Aggregation & Validation Eclipse b3 aggregator › Validate › Copy › Create a final repo › Categorize › https://wiki.eclipse.org/Eclipse_b3/aggregator/manual External repos Ericsson repo
  4. 4. Ericsson Internal | 2014-03-07 | Page 4 Mirror internally › Sources are unstable › Remove references › http://help.eclipse.org/kepler/index.jsp?topic=%2Fo zip External repos Mirrored repos
  5. 5. Ericsson Internal | 2014-03-07 | Page 5 Accumulate versions New repo Old repo Complete repo
  6. 6. Ericsson Internal | 2014-03-07 | Page 6 Categories › P2 category publisher › Composite repositories Complete repo Categories repo Final repo
  7. 7. Ericsson Internal | 2014-03-07 | Page 7 Testing › Repository validator › Collect all the categorized elements › Install then uninstall in distros Final repo
  8. 8. Ericsson Internal | 2014-03-07 | Page 8 Testing – present results
  9. 9. Ericsson Internal | 2014-03-07 | Page 9 Testing – present results
  10. 10. Ericsson Internal | 2014-03-07 | Page 10 What has been added? › Tool to diff two p2 repos › http://eclipsesource.com/blogs/2012/10/10/ introducing-p2diff/ Final repo
  11. 11. Ericsson Internal | 2014-03-07 | Page 11 P2 diff
  12. 12. Ericsson Internal | 2014-03-07 | Page 12 Putting it all together!
  13. 13. Ericsson Internal | 2014-03-07 | Page 13 › Jenkins is not an SCM! – Keep the list of sites to mirror in your SCM › Minimize the number of jobs – We use Matrix builds › Work on a shared drive or specific Jenkins workspace – Save time by saving on files copy – Does not clutter slaves › Problems – Duplication of URLs between what the b3 files refer to and our list of sites – Build avoidance not supported on p2 metadata – Can’t go back to specific build LESSONS LEARNED
  14. 14. Ericsson Internal | 2014-03-07 | Page 14 Future WoRK › Reduce repo size › “Standardize” structure of Eclipse repos to make discovery more easy › Explore ways to use Artifactory more fully to not copy the jars around
  15. 15. Ericsson Internal | 2014-03-07 | Page 15 › Many tools with their strengths and weaknesses, but we love them for what they are! ConcLUSION
  16. 16. Ericsson Internal | 2014-03-07 | Page 16 questions
  17. 17. Evaluate This Session Sign-in: www.eclipsecon.org Select session from schedule Evaluate: 1 2 3

×