dependencies - TeamCity : project parameters inheritance issue? -

-

i have teamcity 8.0.3 project multiple configs inside have common parameter (defined project parameter) : targetserverip. 1 of these configs "1 click deployment" starts others configs using snapshots dependencies. i've set parameter "prompt" ip asked on each run of configs,

problem : individually works fine, on each config run ip asked , applied config. when execute "1 clic deployment" asks ip not transmit other dependants configs (the value stays <empty>).

my question : how can set parameter applyed others configs when prompted ?

ps : i've tried set env. parameter not helps.

ps2 : using templates not seems solution me.

there 2 problems. 1 can with, one trying solve myself solved myself.

your problem how setup chain. 1 click deployment "depends" on others.

it cannot pass parameters other builds.
can use parameters dependent builds dep.dependent_build_configuration.paramter_name.

the fix

there 2 things have do.

  1. setup artifact dependencies
  2. setup triggers

build a

- parameters

globalparameter

  • display: normal
  • type: text
  • allowed value: not empty

build b

- parameters

localparameter

  • display: hidden
  • type: text
  • value %dep.build_a_globalparemeter%

- snapshot dependency

  • depends on: "build a"

- triggers

  • triggertype: finish build trigger
  • build configuration: build a

how works

the artifact dependency makes variables available via %dep.build_a.globalparameter% syntax. finish build trigger causes build a trigger build b. have access parameters because saved previous build.


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

c++ - Clear the memory after returning a vector in a function -

-
i have function processes , stores lot of data in , returns results vector of class. amount of data stored in function tremendous , want clear storage memory of function after finished job. necessary (does function automatically clear memory) or should clear memory function? update: vector<customers> process(char* const *filename, vector<int> id) { vector<customers> list_of_customers; (perform actions) return list_of_customers; } variables defined locally within function automatically released @ end of function scope. destructors objects called, should free memory allocated objects (if objects coded correctly). example of such object std::vector . anything you've allocated new must have corresponding delete release storage. try avoid doing own allocation , use raii instead, i.e. containers or smart pointers.
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more