I am new here. How to configure PHP UNIT with Bamboo? Any Idea, I wasn't able to find out a proper documentation for this.
Thank you in advance
It would be better if you do little research about your problem and then post a more precise problem here.
Here you go:
https://confluence.atlassian.com/display/BAMBOO/Getting+started+with+PHP+and+Bamboo
ALSO
While setting Executable path you have to set path as: path/to/executable(phpunit folder).cmd
and not just:
path/to/executable(phpunit folder)
Related
Is it possible to use Symfony CLI command (ex: php bin/console translation:update --force -en) to build translation if I use a constant in a translator like that:
$translator->trans(self::ANY_CONSTANT);
That doesn't work for me now... But, if I put a string on it, that's work!
I am using Symfony 5 with twig.
I am not used Symfony for long and english is my second language, so, please, be indulgent.
Thanks in advance for your answers. ;)
PS: I did many research before asking this question. I found many things about translation, but no good information about how work this CLI command.
Translator and Console are two different component of symfony. Problem doesn't come from Console, please check if your CONSTANT value is an existing translation key.
If you got an error, please put here also your error message
I just created a new symfony3.2.6. project and added a few vendors (FOS User Bundle, Propel2 and Twig) but no new console seem to be available. At least I do not see any of them when using 'app/console' or 'bin/console' command.
/app/autoload.php is loaded from the console-file which also seems to load the /vendor/autoload.php file.
Are you able to give me a hint on what I might have done wrong?
Thanks a lot!
Steffen
figured it out. The problem was a wrong version-requirement description on packagist.org THANKS FOR YOUR HELP!!!
Everyone.
I want to create plugin as the introduction told. Adding a new API module, but I got this error.
Any idea to solve this problem?
Please make sure to enable development mode:
./console development:enable
I wasn't certain whether to put this question on stackoverflow or serverfault, but I think it is more coding related than IT infrastructure related.
I'm adding a new Neutron L3 plugin and have attempted to mimic the functionality of a few good examples thus far. My problem is here: while my config file is following the same naming conventions/locations, I keep having empty strings returned from Oslo Config.
Edit: my plugin myapp is in /opt/stack/neutron/neutron/plugins/ml2/drivers/myapp and my configuration file ml2_conf_myapp.ini is in /opt/stack/neutron/etc/neutron/plugins/ml2/.
How do you specify to Oslo config where to find new plugin configuration files and what their names are?
Thank you!
I ended up solving this issue by reading through the code in devstack/lib/neutron.
In devstack/local.conf, you can set the variables Q_PLUGIN_EXTRA_CONF_FILES and Q_PLUGIN_EXTRA_CONF_PATH.
In my case, I have:
ML2_L3_PLUGIN=neutron.plugins.ml2.drivers.myapp.myapp
Q_PLUGIN_EXTRA_CONF_FILES+="myapp_conf.ini"
Q_PLUGIN_EXTRA_CONF_PATH="$DEST/neutron/neutron/plugins/ml2/drivers/myapp"
Now Oslo is able to pick up the configurations.
I hope this helps someone else save some work.
i´ve just installed the ChillDevProxyTemplating Bundle for symfony2, described here:
https://github.com/chilloutdevelopment/ChillDevProxyTemplatingBundle/blob/master/Resources/doc/installation.md
My templates was rennamed correctly by the bundle (from 'default' to 'php'), but when i try to call my controller I get the following error:
Cannot import resource "." from (...)app/cache/dev/assetic/routing.yml". (The following loader(s) are not registered: default).
Has anyone an idea how to fix??
Thanks a lot !
As explained here: https://github.com/chilloutdevelopment/ChillDevFileManagerBundle/issues/27
You might just need to install ChillDevViewHelpersBundle to get it working.
I previously added answer to this question, but it was removed by moderator since my reputation was not high enough to post a comment.
But now thanks to support of community I was able to investigate this problem:
https://github.com/chilloutdevelopment/ChillDevProxyTemplatingBundle/issues/2
It's now fixed :). Thank you for pointing the problem.
The problem was, that Assetic, in dev environment tries to parse all the templates based on templating engine name so it needs loader for each templating engine - of course for "default" there was no loader and thus caused an exception.