Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Rework Travis to perform integration tests separately #419

Closed
jcjones opened this issue Jun 26, 2015 · 1 comment
Closed

Rework Travis to perform integration tests separately #419

jcjones opened this issue Jun 26, 2015 · 1 comment
Assignees
@jcjones
Milestone
General Availability

Comments

@jcjones
Copy link
Contributor

jcjones commented Jun 26, 2015

Goal: Know what causes a Travis failure.

  • Print super-clear errors at the end of test.sh as to what set the failure status
  • Don't fail if the Python client integration fails
  • Do fail if Node client integration fails
  • Try to remain fast
@jcjones jcjones self-assigned this Jun 26, 2015
@bdaehlie bdaehlie added this to the General Availability milestone Jun 26, 2015
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
dffc43f 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
7f4ef16 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
e18601d 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
d7fc834 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
1f04f93 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
678f24e 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
2ba3bef 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.

- Also post comments from Golint
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
df686dc 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.

- Post comments from static analysis tools
- Change to posting from LetsEncryptBot
- For integration testing, only fail if the compile fails, or
  the NodeJS-client fails. Log if the Python client fails.
@jcjones jcjones mentioned this issue Jun 30, 2015
Merged
jcjones pushed a commit that referenced this issue Jun 30, 2015
Issue #419 - Provide more details from Travis on PRs.
4d3731b 
This uses a node.js module to post `status` updates to Github, and uses a Travis
secret to authenticate.

- Post comments from static analysis tools
- Change to posting from LetsEncryptBot
- For integration testing, only fail if the compile fails, or
  the NodeJS-client fails. Log if the Python client fails.
jcjones added a commit that referenced this issue Jul 8, 2015
@jcjones
Merge pull request #422 from letsencrypt/419_travis_details
dc7e21b 
Issue #419 - Provide more details from Travis on PRs.
@jcjones
Copy link
Contributor Author

jcjones commented Jul 8, 2015

Handled in PR #422.

@jcjones jcjones closed this as completed Jul 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcjones jcjones

Labels
None yet
Projects
None yet
Milestone
General Availability
Development

No branches or pull requests
2 participants
@bdaehlie @jcjones