OpenHD
GitHubTelegramDonate
2.0
2.0
  • Introduction
  • General
    • Features
    • Getting Started
    • FAQ
    • Contributing
  • Hardware
    • Wiring
    • WiFi Adapters
    • Supported SBC's
    • Cameras
    • Displays
    • Antennas
    • Audio
  • Software Setup
    • Telemetry and OSD
    • SmartSync
  • RC Control
    • General
    • RC over MAVLink
    • RC over Serial
  • Advanced Setup
    • Bidirectional Telemetry
    • USB Tethering
    • WiFi Hotspot
    • Ethernet Hotspot
    • Ground Recording
    • Using only a USB Camera
    • Using only an IP Camera
    • Using an IP or USB Camera as second camera
    • Bandwidth switching
    • LTE Connection
    • Ground Power Monitoring
  • Ground Station Software
    • QOpen.HD (recommended)
    • Mission Planner
    • QGroundControl
    • Tower
    • FPV_VR
    • GStreamer
    • FishingFanCam
    • RaspberryPi Camera Viewer
  • Developer Corner
    • The Open.HD Ecosystem
    • Making a Release
    • Update packages on a Pi
    • Change packet source on a Pi
    • Building an Image
    • Essentials
    • QOpenhd Tips
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Developer Corner

Making a Release

In order to push to the cloudsmith package group that is NOT for testing you have to create a tag in github from a terminal. It cannot be a lightweight tag. Correct format is: git tag -a 2.0.9 -m "2.0.9" Other useful commands in terminal in git playing with tags:

  • See if there is a match git describe --exact-match HEAD

  • Push your new tag (will also trigger the build in drone.io since its a commit) git push --tags

  • Delete a tag git tag -d 2.0.9

This way the package.sh script will see the tag in the git describe command and thus trigger a push to the appropriate directory. To pull the correct version of openhd you must define the version in the image builder stage 2 OPENHD_PACKAGES="openhd=2.0.9"

PreviousThe Open.HD EcosystemNextUpdate packages on a Pi

Last updated 2 years ago

Was this helpful?