Brent P Atlassian Team

Comments

  • @chihara Thanks a ton for reporting this problem. I created BSERV-19543 and attached the 9.0.0 SBOM to that issue (if the direct link doesn't work, see the "Workaround" section or "Attachments"). We've already made the required fix and SBOMs will be included with Bitbucket DC 9.0.1+.
  • Hi @Edie Uwase, Are you using an SSH access key when pushing instead of a personal SSH key? Because SSH access keys are intended for system use, the "Verify Commit Signature" hook allows them to push commits that aren't signed. Unfortunately, we haven't documented that anywhere. I've just made some changes to our "Using…
  • We added the ability to have default reviewers per branch in Bitbucket Server 4.8: https://confluence.atlassian.com/bitbucketserver/add-default-reviewers-to-pull-requests-834221295.html
  • We intend to improve the backup client to allow for scripted backups with the potential for significantly reduced downtime. This would be achieved by taking advantage of database/filesystem snapshots and/or iterative copying (such as rsync) that may be available in the underlying storage infrastructure.
  • Keep in mind that GitHub's "check out this PR" is just checking out the source branch. Nicola's article shows how to use Stash to pull the result of the PR merge (ie. what the target branch will look like if the PR is merged). It's a subtle but important difference.
  • The backup client backs up data in the database that your Stash server is currently connected to - whether it's an internal or external database. In your case, backups will include the data in your Oracle database. The JDBC restore properties are ignored when backing up. Sorry for the confusion. We'll make some changes to…
  • Hi Rich, There are two users involved in the backup: * The OS user that runs the backup client - This user needs to have ownership of the Stash home directory. * A user in Stash with system admin privileges - The backup client uses this user's credentials to lock Stash and request a database backup. It sounds like you've…
  • Hi Michael, There is no way to tell the backup client to backup only the database or only repositories. The backup client is intended to backup the entire Stash server and it's crucial that the database and repositories are in-sync with each other. We investigated a number of backup methods when writing the backup client,…
  • It's difficult to tell without more information. Could you please raise a support request so we can confidentially gather information about your system and log files, etc? https://support.atlassian.com/servicedesk/customer/portal/24
  • @Aleksey Misyuk - It's difficult to tell without more information. Could you please raise a support request so we can confidentially gather information about your system and log files, etc https://support.atlassian.com/servicedesk/customer/portal/24
  • There's a note on the Stash upgrade guide about this: If upgrading from a previous version of Stash where the Stash home directory is owned by a local user, the ownership of all files will be updated to atlstash . Please allow sufficient time for the installer to complete this process (it could take up to 30 minutes). It…
  • That error appears to have something to do with long paths (>100 characters long). We are accomodating for long paths, but clearly something isn't working. Could you please raise a Stash support request and post the backup client's logs (in the backup client "logs" directory)? I'll investigate as soon as I see the logs.…