Στις 17/2/2019 17:47, ο Massimo MANGHI έγραψε:
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 think yes. It will also attempt to deploy it to github, if a tag is
added (as a draft pre-release).
I guess we have to copy the
current .appveyor.yml file from master.
Yes. The artifacts will be generated with every commit. They will get
deployed in github with every tag added.
(If my credentials work of course).
Best,
George
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org
For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
