- Generated hpi can be used as plugin on Jenkins.
- There are tests to launch FreeStyle jobs and serve them via API
- No workflow/pipeline style jobs based tests yet. There is some problem using workflow-plugin:
some maven depency issue causing compilation failure.
- There might be authorization lapses, will be tested after UX-6/UX-7
- model clean up and bug fixes:
- Run model is enhanced to include RunTrend, other run status and enQueueTime
- LoginDetails handling is cleaned-up, it is handled polymorphically with JSON/Jackson
- Service apis, commons and security apis don't depend on core, only embedded-service module depends on core
* initial skeleton of app container component, crappy stylesheet
* beginnings of an external plugin (plain js for now)
* beginnings of plugin manager
* integration with react-router, which will need replacing or a replacement "*" route to show dynamic routes
* initial .flowconfig
Squashed commit of the following:
commit f19f201140
commit 2e3d38463f
commit 5e13467fde
commit cb7781456c
- Added ServiceException and added to java docs of apis
- ProfileService and PipelineService appears as ExtensionPoint to be
implemented as @Extension
- Added Identity to abstract user Pricipal
- Convinience ServiceException classes created
- UserDetails gives LoginDetails of various providers
Passing user Identity to Service API implementations:
----------------------------------------------------
Current approach is to pass Identity as parameter of each and every API method.
Any future Service API must have Identity as parameter or things wont work as
expected.
We have it this way at present which is bit ugly and it definitely needs revist.
Once we have Guice based infrastructure in place and we have code to prove how
it is going to work, these interfaces may change.
For example, an API implementation can always ask for instance of Identity via
Guice injection at the same time service client can call any service API and
inject identity with escalated privilege.