octopus-deploy

问题 Is there any way to export Octopus variables to json file, using "Command" step in Jenkins? According to official Octopus documentation I only able to export Projects and Releases. Is there any way to export particular variables from particular project? 回答1: Currently you can not do this using Octo.exe. However you can still use Octopus REST API for your purpose. First you have to create a API Key, which is required to access those APIs. Then call following API end point to get your specific

问题 I'm a developer whose transitioning into Devops. By observation, I've noticed that a lot of dev shops have started using Octopus Deploy and Azure Devops Services (AzDo, formerly VSTS), or they are starting new projects to setup devops ci/cd pipelines AND they spec to use both tools. I've been through some quick training for both tools and though they aren't perfectly the same, AzDo seems to offer all of the same features as Octopus Deploy. So, my question is if a company is already using AzDo

来源： https://stackoverflow.com/questions/50402029/only-install-powershell-packageprovider-and-module-if-not-already-installed

来源： https://stackoverflow.com/questions/50402029/only-install-powershell-packageprovider-and-module-if-not-already-installed

问题 Within Octopus Deploy I've setup a Terraform Apply Step using their Apply a Terraform template In my Terraform main.tf file I want to use a connection to run an remote-exec on a Amazon Linux EC2 instance in AWS resource "aws_instance" "nginx" { ami = "${var.aws_ami}" instance_type = "t2.nano" key_name = "${var.key_name}" connection { type = "ssh" user = "ec2-user" private_key = "${var.aws_key_path}" } provisioner "remote-exec" { inline = [ "sudo amazon-linux-extras install epel -y", "sudo yum

问题 Within Octopus Deploy I've setup a Terraform Apply Step using their Apply a Terraform template In my Terraform main.tf file I want to use a connection to run an remote-exec on a Amazon Linux EC2 instance in AWS resource "aws_instance" "nginx" { ami = "${var.aws_ami}" instance_type = "t2.nano" key_name = "${var.key_name}" connection { type = "ssh" user = "ec2-user" private_key = "${var.aws_key_path}" } provisioner "remote-exec" { inline = [ "sudo amazon-linux-extras install epel -y", "sudo yum

问题 Have a powershell script that will create a scheduled task, for deployment, by way of Octopus, to a Windows 2012 server. Function Create-ScheduledTask($TaskName,$RunAsUser,$TaskRun,$Schedule,$StartTime,$StartDate,$Arguments,$RunWithElevatedPermissions,$Days,$Password){ # set up $Command = "schtasks.exe /create /ru `"$RunAsUser`" /tn `"$TaskName`" /tr `"'$($TaskRun)' $Arguments`" $cmdSchedule $cmdDays $cmdStartDate $cmdStartTime /F $cmdInterval $cmdDuration $cmdRunLevel $cmdPassword" echo

问题 I have a multiple project solution and am using Octopus Deploy and TeamCity for deployment. I have installed the Octopack NuGet package on two projects that I wish to be created as artifacts during the CI build. I have set the follwing in my build step: and have checked the csproj files of both projects and can see: <Import Project="..\packages\OctoPack.2.0.26\targets\OctoPack.targets" /> However, after the build runs one of the projects has been packaged as an artifact and the other one hasn

问题 I've got an Octopus Tentacle running a deploy script. The tentacle is running as the LocalSystem account. Inside the script, I'm able to do pretty much everything I need, aside from some archive bit. The archive needs to be done under different domain credentials because it's on a network share. The frustrating this is that the code below works locally, but when run off the tentacles, it fails with the error ----------------------------------------------------[ Backup Nupkg ]-----------------

问题 When using create-release can I specify the user who is creating the release independent of the user I'm using to execute octo.exe ? The scenario in mind is our build server will begin a build based on a push (and it knows who made the commit), but as far as Octopus Deploy is concerned the build server created the release, and not the person who committed. 回答1: We use an Octopus Service Account with an API Key, and we call it build-deploy-bot . This is the account that TeamCity uses to create