Re: [Fedora QA] #330: Blocker Components are not updated when bug is reassigned
by fedora-badges
#330: Blocker Components are not updated when bug is reassigned
---------------------------------------+-----------------------
Reporter: tflink | Owner: mkrizek
Type: defect | Status: closed
Priority: major | Milestone: Fedora 19
Component: Blocker bug tracker page | Version:
Resolution: fixed | Keywords:
Blocked By: | Blocking:
---------------------------------------+-----------------------
Changes (by tflink):
* resolution: => fixed
* status: reopened => closed
Comment:
fixed in e6d9d4ce42c709cdc553ea06a66c6f084c233a41
merged into develop and master, released in 0.3.0.2 and deployed on stg
and prod
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/330#comment:6>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 11 months
Taskbot and Automation
by Tim Flink
I've not been talking about this a whole lot but I've been working on a
slightly different take on test automation as of late. The system as a
whole is very rough and nowhere near complete but I think it does
demonstrate several of the ideas I'm interested in from a high level.
I wrote several blog posts describing what I'd like to do:
http://tirfa.com/down-with-test-automation-long-live-task-automation.html
http://tirfa.com/an-initial-idea-for-taskbot.html
http://tirfa.com/how-is-taskbot-different-from-autoqa.html
I have my proof-of-concept demo running on my local systems:
http://taskbot.tirfa.net
Before spending a bunch more time on this, I want to see what the
general thoughts were on the approach.
- Does the general concept make sense for Fedora?
- Is this something we should pursue?
If so, I think that some of the next steps should be:
- move the code somewhere so that others can contribute
- migrate the proof-of-concept system to either autoqa-stg or fedora
cloud systems (95% of the setup is ansible-ized so migration isn't
too painful)
- polish the bits that are there so that they actually do most of the
things I'm talking about
- do some investigation to be somewhat sure that we're not ignoring
existing tools (autotest is first on my list, beaker is probably
worth exploring a bit)
Thoughts?
Tim
10 years, 11 months
Re: [Fedora QA] #330: Blocker Components are not updated when bug is reassigned
by fedora-badges
#330: Blocker Components are not updated when bug is reassigned
---------------------------------------+-----------------------
Reporter: tflink | Owner: mkrizek
Type: defect | Status: reopened
Priority: major | Milestone: Fedora 19
Component: Blocker bug tracker page | Version:
Resolution: | Keywords:
Blocked By: | Blocking:
---------------------------------------+-----------------------
Changes (by tflink):
* status: closed => reopened
* resolution: fixed =>
Comment:
Well, this isn't fixed and I'm not sure that it ever could have been. The
db update issue was fixed, but the bugzilla query is not set up to detect
changes in component.
This should be a pretty simple fix of adding the component change to the
bz query we're using.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/330#comment:4>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 11 months
Downtime for AutoQA (nowish)
by Tim Flink
As usual, this is rather last minute but I'm in the process of bringing
autoqa and autoqa-stg down for updates.
I don't think there will be any problems, will send out an all-clear
when I'm done.
Tim
10 years, 11 months
[Fedora QA] #370: Change active milestone list on index to clickable links
by fedora-badges
#370: Change active milestone list on index to clickable links
--------------------------------------+----------------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: minor | Milestone: Undetermined Future
Component: Blocker bug tracker page | Version:
Keywords: easyfix | Blocked By:
Blocking: |
--------------------------------------+----------------------------------
= problem =
Currently, the milestones listed as current on the index are not links. It
would be nice if they linked to the milestone's buglist
= enhancement recommendation =
Change the index template such that the list of currently active
milestones also links to the named milestone's buglist
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/370>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 12 months