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

Common build provider to hide specific build system #268

Merged
merged 3 commits into from
Nov 17, 2018
Merged

Common build provider to hide specific build system #268

merged 3 commits into from
Nov 17, 2018

Conversation

vhatsura
Copy link
Contributor

@vhatsura vhatsura commented Nov 5, 2018

Base implementation for #259

@gep13
Copy link
Member

gep13 commented Nov 6, 2018

@pascalberger can I get your thoughts on this? Thanks

@pascalberger pascalberger self-requested a review November 8, 2018 12:49
Copy link
Member

@pascalberger pascalberger left a comment

Choose a reason for hiding this comment

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

Added some suggestions to discuss. Otherwise LGTM as a base implementation for the parameters. Later other AppVeyor specific functionality should also be abstracted. Long term I would also prefer to get rid of build parameters in its current form in favor of using typed context. But we should wait with this until we have a version released as it will introduce breaking changes.

Cake.Recipe/Content/buildProvider.cake Show resolved Hide resolved
IBuildInfo Build { get; }
}

public class AppVeyorTagInfo : ITagInfo
Copy link
Member

Choose a reason for hiding this comment

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

I would suggest to move AppVeyor specific code into a separate file to make it easier maintainable once we support more build servers.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agree with you. Will do it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

Copy link
Member

@pascalberger pascalberger left a comment

Choose a reason for hiding this comment

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

LGTM

@gep13 If also OK for you I'll squash the commits and merge the PR

@pascalberger
Copy link
Member

@vhatsura Can you rebase on current develop or check the Allow edits from maintainers. checkbox on the right side of this PR?

@vhatsura
Copy link
Contributor Author

@pascalberger, Allow edits from maintainers was checked and didn't changed. Will rebase on current develop

@pascalberger
Copy link
Member

@vhatsura Are you sure Allow edits from maintainers is enabled? I get permission denied when I try to write to the branch. Or maybe you have some branch policy enabled?

It would be nice to have it rebased before merging, to get rid of the merge commits (you updated the branch with an additional merge commit). While I could squash together the commits, to get rid of them, GitHub will lost track that these changes are made by you and attribute them to me (if this is OK for you I can also do it this way).

@vhatsura
Copy link
Contributor Author

vhatsura commented Nov 17, 2018

@pascalberger, hmm, yes I'm sure that checkbox is checked. Also I checked branch and repo policies. All looks fine.

By the way, I rebased my branch onto upstream.

@pascalberger pascalberger merged commit 3d8c14b into cake-contrib:develop Nov 17, 2018
@pascalberger
Copy link
Member

@vhatsura Sorry, there was some config issue on my side. I've now cleanup the branch (you were creating merge commits from upstream develop into your develop branch, not rebasing on upstream develop).

The changes have now been merged, thanks for your contribution 👍

For the future GitHub workflow is easier if you make changes on a separate branch in your fork, as now the develop branch in your fork and the one in the upstream repository has diverged. See GitHub Flow.

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.

3 participants