We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to the complexity of this PR – jenkins-infra/packer-images#1430
We are splitting the tasks into 4 stages, this issue is related to adding Win-19, Win-22 (AMD64 and ARM64) AMIs for our jenkins EC2 agents.
We are reintroducing the amazon logic that we were using with our previous AWS jenkins account – jenkins-infra/packer-images#734
build-jenkins-agent-windows.pkr.hcl
datasources.pkr.hcl
windows-2019
windows-2022
windows_winrm_user
locals.pkr.hcl
amazon-ebs
sources.pkr.hcl
Originally posted by @jayfranco999 in #4316 (comment)
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
No branches or pull requests
Due to the complexity of this PR – jenkins-infra/packer-images#1430
We are splitting the tasks into 4 stages, this issue is related to adding Win-19, Win-22 (AMD64 and ARM64) AMIs for our jenkins EC2 agents.
We are reintroducing the amazon logic that we were using with our previous AWS jenkins account – jenkins-infra/packer-images#734
build-jenkins-agent-windows.pkr.hcl
datasources.pkr.hcl
to look-upwindows-2019
andwindows-2022
AMI ids for respective architecturewindows_winrm_user
inlocals.pkr.hcl
as administrator foramazon-ebs
since admin permissions are required to ssh our windows ec2 agentssources.pkr.hcl
Originally posted by @jayfranco999 in #4316 (comment)
The text was updated successfully, but these errors were encountered: