Branch: refs/heads/2.7
Home: https://github.com/openSUSE/open-build-service
Commit: a06b1ad1196b37be3ffdf6b4a2b8e59b17f6d1bc
https://github.com/openSUSE/open-build-service/commit/a06b1ad1196b37be3ffdf6...
Author: Adrian Schröter
Date: 2016-04-14 (Thu, 14 Apr 2016)
Changed paths:
M src/api/app/controllers/webui/package_controller.rb
M src/api/app/controllers/webui/patchinfo_controller.rb
M src/api/app/controllers/webui/project_controller.rb
M src/api/app/helpers/webui/project_helper.rb
M src/api/app/models/project.rb
M src/api/app/policies/project_policy.rb
M src/api/app/views/webui/package/_live_log_controls.html.erb
M src/api/app/views/webui/package/live_build_log.html.erb
M src/api/app/views/webui/project/_packages_table.html.erb
M src/api/app/views/webui/project/_tabs.html.erb
M src/api/app/views/webui/project/show.html.erb
Log Message:
-----------
[webui] rename Project.is_remote? to defines_remote?
The Project database object for remote usages is always the project
defining the remote instance. find_remote delivers an additional string
identifing the remote project name.
We could have a is_remote? for repositories, because they can be indeed
local active record objects for remote projects, but it seems we don't
have the use case yet for adding this.
Cleaning up some misleaded code which just crashes so far when operating
on a remote project.
Commit: 9dd3c0e5e7efabd77aa73abc0588141476e1264a
https://github.com/openSUSE/open-build-service/commit/9dd3c0e5e7efabd77aa73a...
Author: Frank Schreiner
Date: 2016-04-14 (Thu, 14 Apr 2016)
Changed paths:
M dist/Makefile
M dist/t/0020-test-appliance.ts
A dist/t/0050-test-appliance.ta
Log Message:
-----------
[ci] split testing into system and appliance
Compare: https://github.com/openSUSE/open-build-service/compare/7cd1df560459...9dd3c0...
