Closed Bug 533997 Opened 12 years ago Closed 12 years ago

Set up one repo for release repository testing, and another repo for the live release

Categories

(Release Engineering :: General, defect)

x86
Maemo
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sethb, Assigned: aki)

References

Details

(Whiteboard: [fennec l10n])

Attachments

(2 files)

We need to set up release repositories for Fennec single locale builds.
Assignee: nobody → aki
Blocks: 534002
We need to figure out where these go.

mobile/repos/* will be one of these; not sure if they should be in bouncer or not (mounted somewhere?)  If they are in bouncer, we can potentially measure both nightlies and releases.

The release-testing repos should probably be accessible to the community, but not be advertised as the place to download the release.

I'll make my stuff generic so we can change these locations. Not sure who makes the decision though.
I'm currently thinking mobile/candidates/1.0rc1-candidates/repos/ as the candidate release testing repo area, mobile/repos/ for live nightly and release debs.
Attached patch signdebs.mk fixSplinter Review
'Cause I've been tormenting nthomas and bhearsum.  nthomas does know this code better than anyone but me, though, so I can pester him again if that's best.

This also contains the fixes for bug 533341.

- allow for a staging repo working area, so the same slaves can be used for staging and production without dirtying each others' local repos
- rebuild the install file every time, but get rid of the non-functional touch workdir
- allow for a new repo
- remove tmp.deb in case the makefile errors out during xulrunner-hack.
Attachment #418129 - Flags: review?(catlee)
Comment on attachment 418129 [details] [diff] [review]
signdebs.mk fix

> download-repository:
>-	rsync -azv -e 'ssh -i $(SSH_KEY)' $(RSYNC_ARGS) $(STAGE_USERNAME)@$(STAGE_SERVER):$(STAGE_PATH)/dists/. $(WORKDIR)/dists/.
>+	ssh -i $(SSH_KEY) $(STAGE_USERNAME)@$(STAGE_SERVER) "test -d $(STAGE_PATH)/dists" && \
>+	  rsync -azv -e 'ssh -i $(SSH_KEY)' $(RSYNC_ARGS) $(STAGE_USERNAME)@$(STAGE_SERVER):$(STAGE_PATH)/dists/. $(WORKDIR)/dists/. || \
>+	  echo "No repository to download."

Are you intending for this to ignore the error if there's no repository to download?  I think this will return 0 if there's no repo, and so future steps will still proceed.
Comment on attachment 418130 [details] [diff] [review]
updates to get release candidate repos / release repos working

rubber-stamp applied.  I don't see anything wrong with this patch, but I also don't know what I'm looking for.

I'm curious why you moved get_fennecURL to an instance method.
Attachment #418130 - Flags: review?(catlee) → review+
(In reply to comment #5)
> Are you intending for this to ignore the error if there's no repository to
> download?  I think this will return 0 if there's no repo, and so future steps
> will still proceed.

True. I can remove the echo.

> I'm curious why you moved get_fennecURL to an instance method.

I wanted to check self.release, and don't know how to get self from build.
(In reply to comment #5)
> Are you intending for this to ignore the error if there's no repository to
> download?  I think this will return 0 if there's no repo, and so future steps
> will still proceed.

Oh, I think I misunderstood your question.

Yes, I want it to proceed.  Otherwise we'll have to create a dummy repo on the server any time we add a new branch or locale or repository location.  The final "|| echo ..." is probably unnecessary, but I do want to catch the error on "test -d" since I want it to proceed.
Attachment #418129 - Flags: review?(catlee) → review+
Comment on attachment 418130 [details] [diff] [review]
updates to get release candidate repos / release repos working

http://hg.mozilla.org/build/buildbot-configs/rev/c40e578c5e93
Attachment #418130 - Flags: checked-in+
I'm going to work on documenting all this now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.