Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven installation in Slave should make use of Nexus as proxy #6

Open
deors opened this issue Nov 10, 2016 · 0 comments
Open

Maven installation in Slave should make use of Nexus as proxy #6

deors opened this issue Nov 10, 2016 · 0 comments

Comments

@deors
Copy link

deors commented Nov 10, 2016

Maven installation in Slave should make use of Nexus as proxy, optimizing bandwidth when downloading artefacts from public repositories, and enabling deployment of artefacts built in ADOP builds.

Executing this command:
$ sudo docker exec jenkins-slave cat tools/hudson.tasks.Maven_MavenInstallation/ADOP_Maven/conf/settings.xml
I can see that Maven configuration is the vanilla one.

We should evaluate which mechanism would be the better to have Maven settings appropriately loaded into the Slave:
a) Do this during Platform init
b) Install Maven along with our settings in Dockerfile (vs. automatic install)
c) Any other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant