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

New Cake Build for ChocolateyGUI #369

Merged
merged 13 commits into from Jan 15, 2017
Merged

Conversation

gep13
Copy link
Member

@gep13 gep13 commented Dec 21, 2016

  • Makes use of Cake.Recipe (https://github.com/cake-contrib/Cake.Recipe)
  • This is likely going to fail on AppVeyor, as I have removed the WiX Binaries that were in the tools folder
  • This portion will need to be refactored

@RichiCoder1 @pascalberger Happy to accept any comments that you have on this.

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

Interesting... AppVeyor already has WiX installed (https://www.appveyor.com/docs/installed-software/) so the build is working.

I don't like relying on that though, and I will switch to using the WiX NuGet package at some point, but for now, I think I will keep working on the other parts.

There are some dupfinder issues in the code base just now, that it the reason for the build failure.

@RichiCoder1
Copy link
Member

Weirdly enough, I'm ok having Wix as a preinstalled dependency for now (as long as we document it).

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

@RichiCoder1 said...
Weirdly enough, I'm ok having Wix as a preinstalled dependency for now (as long as we document it).

The experience for new people coming onto the project could be a little jarring, when they try to build, and it doesn't work, so yes, we will need to document it. Something I will need to get fixed though. Not the highest priority just now though.

@RichiCoder1 RichiCoder1 self-requested a review December 21, 2016 20:34
Copy link
Member

@RichiCoder1 RichiCoder1 left a comment

Choose a reason for hiding this comment

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

That's seriously impressive how compact that setup.cake is.

@RichiCoder1
Copy link
Member

Yah, that dupfinder is going to be super unhappy for now. Lots of duplicate code.

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

@RichiCoder1 said...
Yah, that dupfinder is going to be super unhappy for now. Lots of duplicate code.

Ha ha, yeah, noticed that. If there are other files that you want to exclude from the dupfinder check, we can add them into the SetToolSettings call.

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

@RichiCoder1 said...
That's seriously impressive how compact that setup.cake is.

Thanks! It has taken a while to get Cake.Recipe to where it is just now, but it is starting to take shape, and the more projects it is used on, the more flexible it can become. Having to add in some features just now, to accommodate what ChocolateyGUI requires, but it is all for the greater good 😄

@RichiCoder1
Copy link
Member

RichiCoder1 commented Dec 21, 2016

@RichiCoder1 said...
Yah, that dupfinder is going to be super unhappy for now. Lots of duplicate code.

Ha ha, yeah, noticed that. If there are other files that you want to exclude from the dupfinder check, we can add them into the SetToolSettings call.

I'm going to say probably Hacks.cs and one other, but I'd need to the report. Speaking of which....

Copy link
Member

@RichiCoder1 RichiCoder1 left a comment

Choose a reason for hiding this comment

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

Reports and other build artifacts don't appear to be getting picked up in appveyor.

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

@RichiCoder1 said...
Reports and other build artifacts don't appear to be getting picked up in appveyor.

Yip, I haven't added any of the Environment Variables for the Project in AppVeyor yet. Cake.Recipe is really controlled by the top level settings in setup.cake and the presence of certain Environment Variables. If they aren't there, then the build silently skips those steps.

@gep13
Copy link
Member Author

gep13 commented Dec 21, 2016

@RichiCoder1 currently working on adding the download of the ReleaseNotes into the build process, and then was going to circle back around to that.

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 ok, this is now successfully creating the Chocolatey Package, as you can see here:

https://ci.appveyor.com/project/chocolatey/chocolateygui/build/0.14.0-PullRequest.369+175.build.125#L771

All that is left to getting a successful build is fixing the dupfinder issues 😄

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 said...
Reports and other build artifacts don't appear to be getting picked up in appveyor.

That normally happens at the end of the build, i.e. when it is successful, but sounds like you have another expectation, or, I am simply not understanding. With the build in it's current "broken" state, what artifacts would you expect to see?

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 I guess the DupFinder report would be very useful in this scenario. Ok, let me take care of that, this will be a change in Cake.Recipe.

@RichiCoder1
Copy link
Member

@gep13 Yup, test results & dup finder/other analysis reports. If it fails the build, I want to be able to quickly and easily diagnose why :)

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 ok, now we are getting somewhere 😄

Have a look here:

https://ci.appveyor.com/project/chocolatey/chocolateygui/build/0.14.0-PullRequest.369+175.build.126/artifacts

And you will find that a dupfinder.html is not an artifact of the build. If you download this, you will see something similar to this:

image

If you have the TeamCity Extension for Visual Studio installed, within the ChocolateyGUI solution open, clicking on those links should take you directly to the affected lines.

@RichiCoder1
Copy link
Member

Whoop, nice!

@RichiCoder1
Copy link
Member

I'll see about getting those Dups "fixed" so we can get a green build.

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 said...
I'll see about getting those Dups "fixed" so we can get a green build.

I have taken a stab at it. Just away to push. You can let me know what you think of the changes.

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

@RichiCoder1 and we have a green build! 🎉

@RichiCoder1
Copy link
Member

@gep13 Nice! I'm all good to merge whenever you're comfortable :)

@gep13
Copy link
Member Author

gep13 commented Jan 6, 2017

Assuming you are ok with the dupfinder changes, then I think this is good to go.

@RichiCoder1
Copy link
Member

👍 :shipit:

@RichiCoder1
Copy link
Member

@gep13 What's status here?

@gep13
Copy link
Member Author

gep13 commented Jan 12, 2017

Only thing that is missing is the style cop addition.

@gep13
Copy link
Member Author

gep13 commented Jan 13, 2017

@RichiCoder1 so, having some "issues" getting the StyleCop.Analyzers to work. They seem to work for one, or the other project (i.e. ChocolateyGui and ChocolateyGui.SubProcess) but not for both projects at the same time. Not sure what is going on. Will try to dig into it some more over the weekend.

@gep13
Copy link
Member Author

gep13 commented Jan 14, 2017

@RichiCoder1 ok, StyleCop has now been added to the build. Let me know your thoughts on the rules that I have left in place.

@gep13 gep13 changed the title [WIP] New Cake Build for ChocolateyGUI New Cake Build for ChocolateyGUI Jan 14, 2017
@gep13
Copy link
Member Author

gep13 commented Jan 14, 2017

@RichiCoder1 okay, this is ready to go.

I have set up the MyGet feed to use again use https://www.myget.org/F/chocolateygui/api/v2 rather than my personal one.

@RichiCoder1
Copy link
Member

LGTM! I'm sure I'll probably end up tweaking it, but nothing objectable so far.

@gep13
Copy link
Member Author

gep13 commented Jan 15, 2017

@RichiCoder1 sweet!

@RichiCoder1
Copy link
Member

Are we good to merge, or is there anything else you'd like to tackle first?

@gep13
Copy link
Member Author

gep13 commented Jan 15, 2017

I think we are good. I have raised another issue for the Wyam Docs.

@RichiCoder1 RichiCoder1 merged commit e5deb01 into chocolatey:develop Jan 15, 2017
@RichiCoder1
Copy link
Member

Whoop! I'm going to be working tomorrow(today) on a lot of backlog that still present. Hopefully should have something close to delivery soon :)

@gep13 gep13 deleted the feature/GH-349 branch January 15, 2017 12:26
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.

None yet

2 participants