Pushing to remote Git repository from a build doesn't work about website HOT 9 CLOSED

Could you please drop your appveyor.yml (with sensitive data removed)?

from website.

1. That's only a tiny snippet of an appveyor.yml (one that I got from your help page)
2. It's from a public github project so it's all public and readily viewable anyways
3. I did scrub the "sensitive" (public) data. My name isn't actually "First Last" and my email is not "[email protected]"

The other than the fake name and email the rest is straight from the help doc.

Also I figured out how to fix it, though I don't know if it's the the really correct way to do it:

environment:
  access_token:
    secure: cUFRT/gTMFUL6JvjnVcEZ89q3W2k7YQRtqfQhjlsZ6oigK3cyurRIl3QZBRl4Vgc
on_success:
  - git config --global credential.helper store
  - git config --global push.default matching
  - ps: Add-Content "$env:USERPROFILE\.git-credentials" "https://$($env:access_token):[email protected]`n"
  - git config --global user.email "[email protected]"
  - git config --global user.name "Not My Name"
  - git add -A *.zip *.dll
  - git commit -m "Adding newly built binaries for release[ci skip]"
  - git push origin

And yes the name, email and access_token are fake.

from website.

Ok, I actually checked the repository and the files are all still a month old. It looks like it's succeeding, but where is it pushing to? Do I need to specify a custom checkout command and then in on_success add my repository as a remote and specifically push to the repository I added?

from website.

Try calling git status after git add command to see what was added.

from website.

I'm just wondering why would you need pushing produced DLLs and executables back to repository?

from website.

That's where I was storing releases so people don't have to download and
build the project from sources.

On Fri, Jan 8, 2016 at 2:56 PM, Feodor Fitsner [email protected]
wrote:

I'm just wondering why would you need pushing produced DLLs and
executables back to repository?

—
Reply to this email directly or view it on GitHub
#114 (comment).

Thanks,
Joel

from website.

Why not pushing them to repository Releases then: http://www.appveyor.com/docs/deployment/github? This is a "standard" way of distributing releases.

from website.

Yeah that's what I do now.

On Fri, Jan 8, 2016 at 3:01 PM, Feodor Fitsner [email protected]
wrote:

Why not pushing them to repository Releases then:
http://www.appveyor.com/docs/deployment/github? This is a "standard" way
of distributing releases.

—
Reply to this email directly or view it on GitHub
#114 (comment).

Thanks,
Joel

from website.

@FeodorFitsner: can we close this since it's not related to the website?

from website.