Skip to content

Settings and activity

3 results found

  1. 12 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 » Deployments  ·  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
    Thomas B commented  · 

    Just wanted to write a custom c# script which uses an HttpClient.

    But I am stuck with SendAsync() method and scriptcs which does not supports async/await invocation.

    Sad to see that c# scripts are still stuck on windows full .net framework. dotnet-script should be the way to go.

    Thomas B supported this idea  · 
  2. 5 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 » Integration  ·  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
    Thomas B commented  · 

    Please also note that often the internal url will be different from the external one.

    I don't know how the system retrieve issues details from the different commits, but the could be problems if using internal urls.

    Edit: As suspected, the server tries to use the URL in the json directly, and fail because this URL is an internal one.

    All the new issue system connectors are only aimed at cloud / public services. You will never be able to setup an internal on-premise server with this connectors.

    As suggested, you should be able to :
    - accept to upload work items details with the package information
    - add a parameter to provide a custom buildinformation.json file

    An error occurred while saving the comment
    Thomas B commented  · 

    I agree with this suggestion. The current system does not allow to have multiple on-premise services.

    Even with that, accessing JIRA or Azure DevOps server from the octopus deploy server is often not possible.

    Why not simply allowing to push work item details with the build information ?

    Thomas B supported this idea  · 
  3. 60 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

    11 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
    Thomas B commented  · 

    This suggestion should be marked as Completed.

    An error occurred while saving the comment An error occurred while saving the comment
    Thomas B commented  · 

    And I see that a github issue try to address this suggestion: https://github.com/OctopusDeploy/Issues/issues/2701

    An error occurred while saving the comment
    Thomas B commented  · 

    I agree with Sam : a more generic solution should be to allow binding a certificate by name instead of thumbprint. And if multiple certificates match, should use the most recent one.

    Thomas B supported this idea  ·