Community
Participate
Working Groups
Long ago, when we stated, like ... 5, 6 years ago? ... we had to do signing from our build id (wtpBuild) by using SSH to "send over" to a real committer id. This worked fine as long as only one person used 'wtpBuild' but is less than ideal when multiple people use wtpBuild, as it is intended. In recent years, since hudsonBuild is used for so much, the webmasters have a system to allow "build ids" to do signing ... not sure if its based on ID, or GROUP, but ... they are going to set up our signing directory soon to allow this. At that time, we need to modify our build scripts to remove 'david_williams' (and, david_williams needs to modify his SSH authorized keys file :)
The kind webmaster have worked their magic to allow 'wtpBuild' to sign, now, which I've tested "manually". So, all that's left is the little issue of changing our scripts. I'll try that later today, after our M build is complete.
> I'll try that later today, after our M build is complete. Status: the new script appears to work. I did have to stop the cc build process, and restart it, before the system could "see" that wtpBuild had permission to execute 'sign'. Still some cleanup required to script, and, we'll have to get this new signing script into maintenance branch, and, eventually patch builds too. (Those are a little more tricky, since for old patch builds, the builder is (often) branched, rather then "use latest" version, as we use for head and maintenance builds).
mass change back to default assignee and qa contact. I'm not saying I won't work on some :) ... but, won't be all ... so, I think defaults would be best to start over.
