It's a hosting request.
I've already read this url and this is the hosting request.
I'm sorry if it wasn't clear :)
On Monday, August 5, 2013 4:08:29 PM UTC+3, Ikedam wrote:
Oh, this wasn't hosting request...
Why don't you request your plugin hosted in jenkinsci repository, and
release to
I don't use Maven at all but I'd think that introducing a new feature like
Maven 3.1 support would be something for a main release not a point release.
Richard.
On Tue, Aug 6, 2013 at 8:51 PM, ogondza ogon...@gmail.com wrote:
The change is really huge and to me support for maven 3.1 sounds
AFAIK this is an issue confined to the (IMHO crappy) Maven project type.
You can build Maven 3.1 based projects quite happily with a Free-style
project and a Maven Build step.
The reason I raise this is that the context of this change is thus a lot
smaller. It only affects one project type, so it
Anyone got any idea on this question? It's ugly to have to state that the
code is maintained elsewhere.
Jim
On Thursday, 1 August 2013 10:02:08 UTC+1, Jan Molak wrote:
That's an excellent question Jim :) I'd like to update the links as well
on
Sorry don't know the answer but out of interest just wondering why you
don't want it hosted under the JenkinsCI org in Github?
Richard.
On Tue, Aug 6, 2013 at 9:43 PM, Jim Gallagher jegallag...@gmail.com wrote:
Anyone got any idea on this question? It's ugly to have to state that the
code is
I suspect that it's because he was actually born outside the pale and he is
trying to disguise that fact ;-)
On 6 August 2013 10:47, Richard Bywater rich...@byh2o.com wrote:
Sorry don't know the answer but out of interest just wondering why you
don't want it hosted under the JenkinsCI org in
I added you as a committer. So if you feel comfortable with the patch please go
ahead and commit the changes...
Welcome aboard!
Ulli
Am 06.08.2013 um 03:50 schrieb Raymond Munian raymond.mun...@gmail.com:
My id is rym002. I probably wont commit yet since the plugin seems to need to
be
Hi Omer,
I don't use matrix builds by myself but wouldn't it be easier for users if the
use cases of your new plug-in would be integrated into the matrix reloaded
plug-in?
Ulli
Am 06.08.2013 um 09:10 schrieb Omer Shem-Tov omer...@gmail.com:
It's a hosting request.
I've already read this
Looks like Prune option is completly removed in refactoring branch. Why?
Here the bug in JIRA:
https://issues.jenkins-ci.org/browse/JENKINS-18834
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop
Isn't
https://github.com/jenkinsci/git-plugin/blob/refactoring/src/main/java/hudson/plugins/git/extensions/impl/PruneStaleBranch.javawhat
your looking for ?
2013/8/6 Sapone mylniko...@gmail.com
Looks like Prune option is completly removed in refactoring branch. Why?
Here the bug in JIRA:
I'm not sure if I understand the question, but there is a Prune stale
remote-tracking branch selection in the Additional Behaviors drop down.
I've attached a link to a screenshot into the bug report.
Mark Waite
On Tue, 8/6/13, nicolas de loof
Hi, Ulli I think it's different from the BuildPipelinePlugin, but a few
inspiration from it. My plugin can show the multiple build line relationship in
one view. In my company, multiple teams has their own build line, and manager
or others want to see the every team CI status in one view. So I
Hi, Ulli
I think it's different from the BuildPipelinePlugin, but a few inspiration
from it.
My plugin can show the multiple build line relationship in one view. In my
company, multiple teams has their own build line, and manager or others want
to see the every team CI status in one view. So I
Is there any community interest in an Open Services for Lifecycle
Collaboration (OSLC) Automation plugin for Jenkins? Would anyone be
interested in helping to develop one?
*http://open-services.net/wiki/automation/*
Some of the scenarios for OSLC Automation are described here.
From all the alternatives
- not including the fix for JENKINS-18776 in 1.509.1
- reverting the bug in stapler, releasing it and using blending edge
stapler in LTS Jenkins
- or backporting necessary fix and using stapler 1.207.1
I prefer the last one but the decision is on you and Kohsuke.
Complete.
On Tue, Aug 6, 2013 at 12:32 PM, prithish chanda
prithish.cha...@gmail.com wrote:
Can you please review the code once and give me commit access, my changes
can be found @https://github.com/jenkinsci/sitemonitor-plugin/pull/4
username :- prithishchanda
IRC: jenkins-admin : Added
Done: https://github.com/jenkinsci/build-line-plugin
Welcome aboard!
Ulli
Am 06.08.2013 um 01:51 schrieb k.qing k.q...@outlook.com:
Hi, Ulli
I think it's different from the BuildPipelinePlugin, but a few inspiration
from it.
My plugin can show the multiple build line relationship in one
On Tue, Aug 6, 2013 at 12:22 PM, ogondza ogon...@gmail.com wrote:
the decision is on you and Kohsuke
I agree that this seems like the safest approach. BTW only Kohsuke can
do Stapler releases last I checked.
--
You received this message because you are subscribed to the Google Groups
Jenkins
Hello,
I am writing in hopes of resolving a possible bug with Jenkins. I am
running into an issue with the standalone jenkins installation and AJP/SSL.
According to the bug report below, this issue should be resolved. However,
it seems to persist with version 1.525 of Jenkins.
Please ignore.
Fixed in 1.526.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit
Hi,
AFAIK this is an issue confined to the (IMHO crappy) Maven project type.
IMHO the main issue is that backporting bigger changes done on top of the
trunk could be quite tricky and even if the code can be compiled, you can
easily break something - this backport e.g. requires also changes in
Oh, now I see what happens... Thanks a lot!
But what about fact, that prune should be done before fetching? (see JIRA
bug)
On Tuesday, August 6, 2013 6:39:20 PM UTC+7, nicolas de loof wrote:
Isn't
Thank you very much.
Date: Tue, 6 Aug 2013 10:47:35 -0700
From: ml-node+s361315n4676094...@n4.nabble.com
To: k.q...@outlook.com
Subject: Re: Join the jenkins development group
Done: https://github.com/jenkinsci/build-line-plugin
Welcome aboard!
Ulli
Am 06.08.2013 um 01:51 schrieb
Just a thought - would something like view-build-line-plugin or something
be a bit better? Right now we've got build-line-plugin,
build-pipeline-plugin, and build-flow-plugin and I wonder, if this plugin
in fact is a view (which it appears to be?), if prefixing it with view or
something would
Hi Jenkins Developers
As per the instructions on the Hosting Plugins [1] page, we'd respectfully
like to request creation of a plugin repository for the XebiaLabs Deployit
plugin [2]. Please grant commit rights initially to GitHub users mkotsur [3]
and XebiaLabsCI [4].
Thanks!
Andrew
[1]
25 matches
Mail list logo
