Re: [Spacewalk-devel] Travis CI for Spacewalk git

2015-06-09 Thread Jan Dobes
- Original Message -
 From: Paul Robert Marino prmari...@gmail.com
 To: spacewalk-devel@redhat.com
 Sent: Friday, June 5, 2015 5:32:16 PM
 Subject: Re: [Spacewalk-devel] Travis CI for Spacewalk git
 
 on the subject Ubuntu I may be creating the client packages for 2.3 on
 Ubuntu trusty soon if I do I will publish them on launchpad.
 I'm not sure yet if i will have the time to take over maintaining the
 packages for Ubuntu but it is a possibility. The problem is I would
 need to figure out how to handle supporting multiple versions of
 spacewalk. I was wondering if it would be possible to publish apt
 repos on yum.spacewalkproject.org using the same structure.
 

We do not currently support Debian/Ubuntu, however any effort from community is 
welcome. But I'm afraid packaging is the least problem, the Debian client code 
is not up to date with RHEL/Fedora neither is tested, some patches would be 
needed.

Regards,
-- 
Jan Dobes
Satellite Engineering, Red Hat

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Travis CI for Spacewalk git

2015-06-09 Thread Jan Dobes
 If you want to integrate Java or Python unit tests I think we can help - we
 have a homegrown Docker infrastructure to run them through Jenkins at every
 commit. I guess that needs to be adapted to be used in Travis, but it should
 be doable and it would be a further step in the same direction.

Depends how difficult would be to implement it but in general I'm interested, I 
was already thinking about something similar.

Regards,
-- 
Jan Dobes
Satellite Engineering, Red Hat

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Travis CI for Spacewalk git

2015-06-08 Thread Silvio Moioli

On 05/06/2015 16:32, Jan Dobes wrote:

as you may already noticed, we enabled Travis CI [1] for Spacewalk Github 
account several weeks ago. Since then, few bugs were fixed and now it works 
with every package in our git except some thirdparty packages in 'spec-tree' 
directory (if they are explicitly requiring Oracle RPMs or are not buildable on 
Fedora 21 for any reason).


Thank you Jan, great work, this really helps!

If you want to integrate Java or Python unit tests I think we can help - we 
have a homegrown Docker infrastructure to run them through Jenkins at every 
commit. I guess that needs to be adapted to be used in Travis, but it should be 
doable and it would be a further step in the same direction.

Regards,
--
Silvio Moioli
SUSE Manager Development Team

--
Silvio Moioli
SUSE LLC
Maxfeldstraße 5, 90409 Nürnberg Germany

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


[Spacewalk-devel] Travis CI for Spacewalk git

2015-06-05 Thread Jan Dobes
Hello Spacewalkers,

as you may already noticed, we enabled Travis CI [1] for Spacewalk Github 
account several weeks ago. Since then, few bugs were fixed and now it works 
with every package in our git except some thirdparty packages in 'spec-tree' 
directory (if they are explicitly requiring Oracle RPMs or are not buildable on 
Fedora 21 for any reason).

The only thing we are testing at the moment is if we are able to build RPM 
package(s) from sources - yes, we are building RPMs on Travis Ubuntu machines! 
Basically, it's just syntax check where we are compiling java classes, running 
checkstyle, pylint etc.

It's beneficial mainly for pull request processing - contributor can see why 
his patch didn't pass and post additional patch shortly, doesn't have to wait 
days until someone tries his patch and pokes him back. It's also fork-friendly, 
so you can easily enable building for your own account.

Currently, builds are triggered on every new or updated pull request and push 
into master branch. Only packages affected by these commits will be built.

[1] https://travis-ci.org/spacewalkproject/spacewalk

Regards,
-- 
Jan Dobes
Satellite Engineering, Red Hat

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Travis CI for Spacewalk git

2015-06-05 Thread Paul Robert Marino
on the subject Ubuntu I may be creating the client packages for 2.3 on
Ubuntu trusty soon if I do I will publish them on launchpad.
I'm not sure yet if i will have the time to take over maintaining the
packages for Ubuntu but it is a possibility. The problem is I would
need to figure out how to handle supporting multiple versions of
spacewalk. I was wondering if it would be possible to publish apt
repos on yum.spacewalkproject.org using the same structure.

On Fri, Jun 5, 2015 at 10:53 AM, Paul Robert Marino prmari...@gmail.com wrote:
 Any chance you can get it to do deb packages too :)

 On Fri, Jun 5, 2015 at 10:32 AM, Jan Dobes jdo...@redhat.com wrote:
 Hello Spacewalkers,

 as you may already noticed, we enabled Travis CI [1] for Spacewalk Github 
 account several weeks ago. Since then, few bugs were fixed and now it works 
 with every package in our git except some thirdparty packages in 'spec-tree' 
 directory (if they are explicitly requiring Oracle RPMs or are not buildable 
 on Fedora 21 for any reason).

 The only thing we are testing at the moment is if we are able to build RPM 
 package(s) from sources - yes, we are building RPMs on Travis Ubuntu 
 machines! Basically, it's just syntax check where we are compiling java 
 classes, running checkstyle, pylint etc.

 It's beneficial mainly for pull request processing - contributor can see why 
 his patch didn't pass and post additional patch shortly, doesn't have to 
 wait days until someone tries his patch and pokes him back. It's also 
 fork-friendly, so you can easily enable building for your own account.

 Currently, builds are triggered on every new or updated pull request and 
 push into master branch. Only packages affected by these commits will be 
 built.

 [1] https://travis-ci.org/spacewalkproject/spacewalk

 Regards,
 --
 Jan Dobes
 Satellite Engineering, Red Hat

 ___
 Spacewalk-devel mailing list
 Spacewalk-devel@redhat.com
 https://www.redhat.com/mailman/listinfo/spacewalk-devel

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel


Re: [Spacewalk-devel] Travis CI for Spacewalk git

2015-06-05 Thread Paul Robert Marino
Any chance you can get it to do deb packages too :)

On Fri, Jun 5, 2015 at 10:32 AM, Jan Dobes jdo...@redhat.com wrote:
 Hello Spacewalkers,

 as you may already noticed, we enabled Travis CI [1] for Spacewalk Github 
 account several weeks ago. Since then, few bugs were fixed and now it works 
 with every package in our git except some thirdparty packages in 'spec-tree' 
 directory (if they are explicitly requiring Oracle RPMs or are not buildable 
 on Fedora 21 for any reason).

 The only thing we are testing at the moment is if we are able to build RPM 
 package(s) from sources - yes, we are building RPMs on Travis Ubuntu 
 machines! Basically, it's just syntax check where we are compiling java 
 classes, running checkstyle, pylint etc.

 It's beneficial mainly for pull request processing - contributor can see why 
 his patch didn't pass and post additional patch shortly, doesn't have to wait 
 days until someone tries his patch and pokes him back. It's also 
 fork-friendly, so you can easily enable building for your own account.

 Currently, builds are triggered on every new or updated pull request and push 
 into master branch. Only packages affected by these commits will be built.

 [1] https://travis-ci.org/spacewalkproject/spacewalk

 Regards,
 --
 Jan Dobes
 Satellite Engineering, Red Hat

 ___
 Spacewalk-devel mailing list
 Spacewalk-devel@redhat.com
 https://www.redhat.com/mailman/listinfo/spacewalk-devel

___
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel