Hi here,
Just an update on configuration-as-code effort (JEP-201)
I've started implementing schema generation for the configuration-as-code
yaml file.
it's only first iteration, so I expect some corner cases, but the main
benefits is we will be able to validate this configuration without having
to start jenkins and wait for potential failure. Another way to say, is we
can check a configuration file will result in a healthy jenkins instance.
jenkins.model.Jenkins:
{
- type: "object",
- properties:
{
- agentProtocols:
{
- type: "array",
- items:
{
- type: "string"
}
},
- authorizationStrategy:
{
- schema:
{
- oneOf:
[
-
{
- loggedInUsersCanDoAnything:
{
- type:
"#/definitions/hudson.security.FullControlOnceLoggedInAuthorizationStrategy"
}
},
-
{
- legacy:
{
- type:
"#/definitions/hudson.security.LegacyAuthorizationStrategy"
}
},
-
{
- unsecured:
{
- type:
"#/definitions/hudson.security.AuthorizationStrategy$Unsecured"
}
}
]
}
},
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzmiMYA1OUBm64Ab1UUY5%2BtMMRUMPeiOATiXukpR%2BLqz4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
