I have an Artifact path like the following:
%system.teamcity.build.workingDir%\Presentation\obj\Release\Package=>Package.zip
But I need to exclude a folder from "Package", I´ve tried things like:
%system.teamcity.build.workingDir%\Presentation\obj\Release\Package
-:%system.teamcity.build.workingDir%\Presentation\obj\Release\Package\PackageTmp
-:Package\PackageTmp
But nothing seems to work, any ideas ?
Greetings.
Exclusion patterns are not supported yet for artifact paths. There is an issue in TeamCity tracker requesting this functionality. Please watch/vote.
Additionally, there is this workaround. Have a look, if it fits your needs
Related
Basically I want to exclude cache folders and files from Crashplan backups using their regex exclusions and create other exclusions based on the solution to this.
Files like these:
C:\Users\username\AppData\Local\Microsoft\Windows\Explorer\iconcache_16.db
C:\Users\username\AppData\Local\Spotify\Browser\ChromeDWriteFontCache
and folders like these
C:\Users\username\AppData\Roaming\LibreOffice\4\user\uno_packages\cache
C:\Users\username\AppData\Local\Google\Chrome\User Data\Default\Pepper Data\Shockwave Flash\CacheWritableAdobeRoot\AssetCache
This is what I came up with using Crashplans basic instructions and no real regex knowledge:
(?i)/AppData/.*/*cache*/*.*
It doesn't seem to do the trick however, I'm guessing I'm missing something with the subfolders.
This works fine for specific folders I want something that covers multiple ones:
.*/AppData/Local/Google/Chrome/User Data/Default/Media Cache/.*
Can anyone nudge me in the right direction so it can check in any and all subfolders?
Try the following:
(?i)\/AppData\/.*?cache.*?$
I'm looking at using Mercurial for version control in a project, and was hoping you stackers could help me out with the regex, so that the .hgignore isn't a disgusting GLOB-by mess.
The big ignore directories are easy, however keeping certain sub-folders tracked has me stumped.
Here's the list of what I (believe) need INCLUDED for coding purposes.
Development/Src/OurGame
Development/Src/<all files in this directory, but not subfolders>
UDKGame/Config/DefaultGame.ini
UDKGame/Config/DefaultEngine.ini
If only there was the option for a .hginclude rather than .hgignore...
You could ignore everything and then use hg add to add the specific files that you want. The .hgignore file is only used to ignore things that haven't already been added to the repository.
Other than that, you do need to specify the files to ignore so I don't think that people could help you with this question without know what the files are that you don't want to track.
I have a simple build definition which I want to use to build just one project, and every time I choose to run this build, I want to get latest from the branch/directories that pertain only to the project in question. How do I do that? The call to "Get Workspace" gets everything from source control, and I do not want to (or need to, for that matter) get latest from everything for various reasons.
I hope I am not asking for much.
Thanks in advance.
Check the workspace mapping in the build definition. The build only gets the items that you have specified over there. If you want to exclude some folders within the path that you are mapping, you can choose to cloak some folders.
You can adjust your ItemsToBuild in Process Tab in Required section
I need to apply xdt transformations to other files than *.config ones.
I found the SlowCeetah extension which seems to provide this kind of feature as authors and extension page says, but, even if I setup the trasformation for xml files, and note that the
preview tool works well.., according to solution configuration manager configuratoins, no
transformation is applied.
For example I setup the trasformation for log4net.xml file, by using the tooling command "Add Transformation" which added log4net.{configname}.xml files but nothing happen when I deploy the solution or simply build with the specific build configuration.
Anyone has seen this issue?
Googlin' around I found that trasnformations to xml files should be applied to files setup as Content and Copy Always, anyone has suggestion about that?
I 'm very sad becaues I made all my configurations with transformations, and if I cannot solve that issue I lost 2 days of boring config job and I just can do that manually
Thanks in advance
Cheers
I am currently developing/hacking an image analyzing/transforming tool.
The filters therein will be loaded at runtime using dlopen&co.
My question is where do *nix tools usually put plugins (*.so files) when installed?
bin/program
lib/program/plugins/thisandthat.so
maybe?
Secondly how do I use it and where do I put it during development without installing it. (this is probably the tricky part)
I want to avoid shell-scripts if possible.
thanks in regard
Ronny
Usually /usr/lib/programmname should be a good spot
During development I'd create a command line paramter to specify the plugin search path and just leave the plugins in the build-dir for example.
Consider:
/usr/lib/program/*.so
A good guide for choosing is Filesystem Hierarchy Standard.
Most Linux distribuitions use this standard.
Here is a very short summary.
Place application binary in:
/usr/bin/progname, /usr/local/bin/progname or /opt/progname
Place plugins or library files in:
/usr/lib/progname, /usr/local/lib/progname or /opt/progname/lib
Place host configuration for the application in:
/etc/progname or /etc/opt/progname
Place user configuration in:
$HOME/.progname
Place application manual page in:
/usr/shar/man/man1/
There is separate hierachy for /var. As an example use /var/log/progname for logging.
In responce to caf's comment. I find it very usefull to choose target directory at compile time. Using a $PREFIX also makes it easy to separate devellopment build's from shippment.
Most use /usr/progname, /usr/lib/progname and /etc/progname
Do not forget:
$HOME/.program/
The layout seems sensible. You can, for instance, look in current directory, look up environment variable or command line switch during development. It depends on the details of your development environment and workflow.