search

seandepagnier / weatherfax_pi

weather fax plugin for opencpn
GNU General Public License v3.0
20 stars 27 forks source link

appveyor auth_token, changes, version 1.9.2 ov42 #135

Closed rgleason closed 5 years ago

rgleason commented 5 years ago

new auth_token, cleanup, simplify, test Version 1.9.2, date 4/24/2019

Appveyor.yml configured so that

  1. New commits that compile ---> Artifacts Tab
  2. New Tag pushed to remote Git repository ---> Creates a new Release Tag and Appveyor then pushes the Artifact files (windows version *.exe appropriately named) to the Release directory.

What is required to do this?

  1. An account (opensource, developer, free) with Appveyor
  2. Appveyor webhooks (with read & write permission) to the repository and the plugin repository included in the builds.
  3. A new and working yaml encrypted Personal auth_token from Github entered into the appveyor.yml file.
  4. For better directions about the steps taken for the auth_token, see the bottom of https://github.com/seandepagnier/weatherfax_pi/issues/134
rgleason commented 5 years ago

Sean would you mind merging this?

It just updates the patch number and updates the Appveyor file so that we can push a new tag to the remote repository and then appveyor will push the windows artifact into the Release (new tag). (This just requires the setup of a personnal auth_token and copying the Yaml encrypted version of that into the appveyor file.)

I've tested it and it seems to work fine. It's a nice efficient way to make a release with an identical tag. This is what I've done on my repository:

  1. In your github account setup your own github personnal auth_token, (copy the token to somewhere).
  2. Go to your appveyor account encrypt the personnal auth_token, take that code an put it in the appveyor.yml file. No it should work.
  3. Change VERSION.cmake patch number and date, commit and push.
  4. Push a new tag (eg: git push origin v1.9.1-ov50), then Appveyor will build the artifact ( *exe) again and push the file to a new Github Release using the tag (eg: v1.9.1-ov50)

If you can accept this PR, I will then make another PR that updates appveyor to compile for Opencpn 5.0 If you can get thee security token working and push a new tag, that pushes the windows plugin_pi.exe file to the Release Directory, then we can have K link to that.

The next improvement would be to get travis or avppeyor to build MacOS and push that to same Release.

PS: I found out that you cannot include TAGS in a PULL REQUEST. Tags can be pushed and removed from a Remote or Local Repository, but Tags must be made by the author of the repository. In other words I cannot make a Tag for your repository by including one in a PR.

rgleason commented 5 years ago

Sean, what is the problem that you have with merging this?

rgleason commented 5 years ago

Sean, if you will please merge this to improve appveyor for ov42, I will then make a PR to change CI .travis and appveyor for compiling ov50.