Skip to content

Adding Travis CI config #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Sep 28, 2017
Merged

Adding Travis CI config #16

merged 9 commits into from
Sep 28, 2017

Conversation

mattsb42-aws
Copy link
Member

Adding Travis CI config, adding badges to readme, and updating integration test configuration methodology from config file to environment variables (primarily to simplify in running integration tests in Travis).

@mattsb42-aws
Copy link
Member Author

Travis blocks secure environment variables in builds for pull requests from forked repositories. We'll need to decide how we want to handle that so that integration tests can pass but we're not opening ourselves to security issues.

Latest build from my fork:
https://travis-ci.org/mattsb42-aws/aws-encryption-sdk-python/builds/278062847

@mattsb42-aws
Copy link
Member Author

Per offline discussion, I disabled integration tests in Travis until we have a story on how we want to handle credentials for them.

Copy link
Contributor

@lizroth lizroth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, couple little things

env: TOXENV=doc8
- python: 3.6
env: TOXENV=readme
# pending reorg of deserialize_header
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed, flag this as TODO and link to some tracker so we don't forget?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Issue opened to fix the underlying issue: #17

aws-encryption-sdk Integration Tests
************************************

In order to run these integration tests successfully, these things which must be configured.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: wording polish ("these things which must be configured")

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to "these things must be configured".

"""Only run tests if both required environment variables are found."""
test_control = os.environ.get(TEST_CONTROL, None)
key_id = os.environ.get(AWS_KMS_KEY_ID, None)
return not (test_control == 'RUN' and key_id is not None)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor: not a huge deal given the context, but could be a bit more readable for maintenance's sake; even just expanding the negate out would help: test_control != 'RUN' or key_id is None (if I did that right)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll be refactoring a decent chunk of the integration test utils when we get the test vectors packaged as a Python package, so I'll leave refining this bit until then.

@mattsb42-aws mattsb42-aws merged commit 33badf5 into aws:master Sep 28, 2017
@mattsb42-aws mattsb42-aws deleted the travis branch September 28, 2017 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants