[
https://issues.apache.org/jira/browse/IVY-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles Scokart updated IVY-1059:
--------------------------------
Priority: Major (was: Critical)
Issue Type: Improvement (was: Bug)
Summary: Incorrect usage of the resolution cache should be reported
nicely (was: Incorrect branch information is taken during publish)
Hudson launch a new JVM for each build. So it can not be a static value in
memory. If the branch name leak from one build to the other build, that must
happen via the file system. Most probably for the resolution cache as Maarten
said.
I identified a probable flow. The resolve stores the resolved module
descriptor in the resolution cache (containing the branch info contained in
your original ivy file). When you publish, ivy take the module, the
organisation and revision from the ant properties defined by the resolve. It
use this info to find back the resolved module descriptor in the resolution
cache. If the file has been replaced by an other build, you have a problem...
So really, if you have concurrent build, you should use a different resolution
cache.
I reduce the severity. Feel free to increase it again if you still have the
problem whit separate resolution cache.
I didn't close it, because I think we should find a way to ensure that the
content of the cache is the right one. But I don't see a nice solution for the
moment.
Also, we should maybe use a default directory that is no global (something
relative to the build directory maybe). But for that I don't see a good choice
for the moment.
> Incorrect usage of the resolution cache should be reported nicely
> -----------------------------------------------------------------
>
> Key: IVY-1059
> URL: https://issues.apache.org/jira/browse/IVY-1059
> Project: Ivy
> Issue Type: Improvement
> Components: Ant
> Affects Versions: 2.1.0-RC1
> Environment: Ant 1.7 Hudson continues integration environment
> Reporter: Evgueni Smoliar
>
> I have 2 ant builds for the same project running in hudson build environment.
> One build is for branch="" second for branch="1.0".
> Branch information is configured in *.ivy files for this projects.
> Problem is that if this builds are started at the same time, one build takes
> a branch information from the other build.
> I don't understand how could this happened. Looks like there are some static
> configuration is set in ivy .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
