522 results found

1. Search on Step Templates

   Search on Step Template(s)

   Please add search option for "Library->Step Templates".
   This will help us to find the existing step templates easily rather than browsing through all pages.

   Thanks,
   Benitha

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

2. Expand variable values when a deployment step fails.

   Debugging a deployment step failure can be difficult when there is no way to make sure the values passed in are what you expect. I currently have to update the step template with debug out-put statements to verify them. If there was a way to expand of view the values at the time of the step failure it would help.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

3. Pre-Deployment Steps/Checks

   We have a scenario were we do not want deployments which interact with the same set of servers (since we have LB draining and rollbacks) to be able to deploy at the same time.

   We would like the ability to create "Pre-Deployment' steps which can "block" a build with a user-friendly message rather than (a) failing the build or (b) forcing the user to comb through logs.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

4. Meta Release Management

   Warning: the term 'release' is a bit overloaded in this description. :)

   A Release (in its most general sense, not how it is defined in OD), may contain many applications, each with a specific version to be deployed during a given window to an environment.

   So, you would have something like this for any given release window:
   - Application A - v1.1
   - Applicatoin B - v2.1
   - WebService Z - v1.2

   Currently the concept of an OD release is at the application layer and I would have to track externally the connection between applications and/or versions.

   So, what I'm looking for is a way to define an OD 'Meta-Release' that may contain many releases (you were warned) from one or more jobs within OD (one release per OD job).

   I would then be able to define my November 2016 'Meta-Release' as being a culmination of the latest releases of each of my apps (above) that has passed QA (as defined in my Lifecycle).

   Effectively this SHOULD give me a single button to deploy the given versions of the applications simultaneously so there is no chance something will be missed once reaching that point.

   I know this whole concept of a monolithic release is somewhat archaic and no longer chic in the software delivery world. In an ideal situation this wouldn't be necessary as everyone would be using well defined continuous delivery methodology. But, snap back to reality and we find that many organizations definitely still use the idea of schedule release windows. My organization (and I'd wager many others) would definitely benefit from this kind of feature.

   Warning: the term 'release' is a bit overloaded in this description. :)

   A Release (in its most general sense, not how it is defined in OD), may contain many applications, each with a specific version to be deployed during a given window to an environment.

   So, you would have something like this for any given release window:
   - Application A - v1.1
   - Applicatoin B - v2.1
   - WebService Z - v1.2

   Currently the concept of an OD release is at the application layer and I would have to track externally the connection between applications and/or versions.

   So, what I'm… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

5. Obfuscate sensitive variables in the release description

   Octopus replaces the place holders for the plain values, even when they are sensitive, in the release descriptions.
   I discovered this when I sent my passwords to my slack channel :P

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

6. Support customisation of package upload directory on linux targets

   For linux deployments, packages are currently uploaded to $HOME/.octopus/...

   For some customers this can cause problems if the home directory is stored in a remote data centre or if the home directory has limited space.

   It would be good to allow customisation of the location where these packages are uploaded.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →

7. Show which releases are currently deployed on the Releases screen

   We have two environments and auto-deploy to staging in a lot of our projects. We have a release per CI build, CI builds correspond to a PR merge so usually a deployable feature.

   Current flow: Some feature or features are approved for release, I go to the overview screen and memorise which version is deployed in production, then I go to the releases screen, scroll down the last release deployed to production, scroll up checking the release notes to see if there is anything that can't go out to production.

   In a lot of cases we have 4-5 new releases between staging and production (more if our translations team have been working on a project). We also sometimes have batches of features approved through our QA process so it's a case of doing this flow repeatedly for several projects at once.

   It would be really helpful to either see all of the release notes that are between the current production deployment and a given release, or even just an <HR> or something between entries on the Releases page that says "Environment X is here".

   We have two environments and auto-deploy to staging in a lot of our projects. We have a release per CI build, CI builds correspond to a PR merge so usually a deployable feature.

   Current flow: Some feature or features are approved for release, I go to the overview screen and memorise which version is deployed in production, then I go to the releases screen, scroll down the last release deployed to production, scroll up checking the release notes to see if there is anything that can't go out to production.

   In a lot of cases we have 4-5 new releases… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

8. Add a test-AzureRMResourceGroupDeployment step

   We have a robust step to do ARM deployments in Azure. We are just missing the a similar step to test the template deployment. Currently we have an ugly 2 step workaround - deploy the package to the server and run azure powershell to run this command using SPN (password as a var :( ).

   It would be great to have a replica of the actual deployment step to Azure resource group - but with one command changed (test).

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

9. Provide a more intuitive/accessible/functional use and management of variables

   I've not used Octopus Deploy that much, at present, but I have found that the variables and the configurable nature of the steps to use these variables is key to what I have done so far, and what I'd like to do and use more efficiently going forward.

   At present, I find the variable screen/page a "problem" to work with if there are more than about 20 or 30 variables.

   In my view, requirements of this "Variable" screen/page would include:

   • Be able to filter the variables to a specific "Scope" so you can see what attributes will apply for a particular Environment, Role, Target or Step (or combinations of these). This would be really useful for debugging what variables are being passed to a target/environment. Or limit them to those used by a particular project or step etc.

   • As part of the above, it would also be useful if, where you had variables defined as other variable's values, you can see in the preview the value it was actually outputting based upon the resolution of the variable references/hierarchy.

   • Be able to see variable references used in the variables (and be able to see a list of all usages of variables that didn't exist and warn/prevent if trying to delete a variable where there was a reference to it that did exist)

   • Renaming a variable renames all references where used (at present you have to manually change them in the processes, for example, I believe). Or you should be blocked from renaming if there is a dependancy - i.e. create a new variable, remap the references, then delete the old one.

   • If there are variables of the same names (that use different scopes) then these variables should be grouped into one summary group/entry that can be opened/expanded to show the different variations of that variable. This would also be good if it would show which Scope combinations hadn't been covered by the logic (setting up the same variables with different scopes leaves the opportunity for missing one of the logical scope combinations).

   • Being able to group variables into sets per Octopus Deploy server, per user group, per Project, per Environment, per Target, per Role, per process, and even per Step would give added flexibility. A number of the build tools provide the ability to define a hierarchy of variables at application, project and step level - They work quite well in my opinion.

   • Access to create/amend/modify variables could be granted against one or more of the above scopes so granularity of permissions can be suitable to requirements.

   • At present, if you have the same variable with different scope configurations, but the scopes of those overlap, it seems to be a "random" chance of which value is returned. I'd suspect the interface/page should stop this happening and not leave it open to non-deterministic outcomes.

   • There is another suggestion on loading variables from a configuration file. I'd suggest this may also provide some use if you didn't know the variable values until you built the solution you were to deploy.

   • An audit history of variable values (i.e. when they changed and what they changed to) - This might be useful if something breaks as a result of a change and you need to see the last working value.

   • Coupling the above point, with the point about seeing what variable values were being used in a particular scope, this could even be "at a particular point in time" if Octopus was storing an audit of the changes.

   • Being able to Order by Scope (i.e. the items within Scope such as Target or Environment).

   There are a number of items I've listed above but I'm sure I've not covered all the points/frustrations I have come across. I'll add comments if I remember any more. I hope that provides some food for thought and consideration.

   Other than the variables screen, I'm enjoying using the tool.

   Cheers,

   Paul

   I've not used Octopus Deploy that much, at present, but I have found that the variables and the configurable nature of the steps to use these variables is key to what I have done so far, and what I'd like to do and use more efficiently going forward.

   At present, I find the variable screen/page a "problem" to work with if there are more than about 20 or 30 variables.

   In my view, requirements of this "Variable" screen/page would include:

   • Be able to filter the variables to a specific "Scope" so you can see what attributes will apply for a… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Deployments  ·  Delete…  ·  Admin →

10. Add Channel Groups

    Allow for the creation of a "Channel Group" which contain existing channels. This would allow for a release to be sent to multiple channels, and allow for finer filtering of steps in a deployment. For a given project I have 10 prep steps, 8 potential pkg deployments, and 10 cleanup steps. Being able to group a prep channel, a cleanup channel, and subset of deployment channels would be handy.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

11. "Create or update an IIS Web Site and Application Pool" setting to have option to verify only

    setting "Create or update an IIS Web Site and Application Pool" is currently True/False. Would be nice to have a 3rd option which is check the settings and error if they're not as expected, but don't try to change them.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

12. Add version checks on a lifecycle

    We should be able to check compatible version numbers on a lifecycle.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

13. During Release Creation, check local cache first for latest Package version

    When creating a Release, at the stage where Octopus checks for latest Package version for a Step, first check whether we've already got the latest version for that Package.

    See this Question and associated screenshot for more information:

    http://help.octopusdeploy.com/discussions/questions/8191-when-creating-a-release-why-does-octopus-repeat-the-process-to-get-latest-version-from-teamcity

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

14. Allow scoping variables to rolling step

    I have rolling step with multiple child steps in my deployment process. I would like to scope some variables to all of the child steps in rolling step. Now to do that i have to specify every child step in variable scope.
    It would be much easier if i could set scope just to rolling step (parent step) instead and it would be applied to all child steps in the rolling step.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

15. Time delay between Lifecycle steps

    Define a minimum time delay between phases in a lifecycle.

    In our situation, we do a limited deployment to a small number of targets, and then wait a few days for a bit of real world soak testing.
    It would be great to be able to define a time delay between phases to enforce and standardise the minimum length of time to wait between deployment to different environments

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

16. Allow offline drop from atentacle

    We need to drop a number of files across multiple VLAN sections. What we'd like to do is to drop push one or more packages to a tentacle deep inside the VLANs which will then do the final package drop.

    Having the tentacle perform the drop would allow us to keep the Octopus server very isolated from it's deployment targets and we'd be sure that all communication happens using the existing security protocol enforced by Octopus and that we'd be able to forego domain trusts and other messy solutions to allow the Octopus server to deploy from one network segment to another and drop files on a share which is hosted by a server on a different domain.

    We need to drop a number of files across multiple VLAN sections. What we'd like to do is to drop push one or more packages to a tentacle deep inside the VLANs which will then do the final package drop.

    Having the tentacle perform the drop would allow us to keep the Octopus server very isolated from it's deployment targets and we'd be sure that all communication happens using the existing security protocol enforced by Octopus and that we'd be able to forego domain trusts and other messy solutions to allow the Octopus server to deploy from one network segment… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

17. Capturing Configuration Drift using DSC in Octopus

    Currently Octopus do not have capability to capture drift in Content and Configuration. Can we add it leveraging DSC

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

18. See the deployment steps of an older release

    It would be nice to be able to read / see the deployment steps of an older release.

    Example:

    • I've 3 steps defined in a project A
    • I create a release 1.0.0
    • I add a 4th step to the project A
    • I create a new release 1.0.1

    I this case I can check the process of 1.0.1 just by clicking on the project configration process tab but if I would like to see the process of 1.0.0 I'm unable to do so. I don't know what to expect from relase 1.0.0 because maybe too much has passed from the release creation.

    It would be nice to be able to read / see the deployment steps of an older release.

    Example:

    • I've 3 steps defined in a project A
    • I create a release 1.0.0
    • I add a 4th step to the project A
    • I create a new release 1.0.1

    I this case I can check the process of 1.0.1 just by clicking on the project configration process tab but if I would like to see the process of 1.0.0 I'm unable to do so. I don't know what to expect from relase 1.0.0 because maybe too much has passed from the release… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Delete…  ·  Admin →
    AdminProduct Team (Admin, Octopus Deploy) responded

    Currently this feature is available via the BlueFin Chrome plugin created by David Roberts. We at Octopus are fans, and are happy to support and promote it. The only problem would be those who can’t use Chrome. Could I get some feedback on anyone restricted from using Chrome?

19. When using Deploy Azure Website, if the WebApp Name is set using a custom expression, don't go and fetch the list of WebApps from Azure

    When I setup to deploy an Azure WebApp, if I have specified the Name as a custom expression, when ever I open the step, it sits there retrieving the list of apps from Azure when it doesn't need to.

    Can you make it so it only retrieves if the Name is not a custom expression or if the user toggles back from a custom expression

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →

20. enhance Azure deployment support

    Octopus 3 provides a lot of good features, like unpacking and repacking cspkg files. But there are a couple of features that I feel are missing:

    1. Set VMSize per environment (and step) without hacking in variable sub feature
    2. Set instance count per environment (and step)
    3. Set certificate thumbprints directly from the step (i.e. without custom powershell script)
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Edit…  ·  Delete…  ·  Admin →