https://github.com/fedora-modularity/base-runtime-tools

Various helper scripts and hacks the Base Runtime team uses
https://github.com/fedora-modularity/base-runtime-tools

Last synced: about 1 year ago
JSON representation

Various helper scripts and hacks the Base Runtime team uses

• Host: GitHub
• URL: https://github.com/fedora-modularity/base-runtime-tools
• Owner: fedora-modularity
• License: mit
• Created: 2017-04-10T13:31:43.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2017-08-08T10:20:56.000Z (almost 9 years ago)
• Last Synced: 2025-02-17T16:52:08.238Z (over 1 year ago)
• Language: Perl
• Size: 33.2 KB
• Stars: 0
• Watchers: 6
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Base Runtime Tools

Various helper scripts and hacks the Base Runtime team uses.

The contents of this repository are meant to be deployed in

the `build` user's home directory.

All builds should run under the `build` user.

Some brief info on the currect directory structure:

* `compose/`

    * contains a compose-like repo, with only the right

      builds in it; includes the `modulemd` file

    * suitable for sharing publicly

    * created by `compose.pl`

* `logs/`

    * contains logs for component build failures for each

      module build

* `mbs/`

    * the MBS root, with configuration and possibly custom

      patches applied to make it work

* `misc/`

    * various helper scripts go here

    * `newimage.pl` creates, tests and optionally pushes a new

      docker base image to Docker Hub; it also sends a notification

      e-mail

    * `savelogs.sh` saves given module component build failure logs

      to `logs/`

* `mock/`

    * source for the `/var/lib/mock` bind mount

    * this is for convenience; `/home` is much larger and we don't

      have to move data between filesystems all the time

* `modules/`

    * module checkouts; not necessarily up to date

    * should be updated before running a compose

* `repos/`

    * local repos created from koji tags

    * `f26-modularity` -> `module-bootstrap-master-1` lives here

    * also useful for creating composes

    * `syncrepos.sh` downloads the given koji tag and creates a repo

      with the RPMs in it; x86_64 only

* `results/`

    * MBS build results go here

* `rpmbuild/`

    * rpmbuild stuff goes here; used by the MBS

* `tests/`

    * our tests repos go here

* `compose.pl`

    * find RPMs in given directories and creates a compose-like

      structure using the modulemd file found in `modules/base-runtime`

* `mbs.sh`

    * creates or connects to a tmux session with the MBS running

* `status.pl`

    * a helper script for checking module build status