Skip to content

Commit

Permalink
fixed action triggers
Browse files Browse the repository at this point in the history
  • Loading branch information
ennerf committed Jan 31, 2024
1 parent 722a89f commit f3ce66b
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 3 deletions.
1 change: 1 addition & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ jobs:
maven-artifacts:
needs: [native-plugins]
runs-on: [ubuntu-latest]
if: ${{ github.event_name == 'workflow_dispatch' }}
timeout-minutes: 30
continue-on-error: false
steps:
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ The message generator `protoc-gen-quickbuf` is set up as a plugin for the protoc
protoc-quickbuf --quickbuf_out=${options>:<outputDir> <protoFiles>
```
or use a [protoc-gen-quickbuf-${version}-${arch}.exe](https://github.com/HebiRobotics/QuickBuffers/releases) plugin binary with an absolute `pluginPath`:
or use a [protoc-gen-quickbuf-${version}-${arch}.exe](https://repo1.maven.org/maven2/us/hebi/quickbuf/protoc-gen-quickbuf/) plugin binary with an absolute `pluginPath`:
```sh
protoc --plugin-protoc-gen-quickbuf=${exePath} --quickbuf_out=${options>:<outputDir> <protoFiles>
Expand Down
4 changes: 2 additions & 2 deletions protoc-gen-quickbuf/Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ In order to support the `pluginArtifact` parameter (`"us.hebi.quickbuf:protoc-ge

The Java bytecode can be compiled to a standalone native executable using [GraalVM](https://www.graalvm.org/). This also gets rid of requiring an installed Java runtime and significantly speeds up execution due to ahead of time compilation and faster startup time. The caveat is that the images need to be compiled on each supported platform, which currently requires a self-hosted runner for linux-aarch64.

Releasing to Maven Central as well as Conveyor packaging happen automatically in a Github action. It can be triggered manually in the action interface, or by pushing to `release/native-plugins`.
Releasing to Maven Central as well as Conveyor packaging happen automatically in a Github action. It can be triggered manually in the action interface.

### Release procedure

Expand All @@ -13,7 +13,7 @@ Releasing to Maven Central as well as Conveyor packaging happen automatically in
* update `app.version` in `../conveyor.conf`
* update version in `../Readme.md`
* Create a tag
* Push to `release/native-plugins`
* [Trigger Github Action](https://github.com/HebiRobotics/QuickBuffers/actions)
* Upload `conveyor-site` contents to a Github release
* Copy the `icon.png` and `download.html` site to `../docs/`

Expand Down

0 comments on commit f3ce66b

Please sign in to comment.