Hi,

I am not able to create the copy the job from copy-job command

Explain:

I created Jenkins user suresh and password suresh

Below command i tried but did not work

>java -jar c:\jenkins.jar -s http://localhost:8181/jenkins copy-job 
project1 project2 --username suresh --password suresh


Below command also i tried but did not work

>java -jar c:\jenkins.jar -s http://localhost:8181/jenkins copy-job 
 --username suresh --password suresh project1 project2

Output:

No such job 'project1'

java -jar jenkins-cli.jar copy-job args...
Copies a job.
 SRC                 : Name of the job to copy
 DST                 : Name of the new job to be created.
 --username VAL      : User name to authenticate yourself to Jenkins
 --password VAL      : Password for authentication. Note that passing a
                       password in arguments is insecure.
 --password-file VAL : File that contains the password

Please help on this how to resolve 

Regards,
Suresh

On Wednesday, July 24, 2013 3:20:04 PM UTC+5:30, Andreas Ebbert-Karroum 
wrote:
>
> Hi,
>
> at my current client, they will have many similar jobs to manage. 
>
> The jobs are basically parametrized ant jobs that pull sources from 
> Subversion. Besides there are some other options and plugins enabled :
>
>    - Discard Old Builds
>    - Delete workspace before build starts
>    - Copy files into the job's workspace before building
>    - Scan workspace for open tasks
>    - Editable Email notification
>
>  As far as I can tell, there are currently mutliple options available to 
> handle that situation:
>
> 1) Use the configuration slicing plugin. This sounds really nice, but the 
> biggest blocker at the moment is, that I cannot 'slice' the ant build step. 
> The builds are parametrized, and I use push many parameters forward to ant 
> with -DantName=$parameter options. Am I just too blind to see, or is that 
> currently not supported by the plugin?
>
> 2) Use the template project plugin. I haven't tried it, but am a little 
> scared by "It has had virtually no testing." in the wiki. 
>
> 3) Use the REST API and some custom scripts to manage the jobs.
>
> 4) Generate the xml files for the jobs and read them. 
>
> While I would love to use one of the two options above, I feat that some 
> scripting needs to be done. What are your experiences? 
>
> -- 
> Mit freundlichen Grüßen / Best regards
>
> Andreas Ebbert-Karroum
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to