apache / apache/maven-build-cache-extension
[MBUILDCACHE-33] Support remote cache credentials from environment variables
- Dominant language
- Java
- Stars
- 163
- Forks
- 77
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 4
Description
**[Alexander Ashitkin](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alex_ashitkin)** opened **[MBUILDCACHE-33](https://issues.apache.org/jira/browse/MBUILDCACHE-33?redirect=false)** and commented
In my current environment settings.xml are managed by a build team which is not allowing any modification because the same build service is used by all teams. Atop of that, maven build runs in a fresh container which doesn't have any credentials injected for security reasons. Because of that cache cannot read/deploy build artifacts to an authenticated http server. Still, our build service allows to inject credentials from environment variables into build container. Need to support cache setup without settings.xml by injecting environment variables:
* MAVEN_BUILD_CACHE_DIRECT_CONNECT
* MAVEN_BUILD_CACHE_USER
* MAVEN_BUILD_CACHE_PASSWORD
* MAVEN_BUILD_CACHE_PROXY_USER
* MAVEN_BUILD_CACHE_PROXY_PASSWORD
---
**Remote Links:**
- [GitHub Pull Request #35
](https://github.com/apache/maven-build-cache-extension/pull/35)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the requested MAVEN_BUILD_CACHE_* environment variables, the existing settings.xml constraint, and the linked GitHub Pull Request #35. Done means cache setup can obtain direct-connection and server or proxy credentials from the specified environment variables without requiring settings.xml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100