If it helps, I am seeing a similar behaviour. I am using Jenkins ver.
1.464<http://jenkins-ci.org/>
and whenever I uncheck "Use private Maven repository" it magically
reappears to be checked when I look at it the next day. Am still
investigating...
On Friday, 24 June 2011 16:42:05 UTC+1, Stevo Slavic wrote:
>
> Hello Jenkins users,
>
> Maven build job A had "Use private Maven repository" checked. Then I
> created another build job B by copying A. B was created and had "Use
> private Maven repository" checked as well. Building B created and used
> ${WORKSPACE}/.repository as B's repository as it should.
>
> Then I tried to run off "Use private Maven repository" for B, saved
> that build job configuration, and wiped-out it's workspace. Problem is
> that regardless of the configuration building build job B would
> continue to use private Maven repository. I thought maybe B
> references/uses A's configuration for "Use private Maven repository"
> so I turned that one off for A as well, but in vain - B would always
> use private Maven repository.
>
> I'm using Jenkins 1.417.
>
> Can anybody reproduce this unwanted behavior?
>
> Regards,
> Stevo.
>
>
