Details
Details
- Reviewers
deadalnix Fabien - Group Reviewers
Restricted Project - Commits
- rSTAGINGcbc12967970f: Added build-secp256k1.sh for running secp tests in TeamCity
rABCcbc12967970f: Added build-secp256k1.sh for running secp tests in TeamCity
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- teamcity-jni-support
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 5214 Build 8491: Bitcoin ABC Buildbot (legacy) Build 8490: arc lint + arc unit
Event Timeline
contrib/teamcity/build-secp256k1.sh | ||
---|---|---|
8 | Why? |
contrib/teamcity/build-secp256k1.sh | ||
---|---|---|
8 | Dunno. This was just copied from build.sh |
contrib/teamcity/build-secp256k1.sh | ||
---|---|---|
8 | Shammah @jasonbcox answer to your question is when the git repo is stripped in transfer. (E.g. when rsyncing it to a remote machine to build, or server side checkout (vs agent checkout)) Or if you download a zip of the source Jason Cox so for running locally, right? I dont think teamcity would ever have hit this path Shammah If agent checkout is turned off it will. It checks out the code on the master node and only transfers the source to the build environment. Without ssh keys or the git metadata. |
contrib/teamcity/build-secp256k1.sh | ||
---|---|---|
1 ↗ | (On Diff #7766) | #!/usr/bin/env bash ? |
contrib/teamcity/build-secp256k1.sh | ||
---|---|---|
1 ↗ | (On Diff #7766) | I haven't tested this on the TeamCity agents. a future diff maybe |