Settings and activity

  1. 38 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Product Feedback  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Tomas commented  · 

    How our deploy procces works is:
    - get package from octo (using this pre-made step)
    - each tenant unzips it to its own directory temp (yeah this step could maybe be skipped, but in that case problem 2 would not be solve-able cos first copy of same version would contain confugarations, so you would still need bazilion copies of same version)
    - some configuration is done, for each tenant different
    - moves configured package where it needs to be, makes backup of current stuff

    Currently what happens is that if i select 100 tenants it creates 100 copies of same package version on one environment. (WTF?)
    If i make new deploy with SAME version i get another 100 copies of same package version, this time with (2) in name (Seriously?)

    -----------------------
    Please create step to store each package OCE PER VERSION. Or add option to some current step to do it this way. E.g.: C:\Octopus\Applications\packageName\v_0.0.1
    Please do not store packages per tenant nor per deploy.
    This way i would be able to just grab package to temp workplace and do whatever i want with it.
    Instead of waiting for 100 copies to be made for each tenant one.
    Yes, i know i will create 100 copies by myself anyway, point is that package download folder will be intact and not "corrupted" by configurations, because configuration is being made in temp dir managed by me.

    It doesnt make sense to download special copy for each tenant on same environment.
    Its our job to manage temp workplace directories not yours.

    Same as it is super useless to download same version again if its run by another deploy process.
    Its our job to make sure that downloaded package wasnt corrupted between deploys, not yours. You just need to check if it is there and if not, deliver it to download folder.

    Is there such proccess step that behaves like this? Currently it wastes ton of disc space on our server and i need to delete packages every ~2 deploys.

    An error occurred while saving the comment
    Tomas commented  · 

    Copy-pasted text from support ticket. Answer was that currently its not possible. Thus i used same ticket as idea proposal.

    Tomas shared this idea  ·