Re: AppCenter Plugin up for adoption

[Mez Pahlan]

I've raised a PR to remove permissions for upload 
<https://github.com/jenkins-infra/repository-permissions-updater/pull/1943>. 
I've also removed myself from the github team for the plugin. But could I 
also be removed as the default assignee in JIRA please. Cheers.

On Tuesday, 27 April 2021 at 18:09:12 UTC+1 Mez Pahlan wrote:

> Hi everyone
>
> Sadly I can no longer continue to maintain the AppCenter Plugin for 
> Jenkins. :(. In line with the guidance 
> <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#how-can-i-mark-a-plugin-for-adoption>
>  
> I am announcing this decision here. 
>
> If anyone is interested then please apply to take over the maintenance. I 
> will shortly put the plugin up for adoption.
>
> https://github.com/jenkinsci/appcenter-plugin
>
> Thank you all for your help and patience with me over the years I have 
> learned a lot. Especial thanks to Oleg. You've been super brilliant!
>
> Mez
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/af6633b6-a29a-413f-b993-59a601452b5fn%40googlegroups.com.

AppCenter Plugin up for adoption

[Mez Pahlan]

Hi everyone

Sadly I can no longer continue to maintain the AppCenter Plugin for 
Jenkins. :(. In line with the guidance 

 
I am announcing this decision here. 

If anyone is interested then please apply to take over the maintenance. I 
will shortly put the plugin up for adoption.

https://github.com/jenkinsci/appcenter-plugin

Thank you all for your help and patience with me over the years I have 
learned a lot. Especial thanks to Oleg. You've been super brilliant!

Mez

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/38b338df-91a4-4f5a-bb9f-ebe9949d8ec3n%40googlegroups.com.

Re: What is the appropriate settings.xml to use these days?

[Mez Pahlan]

Thanks it 
does. https://github.com/jenkinsci/appcenter-plugin/blob/master/pom.xml#L229

Maybe there is something interfering in my IDE? Apologies I don't often use 
Maven so am learning (relearning) a lot of this for the first time.

On Saturday, 7 November 2020 at 17:34:43 UTC db...@cloudbees.com wrote:

> On Sat, Nov 7, 2020 at 4:35 PM Mez Pahlan  wrote:
>
>> Without the mirrors section I was getting the following error: Could not 
>> find artifact org.jenkins-ci.tools:maven-hpi-plugin:pom in central (
>> https://repo.maven.apache.org/maven2). That plugin is clearly not in the 
>> Central repo which lead me down the path trying to understand mirrors when 
>> I came across this answer 
>> <https://groups.google.com/g/jenkinsci-dev/c/CPH0jKKI23U/m/ciArzkJZJccJ>.
>>
>
> Make sure your project's pom.xml has something like 
> https://github.com/jenkinsci/archetypes/blob/98f86bdb7166893afc6faf0a4b06c75b5c5b18c3/empty-plugin/src/main/resources/archetype-resources/pom.xml#L53-L64
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/acb090aa-ec61-4aaf-8218-519b1722e10cn%40googlegroups.com.

Re: What is the appropriate settings.xml to use these days?

[Mez Pahlan]

Thanks for the pointers!

For anyone else looking as well as the credentials for publishing in my 
~/.m2/settings.xml I also needed to add a mirrors section otherwise I 
started to get weird dependency resolution issues. It looks like this at 
the moment which is significantly smaller to what I had to start with.


http://maven.apache.org/SETTINGS/1.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 
http://maven.apache.org/xsd/settings-1.0.0.xsd;>

  

  *
  public
  https://repo.jenkins-ci.org/public
  public

  

  

  maven.jenkins-ci.org 
  username
  encrypted_password

  



Without the mirrors section I was getting the following error: Could not 
find artifact org.jenkins-ci.tools:maven-hpi-plugin:pom in central 
(https://repo.maven.apache.org/maven2). That plugin is clearly not in the 
Central repo which lead me down the path trying to understand mirrors when 
I came across this answer 
<https://groups.google.com/g/jenkinsci-dev/c/CPH0jKKI23U/m/ciArzkJZJccJ>.

I hope this helps someone for the future.

On Monday, 12 October 2020 at 18:55:21 UTC+1 db...@cloudbees.com wrote:

> On Mon, Oct 12, 2020 at 7:19 PM Jesse Glick  wrote:
>
>> On Mon, Oct 12, 2020 at 7:36 AM Mez Pahlan  wrote:
>> > I am still curious as to what I should be putting in my settings.xml
>>
>> You do not really need one at all, as all Jenkins components declare
>> the Jenkins Artifactory repository.
>>
>
> Well, credentials to publish, but that's probably about it. Documented at 
> https://www.jenkins.io/doc/developer/publishing/releasing/#artifactory-credentials-for-maven
>  
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5d32803c-9216-4740-bfdd-8c076a4cf7d2n%40googlegroups.com.

Re: What is the appropriate settings.xml to use these days?

[Mez Pahlan]

Haha! It's always the way that you post a question and then figure out the 
answer straight afterwards!

To update this the error was a genuine permissions issue. I told a small 
lie above I did once dabble in using Docker and Jenkins on this machine and 
that messed up the permissions in the .m2 directory and set some folders as 
being owned by root. I deleted .m2 and started again and I was able to sync 
dependencies once more.

However I am still curious as to what I should be putting in my 
settings.xml as the last time I touched it was when I first started Jenkins 
plugin development and that was years ago.

On Monday, 12 October 2020 at 12:05:57 UTC+1 Mez Pahlan wrote:

> Hi everyone
>
> I'm getting the following error whilst trying to build a PR branch from a 
> contributor. They've bumped the parent POM version and minimum supported 
> Jenkins version and those changes look fine. However I can't download the 
> *new* artefacts from this PR which then causes some knock on issues in my 
> IDE.
>
> Could not transfer artifact org.jenkins-ci.main:jenkins-bom:pom:2.222.3 
> from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): 
> ~/.m2/repository/org/jenkins-ci/main/jenkins-bom/2.222.3/jenkins-bom-2.222.3.pom.part.lock
>  
> (No such file or directory)
>
> I started to look at my Maven settings.xml just in case and realised I 
> added that about two years ago and it may be out of date. So to rule that 
> out can anyone share a link of what the settings.xml should contain. I 
> realise it is highly personal to the developer but I only use Maven for 
> Jenkins development if that helps? At the moment I've got:
>
>- 
>   - org.jenkins-ci.tools
>   - 
>   - Defining the repositories and pluginRepositories
>   - Both pointing to https://repo.jenkins-ci.org
>- 
>   - A mirror for m.g.o-public 
>   - Pointing to https://repo.jenkins-ci.org
>   - 
>   - My secrets for plugin publishing
>
> Does that seem sensible? If so I can troubleshoot elsewhere. Thanks.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ce6535a3-2e5b-478b-9c3b-b9cf34ca894en%40googlegroups.com.

What is the appropriate settings.xml to use these days?

[Mez Pahlan]

Hi everyone

I'm getting the following error whilst trying to build a PR branch from a 
contributor. They've bumped the parent POM version and minimum supported 
Jenkins version and those changes look fine. However I can't download the 
*new* artefacts from this PR which then causes some knock on issues in my 
IDE.

Could not transfer artifact org.jenkins-ci.main:jenkins-bom:pom:2.222.3 
from/to repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/): 
~/.m2/repository/org/jenkins-ci/main/jenkins-bom/2.222.3/jenkins-bom-2.222.3.pom.part.lock
 
(No such file or directory)

I started to look at my Maven settings.xml just in case and realised I 
added that about two years ago and it may be out of date. So to rule that 
out can anyone share a link of what the settings.xml should contain. I 
realise it is highly personal to the developer but I only use Maven for 
Jenkins development if that helps? At the moment I've got:

   - 
  - org.jenkins-ci.tools
  - 
  - Defining the repositories and pluginRepositories
  - Both pointing to https://repo.jenkins-ci.org
   - 
  - A mirror for m.g.o-public 
  - Pointing to https://repo.jenkins-ci.org
  - 
  - My secrets for plugin publishing
   
Does that seem sensible? If so I can troubleshoot elsewhere. Thanks.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ef07ef09-6ddc-42b8-a0e0-007553376ce0n%40googlegroups.com.

Re: Adopt / co-maintain AppCenter plugin

[Mez Pahlan]

I think I recognise that. Yeah. I suppose you can add a link to this 
discussion if they ask for proof you're a maintainer? I think I've seen 
some other people do that.

On Thursday, 6 August 2020 at 13:06:26 UTC+1 snit...@gmail.com wrote:

>
>
> On Thursday, August 6, 2020 at 12:50:52 PM UTC+5:30, Mez Pahlan wrote:
>>
>> Brilliant! Thanks Nitin. I'll try and figure out how to add you as a 
>> maintainer.
>>
>> On Wednesday, 5 August 2020 at 16:00:11 UTC+1 snit...@gmail.com wrote:
>>
>>> Hello, Im interested. My github handle is snitin315 (
>>> https://github.com/snitin315)
>>
>>
> Hello Mez,  I think I have to add my name here,  
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-appcenter.yml
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/307b4468-14ea-4835-9e31-6b3e33bf8df3n%40googlegroups.com.

Re: Adopt / co-maintain AppCenter plugin

[Mez Pahlan]

Brilliant! Thanks Nitin. I'll try and figure out how to add you as a 
maintainer.

On Wednesday, 5 August 2020 at 16:00:11 UTC+1 snit...@gmail.com wrote:

> Hello, Im interested. My github handle is snitin315 (
> https://github.com/snitin315)

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/93b0d52d-64cd-4af4-b9db-2ff60f1b1235n%40googlegroups.com.

Adopt / co-maintain AppCenter plugin

[Mez Pahlan]

Hi friends!

I'm looking to see if anyone is interested in adopting (or at the very 
least co-maintaining) the Jenkins AppCenter plugin 
. I'm finding myself with 
increasingly little time to dedicate to this project unfortunately :(.

It mostly runs itself and I'm waiting for Microsoft to mature the AppCenter 
APIs to v1 before a bump to 1.0.0 of the plugin. Apart from that there are 
a few outstanding issues that I don't think impact the majority of use 
cases but do need to be looked at to provide a better experience to the 
users.

Is anyone interested / know of anyone? I think I'll leave this up here for 
a month before requesting for it to be marked as up for adoption formally.

Cheers

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0bcf759e-7d47-4eef-b910-806d00a65c2an%40googlegroups.com.

Re: Terminology Updates

[Mez Pahlan]

Why not extend the butler analogy? Majordomo. Or MD for short?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7fe97c15-6492-4764-a4f4-b8a8acc47006o%40googlegroups.com.

Re: accounts.jenkins.io can't login or use password reset

[Mez Pahlan]

I'm glad I checked here first!

Same thing happened to me. My user id is: mezpahlan

I registered more than 3 months ago but I *have* changed my password in the 
last 3 months and don't remember the old one any more. Do I need to 
password reset?

Thanks

On Wednesday, 3 June 2020 16:30:10 UTC+1, Johan Cornelissen wrote:
>
> Up until two days ago I was able to log into Jenkins LDAP without issues.
> Now if I try to login it says invalid password, and a password reset 
> attempt on https://accounts.jenkins.io/ isn't working (I receive no 
> email, even though password resets have worked for me in the past).
>
> Could someone help take a look? I'll send my username privately.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cf850002-2412-49a1-988b-65b992a7e633o%40googlegroups.com.

Re: Unable to perform plugin release to repo.jenkins-ci.org

[Mez Pahlan]

>though if your instructions do fix the issue then jenkins documentation is 
>incorrect: "Log in to Artifactory, and from your profile, obtain the encrypted 
>password."

I've recently changed laptops and have had to re setup my environment and 
obtained the encrypted password correctly using these instructions so they are 
not incorrect. 

I don't doubt you have an issue but could you list the steps you took one by 
one when you logged into Artifactory to when you pasted in your password to 
your settings for.

For the record I've also successfully done it the other way that is described 
in the alternate link by setting up a Maven master password that locally 
encrypts your password as opposed to getting the pre encrypted password from 
the server.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8586b9e2-faa0-4764-b37f-da73756f1c9d%40googlegroups.com.

Re: Release Drafter bug.... for the label bug

[Mez Pahlan]

The two most recent releases I've done didn't work. The last working 
release before that was on 20 March 2020 and contained feature rather than 
a bug. So it has worked in the past but I would struggle to confirm it 
working for PRs labelled with bug as I haven't done one of those since 19 
November 2019.

I don't recall setting up a github action so it must have been the app. Is 
there a way to confirm? I don't see anything enabled under the actions tab 
in the repository settings. Release Drafter is listed underneath 
Integration / Installed Github Apps.

Many thanks

On Saturday, 16 May 2020 20:31:17 UTC+1, Gavin Mogan wrote:
>
> Is it just those two PRs? - i don't know sorry
> or any PRs in general? - did you enable the app or github actions?
>
> On Sat, May 16, 2020 at 9:07 AM Mez Pahlan  > wrote:
>
>> Hi Jenkins Developers!
>>
>> Just a quick question about Release Drafter. I've merged two PRs that 
>> contained a single label named "bug" that failed to show up in the draft 
>> release. I can manually edit the draft so there's a workaround but I wanted 
>> to double check if this was a known issue or I have misconfigured something.
>>
>> This is my .github/release-drafter.yml 
>> <https://github.com/jenkinsci/appcenter-plugin/blob/master/.github/release-drafter.yml>
>>  and 
>> this is what it inherits from 
>> jenkinsci/.github/blob/master/.github/release-drafter.yml 
>> <https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml#L30>.
>>  
>> My label for bug is "bug" so I assume given that configuration things 
>> should work?
>>
>> Many thanks.
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/ba1934d7-9a11-45a4-b1a1-681d9bc15f06%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/ba1934d7-9a11-45a4-b1a1-681d9bc15f06%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/722fe4cf-2ea7-45ff-a3c1-2df191b48c25%40googlegroups.com.

Re: Allocate more memory to Jenkins whilst running hpi:run

[Mez Pahlan]

Thanks! Anecdotally that seems to help. I will give it some proper extended 
use and report back if it hasn't helped. For now it seems good. Thanks!

On Saturday, 8 February 2020 11:42:22 UTC, Mark Waite wrote:
>
> Does it help to run maven with the environment variable (per Java Heap 
> Settings best practice 
> <https://support.cloudbees.com/hc/en-us/articles/204859670-Java-Heap-settings-best-practice>
>  and 
> the Maven manual <http://maven.apache.org/configure.html>):
>
> *export MAVEN_OPTS="-Xms4g -Xmx4g"*
>
>
> On Sat, Feb 8, 2020 at 3:33 AM Mez Pahlan > 
> wrote:
>
>> Hi there
>>
>> I use hpi:run to give me a quick dev version of Jenkins with my plugin 
>> installed so that I can play around with it prior to committing changes. It 
>> works great! However I want to give it more memory so that it is more 
>> responsive and quicker to load pages. Is there a recommended way of doing 
>> this?
>>
>> Thanks
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b9806fc0-80ac-4265-a93d-e0b2b17bfe40%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/b9806fc0-80ac-4265-a93d-e0b2b17bfe40%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/71ab58af-d211-455d-b3d2-8ccfff9f0917%40googlegroups.com.

Allocate more memory to Jenkins whilst running hpi:run

[Mez Pahlan]

Hi there

I use hpi:run to give me a quick dev version of Jenkins with my plugin 
installed so that I can play around with it prior to committing changes. It 
works great! However I want to give it more memory so that it is more 
responsive and quicker to load pages. Is there a recommended way of doing 
this?

Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b9806fc0-80ac-4265-a93d-e0b2b17bfe40%40googlegroups.com.

Re: Lock JIRA issues

[Mez Pahlan]

Thanks for the replies. I think the effort to lock the tickets down sounds 
like it outweighs the benefits of making it easy for people to contribute. 
That's all right. I think upon reflection that's a better principle to 
promote. 

It doesn't happen often so when it does I'll continue to revert the changes.

Thanks everyone!

On Friday, 1 November 2019 02:15:04 UTC, Daniel Beck wrote:
>
> Not easily; we could try some workaround like limiting the permission to 
> edit to, for example, assignees or applicable component leads, but that 
> would just add friction for many legitimate uses. 
>
> We could also maintain a group in Jira that is made up of all plugin 
> maintainers, and limit some actions to that group, which probably has 
> similar problems as above (and if any of these several hundred users 
> perform actions you don't like, you're just out of luck). The necessary 
> APIs exist, and we know who plugin maintainers are, but it's an imprecise 
> tool to capture "users who should be able to perform certain actions" -- 
> and the overhead of manual curation of such a list would easily outweigh 
> the benefits. 
>
> If it's clearly abusive behavior, you could file an infra issue requesting 
> that the offending account be destroyed. 
>
> (Note that Jira's keyboard shortcuts make it extremely easy to 
> accidentally perform certain actions like assign-to-self.) 
>
> > On 31. Oct 2019, at 20:26, Mez Pahlan > 
> wrote: 
> > 
> > I was wondering if there was a way to lock JIRA tickets? I've had a few 
> instances where I've had random people changing the status of a ticket 
> without discussing with the maintainer of the plugin (me). 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/31a4de2f-37f9-4cfc-aece-d87596bcdf8d%40googlegroups.com.

Lock JIRA issues

[Mez Pahlan]

I was wondering if there was a way to lock JIRA tickets? I've had a few 
instances where I've had random people changing the status of a ticket 
without discussing with the maintainer of the plugin (me). I use JIRA to 
prioritise the work on the plugin I maintain and that's quite difficult 
when tickets change in ways you're not expecting.

I realise this is very low priority but I was wondering what other people 
do in these cases?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/84c0c4d4-5dc6-4f79-a02a-04e4f77b5618%40googlegroups.com.

Re: Constant ci.jenkins.io failures - am I just unlucky?

[Mez Pahlan]

Many thanks Baptiste for picking this up. When you say provide a status 
check here do you mean to add your stack traces to this forum thread or to 
the INFRA ticket you linked to or something else?

Cheers.

On Thursday, 31 October 2019 10:28:42 UTC, Baptiste Mathus wrote:
>
> I filed https://issues.jenkins-ci.org/browse/INFRA-2308 after Arnaud 
> rightly recommended to have something public and central for us to fix this.
>
> Pretty please anyone who's been suffering from ci.jenkins.io recent 
> instabilities, do not hesitate to provide a status check here.
> We're especially interested in common stack traces or errors you're seeing.
>
> We have started analyzing support bundles. First step is 
> https://github.com/jenkins-infra/jenkins-infra/pull/1375
>
> More to come.
>
> Thanks!
>
> Le mer. 30 oct. 2019 à 14:56, Arnaud Héritier  > a écrit :
>
>> I still don't have an admin access on the instance but I have a system 
>> level access. 
>> I was able to grab few bundles and we will see if it helps to start to 
>> diagnose the issue
>>
>> On Wed, Oct 30, 2019 at 12:47 AM Daniel Beck > > wrote:
>>
>>>
>>>
>>> > On 27. Oct 2019, at 12:58, Daniel Beck > 
>>> wrote:
>>> > 
>>> > 
>>> > 
>>> >> On 27. Oct 2019, at 11:29, Arnaud Héritier >> > wrote:
>>> >> 
>>> >> Do we have the support-core plugin installed on this instance ? If 
>>> no, can
>>> >> we add it ?
>>> > 
>>> > We had it installed for years and nobody cared. After it showed up 
>>> recently in a thread dump as the likely cause of excessive load while 
>>> generating background bundles, I disabled it.
>>>
>>> And since support-core is disabled, the next restart will disable 
>>> metrics plugin too.
>>>
>>> We're affected by JENKINS-59793, with currently (AFAICT ~30 minutes 
>>> after restart) more than 700 of these threads.
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/38DAE091-615B-48EC-B9BD-904F8A044323%40beckweb.net
>>> .
>>>
>>
>>
>> -- 
>> -
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier AT gmail DOT com
>> Twitter/Skype : aheritier
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8uGtbPdyAyVBoHfXzNPLQre7Rp%3DHc1v_BGWqFeuS%3D9mg%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a93ee5ab-305e-49e7-8b38-77f8a09fbac7%40googlegroups.com.

Re: Constant ci.jenkins.io failures - am I just unlucky?

[Mez Pahlan]

Thanks for the reply Oleg

>
I am sure it is a massive task maintaining the infra side of things and 
more contributors will hopefully help. We all *do* appreciate the hard work 
and my comments were mostly out of frustration last night. I tend to do my 
plugin development on the weekend so maybe I have simply been caught out in 
an unlucky time period. As a suggestion is there a way to notify a 
different build status for Github instead of build failed? With some 
message that easily identifies developers should rerun the build locally?

Good luck with the efforts!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5dfff07a-a92f-48df-a18b-08c5dabf32f8%40googlegroups.com.

Constant ci.jenkins.io failures - am I just unlucky?

[Mez Pahlan]

Am I doing something wrong here? I *constantly* get failures with 
ci.jenkins.io typically with agents not working when I expect them to. Not 
build failures with my plugin but infra issues before the plugin even gets 
built. Typically out of memory issues when the build doesn't even start. At 
the time of writing there are ~320 jobs waiting to be built and most of the 
agents marked as offline. I've seen that number a lot higher in the past. I 
honestly don't know whether this is a common issue or not. Typically I end 
up waiting either days for a Windows agent or in this most recent failure I 
can't even connect to a windows agent so the Linux part of the build 
doesn't even start and the whole build is marked as a failure.

My Jenkinsfile looks like this:

buildPlugin(useAci: true)

I only added useAci after finding out in a similar manner that my builds 
were failing with infra issues without it.

I thought the recommendation was to add a buildPlugin() statement in a 
Jenkinsfile in your plugin's root directory. I therefore assumed that what 
actually builds the plugin is stable most of the time. Have I got the wrong 
end of the stick? Should I be using something else in my Jenkinsfile? I 
can't be the only plugin dev to face these issues which leads me to believe 
I must be doing something wrong or thinking about this in the wrong way. Do 
I just happen to be building my plugin at the wrong time of the week?

I know I can always proceed to with my PRs and builds by ignoring the 
result of the CI build but then. what's the point of the recommendation 
to add buildPlugin() 
?

Yours massively frustrated

Mez

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9914283d-cc5a-40ff-8a0d-ce5a4eca2a6d%40googlegroups.com.

Re: Failed to build https://github.com/jenkinsci/p4-plugin/pull/110

[Mez Pahlan]

Same thing happened to my PRs. If it is any consolation after 10 hours mine 
kicked into life. Run the CI build commands locally and *if you are happy* you 
can merge the PR without waiting for the build to complete. That's just 
what I do, I'm not suggesting this will work for everyone.

The real answer must be to fix the Jenkins Infra CI environment to be more 
stable / provide better feedback to the PR on these types of errors. But 
that will take time.

On Friday, 4 October 2019 15:18:47 UTC+1, Charu wrote:
>
> Hello,
>
> Infrastructure for windows seems to be broken. Could you have a look 
> please? Getting the below messages in build log:
>
> [2019-10-04T11:05:00.301Z] Still waiting to schedule task
>
> [2019-10-04T11:05:00.301Z] Waiting for next available executor on ‘linux’
>
> [2019-10-04T11:07:05.627Z] win2012-121390 was marked offline: Connection 
> was broken: java.util.concurrent.TimeoutException: Ping started at 
> 1570186985625 hasn't completed by 1570187225626
>
> Thank you.
>
> Regards,
> Charu
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9a0c6027-f73c-47fe-8402-6415d736aa7d%40googlegroups.com.

Re: Rechecking Pull Requests

[Mez Pahlan]

I've come to the conclusion that there is no way to do this. You can't 
select Build Now from the Jenkins Infra CI build site (probably to protect 
against spam usage which is fair enough) and nor do you have this on 
Github. So you need to create a new "event" in the PR as described above. 

Whilst it is really frustrating that the build has failed due to no fault 
of your own and that this causes a big red cross to appear, it was 
explained to me that these builds are meaningless and don't *actually* block 
your PR. You can ignore the result of the CI build and merge *if you feel 
it is safe*.

What I would like, given this, is for Jenkins Infra CI builds to send back 
not a build failure but something like *build unstable* if that is possible 
and detect when a build failure is caused by a bad PR or by bad 
infrastructure. If a human can read the logs and determine this then surely 
it is possible to do automatically. Maybe that would be a happy middle 
ground between (what seems to be to me) 90% successful infrastructure 
builds and 10% failures unrelated to your PR. What I would do instead is 
run mvn clean install locally and confirm the build. And maybe a message to 
that effect would be good too.

On Saturday, 5 October 2019 03:28:48 UTC+1, Gavin Mogan wrote:
>
> A lot of people is close the pr. Then wait like 30 seconds. And reopen it.
>
> On Fri., Oct. 4, 2019, 6:56 p.m. Mark Waite,  > wrote:
>
>> The simplest technique for me has been to use `git commit --amend` on the 
>> most recent commit, then force push that change to the repository.  There 
>> is almost always something that I can improve about the last commit in a 
>> pull request.
>>
>> On Fri, Oct 4, 2019 at 7:45 PM Richard Bywater > > wrote:
>>
>>> Hi
>>>
>>> One of my pull requests failed on ci.jenkins.io due to what looks like 
>>> an infrastructure issue ( 
>>> https://ci.jenkins.io/job/Plugins/job/htmlpublisher-plugin/view/change-requests/job/PR-48/3/console
>>>  
>>> )
>>>
>>> Is there a way of getting it to re-run the build job on the PR as I 
>>> don't seem to have access to "Build Now" on the Jenkins infrastructure and 
>>> Github doesn't seem to have a "recheck" option either. 
>>>
>>> Ideally I'd really love to not have to create a dummy commit to do it as 
>>> that doesn't really seem like a very good way of getting around the issue 
>>> of jobs that fail due to infrastructure issues.
>>>
>>> Thanks
>>> Richard.
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwfoQdE%3Dr03LTgqC9_0XvnhgnAVTC4kNPftE6n7jCPV40A%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Thanks!
>> Mark Waite
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEUqBFdHCmubyfkojveMs2Z4hsOXpk9SfU29-tYX%3D%2BJuw%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6eafa9bb-6f0e-4268-9438-1808080fcd3c%40googlegroups.com.

Re: Proxy details

[Mez Pahlan]

If you get an instance of Jenkins via Jenkins.get() then you have access to 
a field that contains the proxy details jenkins.proxy. If you access this 
object you should be able to get the details you need.

On Thursday, 19 September 2019 07:13:06 UTC+1, selva vignesh wrote:
>
> Hi,
> How to get proxy details in Jenkins plugin development.where i am 
> developing plugin for my use, Which need to proxy details of Jenkins.
> Kindly share the example code snippet to get proxy details.
> Thanks in advance.
>
>
> Regards,
> Selva
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/57239e95-3169-4733-b088-7567e2a35b8f%40googlegroups.com.

Re: hpi:run not installing plugin..... half installed?

[Mez Pahlan]

> Have you tried just adding a `provided`-scope dependency on that, as is 
suggested for old mojo versions, rather than configuring 
`maven-compiler-plugin`?

Brilliant! Thanks this did the trick. I removed the whole build block and 
added the dagger-compiler as a provided dependency and now everything works 
as I expect.

Fantastic. Thanks for the help Jesse! And thanks everyone else too!

On Wednesday, 11 September 2019 21:46:15 UTC+1, Jesse Glick wrote:
>
> On Wed, Sep 11, 2019 at 4:19 PM Mez Pahlan  > wrote: 
> > I tried removing the following from my POM which had the effect of 
> making my plugin visible again in the snippet generator. 
> > 
> >  
> >  
> >  
> > org.apache.maven.plugins 
> > maven-compiler-plugin 
> >  
> >  
> >  
> > com.google.dagger 
> > dagger-compiler 
> > 2.24 
> >  
> >  
> >  
> >  
> >  
> >  
>
> Well I checked this artifact and it does define the expected 
> `META-INF/services/javax.annotation.processing.Processor`. Have you 
> tried just adding a `provided`-scope dependency on that, as is 
> suggested for old mojo versions, rather than configuring 
> `maven-compiler-plugin`? That should make everything work, at the 
> minor cost of allowing the build to proceed even if you accidentally 
> linked against a class in that artifact. 
>
> You can see at 
>
>
> https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#annotationProcessorPaths
>  
>
> that the suggested configuration *blocks* the compiler from using 
> standard processors, and Jenkins relies on a bunch of them. 
>
> In other words: the Dagger recommendation for new mojo versions is, at 
> best, incomplete, and arguably very bad advice. It ought to say that 
> you can use `annotationProcessorPaths` only if you are using a new 
> mojo, and either know for a fact that your project uses no other 
> annotation processors, or are willing to enumerate them all in the 
> POM. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/763cd817-27e1-4a4c-9245-7c09310ffd4b%40googlegroups.com.

Re: hpi:run not installing plugin..... half installed?

[Mez Pahlan]

I tried removing the following from my POM which had the effect of making 
my plugin visible again in the snippet generator.




org.apache.maven.plugins
maven-compiler-plugin



com.google.dagger
dagger-compiler
2.24








I got this from the Dagger 2 README Maven setup section 
<https://github.com/google/dagger/blob/master/README.md#maven>. So this 
definitely narrows down the cause of the missing plugin. Unfortunately I 
need this included in some form or the other. Are there any special 
settings I can add to this to ensure that the dagger-compiler runs but 
doesn't break the packaging of the plugin?

Thanks

On Wednesday, 11 September 2019 20:54:01 UTC+1, Mez Pahlan wrote:
>
> Hi Gavin
>
>
> I'm not getting an error which is the tricky bit. Here are some 
> screenshots (hopefully you can click to enlarge, let me know if not).
>
> Here's the plugin in the Plugin Manager:
>
>
>
> [image: Screenshot from 2019-09-11 20-49-10.png]
>
>
> And here's the list of build steps my plugin used to appear in but 
> doesn't. It used to be second in this list.
>
>
> [image: Screenshot from 2019-09-11 20-48-48.png]
>
>
>
>
>
> On Wednesday, 11 September 2019 20:39:38 UTC+1, Gavin Mogan wrote:
>>
>> The pipeline steps are annotations symbols right? @Extension for the 
>> step, and @Symbol for the short name
>> Would an extra annotation parser cause any issue? I would guess they are 
>> non destructive and able to overlap quite easily.
>>
>> What error are you getting when you are trying to use steps?
>>
>> Also check your plugin manager ui, it often lets you know if things 
>> failed to load, sometimes if you are lucky, why they failed to load.
>>
>> Gavin
>>
>> On Wed, Sep 11, 2019 at 12:35 PM Mez Pahlan  wrote:
>>
>>> Hi Matt
>>>
>>> I don't have any experience with Guice but do with Dagger 2. I did try 
>>> and understand the differences but there wasn't a lot of guidance on how to 
>>> use it within Jenkins so I started to implement the Dagger 2 alternative. 
>>> It worked in the IDE in the sense that it compiled correctly and tests that 
>>> I had written in Java to exercise the functionality of my plugin also work.
>>>
>>> > As for running an annotation processor in a plugin, isn't that 
>>> how @MetaInfService, @Indexed, @Restricted, and the like, are handled 
>>> at compile time? 
>>>
>>> Errr.. pass. I don't know about these. Are you saying I should use 
>>> these instead or that I am OK to use an annotation processor as these are 
>>> examples of where ones are already in use?
>>>
>>> For some clarity Dagger 2 uses a compile time annotation processor to 
>>> generate code.
>>>
>>> Hope that helps and thanks.
>>>
>>> On Wednesday, 11 September 2019 20:22:31 UTC+1, Matt Sicker wrote:
>>>>
>>>> Jenkins bundles Guice for dependency injection, though due to some 
>>>> historical API decisions, it's not that easy to use in practice. As 
>>>> for running an annotation processor in a plugin, isn't that how 
>>>> @MetaInfService, @Indexed, @Restricted, and the like, are handled at 
>>>> compile time? 
>>>>
>>>> On Wed, Sep 11, 2019 at 2:17 PM Mez Pahlan  wrote: 
>>>> > 
>>>> > Thanks for the answers Jesse! 
>>>> > 
>>>> > > Try specifically: mvn clean hpi:run 
>>>> > 
>>>> > Same issue. Builds fine no obvious errors in the terminal output and 
>>>> Jenkins starts normally. Plugin is listed in the list of installed plugins 
>>>> but I cannot use it in a Pipeline or Freestyle job. 
>>>> > 
>>>> > > Why? This would be extremely unusual. 
>>>> > 
>>>> > I'm using Dagger 2 for dependency injection because 1) I'm used to 
>>>> using it in other Java projects 2) whilst I've been developing the plugin 
>>>> in the IDE it just worked 3) I am not aware of any banned / incompatible 
>>>> Java libraries that we must not use (but obviously I am happy to be 
>>>> corrected on this). 
>>>> > 
>>>> > Any further tips on attempting to track down the cause of this? 
>>>> > 
>>>> > On Wednesday, 11 September 2019 14:38:04 UTC+1, Jesse Glick wrote: 
>>>> &g

Re: hpi:run not installing plugin..... half installed?

[Mez Pahlan]

Hi Slide

Good question. They have been like that since before this branch of the 
plugin I am working on. Do you think I've not got the correct ones? Or 
they're in the wrong scope?

On Wednesday, 11 September 2019 20:22:21 UTC+1, slide wrote:
>
> Are all the required plugins installed? I noticed you had several items 
> marked as test scope in the pom.xml. 
>
> On Wed, Sep 11, 2019, 12:17 Mez Pahlan > 
> wrote:
>
>> Thanks for the answers Jesse!
>>
>> > Try specifically: mvn clean hpi:run
>>
>> Same issue. Builds fine no obvious errors in the terminal output and 
>> Jenkins starts normally. Plugin is listed in the list of installed plugins 
>> but I cannot use it in a Pipeline or Freestyle job.
>>
>> > Why? This would be extremely unusual.
>>
>> I'm using Dagger 2 for dependency injection because 1) I'm used to using 
>> it in other Java projects 2) whilst I've been developing the plugin in the 
>> IDE it just worked 3) I am not aware of any banned / incompatible Java 
>> libraries that we must not use (but obviously I am happy to be corrected on 
>> this).
>>
>> Any further tips on attempting to track down the cause of this?
>>
>> On Wednesday, 11 September 2019 14:38:04 UTC+1, Jesse Glick wrote:
>>>
>>> On Wed, Sep 11, 2019 at 3:20 AM Mez Pahlan  wrote: 
>>> > I've looked at the local work directory in my IDE that is created when 
>>> hpi:run is executed and I can see a file called appcenter.hpl but there 
>>> isn't an expanded folder called appcenter in the way that other plugins 
>>> have expanded folders. 
>>>
>>> This is normal. The link file points to source directories rather than 
>>> needing an archive to be unpacked. 
>>>
>>> > I have also tried running the mvn hpi:run command from outside of the 
>>> IDE and I get the same issue. 
>>>
>>> Try specifically 
>>>
>>> mvn clean hpi:run 
>>>
>>> > I've added an annotation processor in my POM 
>>>
>>> Why? This would be extremely unusual. 
>>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/c413ae0c-d0eb-4d56-8698-f6eae88664a8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/c413ae0c-d0eb-4d56-8698-f6eae88664a8%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/63bfd923-0010-4c4f-8f8b-dc7ce3135c01%40googlegroups.com.

Re: hpi:run not installing plugin..... half installed?

[Mez Pahlan]

Hi Matt

I don't have any experience with Guice but do with Dagger 2. I did try and 
understand the differences but there wasn't a lot of guidance on how to use 
it within Jenkins so I started to implement the Dagger 2 alternative. It 
worked in the IDE in the sense that it compiled correctly and tests that I 
had written in Java to exercise the functionality of my plugin also work.

> As for running an annotation processor in a plugin, isn't that 
how @MetaInfService, @Indexed, @Restricted, and the like, are handled 
at compile time? 

Errr.. pass. I don't know about these. Are you saying I should use 
these instead or that I am OK to use an annotation processor as these are 
examples of where ones are already in use?

For some clarity Dagger 2 uses a compile time annotation processor to 
generate code.

Hope that helps and thanks.

On Wednesday, 11 September 2019 20:22:31 UTC+1, Matt Sicker wrote:
>
> Jenkins bundles Guice for dependency injection, though due to some 
> historical API decisions, it's not that easy to use in practice. As 
> for running an annotation processor in a plugin, isn't that how 
> @MetaInfService, @Indexed, @Restricted, and the like, are handled at 
> compile time? 
>
> On Wed, Sep 11, 2019 at 2:17 PM Mez Pahlan  > wrote: 
> > 
> > Thanks for the answers Jesse! 
> > 
> > > Try specifically: mvn clean hpi:run 
> > 
> > Same issue. Builds fine no obvious errors in the terminal output and 
> Jenkins starts normally. Plugin is listed in the list of installed plugins 
> but I cannot use it in a Pipeline or Freestyle job. 
> > 
> > > Why? This would be extremely unusual. 
> > 
> > I'm using Dagger 2 for dependency injection because 1) I'm used to using 
> it in other Java projects 2) whilst I've been developing the plugin in the 
> IDE it just worked 3) I am not aware of any banned / incompatible Java 
> libraries that we must not use (but obviously I am happy to be corrected on 
> this). 
> > 
> > Any further tips on attempting to track down the cause of this? 
> > 
> > On Wednesday, 11 September 2019 14:38:04 UTC+1, Jesse Glick wrote: 
> >> 
> >> On Wed, Sep 11, 2019 at 3:20 AM Mez Pahlan  wrote: 
> >> > I've looked at the local work directory in my IDE that is created 
> when hpi:run is executed and I can see a file called appcenter.hpl but 
> there isn't an expanded folder called appcenter in the way that other 
> plugins have expanded folders. 
> >> 
> >> This is normal. The link file points to source directories rather than 
> >> needing an archive to be unpacked. 
> >> 
> >> > I have also tried running the mvn hpi:run command from outside of the 
> IDE and I get the same issue. 
> >> 
> >> Try specifically 
> >> 
> >> mvn clean hpi:run 
> >> 
> >> > I've added an annotation processor in my POM 
> >> 
> >> Why? This would be extremely unusual. 
> > 
> > -- 
> > 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 jenkin...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/c413ae0c-d0eb-4d56-8698-f6eae88664a8%40googlegroups.com.
>  
>
>
>
>
> -- 
> Matt Sicker 
> Senior Software Engineer, CloudBees 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c73d39dd-8474-414e-a1d3-6f9c3a440868%40googlegroups.com.

Re: hpi:run not installing plugin..... half installed?

[Mez Pahlan]

Thanks for the answers Jesse!

> Try specifically: mvn clean hpi:run

Same issue. Builds fine no obvious errors in the terminal output and 
Jenkins starts normally. Plugin is listed in the list of installed plugins 
but I cannot use it in a Pipeline or Freestyle job.

> Why? This would be extremely unusual.

I'm using Dagger 2 for dependency injection because 1) I'm used to using it 
in other Java projects 2) whilst I've been developing the plugin in the IDE 
it just worked 3) I am not aware of any banned / incompatible Java 
libraries that we must not use (but obviously I am happy to be corrected on 
this).

Any further tips on attempting to track down the cause of this?

On Wednesday, 11 September 2019 14:38:04 UTC+1, Jesse Glick wrote:
>
> On Wed, Sep 11, 2019 at 3:20 AM Mez Pahlan  > wrote: 
> > I've looked at the local work directory in my IDE that is created when 
> hpi:run is executed and I can see a file called appcenter.hpl but there 
> isn't an expanded folder called appcenter in the way that other plugins 
> have expanded folders. 
>
> This is normal. The link file points to source directories rather than 
> needing an archive to be unpacked. 
>
> > I have also tried running the mvn hpi:run command from outside of the 
> IDE and I get the same issue. 
>
> Try specifically 
>
> mvn clean hpi:run 
>
> > I've added an annotation processor in my POM 
>
> Why? This would be extremely unusual. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c413ae0c-d0eb-4d56-8698-f6eae88664a8%40googlegroups.com.

hpi:run not installing plugin..... half installed?

[Mez Pahlan]

Hi there

I am trying to test my plugin using hpi:run which builds and compiles with 
no errors but I can't see my plugin in the list of plugins when using the 
Snippet Generator. I can see it in the list of installed plugins in the 
Plugin Manager but it is also not available for use in a pipeline.

Previous versions of my plugin worked fine and I can't see anything obvious 
that would cause this behavior. The branch I am trying to build and test is 
https://github.com/mezpahlan/appcenter-plugin/tree/JENKINS-58887-create-internal-tasks-and-public-tasks.
 
This also builds on the CI server and creates an HPI. However when I try 
and install this manually I get no log output and no obvious errors / 
warnings but I still can't use my plugin. I have also tried to list the 
installed plugins using the Script Console which shows me the same 
information that the Plugin Manager does which is that my plugin is 
installed.

I've looked at the local work directory in my IDE that is created when 
hpi:run is executed and I can see a file called appcenter.hpl but there 
isn't an expanded folder called appcenter in the way that other plugins 
have expanded folders. I have also tried running the mvn hpi:run command 
from outside of the IDE and I get the same issue.

I've added an annotation processor in my POM and some new test dependencies 
but other than that I can't see anything obvious. Again, everything 
compiles and my tests pass when I'm running this as a plain Java project.

Any help is much appreciated. Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3e3a8e2b-516e-4b19-856e-c1a0cf1bf544%40googlegroups.com.

Re: Jenkins CI Windows node failed on release - should I be concerned?

[Mez Pahlan]

Thanks Gavin, great explanation and insight. I'm likely worrying about nothing. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1d7a90e2-2aec-4bfd-8861-3e29533ca827%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins CI Windows node failed on release - should I be concerned?

[Mez Pahlan]

Hi again. I'm probably worrying about nothing but this looked strange to me.

https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fappcenter-plugin/activity/

During a release:prepare release:perform maven will request two builds from 
the CI server due to two commits to master. The first commit is the actual 
release the second is preparing for the next development cycle but contains 
no changes apart from a snapshot version number bump in the POM file. 
Should I be concerned that the actual release build failed on the CI server 
but the snapshot build did not? Is my plugin going to be published in this 
state? I know from past experience that if this happens for PR builds you 
can simply close and reopen the PR to trigger another build but what am I 
supposed to do here? Create a new release?

Again. I might be worrying about nothing but I thought I should ask :)

Thanks!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a685c8ac-e178-44c1--1242347c2f17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a master-slave setup when developing a plugin

[Mez Pahlan]

Thanks both. Great suggestions. I'll give them a go.

On Monday, 8 July 2019 17:57:51 UTC+1, Jesse Glick wrote:
>
> On Sat, Jul 6, 2019 at 9:32 AM Mez Pahlan > 
> wrote: 
> > 1. hpi:run 
> > 2. Configure Jeknins -> Manage Nodes -> Add additional slave 
> > 3. Download the JAR file after setting up the new node 
> > 4. Run the JAR file in a separate command line process 
> > 
> > This is quite tedious but it works. Am I missing something? 
>
> Yes: https://plugins.jenkins.io/mock-slave 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/adf8ccfa-7a7a-4022-8e67-765f3a264c2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Cannot build PR on ci.jenkins.io: no space left on device

[Mez Pahlan]

Hi again

I'm trying to build a PR for my plugin and am running into issues with the 
ci.jenkins.io build server. It keeps telling me that there is no space left 
on the device. I've raised the following issue but it doesn't look like 
anyone else has this issue so I'm wondering if it is just me :(

https://issues.jenkins-ci.org/browse/INFRA-2170

Is there something I can do about this? I'd rather not keep triggering 
unnecessary builds if there is a deeper structural problem. Alternatively 
is this error message misleading and there is something wrong with my 
plugin code? The tests pass on my development machine.

Thanks.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/00cd429a-92a2-4e59-87d1-cb96f1cb963b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Testing a master-slave setup when developing a plugin

[Mez Pahlan]

Hi everyone!

Whilst developing a plugin I find it really useful to be able to run 
hpi:run and quickly get an instance of Jenkins with my plugin that I can 
test. However this only creates a single Master setup. Is there a better / 
easier way to quickly get a master-slave setup so I can test how my plugin 
works in a distributed environment? At the moment I am doing the following:

1. hpi:run
2. Configure Jeknins -> Manage Nodes -> Add additional slave
3. Download the JAR file after setting up the new node
4. Run the JAR file in a separate command line process

This is quite tedious but it works. Am I missing something?

Cheers

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/211d4658-f955-424c-a435-6f5f21041b82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins is Getting Old ! is that true ?!!

[mez . pahlan]

Hi Parker, nice to meet you too . Sure thing, anything I can do to help. I'm a 
bit time limited at the moment but let me know what you need and I'll try and 
make some time to discuss. To save everyone getting spammed on this thread I'll 
email you directly. Cheers.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/694c3092-18ad-4d36-acec-a48cdb552d66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins is Getting Old ! is that true ?!!

[mez . pahlan]

A lot of those points resonated with me. 

I started using Jenkins (well Hudson) years ago to simplify manual 
builds and quickly discovered the power it brings. This was really 
exciting. I am a mobile developer and I also maintain a plugin on Jenkins. 
All the issues I had to struggle with on mobile platforms are still present 
on Jenkins. Hard to test, hard to reason (why things need to happen the way 
they do), poor documentation, lack of examples of "how to do it correctly". 
I'm pleased to say a lot of that has changed on my day to day work as a 
mobile develop but I have to say, I really struggle with Jenkins.

One thing that really helps on other platforms (Android / Spring Boot / 
etc) is having an *opinionated* way of doing things. Maybe I'm missing 
something but the bare bones starter project still allows for a lot of 
deviation meaning plugins can end up looking wildly different.

However, the community is *great*. It really is. Lots of people willing to 
help. So I really cannot fault it there. And of course, I and other 
community members can always update the documentation and contribute back. 
And we should. But personally I've simply not had time to dedicate to this 
as I only dabble in Jenkins as a hobby not full time. I need a CI ecosystem 
that *just works* and that I can easily contribute to. 

I should stress this is my personal opinion and I don't speak for any other 
user of Jenkins but myself. 

On Tuesday, 30 April 2019 16:43:40 UTC+1, hossa...@gmail.com wrote:
>
> Hello my friends , 
> i hope you doing greate.
> i have read an article that talk about jenkins and some of its 
> inconveniences .
> it's a subject to discuss about .
>
> this is the link to the blog:   
> https://itnext.io/jenkins-is-getting-old-2c98b3422f79
>  
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7c0306e2-7986-4e8d-9948-66fc28eb379d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate a token stored in plain text to one that uses Secret

[Mez Pahlan]

> The plain text tokens are already potentially compromised and need to
> be regenerated and stored encrypted anyways. This is specific to each
> plugin on how to go about regenerating keys and whatnot.
>

Yes, when you put it like that it makes more sense not to worry about
migration.

Thank you all again.

>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GuTwZWcUebtpbAjuz4wm3Gm8GcjGNvx%3Dhcae-r8wXMnug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate a token stored in plain text to one that uses Secret

[Mez Pahlan]

>
> There is not any good way that I know of. I would just ignore it.
>

I could ignore it, for sure. But that was the reason I received a security
bug that I'm looking to fix. That the tokens in my plugin were being stored
in plain text. If I leave them in plain text what am I actually fixing? I'm
fixing forward for new configurations but for existing configurations I'd
like to do something.

Anyways, thanks for the suggestions so far.

>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5Guy7%3DtvcvgGJkhO_D-YELLdC7cLt4JqkKkPWdxAwbGLbQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Migrate a token stored in plain text to one that uses Secret

[Mez Pahlan]

Morning

I'm trying to migrate a plugin that used to use plain text for handling 
tokens to one that uses Secret. I am following 
https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility
 and 
have converted all my field types to Secret from String for the token in 
question.

This all works fine when I run the plugin (I think the readResolve method 
is doing some magic at runtime) and if I create a new job configuration (I 
can see an encrypted form of my entered token in the config.xml file). 
However for existing jobs that already that an unencrypted plain text token 
in the config.xml it remains that way and appears never to get resaved in 
the encrypted form. So whilst the plugin uses Secrets, there is still old 
data that is persisted in plain text form.

What's the best way to migrate those over without asking the user to go 
into each of their jobs updating it?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f532cd94-4af2-4c13-bdb9-7a94e024620d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to safely upgrade the minimum Jenkins version

[Mez Pahlan]

Thanks James

Version 3.11 is a weird one. It always existed on the stats before I joined 
the project and to be best of my knowledge it isn't a plugin version we've 
released. No idea how it got onto the stats page.

I think I am reading the stats incorrectly, thanks for the sense check. In 
that case I think I'll bump it straight up to my preferred level in the 
next minor update.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c288b3a9-abaf-45e6-b901-78c64e8efdca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to safely upgrade the minimum Jenkins version

[Mez Pahlan]

I'm looking to bump the minimum version of Jenkins for the plugin I 
maintain. Currently it is 1.625.3 which is a really old version of Jenkins. 
I want to move over to the 2.x line but was wondering what sort of strategy 
people recommend? I've checked out the stats for my plugin 
 and it appears that 
around 75% of the current installs are on a version of Jenkins that I would 
like to bump the minimum version to, 2.73.3. 


   1. Is this too much of a bump? Cutting off 25% of the user base sounds 
   scary.
   2. If I am going to do that would it make sense to bump it up to a more 
   recent LTS version?
   3. Is it worth doing this over a number of minor releases starting with 
   the 2.7.3 LTS and bumping up every time I release another minor.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4dfee1f8-da01-4b8e-949f-c9de6ea2b68f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enforcer fails on Jenkins CI server but passes locally what am I doing wrong?

[Mez Pahlan]

Ahhh.. ok. Yup that did work. Thanks Jesse!

For anyone else. I then investigated why it worked in a shell and not in 
the IDE. Turns out I forgot that I had set my IDE to use the current LTS 
Jenkins version as a Maven profile setting (using ~/.m2/settings.xml). So 
all my IDE runs were using the latest LTS to run Enforcer against but the 
Jenkins CI server was using the version defined in my POM which was 
(correctly) failing.

So in other words the problem was me! Hope this helps anyone else.

On Thursday, 4 October 2018 20:30:05 UTC+1, Jesse Glick wrote:
>
> On Thu, Oct 4, 2018 at 3:20 PM Mez Pahlan  > wrote: 
> > Notice that the parent POM has a Java level set to 8 so I remove my java 
> version tag from my POM 
>
> You must be using an old version of the parent POM. All recent 
> versions treat `java.level` as mandatory (no default). 
>
> > I'm running these through IntelliJ IDEA and executing maven goals from 
> the GUI if that helps? 
>
> When in doubt, run 
>
> mvn clean install 
>
> from a shell. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/92d226e9-6b3b-4eac-a7e3-b870868dc329%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Enforcer fails on Jenkins CI server but passes locally what am I doing wrong?

[Mez Pahlan]

Hello all

As it says in the title. I'm working with a PR for the HockeyApp Plugin and 
after making some changes I dutifully run all tests locally using the 
verify maven goal before I push changes to the PR. All checks pass I'm 
happy, computer is happy, I push. BAM! it fails on the Jenkins CI build 
says that Enforcer is unhappy about Java versions (plugin asks for 7 
however some dependencies ask for 8). OK fair enough, I say, I'll fix that. 
Notice that the parent POM has a Java level set to 8 so I remove my java 
version tag from my POM and double check where the CI build failed: on the 
clean install maven goal. So I run clean and install locally. Everything 
passes. I'm happy, computer is happy, I push. BOOM! It fails again with 
another Enforcer error.. What!?

I must be doing something wrong but can't for the life of me understand 
what. How can I reproduce the checks that are going to be run on the CI 
server before I push? In particular the Enforcer checks? I can play the 
"push a change - wait for build" game but I would rather push working 
changes if possible.

I'm running these through IntelliJ IDEA and executing maven goals from the 
GUI if that helps?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/dfe91aa8-5aed-4d30-826a-a900b84e705f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Wiki plugin labels

[Mez Pahlan]

That's perfect thank you. PR filed. :)

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e322cb15-3972-4bd1-9ef5-713bcf9ca85f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wiki plugin labels

[Mez Pahlan]

I maintain the HockeyApp plugin and was curious as to why the *android* label 
does not appear on the plugin page  
nor on the Android filter on the plugin index 
.

I used the Jenkins plugin API for my plugin and saw that the label is 
indeed not appearing in the returned JSON so can understand why it wouldn't 
appear in the two places I mentioned above. However I can't quite work out 
where to add the label.

{
  ...
  
  "categories": [
"languagesPlatforms",
"buildManagement"
  ],
  "excerpt": "This plugin allows you to upload new versions of your iOS (.ipa), 
MacOS (.app), and Android (.apk) applications to hockeyapp.net.",
  "gav": "org.jenkins-ci.plugins:hockeyapp:1.3.2",
  "labels": [
"upload",
"ios"
  ],
  "name": "hockeyapp",
  "title": "HockeyApp",
  "url": 
"http://updates.jenkins-ci.org/download/plugins/hockeyapp/1.3.2/hockeyapp.hpi;,
  "version": "1.3.2",
  
  ...
}


In the wiki page  
itself I have added a *plugin-android* label in the same way that there 
already existed *plugin-upload* and *plugin-ios* but that hasn't helped. Is 
there someplace else I should be adding it? 

Many thanks.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/86c93fa1-8b7b-46c8-bd19-17e1cc9d71c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Maintaining a dormant plugin

[Mez Pahlan]

Hello everyone

I have recently been added as a maintainer of the HockeyApp plugin and note 
that it has been fairly dormant. My goals are to make the plugin pipeline 
compatible, refactor the project, and add additional unit tests. I have two 
questions for the community.


   1. I'm happy to review other contributor's PRs and merge them, however 
   what should I do with my own? Ideally I would like another maintainer to 
   review and approve them but judging by the activity over the past year I 
   equally do not want to delay this for longer than needed.
  - I have already reached out the the existing team via email and this 
  forum when requesting to become a maintainer. I have also reached out via 
  the Github team.
   2. What is the etiquette for removing dormant maintainers from the 
   project POM, the project team in Github, the wiki information, anywhere 
   else?


I totally understand maintaining a plugin is hard work and people have 
lives so cannot commit to it 100% of their time. I'm just looking to do 
some housekeeping and make it easier for future maintainers to know whom to 
contact. 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b1ed4a6d-cdfd-437b-8e2a-f4ec96211d96%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become a maintainer for hockeyapp

[Mez Pahlan]

Thank you. I'm a little busy over this weekend but will start on these as 
soon as I can and get this plugin moving along again.

I'll take a look at PR45 too :)

On Friday, 25 May 2018 00:31:20 UTC+1, Oleg Nenashev wrote:
>
> Done. You should have access to GitHub now (if no, check your inbox for 
> the organization invitations).
> You are also a default assignee in JIRA now. In order to release the 
> plugin, you will also need to update 
> https://github.com/jenkins-infra/repository-permissions-updater/
>
> Welcome aboard!
>
> Best regards,
> Oleg
>
> P.S: would also appreciate a merge of 
> https://github.com/jenkinsci/hockeyapp-plugin/pull/45
>
>
> On Wednesday, May 23, 2018 at 8:59:53 AM UTC+2, Mez Pahlan wrote:
>>
>> Morning all
>>
>> It has been two weeks since the request. Can we kick off the process for 
>> me to join the maintenance team for the HockeyApp plugin please?
>>
>> Thank you.
>>
>> Mez
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/201401bc-b4b5-4d35-b25a-ae2f23308bec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become a maintainer for hockeyapp

[Mez Pahlan]

Morning all

It has been two weeks since the request. Can we kick off the process for me
to join the maintenance team for the HockeyApp plugin please?

Thank you.

Mez

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GvcmpnAsTFr4jQNf2%2Bqv8_MuQRWoQb1sf73um187FDiAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Request to become a maintainer for hockeyapp

[Mez Pahlan]

Hi everyone

I would like to formally request to become a maintainer for the hockeyapp 
plugin, please.

I have started a PR  
and a thread discussion 
 
detailing why and my efforts to reach the existing maintainers.

Jenkins Infrastructure idt: mezpahlan
Github id: mezpahlan

Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/33806b79-d73b-4ecc-b31f-1417753b74f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: HockeyApp plugin maintainers

[Mez Pahlan]

Thanks for the comments on the PR. It's looking a lot better already!

Yes, four more days and I will then ask officially to be a maintainer - and 
then another two weeks until that goes through. I think that would be 
plenty of time to give the existing maintainers a chance.

Mez

On Tuesday, 1 May 2018 09:43:19 UTC+1, Oleg Nenashev wrote:
>
> Responded to the PR.
> IIUC we have 4 days before the response timeout, right?
>
> On Tue, May 1, 2018 at 8:43 AM, Mez Pahlan <mez.p...@gmail.com 
> > wrote:
>
>> Trying one last time to reach the existing plugin maintainers.
>>
>> Hello could you review this thread please and give me your thoughts on 
>> the existing PRs please.
>>
>> Thanks
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/LBSZruW0Lfs/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GvyFACymV_ai-%3DzciCLDP%3DnBVHaPGf2TJ%3D%3DU0YD9OFkbA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GvyFACymV_ai-%3DzciCLDP%3DnBVHaPGf2TJ%3D%3DU0YD9OFkbA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6e82dfec-81ab-492e-a441-1046ae36cce2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: HockeyApp plugin maintainers

[Mez Pahlan]

Trying one last time to reach the existing plugin maintainers.

Hello could you review this thread please and give me your thoughts on the
existing PRs please.

Thanks

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GvyFACymV_ai-%3DzciCLDP%3DnBVHaPGf2TJ%3D%3DU0YD9OFkbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: HockeyApp plugin maintainers

[Mez Pahlan]

Cc'ing the maintainers.

Hello maintainers, could you give me your thoughts on this thread please.

Thanks.

On 19 April 2018 at 11:49, Daniel Beck <m...@beckweb.net> wrote:

> Please make sure to reach out to the maintainers via email as well (CCing
> them in a response to this thread). Automated notifications are too easy to
> miss.
>
> > On 18. Apr 2018, at 08:24, Mez Pahlan <mez.pah...@gmail.com> wrote:
> >
> > Thank you, you've been great! I'll wait for a reply on Github for two
> weeks and then kick off the explicit request after that. Hopefully that
> will give everyone enough time without rushing.
> >
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/LBSZruW0Lfs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/62336813-1A46-44AA-B629-B732E52F6FFD%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAD7v5GuZ_1f5AW8_C5QvOts5qGP63B5_jQRG54Zx1nMcvq_ZVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: HockeyApp plugin maintainers

[Mez Pahlan]

Hi Oleg

Thank you, you've been great! I'll wait for a reply on Github for two weeks 
and then kick off the explicit request after that. Hopefully that will give 
everyone enough time without rushing.

Mez

On Tuesday, 17 April 2018 21:32:48 UTC+1, Oleg Nenashev wrote:
>
> Hi Mez,
>
> We have a process for abandoned plugins ownership handover (2 weeks after 
> the explicit request and ping of maintainers). More info 
> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess>
>
> If you are interested to take ownership of the plugin, the next step would 
> be to sent them a direct email (see their JIRA profiles). After that we 
> could start countdown and transfer ownership if there is no response. 
> Brantone <https://github.com/Brantone> seems to be active in GitHub 
> though, so hopefully you will get a response earlier.
>
> Hopefully it helps,
> Oleg
>
>
> On Tuesday, April 17, 2018 at 9:53:35 PM UTC+2, Mez Pahlan wrote:
>>
>> Hello Jenkins Devs!
>>
>> I'm interested in contributing to the HockeyApp 
>> <https://www.google.com/url?q=https%3A%2F%2Fplugins.jenkins.io%2Fhockeyapp=D=1=AFQjCNGYvpdMfx8_08zlZsOFmJXqiUgT-A>
>>  
>> plugin and want to reach out to the plugin maintainers to see if they can 
>> help resolve some PRs. My immediate interest is in the PR#48 
>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkinsci%2Fhockeyapp-plugin%2Fpull%2F48=D=1=AFQjCNGpo5kdBnfxvM640tLvabhuxwq1hg>
>>  
>> that I have raised but I also notice that there are a number of outstanding 
>> PRs that have not progressed - some for over a year.
>>
>> Oleg Nenashev has been kind enough to help me with my PR and ping the 
>> current maintainers but I want to try on here as well.
>>
>> ping [brantone - Brenton Barte, dkochetkov - Denis Kochetkov, ohoeltke - 
>> Oliver Hoeltke]
>>
>> In the future, I would like to raise more PRs so want to be sure they can 
>> be progressed. I'd be happy to become a maintainer too but would probably 
>> need some help and guidance on that as I have not done that before.
>>
>> Cheers!
>>
>> Mez
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6d1b6ab7-ff82-4f18-b225-87e9aae8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

HockeyApp plugin maintainers

[Mez Pahlan]

Hello Jenkins Devs!

I'm interested in contributing to the HockeyApp 
 plugin and want to reach out to the 
plugin maintainers to see if they can help resolve some PRs. My immediate 
interest is in the PR#48 
 that I have raised 
but I also notice that there are a number of outstanding PRs that have not 
progressed - some for over a year.

Oleg Nenashev has been kind enough to help me with my PR and ping the 
current maintainers but I want to try on here as well.

ping [brantone - Brenton Barte, dkochetkov - Denis Kochetkov, ohoeltke - 
Oliver Hoeltke]

In the future, I would like to raise more PRs so want to be sure they can 
be progressed. I'd be happy to become a maintainer too but would probably 
need some help and guidance on that as I have not done that before.

Cheers!

Mez

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/41f0970f-3e99-40c9-85c8-d1d4c2989d75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.