> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of dwalling
> Sent: Samstag, 21. April 2012 20:21
> To: Jenkins Users
> Subject: how to build a specific git branch with jenkins
>
> This is almost certainly a newbie questio
No. The best you can get is make Jenkins ignore changes outside the
subdirectory when it considers if the job needs to be triggered.
Included and excluded regions are set under the Advanced button of the
Git SCM part of the job config page.
-- Sami
2012/4/20 John Cartwright :
> Hello All,
>
> I h
If "manage.py" would print test results into standard output, Jenkins build
console would show how the tests are going.
Or did you mean that "manage.py" actually does that, but you do not see the
output from manage.py until it has finished?
If that's the case, the problem is caused by manage.py u
Please show us the full console log of the build.
-- Sami
2012/4/21 dwalling :
> This is almost certainly a newbie question, so apologies in advance.
>
> I have a Jenkins maven job using Git scm that builds detached head.
> The branch specifier defaults to "**". When I put origin/master for
> the
I have found this relevant issue:
https://issues.jenkins-ci.org/browse/JENKINS-9529
However, I found that (rather embarassingly), my problem came down to a
user permission issue. (Although I feel like I was experiencing problems
even before a recent change to our Jenkins permissions setup).
~
I am experiencing the same issue. My post-commit hooks were working as
expected until recently. Having applied various Jenkins upgrades in
between that time, I cannot say with which version post-commits started to
fail. Currently we're running Jenkins 1.460, subversion 1.4.2.
I'll create an
I usually use the url trigger for any remote process triggering. But there are
a number of triggers that could be used as well as the cli or the build url.
I like the url trigger because I can pass parameters and what triggered the
build.
Steven
From: j
Indeed it did. Thank you Didier.
# yum install dejavu-lgc-fonts
# cd /usr/share/fonts
# ln -s dejavu-lgc dejavu
Then I restarted Jenkins and triggered a new build. My trend graphs are now
perfectly legible.
Thanks again!
alex
On Apr 20, 2012, at 10:30 AM, Didier Durand wrote:
>
> Hello,
>
Jenkins is a powerful tool, but when I build a job, I cannot see runtime
test progress or test results on the console output. The job is built by
way of "Execute shell". For example, I have following test results:
+ ./manage.py test api
..EEFBuild was aborte
But jenkins only show the test result
