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

Team City Artifacts #17

Closed
dazinator opened this issue Jul 9, 2015 · 2 comments
Closed

Team City Artifacts #17

dazinator opened this issue Jul 9, 2015 · 2 comments
Assignees

Comments

@dazinator
Copy link
Owner

During a build, use stdout to inform team city of the Dnn installation zip file that was produced - this means it can automatically show up in the artifacts tab in the team city build (without having to do any config in Team City itself)

It's envisioned that most of the time you won't want to capture the zip file as an artifact - instead you will probably want to capture the NuGet deployment package. Therefore by default this functionality will be switched off, but could be turned on by passing in an MSBuild property:

/p:DnnPackagerPublishDnnInstallZipToTeamCity=true
@dazinator
Copy link
Owner Author

Here is an example in C# of the message syntax to inform TeamCity of an artifact (this is written to stdout)

 if (PublishPackagesToTeamCity && !string.IsNullOrWhiteSpace(Environment.GetEnvironmentVariable("TEAMCITY_VERSION")))
                {
                    LogMessage("##teamcity[publishArtifacts '" + file + "']");
                }

@dazinator dazinator changed the title Better Team City Integration Team City Artifacts Jul 9, 2015
@dazinator dazinator self-assigned this Feb 16, 2016
@dazinator
Copy link
Owner Author

If using Team City, you will now find that the module installation zip will automatically show up on the "artifacts" tab for any given build.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant