Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are some artifacts/information that I'm used to keep at each build:</p> <ul> <li>The tag name of the snapshot you are building (tag and do a clean checkout <strong>before</strong> you build)</li> <li>The build scripts themselfs or their version number (if you treat them as a separate project with its own version control)</li> <li>The output of the build script: logs and final product</li> <li>A snapshot of your environment: <ul> <li>compiler version</li> <li>build tool version</li> <li>libraries and dll/libs versions</li> <li>database version (client &amp; server)</li> <li>ide version</li> <li>script interpreter version</li> <li>OS version</li> <li>source control version (client and server)</li> <li>versions of other tools used in the process and everything else that <strong>might</strong> influence the content of your build products. I usually do this with a script that queries all this information and logs it to a text file that should be stored with the other build artifacts.</li> </ul></li> </ul> <p>Ask yourself this question: "if something destroys entirely my build/development environment what information would I need to create a new one so I can redo my build #6547 and end up with the exact same result I got the first time?"</p> <p>Your answer is what you should keep at each build and it will be a subset or superset of the things I already mentioned.</p> <p>You can store everything in your SCM (I'd recommend a separate repository), but in this case your question on how long you should keep the items looses sense. Or you should store it to zipped folders or burn a cd/dvd with the build result and artifacts. Whatever you choose, have a backup copy.</p> <p>You should store them as long as you might need them. How long, will depend on your development team pace and your release cycle.</p> <p>And no, I don't think it changes if you do continous integration.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat artifacts to save for a nightly build?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser16120
    1. USuser16120
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat artifacts to save for a nightly build?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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