Re: CI/CD Tools

Liquibase can do SQL format changelogs also: https://docs.liquibase.com/concepts/basic/sql-format.html

I use Liquibase SQL format and jenkins to execute liquibase automatically, when changes gets merged in git to the correct release branch. Having good discipline in GIT I think is the most important part here. What I currently do is (enforced rules):
* master branch is used for integrations - jenkins executes automatically and pushes changes to very simple integration test database just to check out that the changes are valid and work
* merges to master require a pull request, reviewed and approved by someone * then changes are merged from master to release branches - release/dev -> release/pt1 -> release/prod. there are jenkins jobs/pipelines listening on changes to each of the brances - triggering liquibase run in the correct environment.

On Fri, Jan 15, 2021 at 7:36 PM Jeff Chirco <backseatdba_at_gmail.com> wrote:

> For those that are, what are you using for Continuous
> Integration/Development in your shop? We are starting to look for some. We
> have a good manual system where all changes get deployed by calling a
> single "install.sql" file, that file calls other files to compile packages,
> modify data and tables,etc but if gives us the DBA a single file to run.
> And we use Git but I would really like to get to the point where we can
> approve changes and then they automatically get deployed when the
> developers want them instead of us always having to run them. It does sound
> kind of scary for things to run on their own but I think we need to get
> there.
> We do a lot of custom development and have a single database that runs
> many different applications with many different schemas. So those pay per
> schemas would not work well for us. There are times where we are doing 10
> or more updates in a day, some big some are single file changes, again
> across different applications. We have another smaller database that is
> also set up similar.
>
> We are looking at Flexdeploy. I did not like Liquabase and having to have
> everything in XML files, that seems like it would cause more work. I know
> there is Jenkins and one of our developers is looking at that.
>
> Let me know what you use or the pros and cons of the whole idea.
>
> Jeff
>

-- 
Ilmar Kerm

--
http://www.freelists.org/webpage/oracle-l