Every packager encounters boring manual tasks every once in a while and these tasks can most probably be automated to some extent. During Hackweek I aim to try and identify such cases in various packagers' workflow and consider creating a tool that would make these tasks easier. Also, I would like to find out whether there is a demand for such tool. In that case, this Hackweek project will turn into a long-term task I plan to keep working on.

Looking for hackers with the skills:

Nothing? Add some keywords!

This project is part of:

Hack Week 14 Hack Week 15

Activity

  • over 4 years ago: ZRen liked this project.
  • over 5 years ago: dsterba liked this project.
  • over 5 years ago: locilka liked this project.
  • over 5 years ago: osukup liked this project.
  • over 5 years ago: mvidner liked this project.
  • over 5 years ago: pjanouch liked this project.
  • over 5 years ago: pluskalm liked this project.
  • over 5 years ago: coolo liked this project.
  • over 5 years ago: kstreitova started this project.
  • over 5 years ago: kstreitova originated this project.

  • Comments

    • locilka
      over 5 years ago by locilka | Reply

      Hi. You be interested in Roman's https://github.com/roman-neuhauser/bs-update

    • locilka
      over 5 years ago by locilka | Reply

      Another idea is what the Yast team does with all packages: https://ci.opensuse.org/view/Yast/job/yast-autoinstallation-master/lastStableBuild/consoleFull

      We have Jenkins jobs that periodically check for changes in Git. If some are found, we checkout the Git repo, create a package, build it, run tests, and if everything is OK, we also submit it to our devel project and create a subtmit request to openSUSE and SLE.

      Of course, we run more tests than just unit tests. We also, for instance, run RuboCop to check the code quality.

    Similar Projects

    This project is one of its kind!