[Suggestion] Different travis builds method at each PR

Hey !

Since pull requesting any changes makestats.py/ stats.exs run all the solutions for all the languages. I suggest to make these build independent from “already builded solutions” and only build new suggested solutions. Also make running all the solutions a possible option (when stats.py is modified for example).

My idea is to try to use destruct.github.io as a data source for ProjectEuler repo since it is hosted 24/7 and we have control of it. If destruct.github.io contains a list of solutions and configurations (as hidden frame, REST page or visible frame ( well presented for visitors too)), we can parse and make sure stats.py / stats.exs make the right job

• Building and validate news problems

• Building news solutions to already existing problems.

• Build all solutions & problems ( actual default build )

• A combination of the listed build ( sync / Async )

[A-Hilaly]

To validate the solutions the hashs is not enough? Well… an user can add too a wrong hash and this is hard to catch.

Exactly. That’s the “validation” thats worries me the most.

Of course it has drawbacks like we are supposing all previous tests are passing and only the current ones are error prone which could later stab us in the back maybe.

@lubien It is true that it can be dangerous to dare building only recent uploads/modifications. On the other hand, I totally agree that git differentials are necessary anyways to catch what was modified or added (even in my suggestion), the hosted service was more like to solve what @ryukinix said about wrong solutions (hashes). I think we all agree on using differentials now. Ill close this issue and create a new one after learning more about using git diffs.

[lubien]

I vote to close this issue and start a new one on the subject of diff-based CI builds.