question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Option to deploy an existing release in OctopusDeploy

See original GitHub issue

Once you crated a release in Octopus Deploy through Cake, there is no option to deploy that release. I’ve got a draft code that can do that, but I see there are a few issues around OctopusDeploy: #1022, pending PR #1218.

I’m not sure what is the conclusion of discussion about duplicating parameters for server and apikey in alias calls and settings object. So here is my proposal:

    [CakeMethodAlias]
    public static void OctoDeployRelease(this ICakeContext context, string server, string apiKey, string projectName, string deployTo, string releaseNumber, DeployReleaseSettings settings)
    {
        // do deploy
    }

    [CakeMethodAlias]
    public static void OctoDeployRelease(this ICakeContext context, string server, string apiKey, string projectName, string deployTo,  DeployReleaseSettings settings)
    {
        OctoDeployRelease(context, server, apiKey, projectName, deployTo, "Latest", settings);
    }

My only concern is #1022 - Should I base the settings object on common OctopusDeploySettings while it still has Server and ApiKey parameters?

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
patriksvenssoncommented, Sep 14, 2016

@trailmax Looks like release number isn’t mandatory, so it should be on the settings class. DeployReleaseSettings is also too generic, so would be better if you called that OctoDeployReleaseSettings to keep consistency with other tools.

[CakeMethodAlias]
public static void OctoDeployRelease(this ICakeContext context, string server, string apiKey, string projectName, string deployTo,  DeployReleaseSettings settings)
{
  // Implementation   
}
0reactions
devleadcommented, Oct 20, 2016

Fixed by #1229

Read more comments on GitHub >

github_iconTop Results From Across the Web

Deploy existing release | Documentation and Support
This script demonstrates how to programmatically deploy an existing release. UsageBookmark. Provide values for: Octopus URL; Octopus API Key; Space Name ...
Read more >
Create and Deploy a Release | Documentation and Support
To deploy the release, click Deploy. The next screen displays a task summary. If you click the TASK LOG, you'll see the steps...
Read more >
Deploy a release step | Documentation and Support
The Deploy a Release step lets you have a project trigger the deployment of a release of another project. This is useful when...
Read more >
Releases and Deployments | Documentation and Support
Releases are snapshots of your deployment process and other associated assets (references to package versions, scripts, variables) as they ...
Read more >
Automatic release creation | Documentation and Support
Automatic release creation allows you to automatically create a new release when a new package is pushed to the built-in package repository.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found