We assume the user's GitHub name is OmniDev <[email protected]>.
Fork the upstream repository via github.com:
https://github.com/OmniLayer/gitian.sigs#fork-destination-box
In the Gitian building environment:
~$ git clone https://github.com/OmniDev/gitian.sigs.gitIf not already done before, import your GPG key in the Gitian building environment. Assuming the GPG private key is stored as private.key, then:
~$ gpg --allow-secret-key-import --import private.keyThe signing identity will be used to map build results to users. It is not strictly related to the GitHub username, or the GPG identity, but ideally the GitHub username is used as signing identify. To define:
~/gitian-builder$ export SIGNER=OmniDevThe release string is used to create a subdir in ../gitian.sigs. If you're building a tagged release, then ${VERSION} may already be defined. If you're building a release based on a commit, then there may be ${COMMIT}.
For tagged releases use the tag as release base string. If ${VERSION} is defined:
~/gitian-builder$ export RELEASE=${VERSION}If ${VERSION} is not defined, and assuming the release tag is 0.0.10.0-rc1, then:
~/gitian-builder$ export RELEASE=0.0.10.0-rc1For untagged releases, which are build based on a specific commit, use the base version, followed by the first 10 characters of the commit. Assuming the base version is 0.0.10.0, and first 10 characters are f95531ffec, then:
~/gitian-builder$ export RELEASE=0.0.10.0-f95531ffecAfter building Omni Core for Linux via ./bin/gbuild, but before switching to the next build target:
~/gitian-builder$ ./bin/gsign --signer ${SIGNER} --release ${RELEASE}-linux --destination ../gitian.sigs/ ../omnicore/contrib/gitian-descriptors/gitian-linux.ymlAfter building Omni Core for Windows via ./bin/gbuild:
~/gitian-builder$ ./bin/gsign --signer ${SIGNER} --release ${RELEASE}-win --destination ../gitian.sigs/ ../omnicore/contrib/gitian-descriptors/gitian-win.ymlAfter building Omni Core for OS X via ./bin/gbuild:
~/gitian-builder$ ./bin/gsign --signer ${SIGNER} --release ${RELEASE}-osx-unsigned --destination ../gitian.sigs/ ../omnicore/contrib/gitian-descriptors/gitian-osx.ymlIt is not required to stay in the Gitian environment, and build results may as well be transferred to the host machine, before continuing with the following steps.
If the Gitian environment is used, and if not done earlier, then set your GitHub username and email address, and optionally a GPG signing key:
~/$ git config --global user.name "OmniDev"
~/$ git config --global user.email [email protected]
~/$ git config --global user.signingkey ABCDEF01 # optionalIf the steps are done on the host machine (or somewhere else), redefine, or replace ${RELEASE} with the actual release tag (e.g. 0.0.10.0-rc1), and likewise the signing identity ${SIGNER} with the actual name of the signer (e.g. OmniDev).
Navigate to the gitian.sigs repository, create a new branch, and add the results via git:
~/gitian.sigs$ git checkout -b ${RELEASE}
~/gitian.sigs$ git add ${RELEASE}-linux/
~/gitian.sigs$ git add ${RELEASE}-win/
~/gitian.sigs$ git add ${RELEASE}-osx-unsigned/Commit the changes, and state the release/tag, as well as the signing entity in the commit message:
~/gitian.sigs$ git commit -m "${RELEASE} build signatures of ${SIGNER}"
# or: $ git commit -m "0.0.10.0-rc1 build signatures of OmniDev"
# or: $ git commit -SAssuming your git remote is origin, then:
~/gitian.sigs$ git push origin ${RELEASE}If another branch, other than ${RELEASE}, was used, then replace the branch name accordingly.
To publish the results, create a pull request for the master branch via github.com for:
https://github.com/OmniLayer/gitian.sigs