'deploying' onw files to agents

Hi there,

our agents always need some extra files to perform a build, for instance:
- a special 'master'-ant-buildfile
- a 1.5jre + 1.4 jre
- a CVSNT-client, because they check out some additional dependencies for a build.

Is there a possibility to use the automatic agent-update to move such files to each agent ?
I tried to put my files into the
/webapps/ROOT/update/buildAgent.zip
but it doesn't seem to be resend to the agents.

Putting the files to
/webapps/ROOT/plugins indeed triggers an agent update, but of course 'just' puts them into the 'plugin' dir on the agent-side.
I'd prefer having them in the root dir of an agent - is there a way to archieve this ?

4 comments

And a second question turns up:
is there an automatic property giving me the build-agent install dir ? My agents show an environment property '=C:' telling the path to the agent-bin dir ... just the name of this property seems a bit strange ?

0

Stefan,

As you've discovered, agent support automatic upgrades for content under "plugin" directory. There is no possibility to install something into directories below agent's home using the agent's upgrade process.

As installing applications can require more then just unpacking into a directory, but also running script or some other procedures, I believe that the support for the feature should be implemented separately from agent upgrade.
You can vote/comment on the corresponding issue in our tracker: http://www.jetbrains.net/jira/browse/TW-3478

For the time being you can create a build that will install the software on the agent it is run on. The tricky point here is scheduling the build on all the necessary agents. This can be done either manually, via custom plugin or via running the builds via GET requests (see http://www.jetbrains.net/confluence/x/pHI for more info).

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Stefan,

Try using "agent.home.dir" property in the build script (Ant or NAnt), or adding an environment property to the build configuration and setting it to %system.agent.home.dir%

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Yegor,

could you be a bit more specific ?

I did deploy all needed extra files now via the plugins-directoy, this works fine and in the meantime I got used to having all important files in the plugin-directory of each agent.

Now when editing a build-plan I can use the following as JDK-location:
%env.=C:%/../plugins/jdk1.5.0_12_patched

I do the same for location of build-file and ant. With such a string installing a new agent works out of the box - I didn't ever had to configure this strange property '=C:' that points to the agents-bin directory.

Using:
%system.agent.home.dir%/plugins/jdk1.5.0_12_patched
(which looks a lot better) doesn't help because now the build says, that it can't find a suitable agent.

I know that I could define that property somehow for each agent, but that would make installing a new agent more complicated (ok - not too much, but I want to eliminate each unnessecary step besides running the build-agent-installer)

0

Please sign in to leave a comment.