Prevent Jazz build property from appearing in build record
Using the Jazz Ant build engine, RTC kindly keeps a record of all the properties that went into a specific build on the properties tab of the build record.
HOWEVER - I have a business sensitive property that I DON'T want to have recorded.
Specifically, the property appears in the build definition without any value. The user provides a value when they kick off the build by entering it on the Request Build screen. But I DON'T want that value to appear in the build on the properties tab.
Any chance there's an easy way to do that?
Accepted answer
http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0/topic/com.ibm.team.build.doc/topics/tcreatepasstxt.html
I'm not sure of your usage, but that is the closest thing to an encrypted value RTC offers.
~Spencer
Hi
Using the Jazz Ant build engine, RTC kindly keeps a record of all the properties that went into a specific build on the properties tab of the build record.
HOWEVER - I have a business sensitive property that I DON'T want to have recorded.
Specifically, the property appears in the build definition without any value. The user provides a value when they kick off the build by entering it on the Request Build screen. But I DON'T want that value to appear in the build on the properties tab.
Any chance there's an easy way to do that?
Comments
Thanks @spencer, but password files can only be used to help login to the jazz server - and not for anything else.
Also, I do want this value to be specified as a build property at build time. I just don't want it to appear in the build record.
One other answer
Comments
Thanks for the input Kevin.
I did consider what you suggest - but ended up not doing this as I wanted a self-serve solution for this user-base i.e. where they could easily go and set up their own builds. Forcing them to manually place files on the build machine just wouldn't work.
Although this doesn't mean it wouldn't be a good solution for other scenarios ;)
The solution I went with is to have the user enter the property in an encoded format - and have the automation scripts decode the properties.
By no means a bullet-proof solution, but it has been working pretty well.
I should add that this only works for us because the value is pretty static and doesn't change often (if at all).
Otherwise the effort of encoding it every time they wanted to change it might put them off.