aboutsummaryrefslogtreecommitdiffstats
path: root/appveyor.yml
Commit message (Collapse)AuthorAgeFilesLines
* AppVeyor: build only pushes to master and develop branchPaweł Bylica2016-10-201-0/+4
| | | | This fixes the issue when PRs from a branch in main repo are built twice.
* fix yml scriptDimitry2016-09-011-1/+0
|
* soltest on windowsDimitry2016-08-311-6/+13
|
* Confirmed that ZIPs work for Solidity.Bob Summerwill2016-08-161-1/+1
| | | | Switching whitelisting back to 'release' branch for TravisCI and Appveyor.
* Flipped solidity whitelisting to develop, to check ZIP workflow is OK.Bob Summerwill2016-08-161-1/+1
|
* Disable AppVeyorBot commentsDenton Liu2016-08-161-0/+6
|
* Merge pull request #837 from chriseth/testsuitecleanupchriseth2016-08-121-1/+1
|\ | | | | Cleanup of test runner.
| * Move custom test options to after --chriseth2016-08-121-1/+1
| |
* | Flip whitelisting to release branch.Bob Summerwill2016-08-121-1/+1
|/
* Flipped back to whitelisting develop, and attempting to fix conditional.Bob Summerwill2016-08-121-1/+1
|
* Switched whitelisting to 'release' branch for Appveyor and TravisCI.Bob Summerwill2016-08-121-5/+1
| | | | | Disabled auto-tagging. We will create our own tags manually now, and for the release branch, this act should auto-generate ZIPs.
* Publish releases for develop branch.chriseth2016-08-121-2/+2
|
* New appveyor key.chriseth2016-08-121-1/+1
|
* Flip whitelisting back to 'release' branch.Bob Summerwill2016-08-121-1/+1
| | | | | | | Also, it looks like my auth token is no good. Christian will likely have to create one for it to work. I that he has super-powers for solidity which I do not. I believe I am a full admin for cpp-ethereum, though, so should be able to generate working auth tokens for that.
* Added comments about 'auth_token' setup for Appveyor.Bob Summerwill2016-08-121-1/+10
| | | | | Switched the white-listed branch to 'develop', so we can dry-run the Windows ZIP generation here. On success, will then delete those artifacts and switch the whitelisting back to 'release', pending creation of a release branch for the solidity repo.
* Re-add the ZIP release flow for Solidity.Bob Summerwill2016-08-111-20/+22
| | | | | | It is all within conditionals such that it only works for 'release'. Just want to start on getting it re-enabled. Also disabled the Appveyor cache, because it is unreliable.
* Re-enabled Appveyor cache.Bob Summerwill2016-08-031-0/+1
|
* OK - Looks like Appveyor softest automation still needs more work before it ↵Bob Summerwill2016-08-031-6/+6
| | | | is ready to do.
* Clear Appveyor cache.Bob Summerwill2016-08-031-2/+1
|
* Re-enable code builds for Solidity unit-tests within Appveyor.Bob Summerwill2016-08-031-1/+1
|
* Let's try Windows Tests-over-IPC and see where we are at.Bob Summerwill2016-08-031-7/+7
| | | | | Will tweak-to-work or drop it back-out. In the absence of working Appveyor PRs, I'm having to do this a bit ugly.
* Make the Solidity repository standalone.Bob Summerwill2016-08-011-0/+76
This commit is the culmination of several months of work to decouple Solidity from the webthree-umbrella so that it can be developed in parallel with cpp-ethereum (the Ethereum C++ runtime) and so that even for the Solidity unit-tests there is no hard-dependency onto the C++ runtime. The Tests-over-IPC refactoring was a major step in the same process which was already committed. This commit contains the following changes: - A subset of the CMake functionality in webthree-helpers was extracted and tailored for Solidity into ./cmake. Further cleanup is certainly possible. - A subset of the libdevcore functionality in libweb3core was extracted and tailored for Solidity into ./libdevcore. Further cleanup is certainly possible - The gas price constants in EVMSchedule were orphaned into libevmasm. - Some other refactorings and cleanups were made to sever unnecessary EVM dependencies in the Solidity unit-tests. - TravisCI and Appveyor support was added, covering builds and running of the unit-tests (Linux and macOS only for now) - A bug-fix was made to get the Tests-over-IPC running on macOS. - There are still reliability issues in the unit-tests, which need immediate attention. The Travis build has been flipped to run the unit-tests 5 times, to try to flush these out. - The Emscripten automation which was previously in webthree-umbrella was merged into the TravisCI automation here. - The development ZIP deployment step has been commented out, but we will want to read that ONLY for release branch. Further iteration on these changes will definitely be needed, but I feel these have got to sufficient maturity than holding them back further isn't winning us anything. It is go time :-)