Introduce Phive about shopware

[szepeviktor]

After that you may consider reducing the repo size by removing those tools https://help.github.com/en/articles/removing-sensitive-data-from-a-repository

[mitelg]

hey @szepeviktor
I'm currently working on moving our CI tooling from platform to the development template. so the main repo size will be decreased. I will take your issue and your PR into account 👍
thanks for your contribution

[szepeviktor]

All right.

[szepeviktor]

moving our CI tooling from platform to the development template

@mitelg Does it mean that platform contribution (PR-s) won't be checked?

[mitelg]

just a little hint 😊 as we are shortly before our first release, it will may take some time, as I don't want to struggle up our CI pipeline before the release 😉

[mitelg]

@mitelg Does it mean that platform contribution (PR-s) won't be checked?

Currently there are no checks here on github anyway 😁 all checks are done internally on bitbucket and bamboo.
I will take that to my task 😉

[szepeviktor]

What a shame! You develop modern code and use Atlassian products? No words can describe their quality.

[szepeviktor]

I don't want to struggle up our CI pipeline before the release 😉

My base package for developer teams includes these 3 zero-coverage tests:

1. parallel syntax check
2. coding standards check (this check can do much more than its name suggests, e.g. find var_dump-s or detect dead code)
3. static analysis

It costs nearly nothing to introduce them, and keeps your code quality very high even if you don't have time to write unit/functional tests.

[mitelg]

Don't get me wrong here, we already use these tools 😊
but if I now move phar files from here to there, or introduce phive, I have to adjust our CI. and this is mostly not done in five minutes 😉

[janbuecker]

What a shame! You develop modern code and use Atlassian products? No words can describe their quality.

We have plans to migrate to an internal GitLab instance and we may can use parts of it's CI configuration for travis ci like we are doing with Shopware 5.

[janbuecker]

Some weeks ago, we've evaluated phive as replacement for the phar files. At the end of the day, the key servers are really unreliable and not all tools are available with a signature, which does not make much sense right now. We'll keep an eye on phive and once it's more mature, we'll evaluate it again.