Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trigger deployments from the build script #36

Open
ecampidoglio opened this issue May 22, 2019 · 0 comments
Open

Trigger deployments from the build script #36

ecampidoglio opened this issue May 22, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@ecampidoglio
Copy link
Member

A deployment is triggered when the commit being built has an annotated tag.

The problem is that, right now, it's AppVeyor that detects the presence of a tag and if so, triggers a deployment:

if ($env:AppVeyor_Repo_Tag -eq $true) {
    .\build.ps1 -Target Deploy -PackageFilePath $artifacts["NuGet"].path
}

It would be better to do this from the build script itself, instead of relying on a particular CI server to trigger the deployments.

@ecampidoglio ecampidoglio added this to the 4.2.0 milestone May 22, 2019
@ecampidoglio ecampidoglio self-assigned this May 22, 2019
ecampidoglio added a commit that referenced this issue Oct 4, 2019
By default, Travis CI only clones the last 50 commits.
This doesn't play well with 'git describe', which we're using
to determine whether the latest commit has a version tag.

This commit disables the commit limit altogether.

https://docs.travis-ci.com/user/customizing-the-build/#git-clone-depth
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant