VCS Triggering based on wildcards

VCS Triggering has properties
"Do not trigger build if all changed file names match any of the following wildcards:"

but i need to trigger when file name match wildcards

for description:
application dependant on sql database and vcs stores sql script to create structure
also build script to execute it
but i don't want to recreate database on any checkin - only when scripts modified

i think that triggering based on wildcards is most suitable for me - but maybe any other solution?

3 comments

Hello,

The solution I can suggest is to create new Project and configure its VCS root to checkout only the files needed for database recreation (if they are located under single directory).

You can watch/vote for a similar issue in our tracker: http://www.jetbrains.net/jira/browse/TW-2813

I hope TeamCity 3.0 with its per- Build Configuration VCS roots will allow more flexibilities with this ;)

--
Best regards,

Yegor Yarko
Quality Assurance Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

yes - for now i make things work in the same style - but that scenario has the following problem: imagine somebody changed the script, build on create database successfully done, but in truth the integration crashed - and application can't work with this new database, and for this event problems will not be detected - because integration tests from application didn't trigger by this build. Ok, this problem can be resolved in different ways, 1) include integration tests in script (smaller number of check-ins, but still bloat) 2) include scripts VCS update in main project - may be suitable, but i don't find feature to define project (not configuration) build sequence/dependency - to ensure that first will be database creation 3) use this exclude tool - and exclude all paths that not rely to database creation scripts - my repository structure in practice allow me to do this - only five or six wildcards, but.... so - i think include tool is pretty much the same as exclude and can be easily added. ..or my previous thoughts that teamcity give me ability not to maintain big custom build script structure are mistaken and i must select from create sophisticated scripts (and went back to cruisecontrol ;)) or say everybody that when they modified database scripts they must run build by hand (in 2nd resolve scenario)

0

yes - for now i make things work in the same style - but that scenario has the following problem: imagine somebody changed the script, build on create database successfully done, but in truth the integration crashed - and application can't work with this new database, and for this event problems will not be detected - because integration tests from application didn't trigger by this build. Ok, this problem can be resolved in different ways,
1) include integration tests in script (smaller number of check-ins, but still bloat)
2) include scripts VCS update in main project - may be suitable, but i don't find feature to define project (not configuration) build sequence/dependency - to ensure that first will be database creation
3) use this exclude tool - and exclude all paths that not rely to database creation scripts - my repository structure in practice allow me to do this - only five or six wildcards, but....
so - i think include tool is pretty much the same as exclude and can be easily added. ..or my previous thoughts that teamcity give me ability not to maintain big custom build script structure are mistaken and i must select from create sophisticated scripts (and went back to cruisecontrol ;)) or say everybody that when they modified database scripts they must run build by hand (in 2nd resolve scenario)

Message was edited by:
vansickle

0

Please sign in to leave a comment.