Offline package drop doesn't provide zip when enabling specific deploy step

Hi,

We have a project which succesfully deploys to multiple tenants. For a new client, we have to use offline package drop.
The deployment consists of 12 steps; but there is 1 specific step (a simple deploy of a package to a map, which we also do in other steps) which seems to prevent the creation of the artifact.
If i disable it, it runs succesfully and creates a Zip in the Task Summary.
The Task log doesn’t seem to show anything out of the ordinary, only that it doesn’t create the expected artifact. The deployment succeeds, according to the summary.

The “create artifacts from offline drops” is as follows:
| == Success: Creating Artifacts from Offline Drops ==
16:55:04 Verbose | Creating artifact
16:55:53 Verbose | Create Offline Drops as Artifacts completed

Kind regards,
Tim

Hi @tbeckers,

Thank you for contacting Octopus Support. I’m sorry you are having an issue with offline package drops.

Would it be possible for you to share a raw task log from this deployment? Also, if you could share your Process JSON, that would be very helpful so that I may reproduce this issue on my end.

Feel free to attach here, via DM, or via the following secure upload link:
https://octopus.com/support/individual/xctgk5mbpfsnrqtnqttgka5mci38godmqb1nhaufrj6o$57A6344$f4z5bofxewjwxc443hcpaikga718fec6

I look forward to hearing back from you.

Best Regards,
Donny

Hi Donny,

Thank you for the fast reply, I attached both a task log which creates an artifact (by disabling step 5: deploy to temp map) and the failing task log, as well as the process json

ServerTasks-8129_with_artifact.log.txt (32.6 KB)

bouwoffice-vnext-local-package-drop-trial-process.json (25.7 KB)

ServerTasks-8098_No_Artifact.log.txt (35.5 KB)

Hi @tbeckers,

Thank you for getting back to me.

I’ll have a look and let you know what I find.

Best Regards,
Donny

Hi @tbeckers,

Thank you for your patience.

I have, thus far, been unsuccessful in reproducing this issue on my end. Would you be willing to give me permission to log into your cloud instance to take a look?

Let me know at your earliest convenience.

Best Regards,
Donny

Hi @donny.bell

That would be fine, go ahead.

Kind Regards,
Tim

Hi, @tbeckers,

I’ve had a look around your instance, and I can’t see anything out of the ordinary that would cause the behaviour you’re reporting.

Would you be able to try cloning the project and see if the same thing occurs when running the clone (if Step 5 is enabled, no artifact is created)?

Let me know if you’re able to perform this test, please!

Kind Regards,
Adam

Hi @adam.hollow

I’ve tried that before, “BouwOffice vNext - Local Package drop - trial” is a copy of “BouwOffice vNext”,
with the same result, i’m afraid.

Kind Regards,
Tim

Hi, @tbeckers,

Apologies for the delay.

Am I right in saying that the OPD target used for both of these steps is the same OPD deployment target?

I wonder if it’s worth testing creating a new OPD target with the same details but a different name and pointing Step 1 or Step 5 at the new target, to see if there’s still an interaction there?

Let me know if you’ve already tried this, as we’ve been unable to reproduce it so far it’s difficult to do much testing!

Kind Regards,

Hi @adam.hollow ,

No problem.
The OPD target is indeed the same one for all testcases, I will try creating a new one in a short while and get back to you with any findings I have!

Kind Regards,
Tim

Hi @adam.hollow,

We tried using another deploy target and it makes no difference. We did however come to the conclusion that the troubling step succeeds with another, identical nuget package (with another name). Is there any way i can securely transfer these files to you? Seeing that it concerns confidential data.

Kind Regards,
Tim

Hi, @tbeckers,

Absolutely!

Thanks for investigating further, the files you’re hoping to send over should prove useful in learning more about what’s going on.

I’ve created the following URL for you to be able to upload, it’s attached to your e-mail address: Support Files Upload.

Let me know when you’ve sent those over, please!

Kind Regards,
Adam

@adam.hollow ,

The upload had finished, the “shell” package is the succeeding one, and the “squirrel” one the failing.
As you can see, they are pretty similar.
The project we tested it with was “BouwOffice vNext - Local Package drop - trial” in the Release project group, to target “PackageDrop” (which is a dummy).

Kind Regards,
Tim

Hi @tbeckers,

Thanks very much for providing the uploads.

I’ll have a look over them, and if I can’t find anything too suspicious, I’ll send over the files to our engineers to have a closer look; they’d likely be able to spot what’s going on!

Any issues in the meantime, please reach out, and we’ll do our best to assist.

Kind Regards,
Adam