Closed
Bug 1083304
Opened 10 years ago
Closed 9 years ago
Migrate jetpack to vcs-sync
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: u429623, Assigned: u429623)
Details
Jetpack has a completely separate home grown method for mirroring content from github to hg.m.o, as they needed the service prior to (legacy) vcs-sync being able to support it. See bug 753527 for history.
The host running that code needs to be upgraded or decommissioned, as soon as practical. Per email discussions, the jetpack needs are part of the default features for vcs-sync. Moving to vcs-sync is the preferred solution.
This move will be slightly tricky, as we need to preserve the existing shas in the current hg mirror. At the time this was put into service, there were still some slight variations in sha's generated by different versions of the tool chain. Approaches possible, in order of implementation ease:
1) try fresh conversion - if shas match, good to go
2) copy over existing conversion repo from hg-sync1-dev
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Comment 2•10 years ago
|
||
I don't think we need to preserve the existing shas. The purpose of this repo is to allow automated testing.
Comment 3•10 years ago
|
||
Sorry I'm confused, is this bug about automating the current uplift process? https://wiki.mozilla.org/Jetpack/Integration_Process
Flags: needinfo?(hwine)
(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #3)
> Sorry I'm confused, is this bug about automating the current uplift process?
> https://wiki.mozilla.org/Jetpack/Integration_Process
The primary goal here is to get an ancient box supporting your current workflow up to snuff. In an email discussion with :dolske, it appeared that migrating it to the supported process would be "best".
The end result of moving it to the supported process would be:
- http://hg.mozilla.org/projects/addon-sdk would be "read only"
- https://github.com/mozilla/addon-sdk.git would be the "official" repository
You'll need to make the call if that changes anything in your wiki process. I'll wait for a positive 'go ahead' before starting.
Flags: needinfo?(hwine)
Comment 5•10 years ago
|
||
(In reply to Hal Wine [:hwine] (use needinfo) from comment #4)
> (In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #3)
> The end result of moving it to the supported process would be:
> - http://hg.mozilla.org/projects/addon-sdk would be "read only"
> - https://github.com/mozilla/addon-sdk.git would be the "official"
> repository
>
> You'll need to make the call if that changes anything in your wiki process.
> I'll wait for a positive 'go ahead' before starting.
Ah ok, that is totally fine, we can actually just kill http://hg.mozilla.org/projects/addon-sdk I'm pretty sure it's not used for anything. Dave might know better than I
Flags: needinfo?(dtownsend+bugmail)
Comment 6•10 years ago
|
||
(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #5)
> (In reply to Hal Wine [:hwine] (use needinfo) from comment #4)
> > (In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #3)
> > The end result of moving it to the supported process would be:
> > - http://hg.mozilla.org/projects/addon-sdk would be "read only"
> > - https://github.com/mozilla/addon-sdk.git would be the "official"
> > repository
> >
> > You'll need to make the call if that changes anything in your wiki process.
> > I'll wait for a positive 'go ahead' before starting.
>
> Ah ok, that is totally fine, we can actually just kill
> http://hg.mozilla.org/projects/addon-sdk I'm pretty sure it's not used for
> anything. Dave might know better than I
oh I guess Dave was saying that git pushes are auto pushed to the hg repo and that is used for testing. If you can just use the git repo then we can kill the hg repo and that would be ideal imho.
Flags: needinfo?(dtownsend+bugmail)
Comment 7•10 years ago
|
||
(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #5)
> (In reply to Hal Wine [:hwine] (use needinfo) from comment #4)
> > (In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #3)
> > The end result of moving it to the supported process would be:
> > - http://hg.mozilla.org/projects/addon-sdk would be "read only"
> > - https://github.com/mozilla/addon-sdk.git would be the "official"
> > repository
> >
> > You'll need to make the call if that changes anything in your wiki process.
> > I'll wait for a positive 'go ahead' before starting.
>
> Ah ok, that is totally fine, we can actually just kill
> http://hg.mozilla.org/projects/addon-sdk I'm pretty sure it's not used for
> anything. Dave might know better than I
We use the hg repo as the source for these tests: https://tbpl.mozilla.org/?tree=Jetpack
(In reply to Erik Vold [:erikvold] (please needinfo? me) from comment #6)
> oh I guess Dave was saying that git pushes are auto pushed to the hg repo
> and that is used for testing. If you can just use the git repo then we can
> kill the hg repo and that would be ideal imho.
Migrating off hg.m.o for test purposes needs to be a separate issue. We'd still need to mirror the github repo to git.m.o. That will be easier to enable with the supported process.
This is no longer part of the jetpack development workflow, and existing box is being decommissioned in bug 1249683.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•8 years ago
|
Component: Tools → General
You need to log in
before you can comment on or make changes to this bug.
Description
•