-
Notifications
You must be signed in to change notification settings - Fork 711
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
No configurator for the following root elements services #2376
Comments
Services is not a valid root element.
|
Also, right before this error occurs I am getting a warning as below: |
Another update, I think this is related to the way I have split the yaml for ec2 plugin...
AMI1.yaml
Similarly I have multiple templates yaml files, hoping that they will merge into a single one. |
Just tried again by merging everything back together into a single yaml file ... Still get the same error. |
Reduce it to a minimal error and post your full yaml. the original error shows you nesting it under ‘services’ which is wrong |
There is nothing named services in any of the twelve YAML config files, so I cannot pinpoint the issue or narrow it down to a particular part of the configuration. |
So, I removed the compose.yaml file from the jenkins home. Now the error I get with the below templates of the ec2 configuration is:
ec2/ami-1.yaml
ec2/ami-2.yaml
|
see https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/ec2 under amazonEc2 templates needs to be indented |
Your checklist for this issue
🚨 Please review the Support Policy
Description
Please describe your issue here, and explain what you have already tried to resolve it.
I am spinning up a new Jenkins instance using the docker image jenkins/jenkins:alpine. The list of plugins I have installed is as follows:
atlassian-jira-software-cloud:latest
blueocean:latest
build-timeout:latest
cloudbees-folder:latest
configuration-as-code:latest
credentials-binding:latest
ec2:latest
email-ext:latest
git-client:latest
gradle:latest
job-dsl:latest
matrix-auth:latest
pipeline-stage-view:latest
saml:latest
ssh-slaves:latest
timestamper:latest
workflow-aggregator:latest
ws-cleanup:latest
I have a set of yaml files with the configuration as code. I am getting an error
SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ConfigurationAsCode.init
io.jenkins.plugins.casc.ConfiguratorException: No configurator for the following root elements services
The configuration was working fine until a week ago and I have not made any changes to it. It stopped working while I was trying to split the configuration for the ec2 plugin into multiple files a few days ago. I thought it was related to the way I split the Yaml but reassembling it in the way it was before did not fix the issue either. So, obviously something else is amiss. I noticed that a new version of the CASC plugin came out a couple of days ago though.
The text was updated successfully, but these errors were encountered: