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

Need a "smoke test" before submits. #4694

Open
milkypostman opened this issue Apr 10, 2017 · 3 comments
Open

Need a "smoke test" before submits. #4694

milkypostman opened this issue Apr 10, 2017 · 3 comments
Labels

Comments

@milkypostman
Copy link
Member

We need a set of packages which we should build that cover all the different dvcs systems for both unstable and stable builds.

Any suggestions? These should be packages which are both "popular" (so we don't break popular packages) and diverse (unique recipes, different dvcs, etc.).

  • ivy: github, uses :files with both :defaults and :excludes. has 0.8.0 style tags
  • evil: github, uses default files. large repo, 1.1.1 style tags
  • m-buffer: github, uses :files with :defaults, v0.8.0 style tags

Lets get some more listed then I'll write a quick script we can put in the repo to run make on all these. It would help us to avoid where we accidentally break builds somehow. e.g.: #4693

@tarsius
Copy link
Member

tarsius commented Apr 10, 2017

It would also be nice if one could do something like make PACKAGE_BUILD=/work/in/progress/package-build.el .... That would make testing much easier.

@alphapapa
Copy link
Contributor

@tarsius This isn't exactly the same, but: 4b770e4

@purcell
Copy link
Member

purcell commented Apr 10, 2017

This smoke test would probably belong with package-build, right?

@tarsius tarsius added the feature label Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants