-
Notifications
You must be signed in to change notification settings - Fork 4
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
Debian packages #2
Comments
Hi Zibi! I think we want to add unit tests, but I don't know how far in the future it will be. I guess it might take a while before I have time to do it. /J |
Thanks for your answer! |
That's great, thanks. Best /J |
Hi Zibi. @cpascual presentation about collaborative packaging is a good idea and we can try it on this project. As we are using rpm based operating system at MaxIV, gitlab-ci is probably a better idea. I started to add basic unittest on the tango server side (PR #5) based on pytest and pytango test context. As far as I understand from tango meeting presentation, we shall create a new repository (on gitlab) where we can put Debian and Centos7 packaging related files, am I right ? Cheers, |
I would say so, but let's wait for @cpascual confirmation. I think he recently explored the gitlab-ci free plans. |
We are packaging this DS for Debian locally at ALBA but was thinking that it may be usefull for other institutes to reuse the same packages instead repeating the packaging efforts. This idea was presented on the last Tango Meeting by @cpascual.
In the above presentation we proposed to use gitlab-ci for automatic creation of packages.
We have two options on where to host the packaging repository gitlab.com or salsa.debian.org.
The first option is better if you plan to implement CI (unittests) of the code (upstream). Otherwise, if the pipeline will consists only packaging steps, salsa is fine. For the moment could you answer if you plan to add unitests in some near future?
The text was updated successfully, but these errors were encountered: