Open voarsh2 opened 12 months ago
In the worse case, I will just take their official image and apply own modifications and see if that works. The only reason to build the image is to customise some aspects.
Thank you for your efforts and sharing. Please forgive me for being extremely anxious about Confluence's security issues in the past few days. I can only take a look at it on weekends or other times
In the worse case, I will just take their official image and apply own modifications and see if that works. The only reason to build the image is to customise some aspects.
A very nice idea. The previous leader attempted to crack the Docker image based on the official Jira/Confluence and automatically generate a license, which should have been successful. I remember he seemed to have shared it with me, but I was too busy during that time and forgot.
If the official Bitbucket image can be successfully cracked, it would be great!!!
@haxqer I hope you're not confusing "that" person - I fixed Bitbucket crack issues...
And that's not what's going on here, I'm simply having issues trying to install Bitbucket using the executable download's from Atlassian.
I would still prefer to be able to build it from source.
@voarsh2
Since 2017, I have been using the GitLab+Jira+Confluence+Jenkins toolchain, which is stable and easy to deploy. As an experienced user, I strongly recommend using GitLab instead of Bitbucket.
Sorry @haxqer.... maybe I'll just... migrate to Atlassian Cloud then!? (Sarcasm).
I have used GitLab since 2020... and know perfectly how good/bad it is, and moved to Bitbucket, because.... Atlassian ecosystem fits best for my use case, since I've been in it for over 5 years.... the only thing I didn't have was Bitbucket..........
I'm not asking for you to tell ME what product I should and shouldn't be using. All I was asking is if you could help build the Bitbucket 8.9 from source, as (as like for 7.21), I've already pointed out, building from source and having the required dependencies.
So far, you've not been able to help build 8.9, and if you can't/won't then I need to do as I said and use their own image and make customisation.... which isn't exactly what I wanted. I wanted to build it myself, not wait on Atlassian to build it..........
Hi @voarsh2!
I would be very grateful if you could help me solve a problem with activating Bitbucket!
I am able to activate the latest official Docker images of Confluence and Jira. For activation, I simply mounted the agent itself into the necessary directory in the container and added the argument 'JAVA_OPTS="-javaagent:/path/to/atlassian-agent.jar ${JAVA_OPTS}" in setenv.sh.
With Bitbucket, when I follow this instructions, I get the following error:
The following problem occurred which prevents Atlassian Bitbucket Server from starting correctly:
SpringMVC dispatcher [springMvc] could not be started."
@voarsh2 your modified agent worked even for this version! Thank you )
@voarsh2 your modified agent worked even for this version! Thank you )
@mrkhachaturov Glad my update to the agent helped you. I assume you mean this one? https://bamboo.hosttweb.com/browse/AA-AA-46/artifact/JOB1/jar/ - https://bitbucket.hosttweb.com/projects/AT/repos/atlassian-agent/browse
Glad my update to the agent helped you. I assume you mean this one? https://bamboo.hosttweb.com/browse/AA-AA-46/artifact/JOB1/jar/` - https://bitbucket.hosttweb.com/projects/AT/repos/atlassian-agent/browse
@voarsh2 yes exactly that repo. thank you again!
Can you please suggest activation steps in ubuntu? I cannot repeat activation in production environment now )) I have docker swarm, maybe later I will go to K8S, but now I want to test the work without docker.
The only difference on test VM, first I installed 8.15.1 after updated to 8.16.0 ( dark theme ready) . On the production VM I installed 8.16.0 and cannot load java agent to environment. If I am trying to add it in the _start-web.app getting error:
The following problem occurred which prevents Atlassian Bitbucket Server from starting correctly:
SpringMVC dispatcher [springMvc] could not be started."
On the test VM I have tried so many options before I activated, that even not sure which step helped me to activate )
First added this line to start-bitbucket.sh
export ATLASSIAN_DIR="/opt/atlassian/bitbucket/app/WEB-INF/lib"
after entered this command on shell
sudo -u atlbitbucket JAVA_OPTS="-javaagent:/opt/atlassian/atlassian-agent-jar-with-dependencies.jar" /opt/atlassian/bitbucket/8.16.0/bin/start-bitbucket.sh
After when trying to supply generated activation key, it is not working, I guess because java agent is not loaded to JAVA_OPTS.
ps aux|grep java
atlbitb+ 1303 0.4 8.3 6898528 1359036 ? Sl 02:38 1:06 /opt/atlassian/bitbucket/8.16.0/jre/bin/java -Xshare:auto -Dopensearch.networkaddress.cache.ttl=60 -Dopensearch.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -XX:+ShowCodeDetailsInExceptionMessages -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.locale.providers=SPI,COMPAT -Xms1g -Xmx1g -XX:+UseG1GC -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30 -Djava.io.tmpdir=/var/atlassian/application-data/bitbucket/tmp/search -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=data -XX:ErrorFile=logs/hs_err_pid%p.log -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m -XX:MaxDirectMemorySize=536870912 -Dopensearch.path.home=/opt/atlassian/bitbucket/8.16.0/opensearch -Dopensearch.path.conf=/var/atlassian/application-data/bitbucket/shared/search/config -Dopensearch.distribution.type=tar -Dopensearch.bundled_jdk=true -cp /opt/atlassian/bitbucket/8.16.0/opensearch/lib/* org.opensearch.bootstrap.OpenSearch -d -p /var/atlassian/application-data/bitbucket/log/search/opensearch.pid
atlbitb+ 1328 0.3 3.9 5622324 641348 ? Sl 02:38 0:44 /opt/atlassian/bitbucket/8.16.0/jre/bin/java -classpath /opt/atlassian/bitbucket/8.16.0/app -Datlassian.standalone=BITBUCKET -Dbitbucket.home=/var/atlassian/application-data/bitbucket -Dbitbucket.install=/opt/atlassian/bitbucket/8.16.0 -Dcom.sun.jndi.ldap.connect.pool.timeout=300000 -Xms512m -Xmx1g -XX:+UseG1GC -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -Djava.io.tmpdir=/var/atlassian/application-data/bitbucket/tmp -Djava.library.path=/opt/atlassian/bitbucket/8.16.0/lib/native;/var/atlassian/application-data/bitbucket/lib/native -XX:+IgnoreUnrecognizedVMOptions --add-opens=java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.naming/com.sun.jndi.ldap=ALL-UNNAMED com.atlassian.bitbucket.internal.launcher.BitbucketServerLauncher start
I just need to give permission to the agent folder. Activation works now!
Glad you fixed your own problem. I usually prefer VM's/docker-compose, or even Kubernetes Helm Chart for "production" style deployments. Makes managing much easier. But up to you. :)
@voarsh2 your modified agent worked even for this version! Thank you )
Ah ha, living on the edge by not using TLS releases? They broke the 1.3.1/1.3.3 agent after 7.21.X, keeping on non-LTS versions, you might find they break it again. Feel free to let me know if that happens.
Are there any chances this repo (and the corresponding image) will get updated to bitbucket 8?
Are there any chances this repo (and the corresponding image) will get updated to bitbucket 8?
I'm looking to build a new Dockerfile for Bitbucket 8.x soon as I am out of support
I'm looking to build a new Dockerfile for Bitbucket 8.x soon as I am out of support
I've made the modifications and updated the files for supporting 8.9x and 8.19.x LTR's (https://github.com/voarsh2/bitbucket-haxqer) and will submit a PR for @haxqer - until he applies and updates for image building on Dockerhub. I've settled for building the image when the docker-compose file is ran.
I have tested and confirmed that the 8.9.x Dockerfile and docker-compose file (PostgreSQL) installs and accepts a DC licence using the updated agent.
8.9.x+ is DC only, and does not allow MYSQL DB, so people would need to setup a PostgreSQL container and use the Bitbucket DB migrator tool
@haxqer I'm been struggling to build the 8.9 LTS (and 8.4 LTS I'm sure) Docker image for Bitbucket.
It starts, but complains about Mesh (the distributed GIT storage) - but it is disabled and opt-in. I can run the official Docker image with no problem. FYI, GIT 2.40+ is required for 8.9.5 +
Here's my take on the Dockerfile:
Here's the error from the container: