nebula-plugins / nebula-plugins/nebula-release-plugin
AWS CodeCommit Support
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
Currently, I'm using CodeCommit and would like to use Nebula within a CodePipeline in order to build and tag releases. Currently I'm running into an authentication issue from JGit
org.eclipse.jgit.api.errors.TransportException: https://git-codecommit.us-east-1.amazonaws.com/v1/repos/REPO_NAME: Authentication is required but no CredentialsProvider has been registered
I have the proper IAM permissions to access CodeCommit.
More a general question to see if this is possible without having to hard code credentials.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing the JGit authentication path that produces the CredentialsProvider error when the plugin runs in AWS CodePipeline with CodeCommit; the issue needs an agreed, non-hardcoded authentication approach before implementation can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, git, groovy
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100