PLTcloud Action
ActionsTags
(2)The PLTcloud action allows publishing firmware releases directly to BCD's PLTcloud backend. It allows you to upload a release to PLTcloud as part of your CI workflow.
Mandatory:
| input | description |
|---|---|
API_TOKEN |
PLTcloud API token. |
PROJECT_UUID |
Project id for PLTcloud project. |
Optional:
| input | description |
|---|---|
FILES |
List of files for upload. Files can be specified with patterns such as: **/prefix*, grandparent/**/child?, **/parent/*, or even just ** |
VERSION |
Release version. (default: ${{ github.ref }}) |
VERBOSE |
Verbose output (default: false) |
DEPLOYMENT_GROUP_UUID |
Deployment Group UUID |
AUTO_DEPLOY |
Auto deploy release to PLT (default: false) |
In order to upload a release, the PLT test plan, and any associated assets such as DUT firmware must be available in a directory.
Setup a GitHub action to build the firmware and copy test plans to a known directory.
- Log in to PLTcloud and select the
Projectmenu item from the project drop-down in the top banner. - Copy the
UUIDfrom the project detail page and a secret namedPROJECT_UUIDin your GitHub project. - Select
API Tokensfrom the drop-down menu under the user menu in PLTcloud - Select
Add Release Token, login and copy theRelease Upload Token - Add the release token to GitHub secrets and name it
API_TOKEN
Add a step in the .github/workflows/main.yml actions workflow,
after the steps that build the firmware:
- uses: bcdevices/[email protected]
with:
FILES: dist/*
API_TOKEN: ${{ secrets.API_TOKEN }}
PROJECT_UUID: ${{ secrets.PROJECT_UUID }}
VERSION: ${{ github.ref }}
PLTcloud Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.
Tags
(2)PLTcloud Action is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.