Can I exclude certain files from an artifact directory?

We have some Bamboo plans that copy directories as artifacts. The copy pattern is "**/test/output/**". Sometimes, some really large core dump files make their way into those directories. It doesn't take too many builds to start running our bamboo server out of space because we're copying all those core files.

Is there a pattern I can use to copy everything in those directories except files that start with the string "core"?

2 answers


You should just separate your artifacts (from the build side) into 3 parts deployments scripts, war file and properties file. Then from the deployment side, you can pick and choose which you want to package/deploy.

This would be the simplest solution. Why worry about the complexities of regex (though I'm not even sure it's possible to exclude artifacts).

Hope this helps!


That makes sense, thank you. :)

Yes, or at least I think so based on this page:

which says in part (after declaring it's the same as the ANT patterns):

The inclusion and exclusion elements of the implicit PatternSet can be specified inside the directory-based task (or explicit fileset) via either:

  • the attributes includes and excludes.
  • nested elements <include> and <exclude>.
  • external files specified with the attributes includesfile and excludesfile.
  • external files specified with the nested elements <includesfile> and <excludesfile>.

The syntax you may have to fiddle with but it is likely excludes=**core** or excludes=*core* or something like that. Since we don't use the xml structure in the copy patterns. May need a comma like **/test/output/**, excludes=*core* or something like that.

Do you have any more information on this? I am creating a deployment artifact which contains the deployment scripts, a .war and a properties file. I want to exclude this properties file from the artifact, because it contains properties which are specific to the build server (for example the location/credentials of our test database instance). The properties file will be overwritten anyway when the deployment is run against a different environment, but it would be nice to have a clean artifact to be completely sure. :)

[EDIT] To be specific I have tried:

  • deployment/**/*, excludes=*.properties
  • deployment/**/* excludes=*.properties
  • deployment/**/*, excludes:*.properties
  • deployment/**/* excludes:*.properties
  • deployment/**/*, exclude=*.properties
  • deployment/**/* exclude=*.properties
  • deployment/**/*, exclude:*.properties
  • deployment/**/*, exclude:*.properties

But all to no avail, I just get: "Unable to publish artifact [DeploymentBuildArtifact]". :(

did you find a way?


Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,595 views 22 17
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you