The problem is that ~/fab/dse_builds/dse-{revision} is never cleaned up and so if a a build of the same revision is triggered (but the revision contains updated files), we end up potentially with multiple cassandra jar files in ~/fab/dse_builds/dse-{revision}/resources/cassandra/lib. The easiest way is to just remove ~/fab/dse_builds/dse-{revision} before the run, since a couple of codelines later, the tarball will be extracted anyway
The problem is that
~/fab/dse_builds/dse-{revision}is never cleaned up and so if a a build of the same revision is triggered (but the revision contains updated files), we end up potentially with multiple cassandra jar files in~/fab/dse_builds/dse-{revision}/resources/cassandra/lib. The easiest way is to just remove~/fab/dse_builds/dse-{revision}before the run, since a couple of codelines later, the tarball will be extracted anyway@aboudreault can you review please?