We store credentials and a file template in CI (Jenkins credentials and config file provider plugin, GitLab CI/CD variables) and then create the file within in our pipeline, then there can also be files in .mvn directory committed to source code.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
We store credentials and a file template in CI (Jenkins credentials and config file provider plugin, GitLab CI/CD variables) and then create the file within in our pipeline, then there can also be files in .mvn directory committed to source code.
Originally posted by @jghal in https://github.com/jfrog/frogbot/issues/559#issuecomment-1781144122
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
The issue does not name a file, entry point, or acceptance criteria. Start by reviewing the CI pipeline configuration and the .mvn directory, then clarify whether the intended outcome concerns Jenkins credentials, GitLab CI/CD variables, generated files, or committed configuration. Done cannot be determined until that scope is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100