Closed Bug 850473 Opened 11 years ago Closed 11 years ago

Deploy BigTent to stage with train-2013.01.17 Release 12

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: ozten, Assigned: gene)

References

Details

(Whiteboard: [qa+])

+++ This bug was initially created as a clone of Bug #848130 +++

Release 12 has a fix for Issues 129 and 130.

SHA: 8062d69662787a63c75f65ef84ccb4432403a8de
tree: https://github.com/mozilla/browserid-bigtent/tree/train-2012.01.17
Is this mission critical? If so, do we get this pushed to current Stage or the new AWS version?

I ask all this because we are actively doing Pass 1 Stage testing of BigTent.
Both of these had been discussed and were waiting for code review. Due to time constraints, I've gone ahead and merged down.

> Is this mission critical?

https://github.com/mozilla/browserid-bigtent/issues/130 - 5 star blocking bug. Gives us a way to rollback the release

https://github.com/mozilla/browserid-bigtent/issues/129 - was a nice to have and let's progress screen render larger on mobile devices, very low risk.

> If so, do we get this pushed to current Stage or the new AWS version?

You guys call. To re-iterate jrgm's earlier points, probably good to either 1) test push this to old stage before doing AWS or 2) make and push this rpm to new AWS based stage, after we've got that working
We switched to using the AWS stage instance about 17:00 PDT today. There appears to be an issue there to track down, which my bet is in on the cause - https://github.com/mozilla/browserid-bigtent/issues/142

I can spin this rpm again tomorrow and push on scl2 stage to check that it starts ok, and when we resolve the other issue, we can take that rpm to aws and continue testing.
So the issue noted in comment 3 above was due to ntp not running on the aws boxes for bigtent stage. 

Today's fun distracted me. I will spin the rpm and test-deploy to stage tomorrow morning. 

I have one moot question about l10n rev that I will confirm with ozten tomorrow morning.
Blocks: 851524
built ~/workspace/browserid-bigtent/rpmbuild/RPMS/x86_64/browserid-bigtent-0.2013.01.17-12.el6_114069.x86_64.rpm on r6. Now going to push onto stage (which is dormant) and then hand to gene to go on to aws.
On physical stage : $ curl -s 'http://127.0.0.1:3030/ver.txt'
8062d69 Bumping to release 12
locale svn r114069
Assignee: nobody → gene
On the r6 build machine:
/home/jrgm/workspace/browserid-bigtent/rpmbuild/RPMS/x86_64/browserid-bigtent-0.2013.01.17-12.el6_114069.x86_64.rpm
aws stage updated
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
curl -s https://yahoo.login.anosrep.org/ver.txt

8062d69 Bumping to release 12
locale svn r114069
Status: RESOLVED → VERIFIED
Blocks: 852746
Blocks: 853238
Blocks: 854596
Whiteboard: [qa+]
Depends on: 861004
No longer depends on: 861004
You need to log in before you can comment on or make changes to this bug.