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.

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

ci: run builds on 'next' branch of git.git #2470

Merged
merged 3 commits into from Aug 3, 2017
Merged

ci: run builds on 'next' branch of git.git #2470

merged 3 commits into from Aug 3, 2017

Conversation

ttaylorr
Copy link
Contributor

@ttaylorr ttaylorr commented Aug 2, 2017

This pull request teaches CircleCI and Travis how to run CI with the version of Git present at the tip of branch 'next'.

This is useful for adding the 'delay' capability to git lfs filter-process (see: #2466), since the 'delay' capability is not yet in master, or a released version of Git. This will give us a chance to test the 'delay' functionality out in CI before it's released in Git.

Once Git releases a version that contains git/git@2841e8f, we can revert this pull request.

This is required work for: #2466.


/cc @git-lfs/core
/cc #2466

@ttaylorr ttaylorr added the review label Aug 2, 2017
@ttaylorr ttaylorr added this to the v2.3.0 milestone Aug 2, 2017
circle.yml Outdated
@@ -4,6 +4,7 @@ machine:
GIT_SOURCE_REPO: https://github.com/git/git.git
GIT_EARLIEST_SUPPORTED_VERSION: v2.0.0
GIT_LATEST_SOURCE_BRANCH: master
GIT_NEXT_SOURCE_BRANCH: master
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't that be next?

Copy link
Contributor Author

@ttaylorr ttaylorr Aug 2, 2017

Choose a reason for hiding this comment

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

@larsxschneider great catch! I fixed that up in: a2e6e2d.

@@ -12,6 +12,7 @@ env:
- GIT_SOURCE_REPO="https://github.com/git/git.git"
- GIT_EARLIEST_SUPPORTED_VERSION="v2.0.0
- GIT_LATEST_SOURCE_BRANCH="master"
- GIT_NEXT_SOURCE_BRANCH="next"
Copy link
Member

Choose a reason for hiding this comment

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

You could also defined GIT_LATEST_SOURCE_BRANCH="next" for the time being.
That's why I called it LATEST and not MASTER back then 😄

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think running on master & next for the time being will be fine.

@@ -4,6 +4,7 @@ machine:
GIT_SOURCE_REPO: https://github.com/git/git.git
GIT_EARLIEST_SUPPORTED_VERSION: v2.0.0
GIT_LATEST_SOURCE_BRANCH: master
GIT_NEXT_SOURCE_BRANCH: next
Copy link
Member

Choose a reason for hiding this comment

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

Same here

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Is this the same line as #2470 (comment)?

@ttaylorr ttaylorr merged commit f950f97 into master Aug 3, 2017
@ttaylorr ttaylorr deleted the ci-run-on-next branch August 3, 2017 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants