Hello,
We recently received 2 new Jenkins Ambassador applications. I am placing
their qualifications below. Xuefeng and Tao will be attending DevOps World
| Jenkins Worlds SF (traveling from China) and are looking forward to
meeting Jenkins contributors. I've added this item for tomorrow's
govern
Hi
Just wanted to put out a call to see who identifies with being the
maintainer for the Bitbucket Branch Source Plugin at the moment.
Reason I ask is that there's a few PRs building up at the moment and one of
them ( https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/115 )
would be
Thanks!
On Tuesday, August 28, 2018 at 3:50:51 PM UTC-4, Daniel Beck wrote:
>
>
>
> > On 28. Aug 2018, at 21:32, Mike Chmielewski > wrote:
> >
> > Connect to maven.jenkins-ci.org:8081 [
> maven.jenkins-ci.org/199.193.196.24] failed: Operation timed out
>
> See
> https://wiki.jenkins.io/displa
> On 28. Aug 2018, at 21:32, Mike Chmielewski
> wrote:
>
> Connect to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24]
> failed: Operation timed out
See
https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues
3rd item
--
You receiv
Hello,
I am finally getting around to releasing a new version of my plugin,
parameter-separator, and it is failing when trying to push to
maven.jenkins-ci.org:8081.
My repo was cloned with SSH, so I have a settings.xml with my
jenkins-ci.org username/password, and I registered my github kep wi
> On 28. Aug 2018, at 15:10, Oleg Nenashev wrote:
>
> I can imagine a local company which installs a single localization plugin
> That's why I lean towards having separate plugins for each locale.
… and an aggregator. It's free. Only needs updates whenever a locale plugin is
added or remove
I wonder how many people plan to separate their localization resource
files. If there is not so much, I suggest that keep other languages files
in current place.
On Tue, Aug 28, 2018 at 9:17 PM Jesse Glick wrote:
> On Tue, Aug 28, 2018 at 9:10 AM Oleg Nenashev
> wrote:
> > I would expect Increm
On Tue, Aug 28, 2018 at 9:10 AM Oleg Nenashev wrote:
> I would expect Incremental Tools to eventually simplify managing of
> aggregator plugins.
How…? `incrementals-tools` does not seem related to me.
I tend to agree that a single localization plugin would be simpler to
manage in most respects.
>
> So they would simply not install any localization plugin. Great, so
> they're completely irrelevant as far as considering their preferences goes
> (beyond removing translations from everywhere else).
I can imagine a local company which installs a single localization plugin
That's why I lean t
> On 28. Aug 2018, at 14:54, Oleg Nenashev wrote:
>
> I do not know any organization which actually does that. Usually Jenkins is
> managed via various shared services teams if it gets to such scale, and
> having different localizations makes the system generally unsupportable.
> Imagine yo
>
> In language diverse communities or organizations, having to install (or
> request installation) of a new translation plugin every month, because now
> a
> French/German/Italian/Russian/Portuguese/Spanish/Chinese/Turkish/Polish/Czech/…
> speaking person wants their Jenkins localized in their own
Thanks for your checklist and suggestion. That's really great.
On Tue, Aug 28, 2018 at 6:57 PM Jesse Glick wrote:
> On Tue, Aug 28, 2018 at 2:34 AM arch wrote:
> > Agree with this solution. And I give a prototype plugin.
> https://github.com/LinuxSuRen/localization-plugin
>
> Nice, did you get
Hi team,
In our *Builder class*(IntegrationLeader and RunActionOnApp) we have a
function called *configure, *which fetches the values of global
configuration using below lines of code.
CustomGlobalConfiguration calmGlobalConfiguration =
CustomGlobalConfiguration.get();
calmIP = calmGlobalConfigur
> On 28. Aug 2018, at 11:00, Robert Sandell wrote:
>
> And from what I've seen so far usernames seems to only be appended to the
> permissions, so it's not a good source of finding the actual current
> maintainer in there.
Perhaps this is something that needs to be clarified -- removing prev
> On 28. Aug 2018, at 08:44, Oleg Nenashev wrote:
>
> I would rather prefer separate plugins for each localization.
> It would allow to properly form reviewer teams and to manage release cycles
> independently.
Only with an aggregator plugin. Otherwise the benefits of managing separate
per-
> On 28. Aug 2018, at 11:00, Robert Sandell wrote:
>
> I don't think jenkins-infra/repository-permissions-updater should be the
> starting point. It's hard to find and harder to remember,
It will necessarily be linked from anywhere documenting the adoption process.
If your experience is that
On Tue, Aug 28, 2018 at 5:00 AM Robert Sandell wrote:
> It's hard to find and harder to remember
That would certainly need to be addressed, at a minimum by having the
adoption wiki page walk you through the steps to patch this.
> it takes me a while to figure out if I have messed something up or
On Tue, Aug 28, 2018 at 2:34 AM arch wrote:
> Agree with this solution. And I give a prototype plugin.
> https://github.com/LinuxSuRen/localization-plugin
Nice, did you get this to work already? There are a few things to check:
· core vs. plugin localization
· `Messages_zh_CN.properties` (so `M
I don't think jenkins-infra/repository-permissions-updater should be the
starting point. It's hard to find and harder to remember, at least for me.
And once found it's hard to find stuff in it. And the couple of times that
I've done changes in there it takes me a while to figure out if I have
messe
Ivan, after many pings I was unable to get the requested actions from the
maintainer (e.g. releasing pending PRs).
Are you still interested in taking ownership?
If yes, I am ready to transfer it.
BR, Oleg
On Tuesday, April 17, 2018 at 4:10:06 PM UTC+2, Oleg Nenashev wrote:
>
> Hi Ivan,
>
> Actua
On Mon, Aug 27, 2018 at 3:03 PM Daniel Beck wrote:
>
> I only read the finished JEP and earlier messages in this thread, so may
> have missed further out of band communication.
>
>
Thanks for the feedback. I have had no out of band communication regarding
this JEP other than this e-mail thread.
21 matches
Mail list logo
