Ross,

Take a look at BSERV-8145. I wrote that 5.7 would remain unsupported in February of 2014. It remained unsupported at that time because the only releases available then were prereleases, not GA. After 5.7 went GA, it was added to backlog for support, which ships in 4.10.

Best regards,
Bryan Turner
Atlassian Bitbucket

I'm looking for more information on why 5.7 will remain unsupported. The comments above do not make this clear.

Good news, everyone! /farnsworth

MySQL 5.6.16 is now available for download, and finally passes Stash's database test suite. Stash 2.11 will be the first version to add support for MySQL 5.6.16+. Note that 5.7 (all current versions) will remain unsupported.

Best regards,
Bryan Turner
Atlassian Stash

Patrick,

The property has not been removed or modified for 2.10.1, and my testing shows it still works as intended (I'm able to start 2.10.1 on MySQL 5.6.15 with the flag set). The flag only allows you to start on an unsupported database. Migrating to one, or selecting one during initial setup, is still not possible. You must manually configure unsupported databases.

Do you see this in your logs?

2014-01-23 08:27:23,400 WARN  [localhost-startStop-1]  c.a.s.i.db.DefaultDatabaseSupplier Not checking database support level; the check has been disabled

If you continue to have issues, please open a ticket at support.atlassian.com and our support engineers will help address it.

Best regards,
Bryan Turner
Atlassian Stash

Seems like jdbc.ignoreunsupported=true doesn't bypass the database support check in Atlassian Stash v2.10.1. If the functionality of this flag was removed, should it be removed from the Stash documentation (https://confluence.atlassian.com/display/STASH/Stash+config+properties)? Or perhaps that is just a bug?

All,

The utf8_bin collation bug was marked fixed in 5.6.15 but is not fixed. I have reopened the issue and hopefully someone from MySQL will respond soon. Stash's test suite continues to fail on MySQL 5.6.15, so it will remain an unsupported platform.

Sorry all,
Bryan Turner
Atlassian Stash

Stefan.

Fortunately, that flag is already available; I introduced it at the same time I added the hard check. You can add the following to stash-config.properties:

jdbc.ignoreunsupported=true

Best regards,
Bryan Turner
Atlassian Stash

Edit: Note We will not provide database-related support for any issues encountered while this is set and an unsupported database is being used. This flag exists purely for the situation where there is no possible alternative other than an unsupported database.

Hi
could you please add a command line switch (or config file switch) to allow stash on "unsupported" mysql versions (instead of the compiled "abort")? (similar to "allow openjdk" on earlier bamboo/jira/confluence versions).
Unfortunately, our DBA upgraded all our databases to mysql 5.6, and now i can not run stash anymore.
Apart from a "ordering" problem, stash should be running fine with mysql 5.6.14. Having only one project in stash, the order of projects does not matter at all

As nobody knows how long it may take until mysql 5.6.15 is available for download, having this command line option in stash would help a lot.

Regards,
Stefan

All,

The utf8_bin collation bug has been marked as fixed/verified for MySQL 5.6.15. As soon as I can download that and run our test suite against it (while the issue is marked fixed, the download site is still showing 5.6.14 as the latest release), assuming our test suite confirms the fix, I will mark 5.6.15+ as supported for Stash. If I can verify it soon enough, MySQL 5.6 support may ship with Stash 2.9.

Note that all existing releases of 5.7 will remain unsupported. We won't support any builds of that prior to an official GA.

Best regards,
Bryan Turner
Atlassian Stash

Nathan,

Unfortunately, I have run our matrix against MySQL 5.6.14 and the ordering bug remains unfixed. Per the latest comments, the "utf8_bin" collation remains broken. Stash requires that collation, so still no joy on MySQL 5.6 support.