Category: Development (page 1 of 12)

All articles in this category are related to the various Development teams in the Fedora Project, such as package maintainers, quality assurance, and more. https://fedoraproject.org/wiki/Development

tmt hint 02: under the hood

After making the first steps with tmt and investigating the provisioning options let’s now dive together a little bit more and look Under The Hood to see how plans, tests and stories work together on a couple of examples.

Continue reading

CPE to staff EPEL work

We are pleased to announce that Red Hat is establishing a small team directly responsible for participating in EPEL activities. Their job isn’t to displace the EPEL community, but rather to support it full-time. We expect many beneficial effects, among those better EPEL readiness for a RHEL major release. The EPEL team will be part of the wider Community Platform Engineering group, or CPE for short.

As a reminder, CPE is the Red Hat team combining IT and release engineering from Fedora and CentOS.
Right now we are staffing up the team and expect to see us begin this work from October 2021. Keep an eye on the EPEL mailing list and the associated tracker as we begin this exciting journey with the EPEL community.

Exploring our bugs, part 3: time to resolution

This is the third and final part of a series I promised during my Nest With Fedora talk (also called “Exploring Our Bugs”). In this post, I’ll analyze the time it takes to resolve bug reports from Fedora Linux 19 to Fedora Linux 32. If you want to do your own analysis, the Jupyter notebook and source data are available on Pagure. These posts are not written to advocate any specific changes or policies. In fact, they may ask more questions than they answer.

Continue reading

Exploring our bugs, part 2: resolution

This is the second part of a series I promised during my Nest With Fedora talk (also called “Exploring Our Bugs”). In this post, I’ll be analyzing the bug report resolutions from Fedora Linux 19 to Fedora Linux 32. If you want to do your own analysis, the Jupyter notebook and source data are available on Pagure. These posts are not written to advocate any specific changes or policies. In fact, they may ask more questions than they answer.

Continue reading

Exploring our bugs, part 1: the basics

This is this first part of a series I promised during my Nest With Fedora talk (also called “Exploring Our Bugs”). In this post, I’ll review some of the basic statistics from analyzing bugs from Fedora Linux 19 to Fedora Linux 32. If you want to do your own analysis, the Jupyter notebook and source data are available on Pagure. These posts are not written to advocate any specific changes or policies. In fact, they may ask more questions than they answer. This first post looks at some basic information, including counts, priorities, and duplicates.

Continue reading

Source-git SIG report #1

Greetings from the Fedora source-git SIG! We are planning to start publishing reports of what we are working on so everyone can easily pay attention and get involved if interested. If you have any ideas, comments or requests, don’t be shy and let us know 🙂

Here’s a short list of things which we are working on.

Continue reading

Migrating the DNF Stack CI to GitHub Actions

DNF’s continuous integration (CI) has historically struggled from multiple standpoints, including: reliability, coverage, and results not being publicly available. We recently migrated to GitHub Actions, which—in addition to increasing our integration test suite stability and coverage—led to it being more reliable and its results available publicly to contributors.

Continue reading

tmt hint 01: provisioning options

After the initial hint describing the very first steps with tmt, let’s have a look at the available test execution options. Recall the user story from the very beginning:

As a tester or developer, I want to easily run tests in my preferred environment.

Do you want to safely run tests without breaking your laptop? Use the default provision method virtual which will execute tests under a virtual machine using libvirt with the help of testcloud:

Continue reading

tmt hints: create a basic test

For those who still haven’t heard: tmt is now fully-supported in Packit, Fedora Continuous Integration (CI) system, and the RHEL CI system. Now you can use the same concise and consistent config to enable tests across all of them, more easily open source tests, share test coverage across releases ,and run tests as early as possible.

In the coming weeks we’ll be sharing short, bite-sized examples demonstrating tmt usage. With these, new users can get started quickly and existing users won’t miss various interesting and useful features hidden under the hood.

Here we go with the first set of examples showing how to quickly enable a simple smoke test for your component, assuming you are in your project git repository:

    sudo dnf install -y tmt
    cd git/fedora/rpms/foo
    tmt init --template mini
    vim plans/example.fmf

Adjust the example plan to run the desired command:

    summary: Basic smoke test
    execute:
        script: foo --version

The very minimal config is really just two lines:

    execute:
        script: make test

Now submit the pull request and wait for the results:

    git add .
    git checkout -b smoke-test
    git commit -m "Enable a simple smoke test"
    git push fork -u smoke-test

Eager to learn more? Not patient enough to wait for the results from the CI pipeline? Willing to safely execute tests from your laptop right now? Check the rest of the first chapter of our brand new guide to learn more.

“Houston, we have video”: Matrix video calls on the PinePhone

The Fedora Mobility SIG is working to get Fedora Linux working on mobile device. This includes the PinePhone, a smartphone built with open hardware. Many distros are working to add support for the features that smartphone users expect, including video calls. I was able to use Firefox as a fully-featured Matrix client to make video calls.

Continue reading
Olderposts

Copyright © 2021 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑