Hi Tyler,
can you please check again? I still didn't get a reset mail.
thanks
Gesendet: Freitag, 27. Mai 2016 um 17:12 Uhr
Von: "Christoph Kutzinski" <ku...@gmx.de>
An: jenkinsci-dev@googlegroups.com
Betreff: Re: Cannot access JIRA/wiki anymore. Password r
No, unfortunately not.
Didn't receive anything until now.
Am 27.05.2016 um 17:33 schrieb R. Tyler Croy:
(replies inline)
On Fri, 27 May 2016, Christoph Kutzinski wrote:
Hi,
I cannot access Jenkins JIRA/wiki anymore (wrong password) and the password
reset e-mails don't arrive in my inbox
More like an ad for "DBmaestro - DevOps for Database" - what ever that's
supposed to mean.
Am 03.04.2016 um 13:46 schrieb Lazer Cohen:
Read this article - "Jenkins has changed everything" http://bit.ly/1RAOWUs
--
You received this message because you are subscribed to the Google
Groups
/Parameterized-Remote-Trigger/2.2-SNAPSHOT/
On 03.08.2015, at 13:57, Christoph Kutzinski ku...@gmx.de wrote:
Maybe the problem with localized Git output and maven-release-plugin 2.5?
https://github.com/jenkinsci/pom/commit/62bd9a118493a16ae6bc8eef715785f06a6303be#diff
-SNAPSHOT/
http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/2.2-SNAPSHOT/
On 03.08.2015, at 13:57, Christoph Kutzinski ku...@gmx.de
javascript: wrote:
Maybe the problem with localized Git output and
maven-release-plugin 2.5
Maybe the problem with localized Git output and maven-release-plugin 2.5?
https://github.com/jenkinsci/pom/commit/62bd9a118493a16ae6bc8eef715785f06a6303be#diff-600376dffeb79835ede4a0b285078036
The plugin still depends on Jenkins Core 1.509 which doesnt have the fixed release-plugin, yet
Hi,
according to the Wiki the latest release should be 2.2.0https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin
However, I cannot find a release commit in Github, though there is a tag for
I can release the plugin, but I really feel any kind of responsibility
as a maintainer of the plugin. So IMO you could just release it by yourself.
Regarding the question of core compatibility: I usually update to
previous before the current LTS release. The newest LTS seems too new to
me most
Can a Wiki admin block the Spam account 'senly senly cantik' please?
Weitergeleitete Nachricht
Betreff: [confluence] Jenkins Issue Tracking
Datum: Sat, 29 Nov 2014 22:00:00 + (UTC)
Von: Jenkins Wiki nore...@jenkins-ci.org
An: ku...@java.net
Space: Jenkins
Hi,
it seems like the automatically created plugin info hasn't been updated
since 2012:
https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin
Latest release show 1.25, but it should at least show 1.28 (1.29 was
released today, so probably not in there, yet)
--
You received this message
Can someone with administrative power block the Wiki spam account adib
samsul?
Weitergeleitete Nachricht
Space: Jenkins (https://wiki.jenkins-ci.org/display/JENKINS)
Page: Issue Tracking
Hi,
so I've developed Jenkins plugins for all these years and still I've got
no clue what the magical InjectTest is actually doing - excepting
stealing some of my time:
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.365
sec - in InjectedTest
And actually I cannot
because I cannot find the test class in
https://github.com/jenkinsci/maven-hpi-plugin
Am 30.10.2014 um 22:16 schrieb Jesse Glick:
On Thu, Oct 30, 2014 at 5:14 PM, Christoph Kutzinski ku...@gmx.de wrote:
So can someone explain, what it is good for?
You can browse its source code in maven-hpi
Hi all,
Jenkins had switched to Java 6 long ago, but the plugins POM still uses
Java 5 (via https://github.com/jenkinsci/pom/blob/master/pom.xml#L583 )
Is this a mistake or on purpose?
cheers
Kutzi
--
You received this message because you are subscribed to the Google Groups Jenkins
Hi all and Stephen especially ;-),
I wanted to give the literate-plugin a try:
git clone ...
cd literate-plugin
mvn clean install
mvn hpi:run
INFO: Listed all plugins
May 09, 2014 3:14:03 PM jenkins.InitReactorRunner1 onTaskFailed
SEVERE: Failed Loading plugin literate
Thanks Stephen and Jesse. It does work now.
Am 09.05.2014 18:02, schrieb Jesse Glick:
On Fri, May 9, 2014 at 11:19 AM, Christoph Kutzinski ku...@gmx.de wrote:
Anyome knows how to fix this?
Bug in maven-hpi-plugin 1.93, from the 1.509 parent POM. I have
updated the baseline to 1.509.4 which
+1 for adding this to the existing plugin.
Probably would make migration to JIRA 7 much less painless for users of
the existing plugin
Am 28.03.2014 22:42, schrieb Slide:
Is there any reason you couldn't add the capability to the existing
plugin instead of writing a new plugin?
slide
On
to the port 5222 your plugin may connect to.
Because image say more than words, i attached a screenshot.
Regards.
*Gesendet:* Freitag, 07. März 2014 um 10:52 Uhr
*Von:* Christoph Kutzinski ku...@gmx.de
*An:* jenkinsci-dev@googlegroups.com
*Betreff:* Aw: Re: Request for commit right - jabber-server-plugin
I guess Ulli's next question will be: Where to find this
jabber-server-plugin you want to have commit access for?
I for myself couldn't find such one on Github
Am 07.03.2014 20:06, schrieb Peter Rader:
jabber-server-plugin is different from jabber-plugin, but i won't
wonder if users will use
I've followed this thread only superficially.
I'd say it depends on how widespread the usage of the external python
tool is. If it's already in use by many existing build setups, then a
new Jenkins plugin for it makes sense.
If not, I'm with Uli that multiple plugins which do basically 'the
Yes, it works on the CLI
Am 15.11.2013 21:55, schrieb Baptiste Mathus:
Hi, First thing I would ask is: does it build on the CLI outside
Eclipse? That'll be a first step to see if this is likely a Maven
issue or more an Eclipse or even a jenkins code one.
My 2 cents
2013/11/15 Christoph
? That'll be a first step to see if this is likely a Maven
issue or more an Eclipse or even a jenkins code one.
My 2 cents
2013/11/15 Christoph Kutzinski ku...@gmx.de mailto:ku...@gmx.de
Hi,
I had several problems with building Jenkins/maven-plugin in
the past
2013/11/16 Christoph Kutzinski ku...@gmx.de mailto:ku...@gmx.de
No Maven Problems, only Java problems:
DescriptionResourcePathLocationType
Cannot make a static reference to the non-static method save()
from the type
Hi,
I had several problems with building Jenkins/maven-plugin in the past,
but the errors I'm getting now are especial nasty:
Eclipse e.g. complains that it cannot find hudson.model.Queue.Item (in
MavenModuleSet) and several other compile errors.
I checked the the Jenkins core jar is intact
Plugins should depend on 1.509 anyway, so they can be used in the LTS branch as well as in the newest master versions, shouldnt they?
Gesendet:Montag, 21. Oktober 2013 um 11:30 Uhr
Von:Mirko Friedenhagen mfriedenha...@gmail.com
An:jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
Thanks for doing this Kohsuke!
However, after looking at the German translation updates
(https://github.com/jenkinsci/jenkins/commit/95f1d4b60d11fb0b68230690af708310de3cf07a),
I doubt that this is in a state ready to be merged.
The main problem I see is that keys, which were already translated
Caan you open a JIRA issue against the plugin? Then Ill have a look at it.
Gesendet:Dienstag, 08. Oktober 2013 um 13:53 Uhr
Von:ohad shai ohads...@gmail.com
An:jenkinsci-dev@googlegroups.com
Betreff:memory leak in jenkins?
Hi,
I am using jenkins 1.531 and suffers in the last few weeks from
BTW: how many test cases do you have in the jobs, you have enabled the plugin in, and what have you configured as Max. history length?
Gesendet:Dienstag, 08. Oktober 2013 um 14:11 Uhr
Von:Christoph Kutzinski ku...@gmx.de
An:jenkinsci-dev@googlegroups.com
Betreff:Aw: memory leak in jenkins?
Olivier, it's now at https://github.com/jenkinsci/maven-plugin
I was a also a bit surprised that it was moved without any prio
announcement - or question if it was cause issues for someone ...
cheers
Kutzi
Am 07.10.2013 22:04, schrieb Olivier Lamy:
What happened with the maven plugin?
Did I
Again, some error when trying to build - this is really eating up some
time and lowering my motivation to invest time to fix bugs.
IANAL, so I have really difficulties to understand why this license
check is needed - at east in every build.
Can't we put it into a profile which is only executed
Or include a fix for JENKINS-19352 - which doesn't exist, yet, ergo
doesn't fulfill the requirements to be included in the LTS?
Sorry, that should read, of course:
Or include a fix for JENKINS-19396
Am 05.10.2013 14:23, schrieb Christoph Kutzinski:
I'm afraid that I'm not getting what you're
Hi,
I've done a fix for https://issues.jenkins-ci.org/browse/JENKINS-19352.
As that is IMO is quite critical, can we have a release of the maven-plugin?
I'm not sure how this is handled now that the plugin is in it's own
repository (*).
Can I do the release myself? How do we handle the
We have https://issues.jenkins-ci.org/browse/JENKINS-15935 in this,
which *may* have caused https://issues.jenkins-ci.org/browse/JENKINS-19352
Can someone confirm (or disprove) that JENKINS-19352 is observable in
the LTS branch? I'll try to find some time this weekend to confirm myself.
cheers
Thats a normal log entry - I can also see it in successful releases. (I guess its related to the generateReleasePomsoption of the release plugin)
I would definitely pursue the path with the non-englishlocale, because its exactly the same sympton as I got, when trying to release in a German
Am 02.08.2013 17:18, schrieb Jesse Glick:
I brought this up earlier on the list but I am not sure anyone
responded, so just checking again: do we want to update war/pom.xml to
use the latest released versions of all bundled plugins? (As of some
cutoff date of course, so that you can do testing
I've just flagged https://issues.jenkins-ci.org/browse/JENKINS-15935
cannot build with Maven 3.1.0
This doesn't satisfy the 1-week battle condition, yet (will so on
Monday), but IMO it would be definitely good, if we support the current
Maven release.
Cheers
Christoph
Am 02.08.2013 08:34,
Cannot say, why it is so, but I agree that it feels like a bug.
I had no luck to get the M2 Release Plugin working with the git plugin
at all - even after following several advises found by googling for the
problem. I have now a freestyle job which does
git clone repo; mvn release:prepare
-final so you can extend it (actually: why do you this this is more messy?)
cheers
Christoph
Gesendet:Mittwoch, 10. Juli 2013 um 08:42 Uhr
Von:Nalin nul...@nullin.com
An:jenkinsci-dev@googlegroups.com
Cc:Slide slide.o@gmail.com, Kawaguchi Kohsuke kohsuke.kawagu...@gmail.com, Christoph
AFAIK, you cannot determine the build number before the build is actually started. So you cannot get it from the queued item.
Gesendet:Mittwoch, 10. Juli 2013 um 12:07 Uhr
Von:nicolas de loof nicolas.del...@gmail.com
An:jenkinsci-dev@googlegroups.com
Betreff:how to retrieve schedule job build
Done: https://github.com/jenkinsci/nuget-plugin
Welcome aboard!
Note: naming conventions say to add '-plugin' and remove any jenkins
prefix as it is redundant in this context.
You need to send pull requests only, if you fork an existing jenkins
repository, change something in it and
Id really look into it, but unfortunately Kohsuke is one of the very vew (only?) persons who knows how to release the SVNKit fork.
This is IMHO really unfortunate and raises once again for me the question how big the truck factor of Jenkins actually is.
Gesendet:Mittwoch, 29. Mai 2013 um
Maybe a Chrome issue, but I havent seen an analogue issue on any other site.
So still some problem on Jenkins side - even if its not a new one.
Christoph
Gesendet:Dienstag, 21. Mai 2013 um 16:00 Uhr
Von:James Nord (jnord) jn...@cisco.com
An:jenkinsci-dev@googlegroups.com
Linards, if your business is critically depending on this plugins
stability, you should do testing on your side before updating the plugin
anyway.
Besides that, Jenkins developers definitely do not intend to screw up
plugins.
thanks
Christoph
Am 06.05.2013 15:56, schrieb
Not exactly a backport, but if I look correctly LTS bundles CVS plugin
1.6 which is really really old
(https://github.com/jenkinsci/jenkins/blob/stable/war/pom.xml) - current
is 2.8 - and has a serious problem which may affect users if they're not
using CVS at all: the dreaded
Looks strange.
Obviously it should compile as the last commit was for the last release.
Can you try it with Maven 3? Most of Jenkins requires Maven 3 in the mean time, so this *could* be the problem.
Gesendet:Mittwoch, 17. April 2013 um 04:55 Uhr
Von:Kenny Ayers theotherwhitem...@gmail.com
@googlegroups.com
Betreff:Re: Which build has that fix?
On 02/17/2013 05:23 AM, Christoph Kutzinski wrote:
Another nuisance are the frequent merge conflicts on changelog.html
Yes, this complicates pull requests, and makes backporting fixes to the stable branch painful
Is it okay to release the cvs plugin?
There are multiple reports of the git plugin failing in conjuction with
cvs plugin - see
https://issues.jenkins-ci.org/browse/JENKINS-16849
The problem probably also has also a git-plugin side, but it could be
easily be solved by releasing the cvs-plugin
Would be a nice addition.
Another nuisance are the frequent merge conflicts on changelog.html
A rough idea would be to create a new single file (XML or so) for each
changelog entry and let the release process merge this into a single
changelog.html.
Am 15.02.2013 13:56, schrieb cjo:
Keeping
I made you a committer on GitHub and made you the default assignee in JIRA.
Welcome aboard!
I noted that the canonical repository of the plugin is still Subversion
- as noted in the Wiki.
You might want to move it to GitHub as a 1st step:
What is your GitHub user id?
Do you also have a JIRA user, so I can create a component there and make
you the default assignee?
Wondering: wouldn't pivotal-tracker-plugin o.s.l.t. be a better name?
'Tracker' is a pretty generic term.
Am 17.02.2013 05:02, schrieb prashantrajan:
Plugin
It's not a requirement, but IMO it would be a good idea to rename it.
Am 17.02.2013 15:27, schrieb prashantrajan:
github userid: prashantrajan
jira userid: prashantrajan
Wrt the name, I selected Tracker for the name as that's what Pivotal
Tracker is commonly referred to as but I get that it's
That's automatically updated by the release process, too.
Am 17.02.2013 18:32, schrieb Lorenzo Bettini:
On 02/17/2013 06:21 PM, Christoph Kutzinski wrote:
Both the information in the Wiki and the update site contents are
updated after you perform a new release of the plugin.
See Jenkins' Wiki
Note that it make take some hours until the changes are propagated to
the update site mirrors.
Am 17.02.2013 18:55, schrieb Christoph Kutzinski:
That's automatically updated by the release process, too.
Am 17.02.2013 18:32, schrieb Lorenzo Bettini:
On 02/17/2013 06:21 PM, Christoph Kutzinski
of the plugin, and I think it
was somehow uploaded by the previous maintainer;
I would like to provide a new file, but I don't understand how to do that...
thanks in advance
Lorenzo
On 02/17/2013 06:55 PM, Christoph Kutzinski wrote:
That's automatically updated by the release process, too.
Am
IMO this is a bug.
Can you open a JIRA issue for this?
Am 16.02.2013 13:40, schrieb Peter Liljenberg:
Hi,
I'm trying to build Maven projects with Jenkins and I notice that I
cannot suppress the (quite large) output from Maven during builds.
If I build it as a Freestyle project (invoking
Did it already myself: https://issues.jenkins-ci.org/browse/JENKINS-16843
Am 16.02.2013 16:03, schrieb Christoph Kutzinski:
IMO this is a bug.
Can you open a JIRA issue for this?
Am 16.02.2013 13:40, schrieb Peter Liljenberg:
Hi,
I'm trying to build Maven projects with Jenkins and I notice
Thanks,
can you create a Github pull request for this?
That would be much easier to handle.
Gesendet:Donnerstag, 31. Januar 2013 um 17:19 Uhr
Von:Julian Schmidt ju.schm...@gmx.de
An:jenkinsci-dev@googlegroups.com
Betreff:Possible fix for
Im not sure but maybe the code part where you are is running in the forked Java VM for the Maven build where the descriptors would be null - AFAIK.
You need to do your work in a callable which executes the code on the master.
Gesendet:Mittwoch, 30. Januar 2013 um 12:49 Uhr
Hi,
it seems that the claim plugin has currently no maintainer, right?
If so, I'd like to go ahead and fix some of the outstanding bugs/issues
for the plugin.
cheers
Kutzi
--
Looks good IMHO, so I'll merge it.
In the future you might want to include the URL to the pull request in
the e-mail as people tend to be lazy ;)
Am 15.01.2013 18:45, schrieb lars.hvile:
Hi there..
I've fixed a rather annoying 'bug' in jenkins-core that keeps crashing
one of our internal
18 janv. 2013 16:46, Christoph Kutzinski ku...@gmx.de
mailto:ku...@gmx.de a écrit :
Hi all,
for reasons best described in
https://issues.jenkins-ci.org/browse/JENKINS-15440 (and accompanying
issues) I'd like to remove the SubversionMailAddressResolverImpl
altogether
to get a clear
note on JIRA + changelog that explain this component was removed and
were to get it when necessary. I volunteer to do it next week if you
don't have much time
2013/1/19 Christoph Kutzinski ku...@gmx.de mailto:ku...@gmx.de
What about: remove it and *only if* somebody complains
Hi all,
for reasons best described in
https://issues.jenkins-ci.org/browse/JENKINS-15440 (and accompanying issues)
I'd like to remove the SubversionMailAddressResolverImpl altogether.
Reasoning in short:
- for big Jenkins instances it can result in an extreme delay before sending
build status
Am 12.01.2013 21:34, schrieb Yves Schumann:
Hi all together
2013/1/7 Yves Schumann starwarsfanl...@gmail.com:
I've triggered a pull-request for some improvements on the
copy-data-to-workspace-plugin around two months ago but nothing happens
since then. Could anyone of you check/approve this or
Done :)
Am 29.12.2012 11:58, schrieb domi:
+1
On 28.12.2012, at 10:43, Christoph Kutzinski ku...@gmx.de
mailto:ku...@gmx.de wrote:
So if no one has objections, I will happily remove these old svn
repositories for mail address resolving :-)
Am 18.12.2012 19:10, schrieb Christoph Kutzinski
, Christoph Kutzinski
ku...@gmx.de mailto:ku...@gmx.de wrote:
So if no one has objections, I will happily remove these old svn
repositories for mail address resolving :-)
Am 18.12.2012 19:10, schrieb Christoph Kutzinski:
Hi,
this is about the problem described in
https
not matter here.
2012/12/29 Christoph Kutzinski ku...@gmx.de mailto:ku...@gmx.de
I'm afraid that I'm not getting your point:
a) we're not doing any deprecation. We're removing a legacy default
config (which is IMO very unlikely to be still of use to anyone).
Users can still reconfigure
So if no one has objections, I will happily remove these old svn
repositories for mail address resolving :-)
Am 18.12.2012 19:10, schrieb Christoph Kutzinski:
Hi,
this is about the problem described in
https://issues.jenkins-ci.org/browse/JENKINS-15440.
The mail address resolving via the svn
Nice.
Is there anything which stops us from using the new version in the
subversion-plugin?
Am 20.12.2012 16:52, schrieb nicolas de loof:
Hi,
svnkit now has an official git mirror : http://svn.svnkit.com/git/svnkit
I've used a graft to reconcile our incoming branch with snvkit repo
svnkit
a commit access.
If you like, I can also make you the maintainer of the twitter-plugin.
Yes, please!
My jenkins-ci.org account is kmaehashi.
Thanks,
Kenichi
2012/12/2 Christoph Kutzinski ku...@gmx.de
Commit access is set.
Good that someone takes care of the twitter-plugin!
If you like, I can also
Commit access is set.
Good that someone takes care of the twitter-plugin!
If you like, I can also make you the maintainer of the twitter-plugin.
cheers
Christoph
Am 02.12.2012 06:01, schrieb Kenichi Maehashi:
Hi Jenkins developers,
I'm currently working on improving Twitter plugin that is
Hi Jan,
remember that Jenkins is an open source project and many if not most developers
work on it in their spare time.
So eventually this issue will probably be fixed, but unless some of the
subversion plugin developers have the urgent need to have this fixed for
themselves, it will probably
+1 for going to Java 6
Original-Nachricht
Datum: Fri, 7 Sep 2012 14:05:01 +0200
Von: David Karlsen davidkarl...@gmail.com
An: jenkinsci-dev@googlegroups.com
Betreff: Re: [VOTE] Bump Jenkins to Java 6
+1.
I'm always running jenkins on latest available release (e.g. 1.7up7
I agree that new contributors should be as smooth as possible.
Do you have any additional information (e.g. test output of the
XStreamDOMTest) and/or any ideas why the tests may have failed? I cannot
see any obvious problems why they would fail (on Windows).
cheers
Christoph
Am 25.08.2012
Hi,
we had experienced lot of inconsistent checkouts in our jobs which use a lot of
subversion-modules per job.
The problem turned out to be that the revision was specified via the
commit-hook. See https://issues.jenkins-ci.org/browse/JENKINS-14254 for a
longer description.
cheers
Christoph
Hi,
I've seen that the subversion-plugin was migrated to GitHub
https://github.com/jenkinsci/subversion-plugin/commits/master
However, the commits of the latest release (1.40) seem to be missing.
Anyone knows what went wrong?
cheers
Kutzi
Interesting.
Did you have a look at the instant-messaging plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Instant+Messaging+Plugin)?
It's aimed at providing a common basis for IM plugins.
Don't know how feasible it would be to use it for IPMessenger as that one seems
to be a server-less
Hi,
in case no one else has mentioned, there are currently a lot of complaints and
a lively discussion in https://issues.jenkins-ci.org/browse/JENKINS-11381 why
Jenkins still doesn't support svn 1.7 now that SVNKit 1.7 is released.
I would fix this myself, but I don't know what the Jenkins
78 matches
Mail list logo
