Hi there,
We will do localization work for some Jenkins core and plugins, more detail
is here https://groups.google.com/forum/#!topic/jenkinsci-dev/QJQ_fzfILcI
In order to do localization better, it will be more convenient if we get
the permission to merge PR request.
--
You received this
Hey there,
I'm updating one of my plugins, and I ran into the RequireUpperBoundDeps
issue:
$ mvn clean package
[INFO] Scanning for projects...
[INFO]
[INFO] ---< br.com.ingenieux.jenkins.plugins:codecommit-url-helper
>---
[INFO] Building AWS CodeCommit URL Helper 0.0.2-SNAPSHOT
[INFO]
Jenn,
Thank you for managing Jenkins pipeline and Blue Ocean. Those technologies
have really improved the user experience of using Jenkins, and adoption is
quickly
growing. In the companies I have worked at, everyone that I have shown
Blue Ocean to
has liked it.
I would like to request two
> On 17. Aug 2018, at 15:38, Jesse Glick wrote:
>
> On Fri, Aug 17, 2018 at 7:57 AM Daniel Beck wrote:
>>> Do you plan to implement this data collection in the core directly or in a
>>> plugin?
>>
>> Core (or core module).
>
> Fine for the initial example of collecting system properties,
Hi,
I'd like to adopt the ec2-plugin. I discussed briefly with the maintainer and
he doesn't have objection.
My credential are :
GitHub Login: thoulen
Jenkins Login: thoulen
I will send a pull request soon.
Br
FM
--
You received this message because you are subscribed to the Google Groups
And to confirm, I support this.
On Fri, 17 Aug 2018 at 10:31, Fabrizio Manfredi
wrote:
> Hi,
> I'd like to adopt the ec2-plugin. I discussed briefly with the maintainer and
> he doesn't have objection.
> My credential are :
> GitHub Login: thoulen
> Jenkins Login: thoulen
>
> I will send a pull
Let's also get a response from Stephen
On Fri, Aug 17, 2018, 18:18 Matt Sicker wrote:
> Great, thanks. Filed a PR at repository-permission-updater.
>
> On Fri, Aug 17, 2018 at 10:58 AM Jesse Glick wrote:
>
>> On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker
>> wrote:
>> > CCing Jesse and Stephen
(replies inline)
On Fri, 17 Aug 2018, Oleg Nenashev wrote:
> I like the JEP draft in the current state.
>
> IMHO it would be great to extend Infrastructure Requirements a bit:
>
>- A new Tweetdeck account is created
>- Jenkins INFRA team has access to Tweetdeck so it can handle the
>
Great, thanks. Filed a PR at repository-permission-updater.
On Fri, Aug 17, 2018 at 10:58 AM Jesse Glick wrote:
> On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker
> wrote:
> > CCing Jesse and Stephen who seem to be the two most active maintainers
> historically for this plugin.
>
> According to
On Fri, Aug 17, 2018 at 10:51 AM Matt Sicker wrote:
> CCing Jesse and Stephen who seem to be the two most active maintainers
> historically for this plugin.
According to history I have never done any material changes to the
plugin at all. If you care to maintain it, go ahead from my PoV.
--
CCing Jesse and Stephen who seem to be the two most active maintainers
historically for this plugin.
On Fri, Aug 17, 2018 at 6:45 AM Oleg Nenashev
wrote:
> Please reach out to the maintainer and get his explicit confirmation in
> this thread.
> If you want to request ownership transfer, the
On Fri, Aug 17, 2018 at 7:57 AM Daniel Beck wrote:
>> Do you plan to implement this data collection in the core directly or in a
>> plugin?
>
> Core (or core module).
Fine for the initial example of collecting system properties, but in
general this sort of collection will need to make use of
I like the JEP draft in the current state.
IMHO it would be great to extend Infrastructure Requirements a bit:
- A new Tweetdeck account is created
- Jenkins INFRA team has access to Tweetdeck so it can handle the
requests if needed
- The account is documented on the Jenkins INFRA
Hello.
Is there a way to check the implementation of the 'Run' button from the
'Restart from Stage' action (job->build number page).
I would want to check how i can build a pipeline from a specific stage and
I thought this functionality would be the same, but in my case I would like
to build
Yes, the request has timed out.
I have granted you permissions in GitHub and made you a default assignee.
If you are not a member of the JenkinsCI org, you should get an invitation
soon.
Welcome aboard!
Best regards,
Oleg Nenashev
On Thursday, August 16, 2018 at 8:01:42 PM UTC+2, Tobias
Hi Oleg,
I saw the e-mails! I hope I will have time next week to update the plug-in
:).
Kind regards,
Hugo Boog
Op donderdag 16 augustus 2018 19:41:50 UTC+2 schreef Oleg Nenashev:
>
> Hi Hugo,
>
> The permissions have been granted.
> Welcome aboard, and thanks for your patience!
>
> Best
> On 17. Aug 2018, at 13:17, Oleg Nenashev wrote:
>
> Do you plan to implement this data collection in the core directly or in a
> plugin?
Core (or core module).
> Obviously, we need to review conflicts with JEP-308 (Telemetry API for
> evergreen) so that the proposals do not conflict
Please reach out to the maintainer and get his explicit confirmation in
this thread.
If you want to request ownership transfer, the process is described here:
https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess
BR, Oleg
On Thursday, August 16, 2018 at
Hi Daniel,
Thanks for the amendment!
Would it be also possible to add an "Announcement" section to reasoning and
explicitly document why proposals (blogpost, administrative warning, direct
maintainer notification) are rejected?
I still disagree with the user notification approach taken in this
Hi Daniel,
Do you plan to implement this data collection in the core directly or in a
plugin?
In any case, it looks like a good opportunity to for us to get some data,
so +1 for implementing the engine.
Obviously, we need to review conflicts with JEP-308
20 matches
Mail list logo
