I had a similar issue when multiple builds were running concurently, iv
patched the gradle executable to create a separate cache folder for each
build:
# my ugly extension point
CACHE_HOME=/var/lib/jenkins/caches/$JOB_NAME
mkdir -p $CACHE_HOME
cp /var/lib/jenkins/.gradle/init.gradle $CACHE_HOME
exec "$JAVACMD" $JAVA_OPTS $GRADLE_OPTS \
-classpath "$CLASSPATH" \
-Dorg.gradle.appname="$GRADLE_APP_BASE_NAME" \
$STARTER_MAIN_CLASS \
"$@" -g $CACHE_HOME
Im not sure its the same issue but thats my workaround until its fixed :)
Ronen
2011/7/26 Szczepan Faber <[email protected]>
> I think there is already a defect reported about this behavior. It's not
> fixed yet.
>
> Cheers!
> --
> Szczepan Faber
> Principal engineer@gradleware
> Lead@mockito
> 26-07-2011 17:31 użytkownik "phil swenson" <[email protected]>
> napisał:
>
> > periodically on our Jenkins server we get an error updating the gradle
> > cache. Is this a known issue?
> >
> > FAILURE: Build aborted because of an internal error.
> >
> > * What went wrong:
> > Build aborted because of an unexpected internal error. Please file an
> > issue at: http://www.gradle.org.
> >
> > * Try:
> > Run with --debug option to get additional debug info.
> >
> > * Exception is:
> > org.gradle.api.UncheckedIOException: Could not add entry '1793' to
> > cache
> '/opt/CBMS/tools/.gradle-homes/BAS/caches/1.0-milestone-3/fileSnapshots/cache.bin'.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list, please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
>
