Re: Git forge requirements discussion
On Thu, Jan 23, 2020 at 04:02:42PM +0100, Kamil Paral wrote: > I don't think we have some very special requirements. For the planned > blocker review async discussion, we need API to be able to add comments and > edit the ticket description, ideally also adjust ticket tags, milestones or > some other properties. We need a webhook support to get notified of changes > or access to a message bus. Nothing unusual I think. Or, of course, native > support for voting/polls (ideally multiple per a single ticket) would be > even better :-) Can you put the voting/polls idea in the form of a user story? -- Matthew Miller Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Re: Self-introduction : Zubin
On Sat, Mar 30, 2019 at 02:56:15PM +0530, zubin choudhary wrote: > Hi, I'm Zubin. I'm 19 years old. Using Linux for a while now wanted to > contribute back to the community, Fedora is a great community to be part > of. I have some experience in python scripting and on Web Programming. > Looking forward to being a part of this community Zubin Choudhary Welcome Zubin! Are there any areas in particular you'd like to work on? -- Matthew Miller Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org
Re: How do I run the standard test interface tests with docker?
On Sat, Apr 21, 2018 at 05:07:16PM +0200, Miro Hrončok wrote: > >I'm trying to follow the following guide: > >https://fedoraproject.org/wiki/CI/Tests#Wrapping > >What piece am I missing? > Is this a wrong place ask? Maybe try c...@lists.fedoraproject.org? -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: Need help ?
On Fri, Sep 01, 2017 at 05:23:42PM -0400, Ellen OSullivan wrote: > >> It is worth noting that to obtain a @fedoraproject.org email alias, you > >> need to be what is called “CLA+1”. > I need to become a “CLA+1” - I am not in a group. Should I ask in > the Fedora-QA list? Yeah, I think someone there should be able to sponsor you. -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: Need help ?
On Fri, Sep 01, 2017 at 08:57:54PM -, Ellen OSullivan wrote: > I'm a newbie, would like to help out with something. I'm dev/qa > automation at work but fairly new to Linux. Willing to clean the > floors, make the coffee :-) Hi Ellen, and welcome! I think we need qa automation expertise even more than we need cleaning and coffeemaking. :) Have you seen this post on getting started with Fedora QA? https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/ -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: Taskotron CI in Taskotron
On Thu, Feb 09, 2017 at 03:29:13AM +0100, Josef Skladanka wrote: > I finally got some work done on the CI task for Taskotron in Taskotron. The > idea here is that after each commit (of a relevant project - trigger, > execdb, resultsdb, libtaskotron) to pagure, we will run the whole stack in > docker containers, and execute a known "phony" task, to see whether it all > goes fine. This is excellent. I'd love, eventually, to get to a point where we can run the checks _pre_ commit and gate on them. Is there a path from this to that? -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: Task Result Dashboards
On Wed, Jan 11, 2017 at 12:43:23PM +0100, Lukas Brabec wrote: > * What is the motivation, what do we want to achieve with such >dashboards and who is the 'non-techincal audience'? I guess that depends on what you mean by the technical audience. Other than people who are steeped in QA day in and day out, I can see several audiences: * Volunteer packagers who have hit a failed check and are trying to dig out what it means. * Users who are following a particular package or an issue they've encountered * Anyone in the project who wants to have some task automated and have results that are shareable. I'm thinking right now of the planned Docs engine (where a git commit triggers an a build or a translations update triggers a cache refresh, and then the build results are pushed to another git repo which backs a static web site) * People not currently in the project who we want to impress and entice into becoming contributors with our awesome and easy-to-use tooling. * Me, trying to get an overview of the current state of Fedora activity :) Is this what you are looking for? -- Matthew Miller <mat...@fedoraproject.org> Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: openQA: run 'all' nightly instead of 'current'?
On Mon, Aug 17, 2015 at 09:08:31AM -0700, Adam Williamson wrote: Hi folks! So I was wondering: what do folks think about running openQA's 'all' mode nightly (on the BOS deployment) instead of the 'current' mode? +1; do it! compose. I think it'd be nice to have an idea every day if Rawhide and/or Branched are broken. We could then actually write some kind of 'israwhidebroken.com' thing. Ideally we'd be doing this with fedmsg How do we get from it's broken today to and someone should do something about it? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Proposal: No Cloud Disposable Clients
On Thu, Dec 04, 2014 at 05:00:31PM -0700, Tim Flink wrote: What if we turned that on it's head a bit and put VM spawning into the task itself - spawn a vm local to the buildslave that is then responsible for the actual work in the task instead of doing all the work inside the buildslave process? This would allow for image and vm requirements to be described in the task without weird multiple parsings and could avoid most if not all of the problems/complexity that we've started seeing in getting buildbot to work with latent buildslaves. This seems both sane and useful to me, but we _will_ want to run at least some tests in the actual cloud environments. Should that stuff go _back_ to fedimg? (Also random other note: if you're using cloud-init to expand image root, ssh keys can be part of that too, right?) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Proposal: No Cloud Disposable Clients
On Thu, Dec 04, 2014 at 06:56:08PM -0700, Tim Flink wrote: This seems both sane and useful to me, but we _will_ want to run at least some tests in the actual cloud environments. Should that stuff go _back_ to fedimg? As I understand it, most of the stuff that the cloud folks want to test can be done on the cloud image in any virt environment. Most, yes. But... There are a couple of things I can think of that would require the full cloud system (does the image boot and have ssh connectivity in Open Stack, AWS etc.) but I think that stuff is somewhat orthogonal to how the client is booted. Does it boot? is definitely key, but there's also other metadata-service related things to test. (Is the userdata read correctly? Is the hostname set? ...) And then there are some environment-specific tests we might want, too. (Can we retrieve the system logs via an API call?) But... It's probably worth asking the question of whether some tests should be in fedimg. If I'm right and the only credential-requiring tests are whether or not the image boots in service and we can ssh into it, it might make more sense to put that into fedimg and not deal with the credential issue in Taskotron. Maybe we start with just the basic test there and not worry about the above until we're _way_ further along on having any automated tests at all. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Next Steps for Taskotron
On Thu, Jul 24, 2014 at 04:14:33PM -0400, Matthew Miller wrote: I don't think a separate openstack instance should be necessary... I'm not sure how ours is currently configured -- and I certainly haven't kept up with the state of the art in openstack networking -- but having a separate vlan for a tenant is a thing openstack is a thing openstack does. Or maybe is a thing in openstack. Either way. /me goes to get some calories in his brain -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
Re: Taskotron and Cloud Image tests
On Thu, Apr 17, 2014 at 09:11:10AM -0600, Tim Flink wrote: Does someone have budget or account time that could be used for this in an account that we could use? I wonder if trying to use the fedora openstack setup be a better route (assuming that valid can work with openstack). I think we can use the Fedora community cloud EC2 account for this, but I will double check. If that's not possible, I'll beg for the required budget. We _should_ test on both OpenStack and EC2. -- Matthew Miller-- Fedora Project--mat...@fedoraproject.org Tepid change for the somewhat better! ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
