Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Common Build Infrastructure/Jar Signing

Draft Content
This page is currently under construction. Community members are encouraged to maintain the page, and make sure the information is accurate.

How does the Athena builder handle signing?

If the build is run in Hudson on, the Hudson user initiates the signing process from a folder within the job's workspace.

If the build is run as anyone else, the build will attempt to upload a zip of jars to be signed as some authorized user on

Here's a snippet of the buildAllHelper.xml code:

<target name="signMasterZip" if="sign">
  <antcall target="-timestamp" />
  <!-- if running as hudson, use simple path in workspace; if running commandline, connect over ssh to remote staging.priv dir -->
      <contains string="${}" substring="hudson" />
      <contains string="${user.home}" substring="hudson" />
    <property name="buildServerUser" value="" />
    <property name="signingDir" value="${writableBuildRoot}/signing" />
    <mkdir dir="${signingDir}" />
    <!-- user with write perms in staging dir & permission to run /usr/bin/sign -->
    <property name="buildServerUser" value="" />
    <property name="signingDir" value="/home/data/httpd/download-staging.priv/commonBuild" />

By default, buildServerUser is set to, but this can be overwritten in your .releng/ if you need to connect as, using your CVS userid from

Back to the top