Thanks for the replies.  I am able to create pipeline jobs by modifying an 
existing config.xml and posting it to the command line interface:so I am 
exploring that route. 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?

Similarly, 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.


This is unexpected since the file is being created, not deleted, and I 
mention it because sounds similar to this issue. 
<https://issues.jenkins-ci.org/browse/JENKINS-55567?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel>

Any ideas/workarounds would be appreciated. In the meantime I am looking 
into leveraging the Jenkins API Client for Java 
<https://github.com/jenkinsci/java-client-api>.


On Monday, January 28, 2019 at 12:48:57 PM UTC-5, Jesse Glick wrote:
>
> On Mon, Jan 28, 2019 at 10:06 AM Artur Szostak <[email protected] 
> <javascript:>> wrote: 
> > the Job DSL and Pipeline combination will allow to have everything in 
> SCM and you can bootstrap the full job creation from SCM. The Pipeline type 
> job alone does not allow this. 
>
> Well…for the specific, common use case of creating one job per repo 
> and keeping branch-specific build instructions, “Pipeline-as-code” ~ 
> `workflow-multibranch` plugin offers a simple solution. Clearly this 
> does not cover more complicated scenarios. JENKINS-37220 has 
> discussion. 
>

-- 
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/8697b8e7-00f9-49e4-aab9-66a8d69dfc39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to