#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Keywords: --------------------+------------------------------------------------------- We want to be able to deploy AutoQA onto a staging server. Mainly it means we must be able to disable or redirect the produced test output. We want to be able to disable or redirect email sending (that includes standard results and also opt-in emails). We want to be able to disable posting Bodhi comments (or logging it somewhere else instead). We want to be able to use a different ResultDB instance.
Make sure all the bits are in place and add required functionality if necessary.
#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: mkrizek Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Changes (by kparal):
* owner: => mkrizek
Comment:
mkrizek started to work on this a few days ago.
#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: mkrizek Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: core | Resolution: Keywords: | --------------------+------------------------------------------------------- Comment (by kparal):
According to the [https://fedorahosted.org/pipermail/autoqa- devel/2010-December/001416.html discussion] we would also like to have configurable URLs for our Koji and Bodhi instances.
#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: mkrizek Type: task | Status: closed Priority: major | Milestone: 0.4.4 Component: core | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by kparal):
* status: new => closed * resolution: => fixed
Comment:
Pushed as commit 5c144110b64ee920a86538bd77b758d32de89f8c.
Thanks, Martin. Closing.
#241: Add support for a staging server ---------------------------+------------------------------------------------ Reporter: kparal | Owner: mkrizek Type: task | Status: reopened Priority: major | Milestone: 0.4.4 Component: documentation | Resolution: Keywords: | ---------------------------+------------------------------------------------ Changes (by kparal):
* status: closed => reopened * resolution: fixed => * component: core => documentation
Comment:
No, not closing :-) These changes may need some documentation changes, adjusting component.
#241: Add support for a staging server ---------------------------+------------------------------------------------ Reporter: kparal | Owner: Type: task | Status: new Priority: major | Milestone: 0.4.4 Component: documentation | Resolution: Keywords: | ---------------------------+------------------------------------------------ Changes (by kparal):
* owner: mkrizek => * status: reopened => new
#241: Add support for a staging server --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: task | Status: closed Priority: major | Milestone: 0.4.4 Component: core | Resolution: fixed Keywords: | --------------------+------------------------------------------------------- Changes (by kparal):
* status: new => closed * resolution: => fixed * component: documentation => core
Comment:
After my and Martin's review it seems that there are no documentation changes needed. Closing.
autoqa-devel@lists.fedorahosted.org