OctoPack: Failed to publish artifacts

Legacy Uncategorised
1

Hi,

We’re having an issue where, even though the NuGet package is created, an error is being thrown when the artifacts are published to the TeamCity nuget server.

Unfortunately the build log doesn’t give much information about the actual error, here’s a snippet from it:

[Publishing artifacts] Collecting files to publish: [C:\BuildAgent\work\37c363422203c03d\...XXX.1.0.901.nupkg]
[17:21:07] :		 [Publishing artifacts] Publishing using [WebPublisher]
[17:21:07] :		 [Publishing artifacts] Publishing using [ArtifactsCachePublisher]
[17:21:18]E:		 [Publishing artifacts] Failed to publish artifacts:

I’ve searched these forums for a similar issue but can’t seem to find anyone else with this exact issue.

I’ve checked the build agent and the nupkg file is definitely being created.
One thing I’ve noticed is that the size of the nupkg file is 365mb. Could this be the cause of the issue?

We’re using TeamCity 9.0.4 (build 32407) and Octopus 2.5.10.567.

Any help would be very much appreciated.

Thanks,
Dan.

2

Hi,

I’ve fixed the issue so I will post the resolution in case it helps someone else out!

Turns out it was a setting in TeamCity:

Administration -> Global Settings -> Maximum build artifact file size

This was set to 300mb, changed it to -1 (unlimited), problem solved!

I’ve attached a screenshot highlighting the setting.

Cheers,
Dan.

artifactsize.PNG
artifactsize.PNG1009×147 10.4 KB

3

Hi Daniel,

Thanks for posting your issue and solution for others :slight_smile:
Glad you got it working.

Vanessa

4

Is it possible to alter this setting on a per project setting ?

Publishing artifacts (2m:32s)
[19:06:22][Publishing artifacts] Collecting files to publish: [target]
[19:06:24][Publishing artifacts] Publishing using [WebPublisher]
[19:06:24][Publishing artifacts] Publishing using [ArtifactsCachePublisher]
[19:08:55][Publishing artifacts] Failed to publish artifacts: Artifact [XXX.XXX.XXX.zip] length [72906098] exceeds maximum allowed [52428800]

5

Hi Mark,

This error is coming from TeamCity itself, not OctoPack and this setting is global and I don’t believe there is a per project setting. You might need to contact TeamCity support to see if they know if there is a way.

Thank you and kind regards,
Henrik