bluesoft / bee Goto Github PK

Windows .bat script doesn't scan for lib jars, so you need to set the CLASSPATH variable manually

Create a maven plugin to include bee tasks on build cicle

create a command line like bee init to setup all necessary configurations to start using bee in a new project

relates to #31
homebrew PR, Homebrew/homebrew-core#39792

relates to Homebrew/homebrew-core#39792

failure build: https://jenkins.brew.sh/job/Homebrew%20Core%20Pull%20Requests/41891/version=mojave/console

==> /usr/local/Cellar/bee/1.68/bin/bee -d /private/tmp/bee-test-20190513-3200-y6qe9u/bee dbchange:create new-file
Picked up _JAVA_OPTIONS:  -Duser.home=/Users/brew/Library/Caches/Homebrew/java_cache
Bee - v. 1.68 - Bluesoft (2013-2019) - GPL - All rights reserved
Exception in thread "main" java.lang.NullPointerException: Cannot invoke method validateParameters() on null object
	at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:91)
	at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:43)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:34)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:119)
	at br.com.bluesoft.bee.runner.BeeModule.parseOptions(BeeModule.groovy:16)
	at br.com.bluesoft.bee.runner.BeeModule$parseOptions$0.callCurrent(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:156)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:168)
	at br.com.bluesoft.bee.runner.BeeModule.run(BeeModule.groovy:25)
	at br.com.bluesoft.bee.runner.BeeModule$run.call(Unknown Source)
	at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:115)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:127)
	at br.com.bluesoft.bee.Bee.main(Bee.groovy:103)
Error: bee: failed

We have some tests with names in Portuguese. We should translate the methods to English. E.g.,

@Test
def "deve pegar a última versão e ela deve ser igual à versão retornada no módulo BeeVersionModule"() {

Should be

@Test
def "must get the latest version and it must match the version returned by BeeVersionModule"() {

It would be cool if we could execute bee in all defined databases at once. Especially if we think about schema/database multi-tenancy. The commands that I'd use are:
dbchange:up
dbchange:down
data:validate
schema:validate

The ideal is to run simultaneously, for better performance (maybe even offering the option to configure the number of threads). Something like:
bee dbchange:up -a, to run in every database
bee dbchange:up -a 5 to run in every database, with 5 parallel threads

If there were errors, the log would be divided by database.
Example:
DATABASE_1
WARNING: Failed to execute: alter TABLE table change id id int (11);

DATABASE_2
WARNING: Failed to execute: alter TABLE table change id id int (11);

Existem cenários em que alguns dbchanges devem ser executados antes de enviar atualização de código, enquanto alguns devem ser executados apenas depois que todos os servidores já estiverem com a nova versão do sistema.

Pensei em resolver isso oferecendo a possibilidade de criar/executar dbchanges por grupos.

Algo como:
bee dbchange:create banco nome-do-dbchange -g NOME_DO_GRUPO
e para executar:
bee dbchange:up banco -g NOME_DO_GRUPO

No cenário explicado acima, poderíamos separar os dbchanges nos grupos "pre-deploy" e "post-deploy" e executar apenas o grupo necessário.

Seria interessante receber um arquivo de exemplo bee.properties ao baixar novas versões do projeto.

Obrigado

Publish Bee on Brew to easy install

The dbschema:generate and dbchema:validate only works on Oracle and MySql databases

Oracle allows you to create an object (procedures, packages, etc) even in invalid state. Then when you make a call to any of this Oracle raise an error.
Bee could check after an object creation either it's valid or invalid and show an Error. DBA_OBJECTS stores this kind of information and can be used for this purpose.

if I insert a new blank line in the end of the data file, bee validate schema with this message
'This line was found in the schema [tipo_conta_bancaria] but was not found in the database:[null]'

Bee should be smart enough to ignore blank lines during data validation.

We have a MySQL database with more than 200 schemas with more than 100 tables each.
When we try to run bee schema:validate in any of them, it takes more than 5 minutes to run (I actually had to stop the process after 5 minutes, because it was afecting the database performance, so I don't know exactly how much time it would take).

The same doesn't happen if we try in our test MySQL database, which only have 10 schemas (with the same number of tables).

fix coverage plugin to monitor coverage in new PRs

make bee hold transaction until dbchange success