LEDO-125: Adding Jenkinsfile to support EKS job runs #596
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adding a Jenkinsfile to describe the job run by Jenkins in EKS. Tries to closely mimic the previous job, including some old debugging lines. Will need to determine if this entire process is still required.
Initially attempted to reuse an existing pipeline, however decided that due to deviations and additional behaviours required - decided to just create a custom pipeline here.
https://issues.corp.rapid7.com/browse/LEDO-125
Motivation and Context
Transferring the release job over to Jenkins EKS.
How Has This Been Tested?
Ran the new job multiple time, including the release process.
Types of changes