project remote handling in webui broken

[adrianschroeter]

The webui does not support handling of remote projects since the webui/api merge.

This is esp. a problem for monitoring, since build logs are not accessable anymore.

We need to decide how to design the handling of remote objects (like project and packages).

Maybe this is a larger task, in that case we need a workaround solution for viewing at least log files again.

[hennevogel]

build logs for remote projects? please explain

[adrianschroeter]

When you rebuild an entire project, but this project is hosted on a remote OBS instance. You can do that via <project link=... and repository configuration in project meta data. Better described here:

http://en.opensuse.org/openSUSE:Build_Service_Concept_project_linking

This leads to the situation that you have local build results (/build/ route), but all sources and package objects do not exist locally.

[hennevogel]

@coolo didn't you already separated them?

[coolo]

I seperated packages in a prj and packages inherited from a project link, correct. But adrian adds remote instances to the mix, so he actually links to a remote project. And quite a bunch of API code and most of the webui code doesn't like remote projects as they are not objects but strings (sic!)

[hennevogel]

Here we are again, doing stuff to things that aren't objects...

[adrianschroeter]

well, question is how they can become objects. We do not want to create and destroy objects just because it got changed on the remote instance IMHO.

So, we need to create some kind of object on the fly when requesting it. Currently it is a string object, which is sub-optimal.

[coolo]

most objects are "on the fly", we don't want them to be activerecords - I agree with that.

[ancorgs]

http://rubydoc.info/gems/activemodel/4.1.1/frames ?

[adrianschroeter]

we still some regressions here, but build logs and some commands are working in most important conditions at least again. So, I close this generic report for now. Created more specific reports the other day and we discussed the generic redesign here some weeks ago.