Project and System Level Variables?

Hi,

Is it possible to set custom project and system level variables.  I would like to set say and output directory and have all the configurations look for that.  If I set a System Property or Environmental Variable for a configuration, I can see it there but I do not seem to have access to it using the %dep.<buildID>% syntax.    

I found that if I put the variable in the configuration name, I can then reference it from other configurations, but that more configurations to projects that are already big.  

In addition to project level variables, it is possible to set custom system system wide variables?

Thanks,
John

8 comments
Comment actions Permalink

You can set agent-wide variables.
http://confluence.jetbrains.net/display/TCD6/Build+Agent+Configuration

Not sure about project-wide.

0
Comment actions Permalink

Hi,

Thanks for the response.  I'm actually looking for the opposite of that.  I would like to set a variable server side and have it pushed down to the configurations and agents.

0
Comment actions Permalink

I don' think I follow...

Variables defined by the method I described are already availble on the agents on build configurations.
Can you explain your use case a bit more?

0
Comment actions Permalink

Hi,

I am building using the command line because we are building for embedded devices.  I have several hundred libraries we need to build once they are built, executables are built that link to the libraries.  To do this, I check out the sources to a central network share.  At this point, agents run on several different machines and start building the libraries saving them to the central location, this way, when the executable is built, the libraries are available.

I'm looking for a way to make the path to the central share dynamic.  That way, if it ever changes, I can just update it in one place.

Thanks,
John

0
Comment actions Permalink

In my org, we check in the libraries back to version control once they are built. They are also labeled.
Executables pull the libraries from the version control via the label as a prep step, then starts the build.

I like this method because we get to loosen the coupling between the libraries and the executables.
This means that, IF the libraries fail to build for some reason, we can still make patches to the executables and release them since there are stable versions of the libraries available on the source control.

0
Comment actions Permalink

Hi John

We've added project-wide parameters in upcomming 6.5 version
Capture.PNG

But let me ask you.
Usually we recommend to isolate build agents - each agent has its own copy of source files, and publishes build artifacts to a central repository on TeamCity server. Later  these artifacts can be reused in other build configurations.
What kind of issues have you met with this approach?

Thanks
Michael

0
Comment actions Permalink

Hi,

I would like to discuss this more, but I do not want to post the specifics of our build process in a public forum.  Do you have an address where I can reach you directly?  I looked on the forums and I did not see a way to send you a private message.

Thanks,
John

0
Comment actions Permalink

Hi John

For paid customers we provide private email support at teamcity-feedback@jetbrains.com.

Michael

0

Please sign in to leave a comment.