However, when Bytebase developed this feature, the latest major version was GitLab 13. And last week, we received an issue report telling our VCS integration is broken, and it turns out it's related to the default OAuth token expiration change introduced in GitLab 14.3 If visitor clicks the commit hash, she will be navigated to that GitLab commit triggering the Bytebase pipeline.īesides complementing our demo, our GitLab instance is also used by our team members to work on GitLab integration features. And we did curate the demo data to let our potential customers better understand our VCS integration feature. User can visit our live demo site from the landing page. We have native VCS integration with GitLab CE/EE from day 1.
Please don't repeat our mistake Backgroundīytebase is an open source database schema change and version control tool for teams. We made the mistake of not reading the GitLab upgrade guide carefully, thus having the extra step 4 and 5. You can jump to the Major Upgrade section if you just want to learn the upgrade steps. (Though we are conducting a GitLab EE upgrade from version 13 to 14, the following steps should apply to GitLab CE / other major version upgrade as well)
Conducting a major version upgrade of a self-managed software is always like a shitshow.
0 kommentar(er)
