-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: automate the build #3
Conversation
167e4c1
to
a00baf9
Compare
So I've installed Varnish from the package, then downloaded the source files and done as suggested, however it still won't get past
|
a00baf9
to
b900333
Compare
@andrew-canaday I've just rebased this and enabled Travis on my fork and its working now, so perhaps can add some tests to run after its compiled but the automation would at least check it can be compiled on each platform |
One thing I did notice is the After copying the files across I could boot Varnish with the plugin installed 🎉 |
Thank you for this! Will look be looking at this early next week while setting up CI for the 1.0 release. |
Awesome, let me know if there is anything I can do to help. This is really just one way to do Im sure there might be a better way that using kitchen-ci @andrew-canaday |
Hey, @gsdevme I'm going to close this out for now, but will add you as a contributor when we push the upcoming CI changes / will re-open, if necessary. (Please feel free to re-open if you find this to be problematic or want to continue discussing this thread, in particular). |
Hey @andrew-canaday
In regard to #2
Ive create a travis file and using kitchen-ci set it to build the package on both CentOS & Debian... likely some more work but just thought Id push the changes to get some thoughts?
I've ran both suites and screenshot the errors, Debian seems to get further than CentOS though but fails at the
make
point.CentOS 6.9
Debian 8
I also checked the folder you was speaking about.