Jenkins-job-builder - getting started problems

70 views
Skip to first unread message

lfast1

unread,
May 7, 2013, 5:21:30 PM5/7/13
to jenkins...@googlegroups.com
I'm just starting down the road of using jenkins-job-builder and I believe
I'm having API connection problems. Unfortunately, even with logging set to
debug, I don't get any messages about my connection.

My commandline:
jenkins-jobs -l debug --conf /etc/jenkins-jobs/jenkins_jobs.ini update
/etc/jenkins-jobs my_1stjob.yaml

My jenkins.ini:

[jenkins]
user=lfast
password=932890938230438983
url=http://localhost:8080

I can even change the url string to something meaningless and jenkins-jobs
reports no error. No matter what I do, no jobs are getting created on my
server.

How should I go about debugging my connection problems?




--
View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-job-builder-getting-started-problems-tp4665583.html
Sent from the Jenkins users mailing list archive at Nabble.com.

William Soula

unread,
May 10, 2013, 11:16:49 AM5/10/13
to jenkins...@googlegroups.com
What's the output on the command line? The way JJB works is it will take a hash of the configuration and unless that changes it won't rerun the job. So if you ran it once and it failed, unless you change the configuration it will not retry to create the job.

Will

________________________________________
From: jenkins...@googlegroups.com [jenkins...@googlegroups.com] on behalf of lfast1 [lfas...@yahoo.com]
Sent: Tuesday, May 07, 2013 4:21 PM
To: jenkins...@googlegroups.com
Subject: Jenkins-job-builder - getting started problems

My jenkins.ini:

--
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


lfast

unread,
May 21, 2013, 6:48:56 PM5/21/13
to jenkins...@googlegroups.com, willia...@drillinginfo.com
Thanks.  I eventually figured out that even after failing to load, JJB thinks the job is up to date.  My work-around was to disable the up-to-date check.  But it took some digging to find the active python code in
/usr/lib/python2.6/site-packages/jenkins_job_builder-0.4.0.64.g56083ed-py2.6.egg/jenkins_jobs/builder.py

Reply all
Reply to author
Forward
Message has been deleted
0 new messages