Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle ubuntu 20.04 deprecation #11354

Merged
merged 10 commits into from
Mar 4, 2025
Merged

handle ubuntu 20.04 deprecation #11354

merged 10 commits into from
Mar 4, 2025

Conversation

emmyoop
Copy link
Member

@emmyoop emmyoop commented Mar 4, 2025

Problem

ubuntu 20.04 is EOL and GHA support is ending

Solution

Switch to use the GH runner postgres container for linux but continue the more manual docker setup for windows + macos. Windows/macos can't use the GHA service containers. However ubuntu-24.04 is causing some permission issues we're having trouble figuring out.

Note: this solution requires updates to dbt-releases since it deletes the action. We need to update that repo anyways though since it uses 20.04.

Checklist

  • I have read the contributing guide and understand what's expected of me.
  • I have run this code in development, and it appears to resolve the stated issue.
  • This PR includes tests, or tests are not required or relevant for this PR.
  • This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
  • This PR includes type annotations for new and modified functions.

@cla-bot cla-bot bot added the cla:yes label Mar 4, 2025
Copy link
Contributor

github-actions bot commented Mar 4, 2025

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

Copy link

codecov bot commented Mar 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.89%. Comparing base (94b6ae1) to head (63faea8).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #11354      +/-   ##
==========================================
- Coverage   88.91%   88.89%   -0.02%     
==========================================
  Files         190      190              
  Lines       24197    24197              
==========================================
- Hits        21514    21510       -4     
- Misses       2683     2687       +4     
Flag Coverage Δ
integration 86.10% <ø> (-0.08%) ⬇️
unit 62.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Unit Tests 62.59% <ø> (ø)
Integration Tests 86.10% <ø> (-0.08%) ⬇️

@emmyoop emmyoop added the Skip Changelog Skips GHA to check for changelog file label Mar 4, 2025
@emmyoop emmyoop force-pushed the er/ubuntu-deprecation-service branch from d8b9e10 to 63faea8 Compare March 4, 2025 17:32
@emmyoop emmyoop changed the title Er/ubuntu deprecation service hanfle ubuntu 20.04 deprecation Mar 4, 2025
@emmyoop emmyoop changed the title hanfle ubuntu 20.04 deprecation handle ubuntu 20.04 deprecation Mar 4, 2025
@emmyoop emmyoop marked this pull request as ready for review March 4, 2025 18:41
@emmyoop emmyoop requested a review from a team as a code owner March 4, 2025 18:41
@emmyoop emmyoop merged commit 77d8e32 into main Mar 4, 2025
58 checks passed
@emmyoop emmyoop deleted the er/ubuntu-deprecation-service branch March 4, 2025 18:41
Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.7.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-11354-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest

Then, create a pull request where the base branch is 1.7.latest and the compare/head branch is backport-11354-to-1.7.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.8.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.8.latest 1.8.latest
# Navigate to the new working tree
cd .worktrees/backport-1.8.latest
# Create a new branch
git switch --create backport-11354-to-1.8.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.8.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.8.latest

Then, create a pull request where the base branch is 1.8.latest and the compare/head branch is backport-11354-to-1.8.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.3.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3.latest 1.3.latest
# Navigate to the new working tree
cd .worktrees/backport-1.3.latest
# Create a new branch
git switch --create backport-11354-to-1.3.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.3.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3.latest

Then, create a pull request where the base branch is 1.3.latest and the compare/head branch is backport-11354-to-1.3.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.6.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-11354-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest

Then, create a pull request where the base branch is 1.6.latest and the compare/head branch is backport-11354-to-1.6.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.5.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.5.latest 1.5.latest
# Navigate to the new working tree
cd .worktrees/backport-1.5.latest
# Create a new branch
git switch --create backport-11354-to-1.5.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.5.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.5.latest

Then, create a pull request where the base branch is 1.5.latest and the compare/head branch is backport-11354-to-1.5.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.4.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.4.latest 1.4.latest
# Navigate to the new working tree
cd .worktrees/backport-1.4.latest
# Create a new branch
git switch --create backport-11354-to-1.4.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.4.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.4.latest

Then, create a pull request where the base branch is 1.4.latest and the compare/head branch is backport-11354-to-1.4.latest.

Copy link
Contributor

github-actions bot commented Mar 4, 2025

The backport to 1.9.latest failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.9.latest 1.9.latest
# Navigate to the new working tree
cd .worktrees/backport-1.9.latest
# Create a new branch
git switch --create backport-11354-to-1.9.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 77d8e3262a1b8b54eed6386c9b9841b73b080366
# Push it to GitHub
git push --set-upstream origin backport-11354-to-1.9.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.9.latest

Then, create a pull request where the base branch is 1.9.latest and the compare/head branch is backport-11354-to-1.9.latest.

emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml
#	.github/workflows/structured-logging-schema-check.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
emmyoop added a commit that referenced this pull request Mar 4, 2025
* handle ubuntu 20.04 deprecation (#11354)

* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml

* remove entire action
emmyoop added a commit that referenced this pull request Mar 4, 2025
* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
emmyoop added a commit that referenced this pull request Mar 4, 2025
* handle ubuntu 20.04 deprecation (#11354)

* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml

* upgrade ubuntu
emmyoop added a commit that referenced this pull request Mar 4, 2025
* handle ubuntu 20.04 deprecation (#11354)

* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml

* upgrade ubuntu
emmyoop added a commit that referenced this pull request Mar 4, 2025
* handle ubuntu 20.04 deprecation (#11354)

* update ubuntu 20.04 to 24.04

* updates to ubuntu-latest instead

* try postgres update

* Change owner of db creation script so postgres can run it.

* Add sudos.

* Add debug logging.

* Set execute bit on scripts.

* More debug logging.

* try a service

* clean up and split the integrations tests by os

---------

Co-authored-by: Peter Allen Webb <[email protected]>
# Conflicts:
#	.github/actions/setup-postgres-linux/action.yml
#	.github/workflows/main.yml
#	.github/workflows/structured-logging-schema-check.yml

* conflict fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants