github.com/sercand/please@v13.4.0+incompatible/docs/index.html (about) 1 2 <div class="index-corner"> </div> 3 4 <p class="index-open"><span class="turquoise">Please</span> supports a number of popular 5 languages and can automate nearly any aspect of your build process. 6 </p> 7 8 <div class="index-layout"> 9 <div> 10 <div> 11 <img src="images/triangle_v.png" class="smol r90"> 12 <h2><span class="violet">Speed up your builds.</span></h2> 13 <p>Please is designed to parallelise builds & tests to make the most of your CPU. 14 It's written in Go so it's fast & efficient itself, and it can build just the required 15 parts of your code on each invocation.</p> 16 </div> 17 <div> 18 <img src="images/square_g.png" class="smol"> 19 <h2><span class="green">Help your deployment.</span></h2> 20 <p>All your code & dependencies get packed into a single file which can easily be 21 deployed & run on a server. This helps deploy languages like Python which don't 22 do this naturally.</p> 23 </div> 24 </div> 25 <div> 26 <div> 27 <img src="images/square_y.png" class="smol r45"> 28 <h2><span class="yellow">Unify your build process.</span></h2> 29 <p>Because Please can build many languages already (and you can easily write rules 30 to teach it about others) you always invoke one tool to build any language or run 31 any test, simplifying your continuous integration and development processes.</p> 32 </div> 33 <div> 34 <img src="images/hexagon_r.png" class="smol"> 35 <h2><span class="red">Continuous integration & pre-merge testing.</span></h2> 36 <p>We've developed Please in tandem with our internal integration tools, so whenever 37 any of our engineers merges a pull request, we invoke it to make sure any affected 38 tests are passing before merging it in. Because Please allows fine-grained dependencies 39 and knows them for every test, we can run just the affected ones to keep this step 40 fast & lightweight.</p> 41 </div> 42 </div> 43 <div> 44 <div> 45 <img src="images/circle_t.png" class="smol"> 46 <h2><span class="turquoise">Isolate your tests.</span></h2> 47 <p>Got integration tests that need to spin up servers, write files, and find ports? 48 No problem, by setting a flag on the test they can be run inside a Docker container 49 to keep them from clashing with one another.</p> 50 </div> 51 <div> 52 </div> 53 </div> 54 </div>