Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Is there nothing to automate? </p> </blockquote> <p>Not really. All but two of the examples are one-line commands. </p> <p><strong>tl;dr</strong> Very little of this is really interesting or complex. Very little of this seems to benefit from "automation". </p> <p>Due to documentation, I don't have to remember the commands to do this.</p> <blockquote> <p>Do most programmers prefer to run stylechecks, tests, etc. manually?</p> </blockquote> <p>Yes.</p> <blockquote> <p>generation documentation, the docs task calls sphinx with the appropiate arguments</p> </blockquote> <p>It's one line of code. Automation doesn't help much. <code>sphinx-build -b html source build/html</code>. That's a script. Written in Python.</p> <p>We do this rarely. A few times a week. After "significant" changes.</p> <blockquote> <p>running stylechecks (Pylint, Pyflakes and the pep8-cmdtool). check calls the pep8 and pylint commandlinetools</p> </blockquote> <p>We don't do this. We use unit testing instead of pylint. You could automate that three-step process. </p> <p><strong>But I can see how SCons or make might help someone here.</strong></p> <blockquote> <p>tests</p> </blockquote> <p>There might be space for "automation" here. It's two lines: the non-Django unit tests (<code>python test/main.py</code>) and the Django tests. (<code>manage.py test</code>). Automation could be applied to run both lines. </p> <p>We do this dozens of times each day. We never knew we needed "automation".</p> <blockquote> <p>dependecies sets up a virtualenv and installs the dependencies</p> </blockquote> <p>Done so rarely that a simple list of steps is all that we've ever needed. We track our dependencies very, very carefully, so there are never any surprises. </p> <p>We don't do this.</p> <blockquote> <p>the test task depends on dependencies enables the virtualenv, starts selenium-server for the integration tests, and calls nosetest</p> </blockquote> <p>The <code>start server &amp; run nosetest</code> as a two-step "automation" makes some sense. It saves you from entering the two shell commands to run both steps.</p> <blockquote> <p>the coffeescript task compiles all coffeescripts to minified javascript</p> </blockquote> <p>This is something that's very rare for us. I suppose it's a good example of something to be automated. Automating the one-line script could be helpful.</p> <p><strong>I can see how SCons or make might help someone here.</strong></p> <blockquote> <p>the runserver task depends on dependencies and coffeescript</p> </blockquote> <p>Except. The dependencies change so rarely, that this seems like overkill. I supposed it can be a good idea of you're not tracking dependencies well in the first place.</p> <blockquote> <p>the deploy task depends on check and test and deploys the project.</p> </blockquote> <p>It's an <code>svn co</code> and <code>python setup.py install</code> on the server, followed by a bunch of customer-specific copies from the subversion area to the customer <code>/www</code> area. That's a script. Written in Python. </p> <p>It's not a general make or SCons kind of thing. It has only one actor (a sysadmin) and one use case. We wouldn't ever mingle deployment with other development, QA or test tasks.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload