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

add datadog initialisation on windows vm #3149

Closed
11 tasks done
smerle33 opened this issue Sep 23, 2022 · 2 comments
Closed
11 tasks done

add datadog initialisation on windows vm #3149

smerle33 opened this issue Sep 23, 2022 · 2 comments

Comments

@smerle33
Copy link
Contributor

smerle33 commented Sep 23, 2022

Service(s)

AWS, Azure, ci.jenkins.io

Summary

following #2980
we need to implement the same process than for linux for the windows ephemeral VM agent.

the same process could apply : Initialization Script
the azure documentation explain that the script will not be launched automatically (https://learn.microsoft.com/en-us/azure/virtual-machines/custom-data: "Custom data is placed in %SYSTEMDRIVE%\AzureData\CustomData.bin as a binary file, but it isn't processed. If you want to process this file, you'll need to build a custom image and write code to process CustomData.bin." ) but the jenkins plugin help seem to state the opposite and provide a sample : https://raw.githubusercontent.com/jenkinsci/azure-vm-agents-plugin/master/docs/init-scripts/windows-ssh.ps1

todo :

  • create a test agent on ci.jenkins.io by casc with the same parameters than azure : win-2019 with a specific label
  • add a Initialization Script
  • try to manually launch a pipeline with this agent to check whether or not the script is launched
  • modify the script to add a datadog.yaml at the correct path with the correct api-key
  • check that the VM appear on datadog host

same with amazon ....

  • create a test agent on ci.jenkins.io by casc with the same parameters than azure : win-2019 with a specific label
  • add a Initialization Script
  • try to manually launch a pipeline with this agent to check whether or not the script is launched
  • modify the script to add a datadog.yaml at the correct path with the correct api-key
  • check that the VM appear on datadog host

and then :

  • add init script to old windows VM and remove test agent

Reproduction steps

No response

@smerle33 smerle33 added the triage Incoming issues that need review label Sep 23, 2022
@smerle33 smerle33 self-assigned this Sep 23, 2022
@dduportal
Copy link
Contributor

  • Nitpick: could you point to the Azure-VM documentation about the feature?
  • Important: we should not consider adding datadog to ACI.
  • Next step: could you check with EC2 plugin how to do it? (smells like tricky because we use the SSH launcher on Windows machines)

@dduportal dduportal added this to the infra-team-sync-2022-10-04 milestone Sep 23, 2022
@dduportal dduportal removed the triage Incoming issues that need review label Sep 23, 2022
@smerle33
Copy link
Contributor Author

  • Nitpick: could you point to the Azure-VM documentation about the feature?
    done

    • Important: we should not consider adding datadog to ACI.
      ok

    • Next step: could you check with EC2 plugin how to do it? (smells like tricky because we use the SSH launcher on Windows machines)
      https://github.com/jenkinsci/ec2-plugin
      I will have to spend more time at this moment ... will first focus on azure.

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

No branches or pull requests

3 participants