Add jobs for esr10 release candidate builds. Fixes issue #155 #156

Closed
wants to merge 2 commits into
from

Projects

None yet

3 participants

@whimboo
Contributor
whimboo commented Aug 27, 2012

No description provided.

@davehunt davehunt and 2 others commented on an outdated diff Aug 27, 2012
...s-master/jobs/release-mozilla-esr10_addons/config.xml
@@ -0,0 +1,183 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<project>
+ <actions/>
+ <description>Execute add-ons tests for ESR10 release candidate builds.</description>
@davehunt
davehunt Aug 27, 2012 Member

To be consistent with other jobs, this should be Execute add-ons tests for ESR10 candidate builds. This applies to all jobs.

@whimboo
whimboo Aug 27, 2012 Contributor

Not sure what you mean here. Those builds are release candidate builds. Skipping release here will be misleading.

@ashughes1
ashughes1 Aug 27, 2012 Contributor

I think I would prefer wording like:

10.0.7esr#1: Execute add-ons tests for ESR10 candidate builds.
10.0.7esrpre: Execute add-ons tests for ESR10 nightly builds.
16.0b1#1: Execute add-ons tests for Beta candidate builds.
15.0#1: Execute add-ons tests for Release candidate builds.

...or something along these lines.

@whimboo
whimboo Aug 27, 2012 Contributor

So lets do it this way then.

@davehunt davehunt commented on an outdated diff Aug 27, 2012
...s-master/jobs/release-mozilla-esr10_addons/config.xml
@@ -0,0 +1,183 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<project>
+ <actions/>
+ <description>Execute add-ons tests for ESR10 release candidate builds.</description>
+ <logRotator>
+ <daysToKeep>-1</daysToKeep>
+ <numToKeep>100</numToKeep>
+ <artifactDaysToKeep>-1</artifactDaysToKeep>
+ <artifactNumToKeep>-1</artifactNumToKeep>
+ </logRotator>
+ <keepDependencies>false</keepDependencies>
+ <properties>
+ <hudson.queueSorter.PrioritySorterJobProperty>
+ <priority>620</priority>
@davehunt
davehunt Aug 27, 2012 Member

This means the priority is equal to release-mozilla-release jobs. I think ESR should have it's own value.

@ashughes1
Contributor

Priority in general should be as follows:
release > esr17 > esr10 > beta > aurora > nightly

Note that we will have 2 overlapping ESR10 releases (12 weeks) to allow enterprise time to conduct internal testing of the massive differences between Firefox 10 and 17.

In other words, we'll need to support:

Firefox 15, 10.0.7esr
Firefox 16, 10.0.8esr
Firefox 17, 10.0.9esr, 17.0esr
Firefox 18, 10.0.10esr, 17.0.1esr
Firefox 19, 17.0.2esr
etc...

@whimboo
Contributor
whimboo commented Aug 27, 2012

So we will have to increase the priority for release builds because of limited room to inject a priority in-between:

ondemand = 1000
release-mozilla-release = 600
release-mozilla-beta = 500

So I would propose:

ondemand = 1000
release-mozilla-release = 800
release-mozilla-esr(CURRENT) = 700
release-mozilla-esr(LAST) = 600
release-mozilla-beta = 500

Once we remove old entries for ESR builds we have to update the priorities. Does that sound fine?

@ashughes1
Contributor

That sounds fine to me.

@whimboo
Contributor
whimboo commented Aug 27, 2012

Pull has been updated accordingly. Please check again.

@davehunt
Member

Looks good.

@whimboo
Contributor
whimboo commented Aug 27, 2012

Landed on all branches.

@whimboo whimboo closed this Aug 27, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment