It's all about the answers!

Ask a question

Personal Build in RTC EE dependency based builds


Dennis Behm (3821114) | asked Apr 24 '15, 2:07 a.m.
Developers usually don't want to set the uss load dir and the high level qualifier manually; in some cases they even should not be allowed to set it (for example set the personal build hlq to the team build hlq).

Regarding the fetchdestination in uss (team.enterprise.scm.fetchDestination) I see a solution, defining the variable on the build agent defintion.
Any hint how to predefine the HLQ (team.enterprise.scm.resourcePrefix)? An option to overwrite it during the personal bulid request would also be sufficient.

On the build request dialog bot fields are required for personal builds.

Thanks,
Dennis

Comments
Jorge Diaz commented Apr 24 '15, 1:05 p.m.
JAZZ DEVELOPER

Hi Dennis,
could you further elaborate the scenario? What would be the predefined value? And also, when it comes to your description that developers don't want to set these values,, they are remembered for subsequent requests, so I wonder what is that you are trying to achieve here.
Regards,
Jorge.


Dennis Behm commented May 07 '15, 3:04 a.m.

Hi Jorge,

the scenario has some preconditions - we use an technical user for the build agent (magic login) and do not impersonate the use build request.

For the USS directory we use a variable uss.work.build; we set the value at the build engine level to:
uss.work.build == /var/rtc/work/dev/build/${buildDefinitionId}
On the build definition we set
team.enterprise.scm.fetchDestination == ${uss.work.build}

So here is a resolved sample:
team.enterprise.scm.fetchDestination=/var/rtc/work/dev/build/OurRelease/

Additionally we use a build engine for personal use, which adds the ${buildRequesterUserId} to the path.

Regards,
Dennis

Be the first one to answer this question!


Register or to post your answer.