Hi,
When I play with jenkins setup I face one issue with rspec modules that
is newly written ( thanks gabi, vmoravec and mfilka for being explorer
). Issue is that some modules have heavy dependencies and idea of
jenkins is to have minimal stable installation so it doesn't need
regular updates
Hi,
when I creating jobs on jenkins I found that we have bunch of modules
that is not dropped ( no single README.md ) and also not in Yast:Head,
so in fact testing on opensuse is not possible.
I like to know if this modules still living and what is reason to not
have it in Yast:Head. Reason is
On Wed, Oct 09, 2013 at 10:45:04AM +0200, Josef Reidinger wrote:
Hi,
when I creating jobs on jenkins I found that we have bunch of modules
that is not dropped ( no single README.md ) and also not in Yast:Head,
so in fact testing on opensuse is not possible.
What has README.md to do with
On Wed, 9 Oct 2013 10:53:02 +0200
Arvin Schnell aschn...@suse.de wrote:
On Wed, Oct 09, 2013 at 10:45:04AM +0200, Josef Reidinger wrote:
Hi,
when I creating jobs on jenkins I found that we have bunch of
modules that is not dropped ( no single README.md ) and also not in
Yast:Head, so in
On 10/09/2013 10:45 AM, Josef Reidinger wrote:
boot_server
certify
cim
cluster
heartbeat
iplb
Dropped.
ipsec
Dropped.
irda
Definitely dropped. Not on GitHub, we need to adjust the README.
mail_server
mouse
Dropped.
mysql_server
nts_utils
oem_installation
openva_security_scanner
On Wed, Oct 09, 2013 at 10:45:04AM +0200, Josef Reidinger wrote:
mail_server
Merged to mail.
In general, I am afraid that we accidentally created many zombies when
converting from SVN to Git, just to put anything to master. For example
mail_server's master directly follows the SLE10 branches
On Tue, 8 Oct 2013 17:24:49 +0200
Josef Reidinger jreidin...@suse.cz wrote:
Hi,
I finish today adding Rakefile to all reasonable modules and setting
hudson to use it. You can see result at [1]. If you miss some modules,
then you may find it in next email, where I write all modules that is
2) mock everything except yast2
... I'd prefer this one as it allows tests over more than one module and
allows us to be more flexible in mocking YaST internals.
Michal
--
To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: yast-devel+ow...@opensuse.org
