Build Agent Plugin Permissions

Hi,

I have an issue with the maven.jar that we package and let the TeamCity server update all the agents where the permissions for "mvn" is not preserved.  I know jar files don't preserve permissions but even when I make it into a maven.zip instead they aren't preserved.  What are my options here?  Can I update the agent.sh to do a chmod 755 plugins/maven/bin/mvn?  Is there a way to have these permissions preserved somehow?  If I wanted to update the agent.sh that gets pushed to all the agent boxes when TeamCity server wants to update it where is the agent.sh that gets pushed to all the agents?  When you update a plugin does it do "agent.sh stop" and "agent.sh start"?  Any help would be great.

Thanks,
Jay

3 comments
Comment actions Permalink

Hello,

Please try creading a build configuration to update permissions on agent. You may run a build configuration on all agents with custom run dialog.

I failed an issue at http://youtrack.jetbrains.net/issue/TW-15465, please vote for it.

Thanks!

0
Comment actions Permalink

Yes, I could create a builder to set this permission but how I could ensure it gets run directly after agents restart or after the TeamCity server updates the agents?

0
Comment actions Permalink

Good question. There is no such support in TeamCity. The only chance is to emulate it.

You may create dependency for it. (You may require dependency to run on the same agent)

Another workaround is to add a build step to the build configuration to patch the flag.

Another approach is to use another maven distribution with property patched files (locally on agent).
To spread the distribution amoung agents you may create a build configuration.

0

Please sign in to leave a comment.