This workflow can be triggered manually or by commit to the master branch and will automatically:
Build against multiple Nginx and libjwt versions.
Upload the results as a Pre-release Development build.
You can see the action working on my fork and the release here.
The Nginx versions to build against can be easily changed by modifying the nginx-version list.
Sadly, it doesn't perform build tests in its current state. I'm sure that can be added but I was not inclined to work on that at the moment.
The rationale behind using multiple versions of libjwt came after I discovered the hard way that the current binary release won't link against any version of libjwt above 1.12.0 and EPEL currently has 1.12.1.
Open to feedback and of course, change anything you want.
Thanks for making this project!
Wrote this up mostly to see if I could. This was mentioned by https://github.com/TeslaGov/ngx-http-auth-jwt-module/issues/73 and I tend to agree.
This workflow can be triggered manually or by commit to the master branch and will automatically:
You can see the action working on my fork and the release here. The Nginx versions to build against can be easily changed by modifying the
nginx-version
list. Sadly, it doesn't perform build tests in its current state. I'm sure that can be added but I was not inclined to work on that at the moment. The rationale behind using multiple versions of libjwt came after I discovered the hard way that the current binary release won't link against any version of libjwt above 1.12.0 and EPEL currently has 1.12.1.Open to feedback and of course, change anything you want. Thanks for making this project!