[
http://jira.codehaus.org/browse/CONTINUUM-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191795#action_191795
]
Wendy Smoak commented on CONTINUUM-1941:
----------------------------------------
Creating the directory if it doesn't exist is fine with me if dist build is not
enabled.
In the dist build case, currently the master passes the value for
-Dmaven.local.repo to the agent.
If you haven't configured any local repos and assigned them to project groups,
then it will just pass whatever the DEFAULT local repo is on the master. In my
case today, it passed /opt/continuum-data/local-repository to a Windows agent
where that directory didn't exist.
I'm not sure what you mean by keys or namespaces. The local repo is just a
string, it's up to the admin to make sure each project group is assigned a
local repo that makes sense for that project, and then the agent passes it
along. There's no way for the master to know if that's a valid value, because
it doesn't know which agent the project will eventually build on.
The local repo probably needs to be moved into the Build Environment. Right
now it's configured at the Project Group level, and what happens if I want to
build my project on two agents that need a different local repo value?
> Continuum should create directory when adding a local repository
> ----------------------------------------------------------------
>
> Key: CONTINUUM-1941
> URL: http://jira.codehaus.org/browse/CONTINUUM-1941
> Project: Continuum
> Issue Type: Improvement
> Environment: ubuntu
> Reporter: Gwen Harold Autencio
> Fix For: Backlog
>
>
> Create a local repository in continuum.
> e.g.
> /home/user/askjdfklsdajfklsajdf/asfsadfsadfsdfsadfasf
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
