| Summary: | Steps to deploy other than Singleton session strategy via GUI could be simpler | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jiri Svitak <jsvitak> | ||||
| Component: | Business Central | Assignee: | Marco Rietveld <mrietvel> | ||||
| Status: | CLOSED EOL | QA Contact: | Lukáš Petrovický <lpetrovi> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0.0 | CC: | kverlaen, mbaluch, wmedvede | ||||
| Target Milestone: | ER3 | ||||||
| Target Release: | 6.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-03-27 20:07:26 UTC | Type: | Enhancement | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Jiri Svitak
2013-11-21 16:33:19 UTC
Yeah, it sounds as a good idea.. I think that Option 2 is the only one that we can apply at this moment. Adding the type of the strategy to the kmodule.xml doesn't seem possible at this point, because that's only used by jbpm and not drools. We can also add an intermediate step for the deployments that ask you about the strategy that you want when there are processes involved in the project. I will think about this issue and try to create some mockups about how this can be improved. IMO by default the strategy should be Per Process Instance and as you mention the Build & Deploy operation should be decoupled into two atomic operations. Maciej, default session strategy can now be configured in deployment descriptor, right?g both options are actually possible:
- use deployment descriptor to specify what strategy your project shall use upon deployment
- more managed repos there will be options to :
- compile only which verifies your project -> Compile
- maven install -> Build and Install
- runtime deploy -> Build and Deploy
So with that in place I am marking this as modified so it can get tested.
Created attachment 971289 [details]
project-build-options.png
I have already tested deployment descriptors and I can confirm that strategy can be set using deployment descriptor configuration file.
Wrt. gui management, I cannot see the options you mention in the business central. See the attached screenshot of BPM Suite 6.1.0 ER3.
Jiri, you need to have managed repository (under asset mgmt) otherwise you won't see these three options. So create new project and then make sure it is managed repository. Thanks Maciej. I had to add myself to a new kiemgmt role, why a new role? Why admin role is not enough to create a managed git repository? Unfortunately there is still no option to convert existing or cloned repositories to managed repositories. As a result the managed repository does not solve the problem. My existing or cloned repositories still have only Build&Deploy button without gui option to deploy using selected session strategy. Adding also Walter to CC. As a side effect of working on this bugzilla, I have filed a new installer BZ about kiemgmt role required to do full repository management: BZ1176597 new role and restriction of features of asset mgmt to that role was added most likely due to that asset mgmt will be tech preview in 6.1 though I'll let Walter to comment on this too. |