Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/liquibase/liquibase
Main Liquibase Source
https://github.com/liquibase/liquibase
continuous-delivery continuous-deployment database database-administration database-management database-migrations db2 devops hacktoberfest java java-library liquibase mariadb mysql oracle sql sqlserver
Last synced: 4 days ago
JSON representation
Main Liquibase Source
- Host: GitHub
- URL: https://github.com/liquibase/liquibase
- Owner: liquibase
- License: apache-2.0
- Created: 2011-07-08T20:08:20.000Z (over 13 years ago)
- Default Branch: master
- Last Pushed: 2024-12-06T13:08:50.000Z (7 days ago)
- Last Synced: 2024-12-06T13:49:30.224Z (7 days ago)
- Topics: continuous-delivery, continuous-deployment, database, database-administration, database-management, database-migrations, db2, devops, hacktoberfest, java, java-library, liquibase, mariadb, mysql, oracle, sql, sqlserver
- Language: Java
- Homepage: https://www.liquibase.org
- Size: 204 MB
- Stars: 4,777
- Watchers: 138
- Forks: 1,869
- Open Issues: 633
-
Metadata Files:
- Readme: README.md
- Changelog: changelog.txt
- License: LICENSE.txt
- Code of conduct: CODE_OF_CONDUCT.md
- Codeowners: .github/CODEOWNERS
- Security: SECURITY.md
Awesome Lists containing this project
- awesome-mysql - Liquibase - Source control for your database (Development)
- jimsghstars - liquibase/liquibase - Main Liquibase Source (Java)
README
# Liquibase [![Build and Test](https://github.com/liquibase/liquibase/actions/workflows/build.yml/badge.svg)](https://github.com/liquibase/liquibase/actions/workflows/build.yml) [![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=liquibase&metric=alert_status)](https://sonarcloud.io/summary/new_code?id=liquibase)
Liquibase helps millions of developers track, version, and deploy database schema changes. It will help you to:
- Control database schema changes for specific versions
- Eliminate errors and delays when releasing databases
- Automatically order scripts for deployment
- Easily rollback changes
- Collaborate with tools you already useThis repository contains the main source code for Liquibase Open Source. For more information about the product, see the [Liquibase website](https://www.liquibase.com/).
## Liquibase Automation and Integrations
Liquibase Open Source has built-in support for a variety of databases. Databases that are not part of Liquibase Open Source require extensions that you can download for free. Here is the full list of [supported databases](https://www.liquibase.com/supported-databases).
Liquibase can be integrated with Maven, Ant, Gradle, Spring Boot, and other CI/CD tools. For a full list, see [Liquibase Tools & Integrations](https://docs.liquibase.com/tools-integrations/home.html). You can use Liquibase with [GitHub Actions](https://github.com/liquibase/liquibase-github-action-example), [Spinnaker](https://github.com/liquibase/liquibase-spinnaker-plugin), and many different [workflows](https://docs.liquibase.com/workflows/home.html).
## Install and Run Liquibase
### System Requirements
Liquibase system requirements can be found on the [Download Liquibase](https://www.liquibase.com/download) page.### An H2 in-memory database example for CLI
1. [Download and run the appropriate installer](https://www.liquibase.com/download).
2. Make sure to add Liquibase to your PATH.
3. Copy the included `examples` directory to the needed location.
4. Open your CLI and navigate to your `examples/sql` or `examples/xml` directory.
5. Start the included H2 database with the `liquibase init start-h2` command.
6. Run the `liquibase update` command.
7. Run the `liquibase history` command to see what has executed!See also how to [get started with Liquibase in minutes](https://docs.liquibase.com/start/home.html) or refer to our [Installing Liquibase](https://docs.liquibase.com/start/install/home.html) documentation page for more details.
## Documentation
Visit the [Liquibase Documentation](https://docs.liquibase.com/home.html) website to find the information on how Liquibase works.
## Courses
Learn all about Liquibase by taking our free online courses at [Liquibase University](https://learn.liquibase.com/).
## Want to help?
Want to file a bug or improve documentation? Excellent! Read up on our guidelines for [contributing](https://contribute.liquibase.com/)!
### Contribute code
Use our [step-by-step instructions](https://contribute.liquibase.com/code/) for contributing code to the Liquibase open source project.
### Join the Liquibase Community
Earn points for your achievements and contributions, collect and show off your badges, add accreditations to your LinkedIn. [Learn more about the pathway to Legend and benefits](https://www.liquibase.com/community/liquibase-legends). Enjoy being part of the community!
## Liquibase Extensions
[Provide more database support and features for Liquibase](https://contribute.liquibase.com/extensions-integrations/directory/).
## License
Liquibase Open Source is [licensed under the Apache 2.0 License](https://github.com/liquibase/liquibase/blob/master/LICENSE.txt).
[Liquibase Pro](https://www.liquibase.com/products/pro) has additional features and support and is commercially licensed.
LIQUIBASE is a registered trademark of [Liquibase Inc.](https://www.liquibase.com/company)
## [Contact us](https://www.liquibase.com/contact)
[Liquibase Forum](https://forum.liquibase.org/)
[Liquibase Blog](https://www.liquibase.com/blog)
[Get Support & Advanced Features](https://www.liquibase.com/pricing)
## Publish Release Manual Trigger to Sonatype
1. When a PO (Product Owner) or a Team Leader navigates to Publish a release from here -> https://github.com/liquibase/liquibase/releases/, the workflow from /workflow/release-published.yml job is triggered.
2. When a release is triggered, the workflow file will stop after `Setup` step and an email will be sent out to the list of `approvers` mentioned in job `manual_trigger_deployment`. You can click on the link and perform anyone of the options mentioned in description.
3. A minimum of 2 approvers are needed in order for the other jobs such as `deploy_maven`, `deploy_javadocs`, `publish_to_github_packages`, etc to be executed.
4. When you view the GitHub PR, make sure to verify the version which is being published. It should say something like `Deploying v4.20.0 to sonatype`