Modern frontend build tooling for Uyuni
an idea by Etheryte
Updated over 3 years ago. 2 hacker ♥️. 2 followers. Has no hacker: grab it!

Project Description

At the moment, Uyuni uses a pretty standard frontend build chain based on Webpack 4, Terser, and a few loaders here and there. This works reliably, albeit fairly slowly. In part this may be attributed to large package sizes, in part to the tooling itself.

Over the past few years, a number of newer competitors have entered the frontend build tooling space: Snowpack, Vite and Esbuild to name a few. Many of them target build speed and development iteration speed as their primary goal. It would be great to check whether one of them can fit Uyuni.

Goal for this Hackweek

The goal for this project is to try and build the Uyuni frontend project with the three aforementioned tools: Snowpack, Vite and Esbuild. Given some of them rely on dependencies being ES modules, they might not work for this specific use case, but that needs further research.

The aim is to reduce both development turnaround times as well as production build times while keeping all existing functionality on par. The resulting tool chain should output both development and production builds, we don't want to maintain two parallel tracks for different builds.

Resources

Snowpack getting started guide: https://www.snowpack.dev/tutorials/quick-start
Vite getting started guide: https://vitejs.dev/guide/
Esbuild getting started guide: https://esbuild.github.io/getting-started/

No Hackers yet

Join this project

Looking for hackers with the skills:

javascript susemanager webpack uyuni

This project is part of:

Hack Week 20

Activity

  • over 4 years ago: j_renner liked this project.
  • over 4 years ago: pagarcia liked this project.
  • over 4 years ago: Etheryte added keyword "uyuni" to this project.
  • over 4 years ago: Etheryte added keyword "javascript" to this project.
  • over 4 years ago: Etheryte added keyword "susemanager" to this project.
  • over 4 years ago: Etheryte added keyword "webpack" to this project.
  • over 4 years ago: Etheryte originated this project.


    • Comments

    Be the first to comment!

    Similar Projects

    Kudos aka openSUSE Recognition Platform by lkocman

    Description

    I started the Kudos application shortly after Leap 16.0 to create a simple, friendly way to recognize people for their work and contributions to openSUSE. There’s so much more to our community than just submitting requests in OBS or gitea we have translations (not only in Weblate), wiki edits, forum and social media moderation, infrastructure maintenance, booth participation, talks, manual testing, openQA test suites, and more!

    Goals

    • Kudos under github.com/openSUSE/kudos with build previews aka netlify

    • Have a kudos.opensuse.org instance running in production

    • Build an easy-to-contribute recognition platform for the openSUSE communit a place where everyone can send and receive appreciation for their work, across all areas of contribution.

    • In the future, we could even explore reward options such as vouchers for t-shirts or other community swag, small tokens of appreciation to make recognition more tangible.

    Resources

    (Do not create new badge requests during hackweek, unless you'll make the badge during hackweek)

    Flaky Tests AI Finder for Uyuni and MLM Test Suites by oscar-barrios

    Description

    Our current Grafana dashboards provide a great overview of test suite health, including a panel for "Top failed tests." However, identifying which of these failures are due to legitimate bugs versus intermittent "flaky tests" is a manual, time-consuming process. These flaky tests erode trust in our test suites and slow down development.

    This project aims to build a simple but powerful Python script that automates flaky test detection. The script will directly query our Prometheus instance for the historical data of each failed test, using the jenkins_build_test_case_failure_age metric. It will then format this data and send it to the Gemini API with a carefully crafted prompt, asking it to identify which tests show a flaky pattern.

    The final output will be a clean JSON list of the most probable flaky tests, which can then be used to populate a new "Top Flaky Tests" panel in our existing Grafana test suite dashboard.

    Goals

    By the end of Hack Week, we aim to have a single, working Python script that:

    1. Connects to Prometheus and executes a query to fetch detailed test failure history.
    2. Processes the raw data into a format suitable for the Gemini API.
    3. Successfully calls the Gemini API with the data and a clear prompt.
    4. Parses the AI's response to extract a simple list of flaky tests.
    5. Saves the list to a JSON file that can be displayed in Grafana.
    6. New panel in our Dashboard listing the Flaky tests

    Resources

    Move Uyuni Test Framework from Selenium to Playwright + AI by oscar-barrios

    Description

    This project aims to migrate the existing Uyuni Test Framework from Selenium to Playwright. The move will improve the stability, speed, and maintainability of our end-to-end tests by leveraging Playwright's modern features. We'll be rewriting the current Selenium code in Ruby to Playwright code in TypeScript, which includes updating the test framework runner, step definitions, and configurations. This is also necessary because we're moving from Cucumber Ruby to CucumberJS.

    If you're still curious about the AI in the title, it was just a way to grab your attention. Thanks for your understanding.

    Goals

    • Migrate Core tests including Onboarding of clients
    • Improve test reliabillity: Measure and confirm a significant reduction of flakynes.
    • Implement a robust framework: Establish a well-structured and reusable Playwright test framework using the CucumberJS

    Resources