Closed jlinkes closed 1 year ago
I had to install osc this way in my testing: sudo apt-get install -y software-properties-common sudo add-apt-repository "deb http://download.opensuse.org/repositories/openSUSE:/Tools/Debian_10/ /" sudo wget -nv https://download.opensuse.org/repositories/openSUSE:Tools/Debian_10/Release.key -O /root/Release.key sudo apt-key add /root/Release.key sudo apt-get update sudo apt-get install -y osc python-m2crypto libssl-dev swig sudo pip3 install M2Crypto
It's possible that python-m2crypto is not needed.
OBS support is not needed any more - the OBS build support wasn't being maintained and we had issues with OBS labs filling up with data. Closing this for now.
The Pull Request attempts to add support for Suse OBS to dpdk. I modeled my changes based on travis code, but there are some differences which I want to ask about:
The OBS code assumes that the utility osc has been installed on the host, obs_mon contains a link to installation instructions - is this okay?
I'm passing OBS username and password in the scripts and creating ~/.config/osc/oscrc with that. Not sure this is the best way to do this - we could just put the file into the repo or maybe even do something else
I added series_obs_project to the database since I followed travis code, but this creates a dependency on obs (as does travis). Not sure if this is right