[wildfly-dev] Timeout errors in JCA bits in testsuite

[Kabir Khan]

The snapshot is local to the build.
On one machine when a core PR is opened:
1) It builds the core snapshot
2) It runs the main build using the snapshot from 1)

The snapshot is not deployed anywhere, and AFAIK removed from the repository when the next build happens.
> On 29 Jan 2016, at 08:02, Carlo de Wolf <cdewolf at redhat.com> wrote:
> 
> I'm not saying, do not use snapshots. I'm saying do not use SNAPSHOT. :-)
> 
> Clearly the path is a shared one, so the build must use timed snapshots or risk interference.
> 
> Carlo
> 
> On 01/28/2016 12:54 PM, Tomaž Cerar wrote:
>> 
>> On Thu, Jan 28, 2016 at 9:58 AM, Carlo de Wolf <cdewolf at redhat.com> wrote:
>> There should be no SNAPSHOT dependencies in any CI build. While it does build core beforehand, it might get overwritten by another CI run.
>> [org.wildfly.core:wildfly-core-parent] [INFO] Installing /opt/buildAgent/work/db872761b443af46/core/pom.xml to /store/repository/org/wildfly/core/wildfly-core-parent/2.0.8.Final-SNAPSHOT/wildfly-core-parent-2.0.8.Final-SNAPSHOT.pom
>> 
>> Would it be possible to use timed snapshots instead?
>> 
>> 
>> As Stuart said, whole point of this builds is to have snapshot builds.
>> Same build agent first builds core (clean install) and than builds full
>> with -Dversion.wildfly.core=<version of wildfly core previousily built>
>> 
>> snapshot used here are only build agent local, not publish on some outside nexus repository.
>> 
>> --
>> tomaz
>> 
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev