Deploy Yak
ActionsTags
(2)This builds and publishes any Rhino and/or Grasshopper plugins (defined by a yak specification yml) to the McNeel Package server OR test server.
see action.yml
Test build and publish to test server
steps:
- uses: crashcloud/yak-publish@main
with:
package-name: 'My Yak Package'
token: ${{ secrets.YAK_TOKEN }}
build-path: 'src/**/bin/**/**/'
publish: 'test'
platform: winCross-platform build and publish to production server
strategy:
matrix:
os: [ 'windows', 'mac-os' ]
runs-on: ${{ matrix.os }}
name: Yak Build & Publish
steps:
- id: yak
uses: crashcloud/yak-publish@main
with:
package-name: 'My Yak Package'
token: ${{ secrets.YAK_TOKEN }}
build-path: 'src/project/bin/**/x64/'
publish: 'production'
platform: ${{ matrix.os }} Arguments
| Argument Name | Expected Value | Comments |
|---|---|---|
package-name |
The name of the package | Enclose in quotes if spaces exist |
token |
${{ secrets.YAK_TOKEN }} |
Use yak.exe --ci locally to get this token. Add to GitHub secrets. |
build-path |
globs accepted | |
publish |
'', 'test', 'production' | '' publishes nothing, 'test' published to the the McNeel Test Server. 'production' published to the real yak package server |
platform |
windows/win or mac/mac-os | Linux not supported |
Recommendations
Building yak packages on the platform you intend to distribute them for leads to less potential problems.
This action is all covered by the MIT License
Deploy Yak 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)Deploy Yak 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.