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

Orka: packer macos11 intel test #3874

Closed

Conversation

UlisesGascon
Copy link
Member

Main Changes

  • Add support for SSH Connection using the default credentials.
  • Use a custom base image developed by us.
  • Add steps for installing Homebrew and basic dependencies.

Related

@UlisesGascon UlisesGascon changed the title Feat/packer macos11 intel test Orka: packer macos11 intel test Aug 27, 2024
@UlisesGascon UlisesGascon marked this pull request as ready for review August 27, 2024 22:47
@UlisesGascon UlisesGascon self-assigned this Aug 27, 2024
@targos
Copy link
Member

targos commented Aug 28, 2024

Didn't we agree on not migrating macOS to 11 but skipping directly to 13 instead?

@UlisesGascon
Copy link
Member Author

UlisesGascon commented Aug 28, 2024

Didn't we agree on not migrating macOS to 11 but skipping directly to 13 instead?

We will skip MacOS 12 for sure, but we need to migrate the current Orka workload (MacOS 10.15 and MacOS 11) to the new cluster, so all the infra in Orka will be ephemeral instances controlled directly by Jenkins.

Good recap in our last meeting (minute 33:19)

@targos
Copy link
Member

targos commented Aug 28, 2024

Ok, I won't object if you want to maintain 10.15 and 11, but I would be in favor of dropping them entirely. The build policy allows to do it for EoL platforms.

@UlisesGascon
Copy link
Member Author

Ok, I won't object if you want to maintain 10.15 and 11, but I would be in favor of dropping them entirely. The build policy allows to do it for EoL platforms.

Oh! I love the idea a lot. I was purely thinking about the migration. I didn't realize that we are "open" to dropping support. Let me create an issue for better visibility, and let's see if the team agrees on dropping support. 👍

@UlisesGascon
Copy link
Member Author

As discussed in #3876. I will close this PR now.

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