Bug: TeamCity and non-existing main/primary artifacts

I really hope there is a quick patch for this because I don't have a good workaround other then not deploy files. I think I've discovered a bug where if a Maven project has no PRIMARY artifact, TeamCity doesn't recognize this and thinks it has one anyway. See:
artifacts.png

This project has NO primary artifact. It's just one with a classifier that gets set to the current branch name.

This is causing the Artifactory plug-in to go nuts:

error.png

It can't find a file. And based on the stracktrace it's because TeamCity is pointing the plug-in to a non-existent file.

Please help!

3 comments
Comment actions Permalink

We are having the same problem. Any update or fix on this?

thanks,
Fred

0
Comment actions Permalink

Andrew - Are you using an artifactory plugin?

0
Comment actions Permalink

Yes, we are using the Artifactory 2.1.8 plugin from JFrog Ltd.

I did notice there is a new 2.1.9 version of the plugin, it works with TeamCity 8.1.2.

We are planning to upgrade to 8.1.2 next week, we are currently running 8.0.5.

Does the new version of the plugin fix this?

thanks,
Fred

0

Please sign in to leave a comment.