GitHub deployment no longer works

obones's Avatar

obones

18 Jan, 2018 01:46 PM

Hello,

I'm using AppVeyor to deploy build artifacts to GitHub and it used to work great, as can be seen here:
https://ci.appveyor.com/project/obones/xgboost-jars/build/1.0.3
As I have made a few changes to the repository lately, a build was triggered but it failed at the checkout step. I was able to fix these by changing the relevant part in appveyor.yml and got back to a working build situation, as can be seen here:
https://ci.appveyor.com/project/obones/xgboost-jars/build/1.0.11

However, the GitHub deployment part no longer works, despite not touching anything in the deploy section. It gives the following error message:
"GitHub" deployment has been skipped as environment variable has not matched ("appveyor_repo_tag" is "false", should be "true")

But what I don't get is that I have that variable set in my config that worked, hasn't changed since then, and looks like this:

deploy:
  provider: GitHub
  tag: '$(XGBOOST_VERSION)'
  description: ''
  force_update: true
  auth_token:
    secure: (obfuscated)
  on:
    appveyor_repo_tag: true

I must have missed some announcement but I could not find it, nor could I find any discussion here that seemed to be relevant to this issue.

  1. Support Staff 1 Posted by Ilya Finkelshte... on 18 Jan, 2018 06:51 PM

    Ilya Finkelshteyn's Avatar

    It looks like everything works as expected. You have the following tag deployment condition:

      on:
        appveyor_repo_tag: true
    

    Therefore build is going to start only when tag was created. Your deployment happened when you created 0.7-20170913161514 tag. It did not started the same way when no tag was created, see this older build.

  2. 2 Posted by obones on 19 Jan, 2018 08:54 AM

    obones's Avatar

    Thanks for your answer.
    It made me think about tags and I remembered that they have to be explicitly pushed to the repository for them to appear.
    This is what I did this morning, and tag 0.7-20180119110000 (along others) is now visible in the github repository.
    This push triggered a build on master that did not deploy, as expected because it is not a tag.
    But I don't see a build being planned because of the 0.7-20180119110000 tag. Should I wait for it a bit longer?

  3. 3 Posted by obones on 19 Jan, 2018 03:14 PM

    obones's Avatar

    Well, never mind, I created a new tag this afternoon with real changes and it triggered properly, with a valid deployment at the end.
    Sorry for the noise.

  4. obones closed this discussion on 19 Jan, 2018 03:21 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac