Hi George On 2/16/19 9:55 PM, Georgios Petasis wrote: > Dear Massimo (and all), > > I have modified .appveyor.yml in master branch, to generate artifacts. > Currently, a zip file is generated, that contains both the module .so > library, and the rivet tcl library. You can see the generated artifacts > if you go to the last build (by following the badges in the github page > https://github.com/apache/tcl-rivet), and checking the "Artifacts" tab > of each build. > > For example here: > > https://ci.appveyor.com/project/petasis/tcl-rivet/build/job/xxfwh9vg6ew5dlck/artifacts > > > > I have also placed the needed code that will upload the artifacts to the > github release, if a tag is added (in any branch).
thank you! Well done This is building a 3.2 which is formally unreleased (actually it's very close to 3.1.1) So if we made a mock 3.1.2 release by adding a tag to 3.1 that would trigger an artifact build? I guess we have to copy the current .appveyor.yml file from master. -- Massimo
