There're also the 'extended' downstream dependencies provided by the
Downstream-ext plugin
https://wiki.jenkins-ci.org/display/JENKINS/Downstream-Ext+Plugin
Maybe you've meant that one.
cheers
Christoph
Original-Nachricht
Datum: Thu, 9 Feb 2012 21:33:28 -0800 (PST)
Von:
AFAIK with the svn plugin it will checkout the revision from the date when the
build was started (or queued - not sure). If you want the latest revision, you
have to append @head to the repo url.
Am 22.02.2012 um 21:40 schrieb Sami Tikka sjti...@gmail.com:
2012/2/22 Les Mikesell
Hi Gabor,
there's currently no way to let the plugin impersonate you - i.e. the
user who is issueing a command via Jabber - in Jenkins. I wonder if
there is a theoretical way to do this without compromising security in
some way.
So yes, commands are issued as either the anonymous user or - if
AFAIR this bug has been reported some time agao and has been fixed in newer
Jenkins versions.
Please check Jenkins JIRA and/or the changelog to find out which version this
has been fixed in.
HTH
Christoph
Original-Nachricht
Datum: Tue, 3 Apr 2012 17:52:41 -0700 (PDT)
Von:
https://issues.jenkins-ci.org/browse/JENKINS-11964
Original-Nachricht
Datum: Thu, 26 Apr 2012 16:09:40 +0200
Von: Olivier Lamy oliver.l...@gmail.com
An: jenkinsci-users@googlegroups.com
Betreff: Re: Maven 3 modules
Is there any jira entry ?
I could have a look later to
IMHO the average user either wouldn't understand these subtle differences
anyway or if she would understand she probably wouldn't care.
So, I would like to see a single name for this in the UI.
E.g. I cannot see any significant difference between 'external job' and
'external project' (just
Hi,
I've repeatedly seeing that builds which are aborted during shutdown (sometimes
we've to restart Jenkins becuase of heap problems) are marked as successful,
while they IMO should be marked as aborted.
This is causing problems for us because warning trends reported by the Analysis
plugins
I've created a new bug report for this:
https://issues.jenkins-ci.org/browse/JENKINS-15084
Am 04.09.2012 14:15, schrieb Christoph Kutzinski:
I've repeatedly seeing that builds which are aborted during shutdown (sometimes
we've to restart Jenkins becuase of heap problems) are marked
I'd say it's intentionally AND a memory leak ;-)
This is IMO one of the major pain points with Jenkins. We keep 'only' 3
weeks worth of builds and still it takes 40 minutes for a Jenkins
startup - spending the majority of the time in loading the builds.
Unfortunately, it doesn't seem to be
I could imagine that this is related to the lazy build loading introduced in
1.485
Look e.g. https://issues.jenkins-ci.org/browse/JENKINS-15439
Original-Nachricht
Datum: Wed, 10 Oct 2012 00:10:55 -0700 (PDT)
Von: Youri your...@gmail.com
An: jenkinsci-users@googlegroups.com
It seems that 1.492 isn't released, yet. At least the changelog doesn't
mention it, yet.
http://jenkins-ci.org/changelog
Am 26.11.2012 11:21, schrieb Ollie Walsh:
I've created an issue for this
- https://issues.jenkins-ci.org/browse/JENKINS-15919
On Monday, 26 November 2012 10:07:18 UTC,
Have you tried the graphviz forums?
http://www.graphviz.org/forums/general-discussion
Am 10.12.2012 02:02, schrieb Z W:
Hi
We are having trouble installing graphviz on Oracle Enterprise Linux
6. We like to use the Dependency Graph View plugin.
Does anyone have notes on how to install graphviz
Which Jenkins version are you using - it seems to be rather old?
I think this has been fixed in newer versions.
Am 18.12.2012 10:53, schrieb Alexander Spetko:
Hi *,
from time to time we get a NullPointerException, during the clean install goal.
The stacktrace:
[INFO]
[INFO]*---
Hi,weve recently updated our Checkstyle and FindBugs plugin (and also static analysis core) to the latest version and since then weve mentioned that the warning summary on the build overview page has gone.Im not sure, if this is a bug or were missing some configuration which we have to do to get
or freestyle jobs? Are there any exceptions on the console? (Or messages that Jenkins cannot assign some values from XML to the actual objects?)UlliAm 29.01.2013 um 10:28 schrieb Christoph Kutzinski ku...@gmx.de:Hi,weve recently updated our Checkstyle and FindBugs plugin (and also static analysis core
From which versions did you upgrade? What Jenkins version are you using? Are the missing summaries in maven or freestyle jobs? Are there any exceptions on the console? (Or messages that Jenkins cannot assign some values from XML to the actual objects?)UlliAm 29.01.2013 um 10:28 schrieb Christoph
?
I changed something in 4.34 of findbugs plug-in (show information of build result evaluation). Maybe that change was not backward compatible? Does the information show up for new builds?UlliAm 29.01.2013 um 11:17 schrieb Christoph Kutzinski ku...@gmx.de:These are the version changes
:30 schrieb Christoph Kutzinski ku...@gmx.de:No, it neither shows for old nor for new builds.Christoph
Gesendet:Dienstag, 29. Januar 2013 um 11:26 Uhr
Von:Ulli Hafner ullrich.haf...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Checkstyle/FindBugs
version did you upgrade from?UlliAm 29.01.2013 um 12:05 schrieb Christoph Kutzinski ku...@gmx.de:Great that you can reproduce it.We updated Jenkins and shortly thereafter the plugins. I think the issue only appeared after the plugin update, but not 100% sure anymore.https://issues.jenkins-ci.org/browse
Could behttps://issues.jenkins-ci.org/browse/JENKINS-16573Do you see any error messages?
Gesendet:Donnerstag, 07. Februar 2013 um 15:34 Uhr
Von:Guillaume Bilodeau guillaume.bilod...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Test results
That's a bug in Jenkins core:
https://issues.jenkins-ci.org/browse/JENKINS-16499
You'll have to wait for Jenkins 1.501 (I wonder why it's not released
yet) or downgrade.
Am 08.02.2013 16:21, schrieb David Hoffman:
I have also gone ahead and upgraded the Mercurial plugin to 1.43 with no
joy
Hi,
sorry that you didn't get any response so far.
Unfortunately I'm not familiar with the JBoss management plugin, but
usually you find the configuration for plugins either in the global
management section (manage Jenkins) or in the jobs' configuration page.
Have you looked there already?
I think you're referring to the changes I had done some time ago.
Previously (before my changes) the relationship was built up to a
'non-predictable' job (means the assigment was stable, but not really
deducable from parameters which are visible from the outside - i.e. only
based on a
Check the build timeout plugin
Gesendet:Donnerstag, 02. Mai 2013 um 17:20 Uhr
Von:Tom tpri...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Mark Build Unstable if it takes to long
Hello,
Does anyone know how to mark a build unstable if it takes to long?
Thanks
-Tom
--
You received
Are you using git?
Theres a bug in the maven-release-plugin with localized git output:
http://www.shredzone.de/cilla/page/373/maven-release-plugin-and-git-fix.html
Gesendet:Mittwoch, 29. Mai 2013 um 13:09 Uhr
Von:James Nord (jnord) jn...@cisco.com
An:jenkinsci-users@googlegroups.com
Works for me
Gesendet:Freitag, 31. Mai 2013 um 16:28 Uhr
Von:mpapo - Michal Pailloncy mpapo@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Wiki down ?
Hi,
The wiki seems to be down : https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API=502 Bad Gateway
Michal
--
I think it would be very helpful to have this as part of Jenkins core.
Christoph
Ulli Hafner ullrich.haf...@gmail.com schrieb:
Wouldn't it be better if Jenkins would already provide a feature to
visualize compile errors? (And plug-ins can add new patterns for new
compiler types?)
I can add
I guess Jesse has something to do with it ;-)
Gesendet:Dienstag, 18. Juni 2013 um 10:59 Uhr
Von:James Nord (jnord) jn...@cisco.com
An:jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
Cc:matthew.web...@diamond.ac.uk matthew.web...@diamond.ac.uk
Betreff:RE: Update to strange
Theres no other documentation (Im aware of) than the one on the Wiki page and - if you like to stick your nose into it - in the GutHub sources (esp.https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/hudson/scm/SubversionRepositoryStatus.java)
If you find that the
Which JVMs are you using for Master and Slave? The error is a serialisation incompatibility between these two.
Gesendet:Freitag, 12. Juli 2013 um 16:18 Uhr
Von:Mehdi Hayani hayani.mehdi...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Jenkins isnt accessible due to several errors
Hi,
Ive got the problem that the sonar task fails when running from Jenkins, but suceeds when running on a developer machine or even on the Jenkins build node when running from the shell.
Console output:
11:53:28 :sonarRunner
11:53:28 11:53:28.124 INFO .s.b.b.BatchSettings - Load batch
For reference:
the problem turned out that the project name on Jenkins contained a whitespace while the directory on my developer machine didnt
Since Gradle automatically takes that as project.name and the sonarRunner obviously doesnt like white space in the project name, it failed on
Harald, seehttps://issues.jenkins-ci.org/browse/JENKINS-19396andhttps://issues.jenkins-ci.org/browse/JENKINS-19352
Gesendet:Dienstag, 15. Oktober 2013 um 11:22 Uhr
Von:Harald Wellmann hwellmann...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Console output in LTS 1.509.4
After
is not clear to me. Does this mean the issue *is* a bug which is fixed (at least for Java 7) on trunk but still present in LTS?
Cheers,
Harald
2013/10/15 Christoph Kutzinski ku...@gmx.de
Harald, seehttps://issues.jenkins-ci.org/browse/JENKINS-19396andhttps://issues.jenkins-ci.org/browse/JENKINS
JVM: Oracle Zero VM 21.0-b17
What kind of VM is that? I've never heard of it.
From the stacktrace it looks like you're trying to run the Maven build
with a Java 5 VM (which is not supported). So you might want to try it
with a Java 6 or 7 VM.
Anyway, the NullPointerException shouldn't
What is your Jenkins and your maven-plugin versions?
From the error it looks like theres a problem with the configured maven installation to use for this job (Maven home seems to be empty).
Can you check that configuration?
Gesendet:Freitag, 01. November 2013 um 15:10 Uhr
Von:William Pughe
in code
That was it, empty maven_home. All set now, thanks for the help.
On Fri, Nov 1, 2013 at 11:46 AM, Christoph Kutzinski ku...@gmx.de wrote:
What is your Jenkins and your maven-plugin versions?
From the error it looks like theres a problem with the configured maven installation
maven2
Gesendet:Freitag, 01. November 2013 um 17:24 Uhr
Von:William Pughe willpu...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Re: build failed due to bug in code
Sure, what component would this be for?
On Fri, Nov 1, 2013 at 12:08 PM, Christoph Kutzinski ku...@gmx.de wrote
No, its much simpler IMO.
The Maven job type always sets maven.test.failure.ignore to true (http://maven.apache.org/maven-1.x/plugins/test/properties.html),
so the build can run to the end and Jenkins can record the test results and set the build result to UNSTABLE -instead of FAILURE which
As part of the Maven goals and options:
-Dmaven.test.failure.ignore=false
Gesendet:Mittwoch, 06. November 2013 um 15:19 Uhr
Von:David Gang michaelg...@gmail.com
An:jenkinsci-users@googlegroups.com
Betreff:Re: Re: jenkins maven project executes maven deploy even when tests fail
Hi,
I wanted
Do you have a test case to reproduce it?
Maven version ranges should be supported since Jenkins 1.481
(see https://issues.jenkins-ci.org/browse/JENKINS-12735)
Am 15.11.2013 12:18, schrieb Bacon, Keith:
Does anyone else wish this would work for version ranges?
Is there a good reason why it
Looks like a bug in the Maven Info Plugin.
Can you open a new JIRA issue for this with a description on how to
reproduce it?
Am 08.12.2013 04:58, schrieb Stephane Odul:
I managed to get out of the issue by cleaning up my pom.xml. It seems
that Jenkins is a little more sensitive about the pom
Hi,
no JENKINS-18574 has nothing to do with credentials. It's only changelog
related AFAIK.
JENKINS-18574 wasn't even mentioned in the changelog of 2.0.
Am 02.05.2014 09:25, schrieb David Aldrich:
Hi
I see that Subversion Plugin 2.3 was released yesterday. The change log
states:
Hi all,
we want to create a project template to make it easier to create new services from scratch.
As part of this template we want to have a single step to create a new Jenkins job for this service.
For example, this should be a simple Gradle call: gradle createJenkinsJob which would create
A simpler - and IMHO much cleaner - way would be to add the target
folder to svn:ignore.
You shouldn't have any local modifications during the release process,
otherwise you're doing it wrong!
Am 16.08.2014 um 07:17 schrieb Adam Guja:
You can use checkModificationExcludes
as stated
here
Looks like a nice tool!
Am 22.09.2014 um 18:28 schrieb oliver gondža:
Hi,
There is a plugin that bring Dumpling DSL into Jenkins:
https://wiki.jenkins-ci.org/display/JENKINS/Dumpling+Plugin
What's Dumpling?
Domain model and DSL to query thread state. Read more here:
Thanks for the info.
Can you open a new JIRA issue against the ircbot and attach the
information below?
thanks
Kutzi
Am 28.10.2014 um 22:02 schrieb Luciano Furtado:
Hi Everybody,
We have a Jenkins instance that connects to a irc server over ipsec,
the Jenkins server after running for over
.
On Oct 28, 2014 9:17 PM, Christoph Kutzinski ku...@gmx.de
javascript: wrote:
Thanks for the info.
Can you open a new JIRA issue against the ircbot and attach the
information below?
thanks
Kutzi
Am 28.10.2014 um 22:02 schrieb Luciano Furtado
I'd *really* like to work in a company which thinks of myself as a
resource instead of a human!
Am 26.12.2014 um 17:25 schrieb david browse:
Urgent Need Java Resources Candidates, Immediate Interview
Contact id:_david@browseinfosolutions.com_ Number: _248 845 2142 ext: 303_
__
__
__
If I understand your requirements correctly, I would use the build flow
plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
Make the controller job a build flow job which calls the other 3 jobs in
a guard-rescue block each and let them re-run once if they fail in the
rescue
Much better of course to use the retry statement of the build-flow plugin:
retry ( 3 ) {
build( this_job_may_fail )
}
Am 10.01.2015 um 11:15 schrieb Christoph Kutzinski:
If I understand your requirements correctly, I would use the build flow
plugin: https://wiki.jenkins-ci.org/display
There's also the jstack tool which comes which each JDK which can take a
stack trace of Jenkins. That might also help to figure out the original
problem.
Am 11.04.2015 um 17:23 schrieb Brian J. Murrell:
On Fri, 2015-04-10 at 11:31 -0400, Brent Atkinson wrote:
You're right, but connecting
handle most relations between builds
and for the others (including build-flow) do offer an extension point to discover other relations
2015-07-21 16:44 GMT+02:00 Christoph Kutzinski ku...@gmx.de:
Thanks!
I didnt know abouthttps://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin
Can
Hi,
Im trying to set up a CD pipeline with Jenkins where I can
I) concisely define the relationship (triggers) between the single pipeline steps (jobs)
II) have a nice visualisation of the full pipeline
The Build Flow plugin is a good fit for I, while the Build Pipeline plugin is a nice
GMT+02:00 Christoph Kutzinski ku...@gmx.de:
Hi,
Im trying to set up a CD pipeline with Jenkins where I can
I) concisely define the relationship (triggers) between the single pipeline steps (jobs)
II) have a nice visualisation of the full pipeline
The Build Flow plugin is a good fit
sequential pipelines
2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:
Hi,
Im trying to set up a CD pipeline with Jenkins where I can
I) concisely define the relationship (triggers) between the single pipeline steps (jobs)
II) have a nice visualisation of the full pipeline
56 matches
Mail list logo
