using Bloom to release into the STRANDS ROS build farm

by mhanheide 10 years ago

GNU/Linux ◆ xterm ◆ bash 610 views

carry out the step of Preparing_the_Upstream_Repository. Be aware that all package.xml in your repository need to be properly set up (license suggest as MIT, author(s) and maintainer entered), and that they all need to be at the same version number (0.0.0 looks like a good starting point).
create a release repository with the same name as the repository you plan to release in the github organisation strands-project-releases (ask @marc-hanheide for permissions or to do it for you). The repository will be automatically populated and is referred to as RELEASE repository url (see https://github.com/strands-project-releases/mongodb_store.git, for instance)
use bloom to create the release:
```
bloom-release --rosdistro hydro --track hydro repository_name --edit
```
This will interactively ask some information from you:
when first asked for the Release repository url, enter the git URL for the just created repo (e.g. https://github.com/strands-project-releases/mongodb_store.git)
when asked for Repository Name, please enter the name of your repository, e.g. mongodb_store
when asked for Upstream Repository URI, please enter the path to your upstream repository, that is the one hosted in the strands-project github organisation that you commit to, e.g. https://github.com/strands-project/mongodb_store.git
when asked for ROS Distro, say hydro (or indigo if that is eventually supported by STRANDS)
when asked Would you like to add documentation information for this repository?, say no
when asked Would you like to add source information for this repository?, say yes, and subsequently tner the URL to your active development repository (usually the same as the upstream repo, so in our example: https://github.com/strands-project/mongodb_store.git again
answer all other questions just by hitting return (accepting the defaults)

You should see bloom creating a lot of stuff for you (debian configurations and other stuff). At the end, bloom should automatically open a pull request against STRANDS’ own distribution.yaml with your package added to this. The STRANDS software management team will have a look at this and eventually accept it. Then the build farm will create debian packages for you (and package maintainers will receive emails automatically if the build fails) which will then be available for everybody to use.

You can download this recording in asciicast v2 format, as a .cast file.

Download

Replay in terminal

You can replay the downloaded recording in your terminal using the asciinema play command:

asciinema play 11741.cast

If you don't have asciinema CLI installed then see installation instructions.

Use with stand-alone player on your website

Download asciinema player from the releases page (you only need .js and .css file), then use it like this:

<!DOCTYPE html>
<html>
<head>
  <link rel="stylesheet" type="text/css" href="asciinema-player.css" />
</head>
<body>
  <div id="player"></div>
  <script src="asciinema-player.min.js"></script>
  <script>
    AsciinemaPlayer.create(
      '/assets/11741.cast',
      document.getElementById('player'),
      { cols: 212, rows: 56 }
    );
  </script>
</body>
</html>

See asciinema player quick-start guide for full usage instructions.

While this site doesn't provide GIF conversion at the moment, you can still do it yourself with the help of asciinema GIF generator utility - agg.

Once you have it installed, generate a GIF with the following command:

agg https://asciinema.org/a/11741 demo.gif

Or, if you already downloaded the recording file:

agg demo.cast demo.gif

Check agg --help for all available options. You can change font family and size, select color theme, adjust speed and more.

See agg manual for full usage instructions.