-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[SDTEST-171] add Ruby to the list of supported languages of Datadog Jenkins plugin #26716
[SDTEST-171] add Ruby to the list of supported languages of Datadog Jenkins plugin #26716
Conversation
Preview links (active after the
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @anmarchenko 👋🏻 For image updates, we sometimes run into caching issues when you update images with the same filename. Could you add the new image as ci-jenkins-plugin-tests-config-2.png
, and update the reference to that image with the new filename? (We have a script that will then delete the old version of the image for you.) Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, will do that!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@janine-c done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
Devflow running:
|
What does this PR do? What is the motivation?
Adds Ruby to the list of supported languages for Jenkins Plugin. Updates Jenkins Plugin settings screenshot.
Merge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/description
naming convention) and then add the following PR comment: