799514 - automate symlink creation for beta and esr releases

Status: RESOLVED DUPLICATE of bug 785965

(Release Engineering :: Release Automation: Other, defect)

Description

[[e-mail] (:bhearsum)]

We just added symlink updating automation over in bug 785965. QA would like symlinks to be maintained for ESRs and Betas, so they can have static download links for their automation. It shouldn't be simple to enable the same automation for these.

Comment 1

[Rail Aliiev [:rail]]

Attachment: tools

configs incoming

Comment 2

[Rail Aliiev [:rail]]

Attachment: configs

Comment 3

[Dave Hunt [:davehunt] [he/him] ⌚BST]

Looking at the attached patches, would it be possible to include a 'latest-esr' instead (or in addition to) 'latest-10.0esr'? The reason is, having the version number will incur a maintenance cost, even if it is once a year or so.

Comment 4

[[e-mail] (:bhearsum)]

I don't want to add a manual step here - that's exactly what we're trying to get rid of. How about we set mozilla-esr10 to symlink to 'latest-esr' for now, and then when we ship the first esr17 we'll set it up to symlink to 'latest-esr', and esr10 to symlink to either nowhere or 'latest-esr10'.

Comment 5

[Dave Hunt [:davehunt] [he/him] ⌚BST]

(In reply to Ben Hearsum [:bhearsum] from comment #4)
> I don't want to add a manual step here - that's exactly what we're trying to
> get rid of. How about we set mozilla-esr10 to symlink to 'latest-esr' for
> now, and then when we ship the first esr17 we'll set it up to symlink to
> 'latest-esr', and esr10 to symlink to either nowhere or 'latest-esr10'.

Sounds good to me.

Comment 6

[Rail Aliiev [:rail]]

Comment on attachment 671968 [details] [diff] [review]
tools

Incorporated into bug 785965

Comment 7

[Rail Aliiev [:rail]]

Comment on attachment 671972 [details] [diff] [review]
configs

Incorporated into bug 785965

Comment 8

[[e-mail] (:bhearsum)]

This is getting fixed is a roll-up patch in bug 785965