Appropriate place to store custom properties in Jenkins `config.xml` -


i'm programmatically generating jenkins config.xml job configuration files, , store/attach metadata xml dom, ignored jenkins, not removed or marked "obsolete data". simple key/value pairs, things client tool build date, user, etc.

where in xml structure appropriate put such thing? i've tried putting under /project/properties branch, data gets culled server when post new job. or there plugin allow (i tried metadata plugin, overwrote sections)?

update: spoke quickly! job config updates after post, gets pruned on next jenkins build.

for still wondering this, able add custom properties under root <project> tag post'ing updated config.xml. looked this:

<project> ...     <mycustomtag>         <customprop>foo</customprop>     </mycustomtag> ... </project> 

i combined of custom properties under 1 custom tag separate them rest of config , avoid accidental name collisions regular config props.

jenkins version 2.0


Comments

Popular posts from this blog

Fail to load namespace Spring Security http://www.springframework.org/security/tags -

sql - MySQL query optimization using coalesce -

unity3d - Unity local avoidance in user created world -