Add config files for automated Jenkins setup #5
Conversation
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
| clouds: | ||
| - amazonEC2: | ||
| # Example: cloud setup in us-west-2 | ||
| cloudName: "<name>" |
There was a problem hiding this comment.
These<value> entries are not pulled from environment, right? It's for the user to replace?
There was a problem hiding this comment.
Yes, these can simply be replaced.
There was a problem hiding this comment.
Might make it more clear to denote that in the comments, so that someone consuming this doesn't miss something
There was a problem hiding this comment.
would be great if these end up later on being some wizard that asks for the values and replaces them (generating the files)
May need some more easier to identify format for them
Should be fine for the mean time
There was a problem hiding this comment.
Good point, I can create a script that converts these templates to .yaml files and prompts the user for the required values.
There was a problem hiding this comment.
Yeah, agree, as a first pass, this is fine. End goal is to have a generator replace everything from a config file or pull from some secure parameter store (probably something like Jinja can do).
There was a problem hiding this comment.
Created this issue to track: #6
| artifactManager: | ||
| artifactManagerFactories: | ||
| - jclouds: | ||
| provider: "s3" |
There was a problem hiding this comment.
Nit: Newline at end of file. Couple other files are missing this as well
There was a problem hiding this comment.
Sure thing, will fix.
| globalNodeProperties: | ||
| - envVars: | ||
| env: | ||
| - key: "<key1>" |
There was a problem hiding this comment.
Maybe put in some required parameters here? For instance, I see that JENKINS_URL and JENKINS_EMAIL_ADDRESS see to be values that are picked from envVars?
There was a problem hiding this comment.
The url and email address are set in jenkins.yaml. I can look at our current env var set and see if there are values that are require to run the pipe.
| - "Overall/Read:<user/group>" | ||
| - "View/Read:<user/group>" | ||
| # Example: grant additional admin permissions | ||
| - "Overall/Administer::<user/group>" |
There was a problem hiding this comment.
Wouldn't failing to set this properly cause the instance to be inaccessible? If so, probably want to at least set a default user
There was a problem hiding this comment.
These permissions are optional. The default admin is set in jenkins.yaml.
configs/aws_ec2_plugin.template
Outdated
| # Example: cloud setup in us-west-2 | ||
| cloudName: "<name>" | ||
| instanceCapStr: "100" # A cap can also be set for each AMI config. | ||
| region: "us-west-2" |
There was a problem hiding this comment.
Maybe turn region: into a variable, which can also be referenced in zone:?
There was a problem hiding this comment.
I can add a default region env var. If multiple regions are required a user can just add them there.
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Signed-off-by: brianherrera <[email protected]>
Adding config files that will be used to automatically setup Jenkins and prevent users from having manually set configs after startup.
The changes in this PR are targeted for customers that will consume the pipeline. This adds a main jenkins.yaml file that stores the recommended default settings to run the pipeline and template files for optional settings. A follow up PR will have the O3DE specific settings that will be stored in another branch (e.g. o3de-prod).
Also added a relevant section to the README.
I tested the settings locally in docker to validate the config formats.