authorjapps / authorjapps/bug-fix-bounty
Env setup for Jenkins and S3
Open
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Points: 5 Complexity: 3
As a Developer
When I push my code to a Git repo
Then it will trigger the Jenkin process
And the build will copy the output artifact to an S3 folder in AWS
And the AWS BuildPipeline/Code Deploy will pick this from S3
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository files or tests. Start by reviewing the Jenkins and AWS setup needed for the stated push-to-deploy flow; done means a Git push triggers Jenkins, the build artifact reaches the intended S3 location, and AWS deployment consumes it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100