I wanted to set up Workbench to use a git daemon shared by other developers who are using the Eclipse plugin.
I can clone the repository into Workbench, but it will not push changes back to that repository. It seems to use that clone to set up its own local repository.
Is this a limitation with Workbench? If we want to use Workbench and the Eclipse plugin in a mixed environment, do we have to use Workbench as the git daemon?
As far as I am aware, there is no functionality in KIE Workbench as yet to push to a remote repo. However, you can still achieve your goal of having an upstream repository rather than letting all developers using the git repo inside the KIE Workbench. You can test it with the existing jbpm-playground repo. Let's assume you have created a fork on Github -
[email protected]:yourGithubUsername/jbpm-playground.git.
and that you and your developers want to work primarily from the forked Github repo on a branch called "devBranch", but non-developers want to work primarily on the KIE Workbench.
You could manage that relationship between the Workbench's git repo and the upstream repo like this:
Initial setup
git clone [email protected]:yourGithubUsername/jbpm-playground.git
cd jbpm-playground
git branch devBranch
git checkout devBranch
git push origin devBranch
git remote add git-in-kiewb ssh://krisv@your-jbpm-server:8001/jbpm-playground
Getting changes by your non-developers from the git repo in KIE Workbench into your Github repo:
git pull git-in-kiewb master
git push origin devBranch
Getting changes by your developers from your Github repo into the git repo in KIE Workbench:
git pull origin devBranch
git push git-in-kiewb master
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With