Hybris deployment is not working as expected via Bamboo to new Ubuntus 22.04 version and the same is working with Ubuntu 18.04 version. During hybris build process required backoffice related folders are not getting created. The same is working with ubuntu 18.04 version
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
According to the Bamboo remote agent installation guide, mixing operating systems between Bamboo Server and Remote Agents is supported and possible as long as it’s running on a supported Operating System and Java version. See here:
https://community.atlassian.com/t5/Bamboo-questions/Recommended-software-upgrade-path-from-bamboo-6-9-1-to-8-8-1-8-2/qaq-p/2028335
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's a pretty old version (6.9.1) ... from 2019 if I recall correctly. Can't you upgrade to "latest"?
See the compatibility matrix for 6.9:
https://confluence.atlassian.com/bamboo0609/installing-and-upgrading/supported-platforms
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the backoffice folders are not being created, check that the agent is running with the appropriate permissions on the appropriate folders where the deployment is expected to happen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the latest version backwards compatible with Ubantu 18.04? We have mix environment, many servers still on Ubantu 18.04. The new ones are Ubantu 22.04.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think there's no strict dependency on the OS version itself. If the Java version you are using is compatible with the OS version, then you should be fine.
Have you checked folder user permissions as mentioned above?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We checked by Logging on to the server with the same account Bamboo is using and worked fine manually. Not working through deployment scripts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you sure Bamboo is running with the Bamboo user you think it is running? I've seen cases of misconfigured Service accounts running with the wrong user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Would you guide me how to check? The person who setup Bamboo is not available.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The easiest way to see under which user Bamboo is running is to run a deployment, and on another terminal, to check which user ID is being used to run the Bamboo automation, you can log in to the server where Bamboo is installed and run the command "ps aux | grep bamboo"
.
This will show you the processes related to Bamboo and the user ID associated with each process.
Since you are running Bamboo on Linux, you can check the user by looking at the init script that starts Bamboo. The script is typically located in /etc/init.d/
or /etc/init/
and should contain a line that specifies the user, such as USER=bamboo
. You can also check the ownership of the Bamboo home directory and its files to see which user owns them.
Please let me know if this helps or if you have any further questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Additionally, changing the user can affect Bamboo’s integration with other systems, such as source code repositories or issue trackers. If Bamboo uses SSH keys or other credentials to authenticate with these systems, you may need to update the keys or credentials to ensure that they are accessible to the new user.
It is important to carefully plan and test any changes to the user under which Bamboo runs to avoid disruptions to your build and deployment processes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank You. We are checking and will update the ticket on findings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.