On Thu, Feb 7, 2019 at 3:02 PM Matt Q <[email protected]> wrote: > I was trying to avoid using the XML file but is it safe to assume that the > config.xml files will be backwards compatible if we upgrade to a newer > version of Jenkins in the future?
Yes, we would make every attempt to retain `config.xml` compatibility, since failing to due so would cause a critical problem for essentially every Jenkins user. > this command works from the command line but not when executed from Java code: > > java.nio.file.FileSystemException: > C:\Users\mqu\.jenkins\jobs\AnotherNewPipeline\config.xml: The process cannot > access the file because it is being used by another process. Without knowing what the “Java code” in question was, I cannot help. There is a supported set of (Java) APIs in Jenkins for creating new jobs from various forms of input. -- 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/CANfRfr1ShdQonzJtjruhstNUwakgHp2R%3DzKkOVn2KyO98BZq3g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
