• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Alma 8, Rocky 8, Fedora 35, Debian 11 - Now being tested

    Scheduled Pinned Locked Moved
    General
    2
    2
    345
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Wayne WorkmanW
      Wayne Workman
      last edited by Wayne Workman

      Hello Fog Community!

      I’m happy to inform that as the title says, Alma 8, Rocky 8, Fedora 35, and Debian 11 have been added to the daily installation tests. Fedora 32 has been removed.

      In addition to this, I’ve re-enabled testing the working-1.6 branch as I see there is now some activity there. I’ve also implemented HTTPS for the installation results. And, I’ve added links at the bottom of the test results to the external reporting dashboard, and vice-versa as well. I’ve also done some extensive maintenance & care on the testing code base. It’s been upgraded from Python2 to Python3, among other improvements relating to speed and cost. If you’re interested, this was the pull request for the changes.

      I’m thinking a lot on bringing back the streak counts, because they were really fun to watch. Though in addition to this, I want to capture execution time and other figures, and produce some pretty graphs for these things rather than just a number. Will be thinking on this.

      Also thinking on adding some CI/CD stuff to the tests, where people can submit changes to the test suite and they “become real” shortly later in the test environment. Though for this, I do need to control it as things are not free in AWS. Thinking to make the test suit it’s own repo, and allowing others to submit pull requests. Upon pull request merge by me, Jenkins would implement the changes automatically. There’s both Terraform as well as the actual tests that could be affected.

      Another thing I was thinking about is adding UI testing via selenium. The UI could be tested for every branch, with a fresh set of OS patches applied, every day, automatically. Though, I have very little experience with Selenium. Though the nice thing about such tests is we’d only need to have 1 set of tests as there’s only one UI, rather than independent code per operating system like I have to maintain for the installation tests. Selenium test results would be displayed on the same page as the installation tests.

      I realize FOG is in maintenance mode. Though, I must admit I really enjoy doing these devops-ey type things for fog.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 1
      • S
        Sebastian Roth Moderator
        last edited by

        @Wayne-Workman Really awesome work. Thank you so much for all this as well as new ideas!

        I definitely vote for more testing as it’s still mostly manual work. Though I have to admit that I can’t see me working on this.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        160

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project