The one answer on here says that git is supported by paid versions only!
How do then people work with the community edition at all?!
It doesn’t seem feasible to do a project of significant size without being able to use a version control system.
How do people deal with this issue? Almost seems like a deal breaker as far as adoption is concerned.
It’s a very interesting question that I’m sure Bonitasoft and other manufacturers of BPM software wrestle with.
If you can find one other manufacturer of BPM software that allows GIT use for version control etc. in their community version then I’m sure Bonitasoft would reconsider, but for them, at present, it’s a paid for model.
That’s why there are three different subscription models. Teamwork, Efficiency and Performance. Speak with Bonitasoft and you may find the version you require is less than what you think it is.
In our case we are too small for Subscription, and therefore we question it’s worth, we’ve written extensions that allow us to do some of what we can do easier with subscription, but it takes effort.
We are lucky to ensure our developments are singular and not spread too widely, we brainstorm the development before developing, 80% planning and 20% coding.
Designing and changing sub-processes is not taken lightly.
We constantly make duplicates of our processes, so one process may have 30-40 versions based on development complexity. But only one person will be working on it.
We keep a very strong asset register of what uses what, and have developed utilities to fix things in the diagram automatically when possible. Otherwise it’s a new version.
We also use automated backup software to back up our drives to a central NAS should things really go wrong. 30 days at 1 hour intervals, yes it adds up but it’s worth it. Using incremental backups helps here as it keeps the size down.
Simply put, we manage ourselves, GIT doesn’t form part of our Group version control management. That’s the price of community, as it is today.
Sorry but I don’t think there is anything to be done at this stage until after a competitor forces the hand…
regards
Seán
PS: If this reply answers your question, please mark a resolved.
bonitahome\workspace\default
this is where you will find (nearly) all developments. Note this could change based on requirements.
Question:
…we think we should store all of these artifacts in Git, where we store all of our other source code. I have not found any documentation that describes how to do this.
Answer from Activiti:
Currently the models are stored and versioned in a relational database. There’s no support to store the models in Git. But I agree that it would be a nice feature to provide.
And that I suspect means for their Paid-For version as well, unlike Bonitasoft who do provide this feature already…
regards
Seán
Thanks for the thoughtful answer!
A couple of followups.
Is it possible at all to manually put the necessary files from the workspace into git? And then check them in whenever they change? Is there a way to know which files would need to be checked in?
How about Activiti? Do you know by any chance if they have similar, almost crippling, restrictions on their product as well?
Answer from Activiti:
Currently the models are stored and versioned in a relational database. There’s no support to store the models in Git. But I agree that it would be a nice feature to provide.
Ah, I see. In addition to the DB schema, I was talking about the other artifacts that the software produces as a part defining and managing processes. I was wondering if Activiti allows that easier than Bonita in their community version.
Your suggestion to just version control the entire workspace is reasonable though.
not related to Bonitasoft but interesting:
https://nickcraver.com/blog/2016/05/03/stack-overflow-how-we-do-deployment-2016-edition/
how StackOverFlow does it’s deployments
regards