Bugzilla – Full Text Bug Listing
| Summary: | Move mwe git to Github instead of gerrit | ||
|---|---|---|---|
| Product: | Community | Reporter: | Christian Dietrich <christian.dietrich.opensource> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | karsten.thoms, sven.efftinge |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Christian Dietrich
Ok I have some questions: 1) Is there a time in the next few days that works for you? 2) How would you like to actually do the move? Did you just want Webmaster to create a new repo at Github and you can push the content when you're ready? -M. @Karsten what would be the best day for you. @M there is already https://github.com/eclipse/mwe so i assume this one could be change to be primary? so i am not keen about doing the move myself. we will be busy enhough with adapting the jenkins jobs It is close to vacation and still plenty of work. Best would be next monday (23th). What do I need to do? i assume this is just about changing the jobs. what do you think matt? (In reply to Christian Dietrich from comment #2) > there is already https://github.com/eclipse/mwe That's a mirror of your current repo, so if it's already current all we may have to do is ask Github to stop the mirroring process, and then you can start using it sometime later. If it's not up to date then we'll probably be best served by removing it, and starting 'fresh'. > so i am not keen about doing the move myself. Ok, well if you can confirm the state of the Github mirror we can sort out how we'll do the move. (In reply to Karsten Thoms from comment #3) > What do I need to do? I expect the biggest task to be re-wiring your builds to use the Github URLs, although you could test that now to get a feel for what will be needed. You might want to get Fred and Mikael involved(file a bug against the CI component asking for help) if you have any specific concerns or issues. Beyond that committers will need to update their repo URLs, and we'll need to add the Github URL to the PMI so our tools can start managing the repo. There will be a slight delay once the sync tool starts managing the repo before you can use it. -M. yes https://github.com/eclipse/mwe is up to date so we could simply start using it after you turned off the mirroring. @Karsten: i think we will get the jobs changed ourselves. correct? Ok, I'll ask Github to stop the mirroring process Monday morning, add the repo to the PMI and we should be good to go a few hours later. The timing will be determined mostly by Githubs response time(I've found them to be pretty quick). -M. > @Karsten: i think we will get the jobs changed ourselves. correct?
Yes, should be rather easy then.
(In reply to Eclipse Webmaster from comment #7) Github has let me know that they've stopped the mirroring process. As such I've added the Github repo to the PMI so MWE committers should start receiving invites to join the Github MWE team when the sync tool runs in an hour or so. After that you may need to do a little 'fixing' to make sure the Github repo has all of the commits the Eclipse.org repo has. Once that's done and you've switched to the Github repo let us know and we'll archive the Eclipse.org MWE repo. -M. looks good. thanks => you can archieve now (In reply to Christian Dietrich from comment #11) > => you can archieve now LOL, that is a great typo :) I've marked the Eclipse.org repo as read only, and scheduled it for cleanup. -M. |