Bug #827
closed
BSA: improve ability to test locally and remotely
Added by Robinson Tryon over 9 years ago.
Updated almost 8 years ago.
Description
In recent emails Rob pointed out that due to domain restrictions, it's difficult to test the BSA on his local machine. This can be especially important when trying to triage bugs inside the BSA codebase.
As we work on migrating to a TDF-hosted Bugzilla instance, we endeavor to make it easier to test the BSA code in TDF infra, as well as determining if there's more we can do to facilitate local test environments for the BSA (perhaps a downloadable VM?)
- Assignee set to Christian Lohmaier
- Priority changed from Normal to Low
Cloph, can you give us feedback on what's required for that? A separate VM, or just a VHost?
- Assignee changed from Christian Lohmaier to Robinson Tryon
Talked to Cloph - he proposed Rob gets access to the testing VM directly
- Subject changed from BSA: Improve ability to test locally and remotely to BSA: BSA is BROKEN - improve ability to test locally and remotely
- Priority changed from Low to High
Updating description and priority, as BSA seems to be broken ATM
- Assignee changed from Robinson Tryon to Christian Lohmaier
I think there are 2 seperate issues. One is that we currently are unable to contact the FDO-bugzilla from the domain that runs the BSA.
The other is that we can't test locally.
- Subject changed from BSA: BSA is BROKEN - improve ability to test locally and remotely to BSA: improve ability to test locally and remotely
Ok, point taken - let's discuss it in today's team call. For a BSA testbed, we might do that after the next chunk of machines has been migrated, and for the broken BSA, Cloph is currently investigating what's going wrong
- Status changed from New to Rejected
I guess #754 is about the same, so rejecting - if I'm wrong, let me know
- Status changed from Rejected to New
- Assignee changed from Christian Lohmaier to Rob Snelders
No. This is still something we need to do. Testing anything is really hard now. We will need a solution for this.
If #754 (later comments, getting access to VM) is solved, what would
still be missing from our side?
- Status changed from New to Closed
Also available in: Atom
PDF