summary refs log tree commit diff stats
path: root/lib/pure/parsesql.nim
Commit message (Expand)AuthorAgeFilesLines
* lib: Trim .nim files trailing whitespaceAdam Strzelecki2015-09-041-109/+109
* renamed writeln to writeLine in libpatrick dw2015-06-191-1/+1
* Don't run non-test code when defined(testing)Oleh Prypin2015-04-211-1/+1
* several modules changedAraq2014-08-281-63/+63
* big renameAraq2014-08-271-75/+80
* fixes #993Araq2014-03-131-1/+1
* stdlib compiles mostly without warnings againAraq2014-02-061-3/+3
* Removes executable bit for text files.Grzegorz Adam Hankiewicz2013-03-161-0/+0
* cleanup: E_Base should not be used for inheriting exceptions; documentation g...Araq2011-01-151-1/+1
* fixed pango/pangoutils new wrappersAndreas Rumpf2010-02-261-0/+0
* continued work on html/xmlparserrumpf_a@web.de2010-02-141-0/+0
* implemented multi methodsAndreas Rumpf2009-09-231-19/+30
* added tools and web dirsAndreas Rumpf2009-09-151-0/+1
* version0.7.10Andreas Rumpf2009-06-081-0/+1333
.highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */
Publishing build artifacts and logs.
================================================================================
There are many ways you can publish artifacts, both privately and publically.

Methods include:
Sending logs/artifacts through e-mail.
Uploading logs/artifacts to an FTP server.
Uploading logs/artifacts to an rsync server.
Uploading it through good ol HTTP.

Basically, if there's a commandline utility for it, you can use it in the
post/failed.sh scripts. Refer to variables.txt for how to use variables for
organizing artifacts.