> Just committing, watching for > errors in the seed job and fixing them isn't very problematic. The > existing jobs are not touched, if the DSL does not parse correctly, and > the errors are usually pretty clear where the issue might be. Just do it > in prod, once it looks about what we want. ;)
Done. Looks good so far. `Cassandra-2.2-artifacts` has been failing for a while, so a manual rebuild there generated the following email: https://lists.apache.org/thread.html/7ad7f05786189117ac3fcf62a4b2a6eecd1dcc7f2ce03ca0f126d84f@%3Cbuilds.cassandra.apache.org%3E (The Cassandra-2.2-artifacts job is failing because of more eclipse-warnings…) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
