I followed the upgrade instructions for Bitbucket but despite that the old Stash Windows service was not uninstalled and replaced with a new Bitbucket service as I would have expected. Or at least I would think that the old service will be starting the new version. However, to run Bitbucket currently on my server I have to manually stop the old service and then run the startup_bitbucket.bat from the installation directory to make it run. Jira service works correctly as before the upgrade.
May I ask you, if you tried to do the steps that are listed in this documentation?
Thanks Johannes. That was part of the problem. For some reason, I'm having, on that particular system, problems with server variables set to JDK as opposed to JRE or vice versa. I'm running 4 Atlassian products on that machine and it seems that much earlier in time they did not like sitting next to each other too much. :) I usually have to fiddle with the environment variables as well as reinstalling the services manually. But since I do not have 2 days to play with this every time I upgrade I do upgrade at most once a year and by then I can't even remember what was wrong before. And since I do not know much about JAVA I usually need help unfortunately. Once again, thanks for yours. We solved it with the help of Atlassian Support.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot