Closed Bug 1050131 Opened 10 years ago Closed 10 years ago

Write a script to auto-extract from mozilla-central the standalone content into the loop-client git repo

Categories

(Hello (Loop) :: Client, defect, P1)

defect

Tracking

(firefox34 fixed)

RESOLVED FIXED
mozilla34
Tracking Status
firefox34 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

Details

(Whiteboard: [p=1])

Attachments

(1 file, 1 obsolete file)

In bug 1042528 we're defining the initial release process for the standalone content/link-clicker UI web parts of Loop.

For ease of releasing to services, we're extracting the code to a git repository from the authoritative mercurial repository, mozilla-central.

Initial requirements I'm setting myself on the script:

- Extract changesets since the last update
- For each changeset that changes the Loop standalone content, create a new changeset in the git-repository with the changes
- Translate the file structure into one that is suitable for releasing the standalone content (using the structure we have today)
- Enable the tests to be run successfully in the loop-client repository with the new structure

The initial aim is to make this suitable for running in a cron job somewhere.
Priority: -- → P1
Whiteboard: [p=1]
Target Milestone: --- → mozilla34
Attached file WIP extraction script (obsolete) —
This is the WIP I have already, it is still in work, so far it does the basic extraction, but doesn't pull the latest versions of repos, nor does it fix the tests yet.
This implements the script.

Remy: Can you review this from a python/services perspective? 

Dan: Can you check that this looks reasonable, and we're happy with the output and the changeset annotations? There's an example output here:

https://github.com/Standard8/loop-client/compare/1050131-auto-extract

The script is based on MercurialAPI and GitPython. I tried using GitPython all the way through it, but it really was difficult and the documentation is poor.

I suspect with more time, we might be able to get GitPython working properly, but given that what we've now got works, the time spent versus correctness trade-off means I don't think its worth spending extra time.

The patch achieves everything in comment 0, and we can at least start up the local server, have it run correctly, and also load the test files with them succeeding.

Hence this is a good place to start any enhancements from, and means we can get the auto-merge running on a regular basis.
Attachment #8469109 - Attachment is obsolete: true
Attachment #8469261 - Flags: review?(rhubscher)
Attachment #8469261 - Flags: review?(dmose)
Blocks: 1050295
Attachment #8469261 - Flags: review?(rhubscher) → review+
Comment on attachment 8469261 [details] [review]
Link to Github pull-request: https://github.com/mozilla/loop-client/pull/38

r=dmose, with comments in the github PR appropriately addressed.
Attachment #8469261 - Flags: review?(dmose) → review+
Untracking for QA. Please needinfo me to request testing.
Flags: qe-verify-
QA Contact: anthony.s.hughes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: