Build infrastructure should NOT use https://ftp-ssl.mozilla.org/ to obtain bundle. Use S3 or the CloudFront CDN.

RESOLVED FIXED

Status

RESOLVED FIXED
3 years ago
a year ago

People

(Reporter: ishikawa, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
I have noticed a flurry of build failures on C-C tryserver since the end of December. 

Typical symptom is 

CalledProcessError: Command '['hg', 'unbundle', '--traceback',
'https://ftp-ssl.mozilla.org/pub/mozilla.org/thunderbird/bundles/try-comm-central.hg']'
returned non-zero exit status 255

But others are also observed.

According to a discussion on dev-moz-build (moz.dev.build newsgroup), 
https://groups.google.com/forum/#!topic/mozilla.dev.builds/rHfqih0fDMo

Gregory Szorc's comment:
--- begin quote

I consider it a bug that we're obtaining bundles from https://ftp-ssl.mozilla.org/. All automation should be using the clone bundles / bundleclone facilities in Mercurial for cloning repos from S3 or the CloudFront CDN. See https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmo/bundleclone.html.

--- end quote

And it was suggested that we file a bug here. So here it goes.

The mentioned URL suggests that "If you think bundles should be made available, let a server operator know by filing a Developer Services :: hg.mozilla.org bug or by asking in #vcs on irc.mozilla.org."

I have no idea where this "Developer Services :: hg.mozilla.org" should be mentioned in the bugzilla. 

Anyway, I hope the people looking after infrastructure take note.

TIA


I've gotten a lot of feedback that the S3 and CloudFront CDN hosting is faster and more reliable. You want to use it.
(Reporter)

Comment 1

3 years ago
Oops. The last sentence is an extra copy from the news post.

> I've gotten a lot of feedback that the S3 and CloudFront CDN hosting is faster and more reliable. You want to use it.
As far as I can tell, this is fixed now.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
(Reporter)

Comment 3

a year ago
(In reply to Tom Prince [:tomprince] from comment #2)
> As far as I can tell, this is fixed now.

Thank you. An occasional patch submitter who uses tryserver build service doesn't know all the details (blackmagic almost) of the innards of the build infrastructure. I suspect we see less failures due to this issue now then.
You need to log in before you can comment on or make changes to this bug.