Hi all,

I have enabled Travis support also for the SLE-12-GA Git branch!


- There is YaST:SLE-12:GA:Travis OBS project [1] which builds
  the core SLE-12-GA Yast packages for Ubuntu.

- YaST:SLE-12:GA [2] contains the original packages (the packages
  in :Travis subproject are linked there plus they contain extra
  Debian/Ubuntu packaging files).

  Unfortunately there is no autosubmit from GIT, the packages
  are autosubmitted to the IBS. So if you do some backward
  incompatible change in the public API of a package in the
  SLE-12-GA branch then you should manually submit it to
  YaST:SLE-12:GA OBS project (or copypac it from the IBS).

  Note: It's not needed for all Yast packages, for Travis builds
  we just need the core packages like devtools, core,
  ruby-bindings, yast2... check the project [1] first.

- .travis.yml files from master have been imported to SLE-12-GA
  branch and modified to use the packages the YaST:SLE-12:GA:Travis
  OBS project.

- Some fixes for Travis builds have been cherry-picked and
  backported from the master Git branch to SLE-12-GA.

- I have updated the global build status overview, now you can
  see the Travis master, Travis SLE-12-GA and Jenkins (the public
  one) build statuses altogether at one place, check [3].


If you have some questions or need help with Travis then just ask me...


Enjoy ;-)



[1] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA:Travis
[2] https://build.opensuse.org/project/monitor/YaST:SLE-12:GA
[3] http://yastgithubio.readthedocs.org/en/latest/build-status-overview/

--

Best Regards

Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o.                              e-mail: [email protected]
Lihovarská 1060/12                              tel: +420 284 028 960
190 00 Prague 9                                 fax: +420 284 028 951
Czech Republic                                  http://www.suse.cz/
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to