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

Set up Travis CI #417

Closed
dmfs opened this issue Sep 12, 2017 · 1 comment
Closed

Set up Travis CI #417

dmfs opened this issue Sep 12, 2017 · 1 comment

Comments

@dmfs
Copy link
Owner

dmfs commented Sep 12, 2017

No description provided.

dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
bf55631
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
885d4b1 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
1852037 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
901d6af 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
1a19dfd 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
0d97baf 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
18ff286 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
4891c51 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
98c07db 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
a73c3fb 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
c9a4474 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
fd115bb 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
69853c3 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
4069713 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 18, 2017
@dmfs
Add .travis.yml. Implements #417
e459cb9 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
dmfs added a commit that referenced this issue Oct 19, 2017
@dmfs
Add .travis.yml. Implements #417 (#466)
9aa367c 
This also changes the version code to be based on commit count in the current branch rather than master. Apparently Travis doesn't fetch the master which caused this to fail.
Since we only publish master builds this should not have any unwanted side effects. Yet we spread the version code to allow inserting version numbers if necessary.
@dmfs
Copy link
Owner Author

dmfs commented Nov 20, 2017

Released in 1.1.10

@dmfs dmfs closed this as completed Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dmfs