Release version column -- how to set

We released the action to the marketplace recently Deploy to Balena 路 Actions 路 GitHub Marketplace 路 GitHub.

I can discuss with the team writing a blog post about this work.

@bversluijs The action allows you to use an environment input which can be your open balena instance :slight_smile:

@20k-ultra awesome! I鈥檒l definitely try that out in our GitHub Actions workflow, once I get that setup right :slight_smile:

But the 鈥榬elease version鈥 field, as asked in the topic start, is that also supported by openBalena?

Thanks!

Yup, openBalena will produce the release version as well just check if you have the latest version as the change was introduced within the last 6 months.

Take a look at my action testing repo to see my workflow file and the output.

If people need any features make an issue and I鈥檒l respond!

In case it鈥檚 useful: It took me a while to figure out how to get Github Actions to ignore readme only changes (why doesn鈥檛 Github make this easier?) so that a deployment is not trigged if I change some documentation without changing the app.

Here鈥檚 my setup鈥 Probably could be better, but it works.

name: Deployment

on:
  push:
    paths-ignore:
      - './docs/**'
      - '**.md'
      - 'README.md'
      - '.gitpod.yml'
      - '.gitignore'
    branches:
      - master

jobs:
  balena_cloud_build:
    runs-on: ubuntu-latest
    steps:

      - name: Checkout
        id: checkout
        uses: actions/checkout@v2
      
      - name: Deploy to Balena
        id: deploy
        uses: balena-io/deploy-to-balena-action@master
        with:
          balena_token: ${{ secrets.BALENA_TOKEN }}
          fleet: ${{ secrets.BALENA_FLEET_SLUG }}

      - name: Log release ID built
        id: log
        run: echo "Built release ID ${{ steps.deploy.outputs.release_id }}"