By using AWS re:Post, you agree to the Terms of Use
/AWS CodeDeploy/

Questions tagged with AWS CodeDeploy

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

code deploy agent duplicate log entries

I'm experiencing an issue with a deployment to one of several Windows servers - other servers with the same job are deploying correctly. The issue is that upon extraction of a zip file the following error occurs: Exception calling "ExtractToDirectory" with "2" argument(s): "The file 'C:\Prog....c.yml' already exists." (path shortened for brevity) After the deployment failed, I looked in the directory and sure enough the file was there and it was written by the code deployment job. I noticed something odd though, in the code deploy agent logs there are two sets of every entry, including the above error. It appears that code deploy is running two instances and they are both trying to perform the same deployment and therefore can't write to the same file. Here is a snippet from the agent log: 2022-04-03T00:01:51 DEBUG [codedeploy-agent(13484)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: PollHostCommand: Host Command = nil 2022-04-03T00:01:51 DEBUG [codedeploy-agent(13484)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: PollHostCommand: Host Command = nil 2022-04-03T00:01:52 DEBUG [codedeploy-agent(13484)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: Calling PollHostCommand: 2022-04-03T00:01:52 DEBUG [codedeploy-agent(13484)]: InstanceAgent::Plugins::CodeDeployPlugin::CommandPoller: Calling PollHostCommand: 2022-04-03T00:01:52 INFO [codedeploy-agent(13484)]: Version file found in C:/ProgramData/Amazon/CodeDeploy/.version with agent version OFFICIAL_1.3.2.1902_msi. 2022-04-03T00:01:52 INFO [codedeploy-agent(13484)]: Version file found in C:/ProgramData/Amazon/CodeDeploy/.version with agent version OFFICIAL_1.3.2.1902_msi. On servers where the deployment succeeds, I only see one line for each of the above in the log files. I have restarted the agent service to no avail as well as reinstalled. Any help is appreciated.
0
answers
0
votes
1
views
AWS-User-4222687
asked a month ago

cdk destroy deleting the stacks from cdk.out/manifest.json not my stage stacks

Hello AWS Community, in my team we have just on AWS Account, and that way we deploy th **PreProd**and ro stages in tghe same account. the Problem is: i wanant to delete all stacks produced through the **PreProd **stage before moving to the **Pre **stage because of duplicat names ... etc. i tried using the command ``` cdk destroy --app 'npx ts-node ./bin/AutBusBackend.ts' --all --force" ``` but the destroy here is deleting the stacks without the prefix ***Pre***, and in this time we don't have anway this stacks. Do you know how can i get ride of this problem to delete the stacks that are preduced in the current stage before and not the default stacks names in cdk.out ? here is my pipeline code ``` const repo = codecommit.Repository.fromRepositoryName(this, 'AutbusBackendRepo', 'AutbusBackend'); const pipeline = new CodePipeline(this, 'AutBusPipeline', { pipelineName: 'AutBusPipeline', synth: new ShellStep('Synth', { input: CodePipelineSource.codeCommit(repo, 'master'), commands: [ 'npm install -g npm', 'npm install', 'npm ci', 'npm run build', 'npm run cdk -- synth' ] }) }); const preProd = pipeline.addStage(new AppStage(this, 'PreProd',{ env: { account: account, region: region } })); const step1 = new ShellStep('IntegrationTesting', { commands: [ 'npm install', 'npm test' ] }); const step2 = new ManualApprovalStep('Manual approval before Prod'); const step3 = new ShellStep('Delete deployed Stacks', { commands: [ 'npm install', 'npm install -g aws-cdk', "cdk destroy --app 'npx ts-node ./bin/AutBusBackend.ts' --all --force" ] }); // step2.addStepDependency(step1); // step3.addStepDependency(step2); // preProd.addPost(step3); // preProd.addPost(step2); // preProd.addPost(step1); const prodStage = pipeline.addStage(new AppStage(this, 'Prod', { env: { account: account, region: region } })); ``` Thanks in adavance for any new insiring idea
0
answers
0
votes
1
views
Yahya
asked 2 months ago

Amplify build failed because the bucket already exists

Hi, I am trying to deploy an amplify app as per https://webapp.serverlessworkshops.io/staticwebhosting/deploy/ but the build is failing because of an existing bucket I am unable to see the bucket in S3. How can I delete the bucket? or how to resolve this issue? ``` 2022-02-25T03:31:32.457Z [INFO]: An error occurred when creating the CloudFormation stack 2022-02-25T03:31:32.459Z [WARNING]: ✖ Root stack creation failed 2022-02-25T03:31:32.464Z [INFO]: AlreadyExistsException: Stack [amplify-wildrydes-prod-32220] already exists at Request.extractError (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/protocol/query.js:50:29) at Request.callListeners (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:106:20) at Request.emit (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:686:14) at Request.transition (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12) at /root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:12) at Request.callListeners (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18) at Request.emit (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:78:10) at Request.emit (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:686:14) at Request.transition (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:22:10) at AcceptorStateMachine.runTo (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:14:12) at /root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/state_machine.js:26:10 at Request.<anonymous> (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:38:9) at Request.<anonymous> (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/request.js:688:12) at Request.callListeners (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:116:18) at callNextListener (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/sequential_executor.js:96:12) at IncomingMessage.onEnd (/root/.nvm/versions/node/v14.18.1/lib/node_modules/@aws-amplify/cli/node_modules/aws-sdk/lib/event_listeners.js:335:13) at IncomingMessage.emit (events.js:412:35) at IncomingMessage.emit (domain.js:475:12) at endReadableNT (internal/streams/readable.js:1334:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) { code: 'AlreadyExistsException', time: 2022-02-25T03:31:32.456Z, requestId: '92bb3d71-1610-43c4-a385-54cb25e459cd', statusCode: 400, retryable: false, retryDelay: 81.16703459454344 } 2022-02-25T03:31:32.487Z [ERROR]: !!! Build failed 2022-02-25T03:31:32.487Z [ERROR]: !!! Non-Zero Exit Code detected 2022-02-25T03:31:32.488Z [INFO]: # Starting environment caching... 2022-02-25T03:31:32.488Z [INFO]: # Environment caching completed Terminating logging... ``` Thank you
0
answers
0
votes
6
views
Sri
asked 3 months ago

install code deploy agent in disabled mode(pre-baking in AMI)

I would like to install code-deploy-agent on windows in disabled mode but I couldn't find any argument in the MSI package. I tried to search on the registry for a specific flag regarding registration. We are trying to install code-deploy agent in an AMI but after the ec2 instance is created it complains about the instance-id. ``` Set-Service : Service 'CodeDeploy Host Agent Service (codedeployagent)' cannot be started due to the following error: Cannot start service codedeployagent on computer '.'. At C:\Windows\system32\config\systemprofile\AppData\Local\Temp\Amazon\EC2-Windows\Launch\InvokeUserData\UserScript.ps1:35 char:1 + Set-Service -Name 'codedeployagent' -StartupType 'automatic' -Status ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Set-Service], ServiceCommandException + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.SetServiceCommand Set-Service : Service 'CodeDeploy Host Agent Service (codedeployagent)' cannot be started due to the following error: Cannot start service codedeployagent on computer '.'. At C:\Windows\system32\config\systemprofile\AppData\Local\Temp\Amazon\EC2-Windows\Launch\InvokeUserData\UserScript.ps1:35 char:1 + Set-Service -Name 'codedeployagent' -StartupType 'automatic' -Status ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OpenError: (System.ServiceProcess.ServiceController:ServiceController) [Set-Service], Se rviceCommandException + FullyQualifiedErrorId : CouldNotStartService,Microsoft.PowerShell.Commands.SetServiceCommand ```
0
answers
0
votes
0
views
aws-lmayorga
asked 3 months ago

AWS CodeDeploy: STRING_VALUE can not be converted to an Integer

Using AWS CodePipeline and setting a Source, Build and passing `taskdef.json` and `appspec.yaml` as artifacts, the deployment action `Amazon ECS (Blue/Green)` will fail with the error: STRING_VALUE can not be converted to an Integer This error does not specify where this error happens and therefore it is not possible to fix. For reference, the files look like this: ```yaml # appspec.yaml version: 0.0 Resources: - TargetService: Type: AWS::ECS::Service Properties: TaskDefinition: <TASK_DEFINITION> LoadBalancerInfo: ContainerName: "my-project" ContainerPort: 3000 ``` ```json // taskdef.json { "family": "my-project-web", "taskRoleArn": "arn:aws:iam::1234567890:role/ecsTaskRole-role", "executionRoleArn": "arn:aws:iam::1234567890:role/ecsTaskExecutionRole-web", "networkMode": "awsvpc", "cpu": "256", "memory": "512", "containerDefinitions": [ { "name": "my-project", "memory": "512", "image": "01234567890.dkr.ecr.us-east-1.amazonaws.com/my-project:a09b7d81", "environment": [], "secrets": [ { "name": "APP_ENV", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:APP_ENV::" }, { "name": "PORT", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:PORT::" }, { "name": "APP_NAME", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:APP_NAME::" }, { "name": "LOG_CHANNEL", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:LOG_CHANNEL::" }, { "name": "APP_KEY", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:APP_KEY::" }, { "name": "APP_DEBUG", "valueFrom": "arn:aws:secretsmanager:us-east-1:1234567890:secret:web/my-project-NBcsLj:APP_DEBUG::" } ], "essential": true, "logConfiguration": { "logDriver": "awslogs", "options": { "awslogs-group": "", "awslogs-region": "", "awslogs-stream-prefix": "" } }, "portMappings": [ { "hostPort": 3000, "protocol": "tcp", "containerPort": 3000 } ], "entryPoint": [ "web" ], "command": [] } ], "requiresCompatibilities": [ "FARGATE", "EC2" ], "tags": [ { "key": "project", "value": "my-project" } ] } ``` Any insights on this issue are highly appreciated!
2
answers
0
votes
6
views
fagiani
asked 4 months ago

CDK v1: Deploy RDS SQL Server and use credential in a connection string for fargate docker instance

I have been trying to find an answer in documentation, github, here and the old forums, but I fail to find the answer to my question. In my CDK v1 (python) I create a RDS instance of SQL Server and set credentials with aws_rds.Cerednetials.from_generated_secret(), but when I later on want to provide environment/sercrets values to the docker container I want to run in fargate I have the following environment variable that I need to be set: DB_CONNECTION_STRING, which has the following syntax: Server=<somehost.aws.com>,144;Database=<databasename>; User Id=<databaseuser>;Password=<databasepassword> All the examples I have seen uses multiple variables like DB_USER/DB_PASS/DB_HOST and then you can easily set those with help of secret_value, but there is no example on generating a connection string. How do you solve this? I took a look at aws glue, but it didn't feel like the right optionand I'm not too keen on making a dockerfile to try to pull the official docker image and then create a kind of a wrapper to have environment/sercret variables and then a script that builds up the connection string and sets it before calling the start script for the application (this has other downsides). The reason why I'm not using the CDK v2 is that the current version seems to be broken when you create a new project in WSL (seems to think it's pure ms-windows and fails to create a number of files needed). Thanks in advance for any reply.
1
answers
0
votes
8
views
BashScripter
asked 4 months ago

Cannot Connect EC2 MongoDB Instance During CodeDeploy LifeCycleEvent

I have an EC2 (RHEL) instance running a NodeJS server. I have setup the start of this server as a systemd service (included below) and run this service via a shell script executed during the ApplicationStart part of CodeDeploy LifeCycleEvent. In the server itself, I am using `mongoose` to connect to MongoDB running on another EC2 instance. My problem is that my server does not connect to MongoDB and instead returns the following error: ``` { message: 'Could not connect to MongoDB!!! getaddrinfo ENOTFOUND undefined', reason: TopologyDescription { type: 'Single', setName: null, maxSetVersion: null, maxElectionId: null, servers: Map { 'undefined:27017' => ServerDescription { address: 'undefined:27017', error: Error: getaddrinfo ENOTFOUND undefined at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:66:26) { name: 'MongoNetworkError' }, roundTripTime: -1, lastUpdateTime: 23933862843, lastWriteDate: null, opTime: null, type: 'Unknown', topologyVersion: undefined, minWireVersion: 0, maxWireVersion: 0, hosts: [], passives: [], arbiters: [], tags: [] } }, stale: false, compatible: true, compatibilityError: null, logicalSessionTimeoutMinutes: null, heartbeatFrequencyMS: 10000, localThresholdMS: 15, commonWireVersion: null }, level: 'error', stack: 'MongooseServerSelectionError: getaddrinfo ENOTFOUND undefined\n' + ' at NativeConnection.Connection.openUri (/home/centos/my-server/node_modules/mongoose/lib/connection.js:847:32)\n' + ' at /home/centos/my-server/node_modules/mongoose/lib/index.js:351:10\n' + ' at /home/centos/my-server/node_modules/mongoose/lib/helpers/promiseOrCallback.js:32:5\n' + ' at new Promise (<anonymous>)\n' + ' at promiseOrCallback (/home/centos/my-server/node_modules/mongoose/lib/helpers/promiseOrCallback.js:31:10)\n' + ' at Mongoose._promiseOrCallback (/home/centos/my-server/node_modules/mongoose/lib/index.js:1149:10)\n' + ' at Mongoose.connect (/home/centos/my-server/node_modules/mongoose/lib/index.js:350:20)\n' + ' at module.exports (/home/centos/my-server/startup/db.js:20:6)\n' + ' at startServer (/home/centos/my-server/index.js:22:9)\n' + ' at processTicksAndRejections (internal/process/task_queues.js:97:5)', label: 'qa-server', timestamp: '1/21/2022, 11:41:15 AM' } ``` I tried the following solutions and these did not work: 1. `https://aws.amazon.com/premiumsupport/knowledge-center/dns-resolution-failures-ec2-linux/` 2. Adding the following lines to my `.service` file: ``` After=network-online.target Wants=network-online.target ``` If anyone could provide some insight as to how I can solve this, it'd be greatly appreciated. **appspec.yaml** ``` version: 0.0 os: linux files: - source: / destination: /home/centos/my-server hooks: BeforeInstall: - location: scripts/cleanup.sh timeout: 300 runas: root AfterInstall: - location: scripts/install_dependencies.sh timeout: 300 runas: root - location: scripts/update_service.sh timeout: 300 runas: root ApplicationStart: - location: scripts/start_server.sh timeout: 300 runas: root ApplicationStop: - location: scripts/stop_server.sh timeout: 300 runas: root ``` **start_server.sh** ``` #!/bin/bash iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 9080 iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 443 -j REDIRECT --to-port 9443 sudo systemctl daemon-reload sudo systemctl restart myserver.service ``` **myserver.service** ``` [Unit] Description=Node.js My server [Service] ExecStart=/usr/bin/node /home/centos/my-server/index.js WorkingDirectory=/home/centos/my-server/ StandardOutput=syslog StandardError=syslog SyslogIdentifier=my-server-log Environment=PATH=/usr/bin:/usr/local/bin Environment=NODE_ENV=production [Install] WantedBy=multi-user.target ``` **index.js** ``` const winston = require('winston'); const express = require('express'); const logging = require('./startup/logging'); const config = require('./startup/config'); const routes = require('./startup/routes'); const db = require('./startup/db'); const validation = require('./startup/validation'); const redirect = require('./startup/redirect'); const app = express(); const successMessage = async () => { const message = 'my-server is up and running and ready for requests..'; winston.info(message); console.log(message); }; const startServer = async () => { await logging(); await config(); await routes(app); await db(); await validation(); await redirect(app); await successMessage(); }; startServer(); ``` **db.js** ``` const mongoose = require('mongoose'); const winston = require('winston'); const nconf = require('nconf'); const fs = require('fs'); module.exports = async function () { // Get the mongodb credentials from config memory const ipAddress = fs.existsSync('/.dockerenv') ? nconf.get('mongodb:dockerIPAddress') : nconf.get('mongodb:ipAddress'); const port = nconf.get('mongodb:port'); const username = encodeURIComponent(nconf.get('mongodb:username')); const password = encodeURIComponent(nconf.get('mongodb:password')); const database = nconf.get('mongodb:database'); const mongoUrl = `mongodb://${username}:${password}@${ipAddress}:${port}/${database}?authSource=admin`; mongoose .connect(mongoUrl, { useNewUrlParser: true, useUnifiedTopology: true, useCreateIndex: true, useFindAndModify: false, }) .then(() => winston.info('Connected to mongodb successfully..')) .catch((err) => winston.error('Could not connect to MongoDB!!!', err)); }; ```
1
answers
0
votes
3
views
AWS-User-8027849
asked 4 months ago

Custom Canary Checks with ECS CodeDeploy Blue/Green Canary Deployment

Hey everyone, I have an ECS Fargate cluster up and running with automated CI/CD via CodePipeline & CodeDeploy. The infrastructure is managed with terraform and works as desired. My deployment strategy is blue/green, and I went for the `CodeDeployDefault.ECSCanary10percent5Minutes` deployment configuration (as described here: https://docs.aws.amazon.com/AmazonECS/latest/userguide/deployment-type-bluegreen.html). The gradual traffic shift between the blue and green task sets works fine, however I haven't found any way to influence the canary checks (like, abort the deployment if something's wrong) or introduce custom canary checks during the deployment process. Also, I found very little information on how Canary determines the health of a deployment. I'd like to perform a number of checks during deployment, and abort if anything's wrong. **My questions are:** * How is a Canary release deemed healthy/unhealthy by default (assumption: The alb target group health check?) * What's a possible best practice to observe deployment health during canary releases and perform automated rollback? Is this even possible currently? Upon googling some more it seems that adding CloudWatch Alarms and an AlarmConfiguration to the Deployment Group could do the trick (as documented here: https://docs.aws.amazon.com/codedeploy/latest/userguide/deployment-groups-configure-advanced-options.html). Is that the idiomatic way to achieve this? If so, how do I ensure that the CloudWatch alarm check is only performed against the service version that is currently being deployed? Thanks for any pointers everyone! Maik
1
answers
0
votes
4
views
maik
asked 4 months ago

AWS ElasticBeanstalk NodeJS Application version cannot be uploaded/deployed/reverted "Unable to create the application version:" / "Validation error"

I have a NodeJS application running via ElasticBeanstalk, have deployed 59 previous application versions via the "upload and deploy" button in the EBS dashboard for the application environment. Before, I uploaded a zip file and the environment updated successfully (all at once strategy), never had issues. - Trying to upload a zip file the last 2 days (for the first time in some months) fails, after uploading the "Upload and deploy" popup shows only a red X icon with text "Unable to create the application version: ", without further information. - The "Application versions" page of the environment shows errors on loading like "Validation error" and "Error Unable to retrieve default rolling update values, leave the options blank to retrieve the defaults:", but is otherwise functional. - Reverting to a previous application version via the "Application versions" page also no longer works. Just like when uploading a new version, when reverting the "Deploy Application Version" popup shows "Unable to create the application version: ", without further information. - Deleting previous application versions errors out frequently, but does succeed after several attempts, I've deleted most of my old versions to make sure I'm under the limit. Is there a problem with the service currently, or has something changed in the past months requiring changes on my end? Is there any way I could debug this, as the "Upload and deploy" popups provide no information about problems? * I also cannot create a new (NodeJS) application environment via EBS dashboard, when creating a new environment from an application or from the environments page, it fails and shows only "Validation error". Update: After trying multiple times, it does succeed eventually.
1
answers
0
votes
6
views
AWS-User-4502449
asked 4 months ago

Codedeploy to server farm - high level understanding and confirmation

Morning all, I want to confirm I am on the right track and just logically trying to put things in order. I have a group of servers that are quite static (no need for autoscaling). It's a java app, and Beanstalk doesn't support the app. So right now the developer is going to each server via custom ports to undeploy and deploy new apps. The farm has grown and its time consuming. Some of the reading is a bit confusing, so for a quick high level, I had these questions/help items. Using the left side nav from codecommit, **Under Source** - its always just one file (a .war file). so regardless, I believe I will need to use either GIT/CodeCommit and can't just have the developer upload a file to an S3 bucket right? That would enable the version control, revert, etc. **Under Deploy** - Applications - I have created the application, service role, type and configuration (by key/value). Also have the enable load balancing checked with a test group (one server right now). I don't think I really need to worry about the artifacts or the build, all I want is for the developer to finish his WAR file, commit. So not sure what is the magic that after I he commits, it takes that code, then push's to the servers. The agent is installed and just not sure if I need a pipeline setup, or there is something between the deploy and the agent and a simple answer here may prove much faster than other resources. So thank you again for the feedback and/or suggestions if there is a better way but think once setup this really is quite simple.
2
answers
0
votes
3
views
lraymond
asked 4 months ago
2
answers
0
votes
17
views
ktsuda
asked 5 months ago
  • 1
  • 90 / page