Skip to content
This repository has been archived by the owner on Aug 4, 2020. It is now read-only.

Setup Travis-CI #66

Open
mvrozanti opened this issue Jun 12, 2019 · 2 comments
Open

Setup Travis-CI #66

mvrozanti opened this issue Jun 12, 2019 · 2 comments
Labels

Comments

@mvrozanti
Copy link
Owner

mvrozanti commented Jun 12, 2019

Due to the recent long push intervals and version-specific failures, I suggest we setup Travis-CI to check which Windows versions are passing and whatnot.

The first step would be to introduce a valid .travis.yml with at least one Windows 7 build on it.

@mvrozanti mvrozanti added enhancement needs testing Test before continuing labels Jun 12, 2019
@mvrozanti
Copy link
Owner Author

🙄

Worker information
hostname: 65d6aa86-70da-402c-921e-723c7b51dc40@1.production-1-worker-org-gce-l0f1
version: v6.2.0 https://github.com/travis-ci/worker/tree/5e5476e01646095f48eec13196fdb3faf8f5cbf7
instance: travis-job-3c646ba7-ebf8-4e62-9e76-9706ed175cbc travis-ci-onion-1803-containers-1542208204-ad01dca (via amqp)
startup: 1m25.157840957s
Secret environment variables are not obfuscated on Windows, please refer to our documentation: https://docs.travis-ci.com/user/best-practices-security
The language 'python' is currently unsupported on the Windows Build Environment.
Let us know if you'd like to see it: https://travis-ci.community/c/environments/windows. Thanks for understanding!

@mvrozanti
Copy link
Owner Author

No problem though, thanks to this badass

Soon I will be adding an obfuscated key so we can actually send/receive messages to test stuff out.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant