629739 - Mozmill Crowd extension needs location to host Mozmill test environment files

Status: VERIFIED FIXED

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

The Mozmill Crowd extension needs additional files to be installed, before any Mozmill tests can be executed. Therefor we have zip packages currently at http://people.mozilla.com/~hskupin/mozmill-crowd/.

But people.mozilla.com doesn't have PHP support and also no secure way of accessing the files, which we absolutely need.

The requirements we have are:
* Allow us to run a simple PHP script which parses the request URL for the client platform, checks for updates, and serves the right zip archive
* SSL support (QMO already seems to have it)
* A fixed URL we can use for the requests ("/extensions/mozmill-crowd/" ?)
* SSH access to upload new versions of the environment

I would really appreciate it when we could fine a solution as soon as possible.

Comment 1

[Aakash Desai [:aakashd]]

I'm not sure if QMO is the right place for this as its meant for interacting
with testers in our community, not for serving up automated test packages.

It looks like Henrik just wants a pace with SSL support, that can run a PHP
script which serves up packages on request.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Those packages contain no automated tests but test environments.

We want to promote the Crowd Extension heavily once we have developed it to a state we can go public for real. Our testers are on QMO, our promotion will be on QMO, why not the parts which are necessary to help them to run automated tests as easy as possible? Also the extension id is [e-mail], which shows the heart of it.

Comment 3

[Matt Evans [:mevans]]

I don't see an issue for serving these files from QMO. Henrik is correct in that this will be heavily promote on QMO. However, who will be responsible for implementation and maintenance of this?

Comment 4

[Aakash Desai [:aakashd]]

Sure, if this is the direction you want it to go, then we can incorporate it into the QMO 4.0 timeframe. Henrik, please file a bug under QMO in regards to what you want out of the php script and mark it with the 4.0 milestone.

Comment 5

[Jeremy Orem [:oremj]]

Is there anything I can do on this bug or should it be assigned elsewhere?

Comment 6

[Aakash Desai [:aakashd]]

Jeremy, there's going to be an IT component here for a release time frame of two months from now for QMO. There'll be a webdev bug linked to from here, but no work is needed for now. So you can un-assign yourself. Thanks for the answers on irc.

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Aakash, what's the ETA for 4.0? In my case we can't wait a half year to make this happen.

Comment 8

[Aakash Desai [:aakashd]]

> for a release time frame of two months from now for QMO

Comment 9

[Matt Evans [:mevans]]

I don't think this request needs to be part of a planned release.

Comment 10

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Why incomplete? This is still a valid bug and has originally filed under QMO. So we have to move it back.

(In reply to comment #8)
> > for a release time frame of two months from now for QMO

That's a bit too long for us, we would need it as soon as possible. At least the files should be hosted on QMO so I could point to them.

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to comment #10)
> That's a bit too long for us, we would need it as soon as possible. At least
> the files should be hosted on QMO so I could point to them.

Aakash, can you please propose a possible solution? Which steps can we do in the near term?

Comment 12

[Aakash Desai [:aakashd]]

To get an idea of what can be done here in the limited time frame you've mentioned, I'll need the following:

1. Why is this a priority? What is this blocking you from doing?
2. Are other groups outside of QA blocking on this? If so, in what way are they blocked?
3. What work would constitute webdev and IT resources being needed?

Comment 13

[Matt Evans [:mevans]]

fwiw, this is the type of request we should be able to handle inhouse (no IT or WebDev resources) required. Al could this be something you could take care of?

Comment 14

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to comment #12)
> 1. Why is this a priority? What is this blocking you from doing?

AMO doesn't support hosting of other packages than extensions. Our Crowd extension needs other packages. Those packages have to be hosted on a secure location. See https://bugzilla.mozilla.org/show_bug.cgi?id=564648#c2

> 2. Are other groups outside of QA blocking on this? If so, in what way are they
> blocked?

We are blocked in not being able to get fully reviewed on AMO.

> 3. What work would constitute webdev and IT resources being needed?

Haven't I already specified everything in comment 0?

Re: webdev, not sure about their time. At least I would need them to review the PHP script. If they would have time to write it, it would be even better.

Comment 15

[Al Billings [:abillings - ex-MoCo]]

(Somehow this wasn't in my bugmail inbox)

This would probably be best served by the Apache server QA is setting up to host the litmus-test repository files and to be used as a resource for manual and automated QA tests. We would just need to add PHP to the server.

Comment 16

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We have discussed that during our automation meeting and we will check what's necessary re: uploads when hosting will be provided by QMO.

Comment 17

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Al, can you please create a new subdomain on mozqa.com, which we can use for hosting all related content for the crowd extension? This subdomain should get the name mozmill-crowd.mozqa.com. Thanks.

Comment 18

[Al Billings [:abillings - ex-MoCo]]

mozmill-crowd.mozqa.com is up and functioning.

Comment 19

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Environment files are now located at: https://mozqa.com/mozmill-env/