How to trigger deploy with existing artifact in S3 instead of zipping files and upload?

Open
#113 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, java
Domain
cloud, devops

Research direction

The issue asks whether the Jenkins CodeDeploy plugin can trigger a deployment from an existing artifact in S3 instead of creating and uploading a zip. No files, tests, or entry points are mentioned; first inspect the plugin's deployment and artifact-upload flow. Done means documenting or implementing a supported path for deploying the existing S3 artifact.

Written by the indexing model from the issue text.

Description

Hi guys,
I wanna use CodeDeploy plugins to trigger deploy with an existing artifact in S3 instead of creating a zip, upload to S3 and move to deploy.
Do we have any option?

Dominant language
Java
Stars
156
Forks
130
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awslabs/aws-codedeploy-plugin

All issues in awslabs/aws-codedeploy-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.