Skip to content
This repository has been archived by the owner on Feb 16, 2024. It is now read-only.

Packaging automated tests #40

Closed
Razican opened this issue Sep 29, 2016 · 3 comments
Closed

Packaging automated tests #40

Razican opened this issue Sep 29, 2016 · 3 comments

Comments

@Razican
Copy link
Member

Razican commented Sep 29, 2016

We don't do CI for packaging, which we should be doing in order to make sure that packages for different distributions work as expected.

@Razican Razican added this to the SUPER 0.2.0 milestone Sep 29, 2016
@Razican Razican modified the milestones: SUPER 0.3.0, SUPER 0.2.0 Oct 27, 2016
Razican added a commit that referenced this issue Nov 21, 2016
Also added .deb generation tests in Travis (let's see how that works).
It should do part of #40.
@Razican
Copy link
Member Author

Razican commented Mar 19, 2017

Package creation is being tested for .deb files in Ubuntu, but no package installation, usage or other distributions / package formats.

@Razican Razican added this to the SUPER 0.5.0 milestone Apr 2, 2017
@Razican
Copy link
Member Author

Razican commented May 27, 2018

Related issue: #163.

Currently not testing installation and usage.

@Razican
Copy link
Member Author

Razican commented May 30, 2018

It has been decided not to implement package installation and running tests, at least for now.

Razican added a commit that referenced this issue May 30, 2018
This will enable deploying Linux packages for Ubuntu, CentOS, Fedora and Debian in each tag. Not only that, packages will be built in each commit, to make sure nothing breaks.

It also adds a new place where the release version must be updated with a new release, maybe that could someday be automated. We now need to check the `Cargo.toml` file, the `travis.yml` file and the `rpmbuild/super.spec` file.

As an extra, given that I was working in this branch, I implemented a fix for #159, so all three, #40, #149 and #159 are fixed now.
@Razican Razican closed this as completed May 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant