Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8645673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T12:36:35+00:00 2026-06-12T12:36:35+00:00

I have a TeamCity Build Configuration that includes the following to publish artifacts: Source\Builder\bin\Release\*.dll=>release

  • 0

I have a TeamCity Build Configuration that includes the following to publish artifacts:

Source\Builder\bin\Release\*.dll=>release

This works fine, however I am wanting to exclude one dll (there are quite a few) and have read that you can use + & – operators to do this. Something along the lines of:

+: Source\Builder\bin\Release\*.dll=>release
-: Source\Builder\bin\Release\Builder.*

As soon as I add these in, no artifacts are published and I get the following error in the build log (looks like it is counting the + as part of the path):

[Publishing artifacts] Collecting files to publish [+:Source\Builder\bin\Release\*.dll=>release]
[Publishing artifacts] Artifacts path +:Source/Builder/bin/Release/*.dll not found

I am using version 7.1.1, anyone any ideas (I am not sure whether these operators are even valid). I have seen a solution with MSBuild but am surprised this functionality is not available.

Thanks in advance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T12:36:36+00:00Added an answer on June 12, 2026 at 12:36 pm

    I don’t believe you can.

    However, if you are using the artifacts in another build configuration as an artifact dependency, you can exclude a particular file there.

    When you set up the dependencies, you can specify a negative operator like this:

    +:release/**=>Dependencies/SomeProject
    -:release/SomeBinary.dll
    

    It is a horrible hack, but one way you could get it to work would be to set up a new build configuration which gets the dependencies as an artifact dependency, excluding the one binary, and then publishes its own artifacts.

    As in, create a new build configuration and publish:

    Dependencies/SomeProject=>release
    

    Then reference the artifacts from this build configuration instead of the other one.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

We are using TeamCity 6.0.2 and have a build configuration that runs SoapUI tests.
I finally have TeamCity setup to build on Source Control changes, and a separate
I am trying to set up a Teamcity build configuration that runs from our
I have a configuration in teamcity that package and deploys. I am using the
I have a separate build configuration used to deploy built files. This configuration uses
I have created a release configuration project in Teamcity 6.5 using the SLN Runner
I'm running TeamCity 5. I have one particular configuration that is preserving 3500+ past
We recently added a new TeamCity build agent. Because it doesn't have ASP.NET MVC
I have a project that I am setting up through teamcity for CI. The
My TeamCity's nightly build produces more than 130Mb java doc as Build Configuration artifact.

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.