>
> Hello,
>
Any news about this request ?
Kind Regards
Olivier
--
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...@googlegroup
github repo: https://github.com/todorus/telegrambot
jenkins repository name: telegrambot-plugin
github user: todorus
jenkins-ci.org user: todorus
description: Allows you to send build results to a Telegram bot
I do not know how far along a plugin needs to be for it to be hosted on the
Jenkins plu
On 02.09.2015, at 23:53, Victor Martinez wrote:
> - The Extra Columns plugin is job based I'm afraid, does it make sense to
> merge those functionalities?
No. You cannot actually hide node columns AFAIK, so every installed + enabled
plugin always contributes its columns to the list. Until th
Hi,
any feedback?
Thanks
On Friday, 4 September 2015 21:11:06 UTC+2, Victor Martinez wrote:
>
> Hi,
>
> Any updates on this? Please let me know your thoughts and if you need
> further details.
>
> Thanks
>
> On Wednesday, 2 September 2015 23:53:22 UTC+2, Victor Martinez wrote:
>>
>> Hi,
>>
Of course if we kill bundled plugins (as in another thread) this
problem goes away.
--
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.
Hi Antonio
I try to reply e-mails/pr's within days, but unfortunately haven't been able to
review yours, sorry. Cesar is busy with some personal projects and won't be
able to help at the moment.
Three weeks is a reasonable time but I prefer to give plug-in maintainers at
least 5 weeks of notice
On Mon, 14 Sep 2015 16:59:11 +0200, Scott Hebert wrote:
In the case of a bundled plugin that has a test in the ATH, it seems that
the test will exercise the bundled version and never the latest version
that is available.
Take matrix-auth for example:
The exercised-plugins.properties file show
No.
Am Montag, 14. September 2015 17:50:53 UTC+2 schrieb Kanstantsin Shautsou:
>
> Have you tried PR/integrate it into existed subversion plugin?
>
> On Monday, September 14, 2015 at 6:30:44 PM UTC+3, Christian Haug wrote:
>>
>> Hi
>>
>> GitHub URL: https://github.com/cjhaug/svn-commit-plugin
>
On Sun, Sep 13, 2015 at 11:50 AM, Kanstantsin Shautsou
wrote:
> Seems that existed ATH code can be extended for creating channel, that can
> support automatic classloading and tests execution on remote side.
> The idea is to programmatically prepare complex environment (my test code)
I guess you
Have you tried PR/integrate it into existed subversion plugin?
On Monday, September 14, 2015 at 6:30:44 PM UTC+3, Christian Haug wrote:
>
> Hi
>
> GitHub URL: https://github.com/cjhaug/svn-commit-plugin
> GitHub username: cjhaug
> jenkins-ci.org username: cjhaug
> Description: Perform Subvers
Hello,
I've been pinging the maintainer of CCM Plugin for a while (@kinow) to
merge this PR: https://github.com/jenkinsci/ccm-plugin/pull/5
The second "official" maintainer (cesar1983, as listed in the pom)
does not seem to be active neither, so, could someone merge and
release this plugin? Or gi
Hi
GitHub URL: https://github.com/cjhaug/svn-commit-plugin
GitHub username: cjhaug
jenkins-ci.org username: cjhaug
Description: Perform Subversion commit on successful builds.
Regards Chris
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
I'm not sure about it. I'll try to evaluate the approach on this evening
and adjust the template if it works. If no, probably I'll just create a new
template for projects with submodules.
суббота, 12 сентября 2015 г., 18:25:54 UTC+3 пользователь Ullrich Hafner
написал:
>
> Ah, there is no manua
Hello guys,
I've received a reply from Stephan. Due to lack of time he can no longer
maintain the plugin (JiraTestResultReporter), so he would be happy if we
could take it over.
Is there a standard procedure of doing this?
Cheers,
Catalin
--
You received this message because you are subscri
On Mon, 14 Sep 2015 13:17:34 +0200, Kanstantsin Shautsou
wrote:
This spirit based on the fact that project leader has no time for
project, SPOF and blocker for almost any actions (btw other projects has
periodic elections, but it another story). In such situation you
providing write for
On Sep 14, 2015, at 13:23, nicolas de loof wrote:
>
> The spirit of jenkins community has always been to lower the entry barrier as
> much as possible (aka "want to contribute ? you can commit now") which for
> most of us do immediately remind the "great power gives great
> responsibilities" s
I'm trying design some "AIT (advanced integrations test)" :D for
docker-plugin/crowd2-plugins that has no tests at all and doesn't fit into
JenkinsRule/ATH, but it requires time and jenkins knowledge (plus
suggestions from experienced devs)
https://groups.google.com/forum/#!topic/jenkinsci-dev/
Thanks for reply. Thanks for plugin.
On Monday, September 14, 2015 at 10:00:23 AM UTC+3, Geoff Bullen wrote:
>
> Hi guys,
>
> Someone forwarded me this thread. Sorry for the misleading info on the
> wiki - I updated the "How to Contribute" page to point at the default one
> on the Jenkins
The spirit of jenkins community has always been to lower the entry barrier
as much as possible (aka "*want to contribute ? you can commit now*") which
for most of us do immediately remind the "*great power gives great
responsibilities*" spiderman-syndrom, and make people act with care and/or
rely o
If you maintain a separate branch with these UI changes, maybe we could
have an "auto release" of it and then run the plugin compat tester on that
version and compare the test results between the UI changed release and the
results of the weekly release to quickly find at least some of the issues
th
Branch may be more critical in plugin rather then master, so implicitly broke
other branches is not a solution IMHO.
Most maintainers has Admin access to their repos and can enable protection if
they want, no need enforcing it.
About [1]. This person was not maintainer of all (?) repos that he
Hi guys,
Someone forwarded me this thread. Sorry for the misleading info on the
wiki - I updated the "How to Contribute" page to point at the default one
on the Jenkins wiki. And sorry that we didn't update you when those email
addresses stopped being active.
We created this plugin whe
22 matches
Mail list logo
