Skip to content
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

SCM imports reads as XML even though YAML has been chosen #1492

Closed
LordMike opened this issue Oct 19, 2015 · 2 comments
Closed

SCM imports reads as XML even though YAML has been chosen #1492

LordMike opened this issue Oct 19, 2015 · 2 comments
Labels
Milestone

Comments

@LordMike
Copy link

When setting up imports, I copied most settings from the export page (file paths, repo paths, key files) and set the import format to Yaml. But when importing any file, the following error appears:

Failed importing: Services/Webfile Watcher-4c3680f2-971e-4c8d-bee7-7a4f98026e05.xml: rundeck.controllers.JobXMLException: Unable to parse xml: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog.

The content of the file in question (in the repo) is very much Yaml.

Sidenote: I'll redo the entire repo anyways, as the UUID's no longer match (I migrated to a MySQL db recently and created new UUID's).

Might be slightly related: #1471

Server version: 2.6.0-1

@LordMike
Copy link
Author

#1471 is related. Renaming all files to .yaml resulted in a successful import.

@gschueler gschueler added the bug label Oct 19, 2015
@gschueler gschueler added this to the 2.6.1 milestone Oct 19, 2015
@gschueler
Copy link
Member

thanks for confirmation about 1471. looks like it is using the file extension to determine the format, not the configuration setting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants