Re: Plugin health scores not updated

[Adrien Lecharpentier]

I haven't say but I'll look into the problem asap

Le mer. 26 juin 2024, 13:04, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> It's not quite that.
> The probe data is fetched every hour or so. Less if the repository hasn't
> changed, or no release since last checked.
> Then the probe data is used to crunch scores through the scoring process.
>
> Those scores are stored in a DB and exposed through /api/scores endpoint.
>
> This endpoint is curled by
> https://github.com/jenkins-infra/infra-reports/blob/main/plugin-health-scoring/Jenkinsfile
>
> This creates a file in https://reports.jenkins.io/plugin-health-scoring/
> which is used when the plugin site is generated.
>
> That's the all process.
>
> Le mer. 26 juin 2024, 12:51, Zbynek Konecny  a
> écrit :
>
>> The plugin score workflow:
>> * plugin health score service crawls GitHub and Artifactory, stores the
>> data and exposes it through API --
>> https://plugin-health.jenkins.io/api/scores
>> * reports generator stores the output of said API in a static JSON file
>> (via
>> https://github.com/jenkins-infra/infra-reports/blob/main/plugin-health-scoring/Jenkinsfile
>> )
>> * this JSON is downloaded each time the plugin site is rebuilt
>> Looks like already the first step is not producing any up-to-date data, I
>> created an issue
>> https://github.com/jenkins-infra/plugin-health-scoring/issues/522
>>
>> Cheers,
>> Zbynek
>>
>> On Wed, 26 Jun 2024 at 10:57, 'Michael Kriese' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>> I can see that the health scores on my plugins are not updated since 2
>>> or 3 month.
>>> https://plugins.jenkins.io/ui/search/?query=viceice
>>>
>>> Is there an issue with the updater?
>>>
>>> https://github.com/jenkins-infra/plugin-health-scoring
>>>
>>> Regards
>>> Michael
>>>
>>> --
>>> 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/12b6393f-6aa4-44bb-b00f-351a89d3ebc8n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/12b6393f-6aa4-44bb-b00f-351a89d3ebc8n%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/CABFvdGpJGNUU0Q6n%2BQj8tK-QVimS2nqRyeW9VeJeFGhF%3D_AKLw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CABFvdGpJGNUU0Q6n%2BQj8tK-QVimS2nqRyeW9VeJeFGhF%3D_AKLw%40mail.gmail.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/CAKwJSvxkaAZ7_jA6wUjPq%3DbJP-NBQe1DOCvgbGbvGji8xoc9HA%40mail.gmail.com.

Re: Plugin health scores not updated

[Adrien Lecharpentier]

It's not quite that.
The probe data is fetched every hour or so. Less if the repository hasn't
changed, or no release since last checked.
Then the probe data is used to crunch scores through the scoring process.

Those scores are stored in a DB and exposed through /api/scores endpoint.

This endpoint is curled by
https://github.com/jenkins-infra/infra-reports/blob/main/plugin-health-scoring/Jenkinsfile

This creates a file in https://reports.jenkins.io/plugin-health-scoring/
which is used when the plugin site is generated.

That's the all process.

Le mer. 26 juin 2024, 12:51, Zbynek Konecny  a écrit :

> The plugin score workflow:
> * plugin health score service crawls GitHub and Artifactory, stores the
> data and exposes it through API --
> https://plugin-health.jenkins.io/api/scores
> * reports generator stores the output of said API in a static JSON file
> (via
> https://github.com/jenkins-infra/infra-reports/blob/main/plugin-health-scoring/Jenkinsfile
> )
> * this JSON is downloaded each time the plugin site is rebuilt
> Looks like already the first step is not producing any up-to-date data, I
> created an issue
> https://github.com/jenkins-infra/plugin-health-scoring/issues/522
>
> Cheers,
> Zbynek
>
> On Wed, 26 Jun 2024 at 10:57, 'Michael Kriese' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> I can see that the health scores on my plugins are not updated since 2 or
>> 3 month.
>> https://plugins.jenkins.io/ui/search/?query=viceice
>>
>> Is there an issue with the updater?
>>
>> https://github.com/jenkins-infra/plugin-health-scoring
>>
>> Regards
>> Michael
>>
>> --
>> 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/12b6393f-6aa4-44bb-b00f-351a89d3ebc8n%40googlegroups.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/CABFvdGpJGNUU0Q6n%2BQj8tK-QVimS2nqRyeW9VeJeFGhF%3D_AKLw%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/CAKwJSvyYKoDw%2BPtJ23Gsc92NhkSsMZi5ehtXJCrTc-VKpOAJFw%40mail.gmail.com.

Re: Unable to Release Plugin

[Adrien Lecharpentier]

Hi,

Could you problem the link of the plugin repository?
This looks like the version on the project is not suffixed with `-SNAPSHOT`
which probably means it wasn't reset after previous release or was manually
removed since.

Le ven. 10 mai 2024, 08:33, selvavi...@gmail.com 
a écrit :

> Hi Team,
> I revamped the existing plug-in and tried to release a latest version.
> However i got error and unable to release the plugin. During previous
> release i did not face the issue like this.
>
> Kindly assist me to release the plugin.
>
> --
> 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/28cdfff9-e4ee-4953-bd94-df391289a45an%40googlegroups.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/CAKwJSvyHbbEBcoFpX6RvCx6fm7oJb_CEY%2BujFsaMkqPUMPfSVw%40mail.gmail.com.

Re: Retire some of my old plugins

[Adrien Lecharpentier]

Thank you Gavin for your contributions and all the time you spent on the
project.

Le mar. 7 mai 2024, 03:46, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Okay, only 2 months later...
>
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3915
> should remove me from everything
> I also added deprecated label to the two dead ones
>
> Plugin site seems updated
>
> thanks ya'll
>
> On Tue, Mar 19, 2024 at 5:27 AM 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> On Sun, Mar 17, 2024 at 9:01 AM 'Alexander Brandes' via Jenkins
>> Developers  wrote:
>>
>>> To mark the plugins as EOL, I recommend adding the “deprecated” topic to
>>> the GitHub repositories, adding a note to the README that the plugin is
>>> EOL, closing open PRs and archiving the GH repository.
>>>
>>
>> In both cases it looks like continued distribution makes no real sense,
>> so I recommend
>> https://github.com/jenkins-infra/update-center2/?tab=readme-ov-file#removing-plugins-from-distribution
>> in addition to the above.
>>
>>
>>> Finally, you can remove yourself from the repository-permission-updater
>>> file.
>>>
>>
>> To clarify (as this has been a problem in the past): Keep the file, just
>> remove your 'developers' list entry (likely resulting in `developers: []`
>> for valid YAML).
>>
>> --
>> 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/CAMo7PtLjLhc_5RtfWU1hgUSs2JjuF13busQWiesve8xGMQw6sA%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/CAG%3D_Dutn2DKh_tyPhH5qBE-pJ4i94JrTzaRUshqW_rpe8tU%2BEg%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/CAKwJSvzh8jK-HSgjbQ6yb_WrcJ95HWi7rXrhHDX5qDWNOQYwng%40mail.gmail.com.

Re: Adopt email-ext plugin

[Adrien Lecharpentier]

Funny thing: link to the pull request is not correct but it's text is.

Link is
https://github.com/jenkins-infra/repository-permissions-updater/pull/3851

Le jeu. 28 mars 2024, 18:55, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> +1 from me.
> Basil is listed as maintainer but the repo has the adopt-this-plugin
> topic. Don't know if +1 are really required here.
>
> Le jeu. 28 mars 2024, 18:00, Kris Stern  a écrit :
>
>> +1
>> --
>> *From:* jenkinsci-dev@googlegroups.com 
>> on behalf of Verachten Bruno 
>> *Sent:* 29 March 2024 00:58
>> *To:* jenkinsci-dev@googlegroups.com 
>> *Subject:* Re: Adopt email-ext plugin
>>
>> +1 from me.
>>
>> On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>> +1 from me!
>>
>> On Thu, Mar 28, 2024 at 11:58 AM Alex Earl  wrote:
>>
>> Howdy,
>>
>> The email-ext plugin is up for adoption. I'd like to re-adopt it (been a
>> few years so I may be a little rusty :) )
>>
>> RPU pull request:
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/3851
>> <https://github.com/jenkins-infra/repository-permissions-updater/pull/3831>
>> GitHub username: slide (already member of jenkinsci organization)
>> Jenkins username: slide_o_mix
>>
>> Thanks
>>
>> Alex
>>
>> --
>> 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/ee3bd5a5-ca18-4642-94c5-3a3b83640515n%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/ee3bd5a5-ca18-4642-94c5-3a3b83640515n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>>
>> --
>> Kevin Martens
>> Technical Content Developer
>> CloudBees, Inc.
>>
>>
>> E: kmart...@cloudbees.com
>>
>> Pronouns: He/Him/His
>>
>> --
>> 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/CAP92yNeKCGoyWDtYh%2B1pQMzi-cXKx2O5ntjRSm6LLVC05qVz1g%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAP92yNeKCGoyWDtYh%2B1pQMzi-cXKx2O5ntjRSm6LLVC05qVz1g%40mail.gmail.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/CACtV%3DdcnuLN4c1U-qESD1U7nNrTiLw4vPO6pO31ULhmfnTeZ_g%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACtV%3DdcnuLN4c1U-qESD1U7nNrTiLw4vPO6pO31ULhmfnTeZ_g%40mail.gmail.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/TYVP286MB316625A66F0976ABCFF929DDA13B2%40TYVP286MB3166.JPNP286.PROD.OUTLOOK.COM
>> <https://groups.google.com/d/msgid/jenkinsci-dev/TYVP286MB316625A66F0976ABCFF929DDA13B2%40TYVP286MB3166.JPNP286.PROD.OUTLOOK.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/CAKwJSvzCqG42ZDNYQQqgy3zPTUmd7JYgZ5UKUydLsFFuSCuydQ%40mail.gmail.com.

Re: Adopt email-ext plugin

[Adrien Lecharpentier]

+1 from me.
Basil is listed as maintainer but the repo has the adopt-this-plugin topic.
Don't know if +1 are really required here.

Le jeu. 28 mars 2024, 18:00, Kris Stern  a écrit :

> +1
> --
> *From:* jenkinsci-dev@googlegroups.com 
> on behalf of Verachten Bruno 
> *Sent:* 29 March 2024 00:58
> *To:* jenkinsci-dev@googlegroups.com 
> *Subject:* Re: Adopt email-ext plugin
>
> +1 from me.
>
> On Thu, Mar 28, 2024, 17:02 'Kevin Martens' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
> +1 from me!
>
> On Thu, Mar 28, 2024 at 11:58 AM Alex Earl  wrote:
>
> Howdy,
>
> The email-ext plugin is up for adoption. I'd like to re-adopt it (been a
> few years so I may be a little rusty :) )
>
> RPU pull request:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3851
> 
> GitHub username: slide (already member of jenkinsci organization)
> Jenkins username: slide_o_mix
>
> Thanks
>
> Alex
>
> --
> 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/ee3bd5a5-ca18-4642-94c5-3a3b83640515n%40googlegroups.com
> 
> .
>
>
>
> --
> Kevin Martens
> Technical Content Developer
> CloudBees, Inc.
>
>
> E: kmart...@cloudbees.com
>
> Pronouns: He/Him/His
>
> --
> 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/CAP92yNeKCGoyWDtYh%2B1pQMzi-cXKx2O5ntjRSm6LLVC05qVz1g%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/CACtV%3DdcnuLN4c1U-qESD1U7nNrTiLw4vPO6pO31ULhmfnTeZ_g%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/TYVP286MB316625A66F0976ABCFF929DDA13B2%40TYVP286MB3166.JPNP286.PROD.OUTLOOK.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/CAKwJSvwrgc9dm2Ni4THGz8JB3YYmpJx50%2BQx8RX1Vn3mJXBbfg%40mail.gmail.com.

Re: Detect Renovate as dependency version manager

[Adrien Lecharpentier]

Normally, every 3 hours.
See
https://github.com/jenkins-infra/plugin-site/blob/32643dc54965c2f4ea9f1327218a23aab47ff827/Jenkinsfile#L14

Infra team is looking into the problem.


Le mar. 19 mars 2024, 11:17, 'Michael Kriese' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Yes, that helps to understand.
>
> How often the plugin sites are updated?
> I still see discrepancies about latest release on github / plugin repo and
> plugin site.
>
> adrien.lec...@gmail.com schrieb am Dienstag, 19. März 2024 um 10:33:59
> UTC+1:
>
>> Hello,
>>
>> I found the culprit and I think I need to address this more generally but
>> I still need to find a good way.
>>
>> TL;DR: There is no problem on the plugin-health-score app, the score are
>> correctly up to date but not on plugins site. This because the plugins site
>> updates the scores it knows when it's built.
>>
>> The scores you see on the plugins site are fetched when the site is
>> built. Not when you look at them.
>> As the site is not built every hour, but the scores are, you can have a
>> discrepancy between the score of a plugin and the score shown on the
>> plugins site.
>>
>> Your plugins up to date scores can be seen at
>> - https://plugin-health.jenkins.io/scores/additional-identities-plugin
>> - https://plugin-health.jenkins.io/scores/scoring-load-balancer
>>
>> There is https://github.com/jenkins-infra/plugin-health-scoring/pull/491
>> coming and I'll add the timestamp on the plugins site when it's available.
>> That will help knowing when the score was computed.
>>
>> I'll also add a link to the plugin-health-score page on the plugins site
>> so it can be reached more easily.
>>
>> I hope this answer the question of "why the scores are not updated?", but
>> I know it's not answering the problem of the discrepancy.
>>
>> -- Adrien
>>
>> Le lun. 18 mars 2024, 14:22, Adrien Lecharpentier <
>> adrien.lec...@gmail.com> a écrit :
>>
>>> I'm looking into this.
>>>
>>>
>>> Le lun. 18 mars 2024, 10:32, 'Michael Kriese' via Jenkins Developers <
>>> jenkin...@googlegroups.com> a écrit :
>>>
>>>> Still no updated 樂
>>>>
>>>> https://plugins.jenkins.io/additional-identities-plugin/healthscore/
>>>> https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>>>>
>>>> adrien.lec...@gmail.com schrieb am Donnerstag, 14. März 2024 um
>>>> 08:49:32 UTC+1:
>>>>
>>>>> No you don't.
>>>>>
>>>>> Le jeu. 14 mars 2024, 08:22, 'Michael Kriese' via Jenkins Developers <
>>>>> jenkin...@googlegroups.com> a écrit :
>>>>>
>>>>>> Do i need to release a new version to get the issue tracker and
>>>>>> renovate changes detected?
>>>>>>
>>>>>> Michael Kriese schrieb am Mittwoch, 13. März 2024 um 16:12:52 UTC+1:
>>>>>>
>>>>>>> https://github.com/jenkins-infra/plugin-health-scoring/issues/483
>>>>>>>
>>>>>>> Will now move my configs to github folder as workaround.
>>>>>>>
>>>>>>> adrien.lec...@gmail.com schrieb am Mittwoch, 13. März 2024 um
>>>>>>> 15:53:59 UTC+1:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Thank you for reaching out.
>>>>>>>>
>>>>>>>> First, you can find the code of the plugin-health-score (PHS) here:
>>>>>>>> https://github.com/jenkins-infra/plugin-health-scoring
>>>>>>>>
>>>>>>>> Second, I think I see the problem. I got under the impression that
>>>>>>>> the renovate.json file has to be in the .github folder. But it's 
>>>>>>>> working
>>>>>>>> for you to have it at the root of the repository.
>>>>>>>>
>>>>>>>> You can see in the code of PHS that we are looking in .github
>>>>>>>> folder (
>>>>>>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/AbstractDependencyBotConfigurationProbe.java#L57)
>>>>>>>> for a file named renovate.json (
>>>>>>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc50

Re: Detect Renovate as dependency version manager

[Adrien Lecharpentier]

Hello,

I found the culprit and I think I need to address this more generally but I
still need to find a good way.

TL;DR: There is no problem on the plugin-health-score app, the score are
correctly up to date but not on plugins site. This because the plugins site
updates the scores it knows when it's built.

The scores you see on the plugins site are fetched when the site is built.
Not when you look at them.
As the site is not built every hour, but the scores are, you can have a
discrepancy between the score of a plugin and the score shown on the
plugins site.

Your plugins up to date scores can be seen at
- https://plugin-health.jenkins.io/scores/additional-identities-plugin
- https://plugin-health.jenkins.io/scores/scoring-load-balancer

There is https://github.com/jenkins-infra/plugin-health-scoring/pull/491
coming and I'll add the timestamp on the plugins site when it's available.
That will help knowing when the score was computed.

I'll also add a link to the plugin-health-score page on the plugins site so
it can be reached more easily.

I hope this answer the question of "why the scores are not updated?", but I
know it's not answering the problem of the discrepancy.

-- Adrien

Le lun. 18 mars 2024, 14:22, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> I'm looking into this.
>
>
> Le lun. 18 mars 2024, 10:32, 'Michael Kriese' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>> Still no updated 樂
>>
>> https://plugins.jenkins.io/additional-identities-plugin/healthscore/
>> https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>>
>> adrien.lec...@gmail.com schrieb am Donnerstag, 14. März 2024 um 08:49:32
>> UTC+1:
>>
>>> No you don't.
>>>
>>> Le jeu. 14 mars 2024, 08:22, 'Michael Kriese' via Jenkins Developers <
>>> jenkin...@googlegroups.com> a écrit :
>>>
>>>> Do i need to release a new version to get the issue tracker and
>>>> renovate changes detected?
>>>>
>>>> Michael Kriese schrieb am Mittwoch, 13. März 2024 um 16:12:52 UTC+1:
>>>>
>>>>> https://github.com/jenkins-infra/plugin-health-scoring/issues/483
>>>>>
>>>>> Will now move my configs to github folder as workaround.
>>>>>
>>>>> adrien.lec...@gmail.com schrieb am Mittwoch, 13. März 2024 um
>>>>> 15:53:59 UTC+1:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Thank you for reaching out.
>>>>>>
>>>>>> First, you can find the code of the plugin-health-score (PHS) here:
>>>>>> https://github.com/jenkins-infra/plugin-health-scoring
>>>>>>
>>>>>> Second, I think I see the problem. I got under the impression that
>>>>>> the renovate.json file has to be in the .github folder. But it's working
>>>>>> for you to have it at the root of the repository.
>>>>>>
>>>>>> You can see in the code of PHS that we are looking in .github folder (
>>>>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/AbstractDependencyBotConfigurationProbe.java#L57)
>>>>>> for a file named renovate.json (
>>>>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/RenovateProbe.java#L45
>>>>>> ).
>>>>>>
>>>>>> Please open a ticket on the PHS repository so we can work this out.
>>>>>>
>>>>>> Le mer. 13 mars 2024, 13:33, 'Michael Kriese' via Jenkins Developers <
>>>>>> jenkin...@googlegroups.com> a écrit :
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm using Renovate to update my dependencies, but it's not deteced
>>>>>>> as  valid manager on plugin health sore
>>>>>>>
>>>>>>> -
>>>>>>> https://plugins.jenkins.io/additional-identities-plugin/healthscore/
>>>>>>> - https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>>>>>>>
>>>>>>> Where we can add / enable the detection?
>>>>>>>
>>>>>>> Regards
>>>>>>> Michael
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>

Re: Detect Renovate as dependency version manager

[Adrien Lecharpentier]

I'm looking into this.


Le lun. 18 mars 2024, 10:32, 'Michael Kriese' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Still no updated 樂
>
> https://plugins.jenkins.io/additional-identities-plugin/healthscore/
> https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>
> adrien.lec...@gmail.com schrieb am Donnerstag, 14. März 2024 um 08:49:32
> UTC+1:
>
>> No you don't.
>>
>> Le jeu. 14 mars 2024, 08:22, 'Michael Kriese' via Jenkins Developers <
>> jenkin...@googlegroups.com> a écrit :
>>
>>> Do i need to release a new version to get the issue tracker and renovate
>>> changes detected?
>>>
>>> Michael Kriese schrieb am Mittwoch, 13. März 2024 um 16:12:52 UTC+1:
>>>
 https://github.com/jenkins-infra/plugin-health-scoring/issues/483

 Will now move my configs to github folder as workaround.

 adrien.lec...@gmail.com schrieb am Mittwoch, 13. März 2024 um 15:53:59
 UTC+1:

> Hi,
>
> Thank you for reaching out.
>
> First, you can find the code of the plugin-health-score (PHS) here:
> https://github.com/jenkins-infra/plugin-health-scoring
>
> Second, I think I see the problem. I got under the impression that the
> renovate.json file has to be in the .github folder. But it's working for
> you to have it at the root of the repository.
>
> You can see in the code of PHS that we are looking in .github folder (
> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/AbstractDependencyBotConfigurationProbe.java#L57)
> for a file named renovate.json (
> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/RenovateProbe.java#L45
> ).
>
> Please open a ticket on the PHS repository so we can work this out.
>
> Le mer. 13 mars 2024, 13:33, 'Michael Kriese' via Jenkins Developers <
> jenkin...@googlegroups.com> a écrit :
>
>> Hi,
>>
>> I'm using Renovate to update my dependencies, but it's not deteced
>> as  valid manager on plugin health sore
>>
>> -
>> https://plugins.jenkins.io/additional-identities-plugin/healthscore/
>> - https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>>
>> Where we can add / enable the detection?
>>
>> Regards
>> Michael
>>
>> --
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/58008a24-3a9e-4954-85af-54025db72e17n%40googlegroups.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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/2c3727e4-cb36-4805-871d-af490560f845n%40googlegroups.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/12f04995-3b7d-45d8-96df-403ea81da7afn%40googlegroups.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/CAKwJSvwFYdkoVHGXDyTH2yY04z0kqoy-jyNg4bjfwSBi1yefUg%40mail.gmail.com.

Re: Detect Renovate as dependency version manager

[Adrien Lecharpentier]

No you don't.

Le jeu. 14 mars 2024, 08:22, 'Michael Kriese' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Do i need to release a new version to get the issue tracker and renovate
> changes detected?
>
> Michael Kriese schrieb am Mittwoch, 13. März 2024 um 16:12:52 UTC+1:
>
>> https://github.com/jenkins-infra/plugin-health-scoring/issues/483
>>
>> Will now move my configs to github folder as workaround.
>>
>> adrien.lec...@gmail.com schrieb am Mittwoch, 13. März 2024 um 15:53:59
>> UTC+1:
>>
>>> Hi,
>>>
>>> Thank you for reaching out.
>>>
>>> First, you can find the code of the plugin-health-score (PHS) here:
>>> https://github.com/jenkins-infra/plugin-health-scoring
>>>
>>> Second, I think I see the problem. I got under the impression that the
>>> renovate.json file has to be in the .github folder. But it's working for
>>> you to have it at the root of the repository.
>>>
>>> You can see in the code of PHS that we are looking in .github folder (
>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/AbstractDependencyBotConfigurationProbe.java#L57)
>>> for a file named renovate.json (
>>> https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/RenovateProbe.java#L45
>>> ).
>>>
>>> Please open a ticket on the PHS repository so we can work this out.
>>>
>>> Le mer. 13 mars 2024, 13:33, 'Michael Kriese' via Jenkins Developers <
>>> jenkin...@googlegroups.com> a écrit :
>>>
 Hi,

 I'm using Renovate to update my dependencies, but it's not deteced as
 valid manager on plugin health sore

 - https://plugins.jenkins.io/additional-identities-plugin/healthscore/
 - https://plugins.jenkins.io/scoring-load-balancer/healthscore/

 Where we can add / enable the detection?

 Regards
 Michael

 --
 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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/58008a24-3a9e-4954-85af-54025db72e17n%40googlegroups.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/2c3727e4-cb36-4805-871d-af490560f845n%40googlegroups.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/CAKwJSvx8yMu6rrCJ_pzWVmDpgd40sqxjuuBLQwLYkRcOPjY44g%40mail.gmail.com.

Re: Detect Renovate as dependency version manager

[Adrien Lecharpentier]

Hi,

Thank you for reaching out.

First, you can find the code of the plugin-health-score (PHS) here:
https://github.com/jenkins-infra/plugin-health-scoring

Second, I think I see the problem. I got under the impression that the
renovate.json file has to be in the .github folder. But it's working for
you to have it at the root of the repository.

You can see in the code of PHS that we are looking in .github folder (
https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/AbstractDependencyBotConfigurationProbe.java#L57)
for a file named renovate.json (
https://github.com/jenkins-infra/plugin-health-scoring/blob/908c24dade7fb2eb3865fc5046e6ab4baec4754c/core/src/main/java/io/jenkins/pluginhealth/scoring/probes/RenovateProbe.java#L45
).

Please open a ticket on the PHS repository so we can work this out.

Le mer. 13 mars 2024, 13:33, 'Michael Kriese' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Hi,
>
> I'm using Renovate to update my dependencies, but it's not deteced as
> valid manager on plugin health sore
>
> - https://plugins.jenkins.io/additional-identities-plugin/healthscore/
> - https://plugins.jenkins.io/scoring-load-balancer/healthscore/
>
> Where we can add / enable the detection?
>
> Regards
> Michael
>
> --
> 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/58008a24-3a9e-4954-85af-54025db72e17n%40googlegroups.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/CAKwJSvxOEhPhCFRrCYnYLS5X3kVEpqOuo_iHokmOB3G6Av099w%40mail.gmail.com.

Re: Adopt plugin openid-plugin

[Adrien Lecharpentier]

The jenkins.version you set in your pom requires java 11 minimum (
https://www.jenkins.io/doc/book/platform-information/support-policy-java/).
However, the jenkinsfile still tries to build the plugin using java 8 on
windows.

As you are not the maintainer for now, changing the Jenkinsfile wouldn't
change anything as it wouldn't be used.

Once you're the maintainer, I'd suggested to open a pull request updating
the jenkinsfile configuration (there is a open rewrite recipe to help you).
Merge that PR and then you can work more deeply on the plugin.

Le dim. 18 févr. 2024, 18:07, Michael Nazzareno Trimarchi <
mich...@amarulasolutions.com> a écrit :

> Hi
>
> On Sun, Feb 18, 2024 at 5:56 PM Adrien Lecharpentier
>  wrote:
> >
> > Even if the plugin is not mark as up for adoption, it currently has no
> maintainer listed in the RPU. So +1 for me.
> >
> > Please note that the plugin has multiple public security issues. I'm
> sure the security team will require you to resolve them before any release
> can be deployed.
> >
>
> Ok I see, mostly my problem is even resolve CI build on jenkins CI too
>
> Michael
>
> > Le dim. 18 févr. 2024, 16:35, Michael Nazzareno Trimarchi <
> mich...@amarulasolutions.com> a écrit :
> >>
> >> Hi all
> >>
> >> https://github.com/jenkinsci/openid-plugin/pull/24
> >>
> >> My github account
> >> https://github.com/panicking
> >>
> >> Pull request for the permission
> >>
> >>
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3776
> >>
> >> Michael
> >>
> >> --
> >> 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/CAOf5uwnO4r%2B-upaC-5wCMXbez-bsBd3LajxyU483ftm%2BMLYq2A%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/CAKwJSvyP%3DkpWEcumyRLhzYBrn4rfB9NguybafT4MwxnTq4f12g%40mail.gmail.com
> .
>
>
>
> --
> Michael Nazzareno Trimarchi
> Co-Founder & Chief Executive Officer
> M. +39 347 913 2170
> mich...@amarulasolutions.com
> __
>
> Amarula Solutions BV
> Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
> T. +31 (0)85 111 9172
> i...@amarulasolutions.com
> www.amarulasolutions.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/CAOf5uwnQTw0z2bO3RRK6xvorCNmBUojQirg%2BpDJR%2BS3h81RxCg%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/CAKwJSvy-ozNe95WkobFbDEidjFz%3DzCeN2rVw_uY_YKY-21kHaw%40mail.gmail.com.

Re: Adopt plugin openid-plugin

[Adrien Lecharpentier]

Even if the plugin is not mark as up for adoption, it currently has no
maintainer listed in the RPU. So +1 for me.

Please note that the plugin has multiple public security issues. I'm sure
the security team will require you to resolve them before any release can
be deployed.

Le dim. 18 févr. 2024, 16:35, Michael Nazzareno Trimarchi <
mich...@amarulasolutions.com> a écrit :

> Hi all
>
> https://github.com/jenkinsci/openid-plugin/pull/24
>
> My github account
> https://github.com/panicking
>
> Pull request for the permission
>
> https://github.com/jenkins-infra/repository-permissions-updater/pull/3776
>
> Michael
>
> --
> 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/CAOf5uwnO4r%2B-upaC-5wCMXbez-bsBd3LajxyU483ftm%2BMLYq2A%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/CAKwJSvyP%3DkpWEcumyRLhzYBrn4rfB9NguybafT4MwxnTq4f12g%40mail.gmail.com.

Re: Hosting New Jenkins plugin on Jenkins

[Adrien Lecharpentier]

I don't recall exactly but someone in the community might know exactly

Le jeu. 30 nov. 2023, 18:59, naveen sharma  a écrit :

> Hi Adrien, Please suggest What's the frequency to update The plugin site (
> plugins.jenkins.io). We are announcing it shortly and expecting to be
> available on plugins.jenkins.io.
>
> On Thu, Nov 30, 2023 at 11:52 AM naveen sharma 
> wrote:
>
>> Got it. I will work with Will to delete original repo this, once we
>> validate plugin on marketplace.
>>
>> The plugin site (plugins.jenkins.io) will be updated soon. -- Within 1
>> hr? or less
>>
>>
>> On Thu, Nov 30, 2023 at 11:43 AM Adrien Lecharpentier <
>> adrien.lecharpent...@gmail.com> wrote:
>>
>>> So, there is a release.
>>> The release is available in the update center (
>>> https://updates.jenkins.io/current/update-center.json)
>>>
>>> The plugin site (plugins.jenkins.io) will be updated soon.
>>>
>>> One thing, for the hosting process, we request that the original
>>> repository of the plugin be deleted so that the one in jenkinsci
>>> organization is not seen as a fork.
>>>
>>>
>>>
>>> Le jeu. 30 nov. 2023, 17:32, naveen sharma  a
>>> écrit :
>>>
>>>> Hi Adrien,
>>>>
>>>> Quick help
>>>>
>>>> We have this final PR
>>>> https://github.com/jenkinsci/amazon-inspector-image-scanner-plugin/pull/3#issuecomment-1834108500
>>>>
>>>> Please suggest by when we can see our plugin to marketplace.
>>>>
>>>> Regards,
>>>> Naveen
>>>>
>>>> On Wed, Nov 29, 2023 at 6:28 PM naveen sharma 
>>>> wrote:
>>>>
>>>>> Thank you for your help!
>>>>>
>>>>> On Wed, Nov 29, 2023 at 5:34 PM Adrien Lecharpentier <
>>>>> adrien.lecharpent...@gmail.com> wrote:
>>>>>
>>>>>> I saw that you tried to enable CD on the repository but the action
>>>>>> description is not located in the correct directory.
>>>>>>
>>>>>> The file must be in `.github/workflows`.
>>>>>>
>>>>>> Then you will need to label a pull request with the label `developer`
>>>>>> for example. (Use the one you'll use to fix the cd action file). Once the
>>>>>> pull request is merged, you should see a new release.
>>>>>>
>>>>>> Le mer. 29 nov. 2023, 23:16, Adrien Lecharpentier <
>>>>>> adrien.lecharpent...@gmail.com> a écrit :
>>>>>>
>>>>>>> Yes you need.
>>>>>>> Everything is detailed here
>>>>>>> https://www.jenkins.io/doc/developer/publishing/releasing/
>>>>>>>
>>>>>>> Le mer. 29 nov. 2023, 21:40, naveen sharma  a
>>>>>>> écrit :
>>>>>>>
>>>>>>>> Hi Adrien, do we need permission for publishing plugin ?
>>>>>>>>
>>>>>>>> Can you suggest process please
>>>>>>>>
>>>>>>>> On Wed, Nov 29, 2023 at 11:26 AM naveen sharma 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Thank you Adrien for all the help. Appreciated.
>>>>>>>>>
>>>>>>>>> When we publish do we have any delay or plugin show in few minutes
>>>>>>>>> to marketplace.
>>>>>>>>>
>>>>>>>>> On Tue, Nov 28, 2023 at 3:06 PM naveen sharma 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Adrien, We updated as you suggested
>>>>>>>>>> https://github.com/aws/amazon-inspector-container-image-scanner-jenkins-plugin/commit/8440e44c203edf6655dff95ec26994cfa5d5c9c9
>>>>>>>>>>
>>>>>>>>>> Please review and help approving.
>>>>>>>>>>
>>>>>>>>>> On Tue, Nov 28, 2023 at 10:09 AM naveen sharma <
>>>>>>>>>> maynav...@gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Adrien, Greetings for the day.
>>>>>>>>>>>
>>>>>>>>>>> Team saying can we get approval and do some research later for
>>>>>>>>>>

Re: Hosting New Jenkins plugin on Jenkins

[Adrien Lecharpentier]

Hello,

The hosting process timing is not really long if there is no major issues
found. The sooner you start it the better.
For the availability of the plugin in the update center (what you called
the market place I believe), you totally control that: once your hosting
request is completed, you can release the plugin whenever you want which
will add it to the update center.

So again, start your hosting process as soon as possible, because this is
the only thing that you don't totally control.

Best regards,

Le ven. 17 nov. 2023, 19:35, naveen sharma  a écrit :

> Hi Team,
>
> We built new plugin and ready to create hosting request. Can someone
> please help how much time it take to approve and can we select specific
> date for plugin to available in marketplace.
>
> Please suggest.
>
> Regards,
> Naveen
>
> --
> 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/6f9f8476-a944-4ee4-9216-c712566294dbn%40googlegroups.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/CAKwJSvw0J0zVAti0AEJQ5A%2BitRmfYBf50_i8ciD4yXwuqtoNnQ%40mail.gmail.com.

Re: Requesting admin access to the jenkinsci GitHub organization

[Adrien Lecharpentier]

+1 as well from me.

Le mar. 6 juin 2023, 10:15, Baptiste Mathus  a écrit :

> +1.
>
> Le lun. 5 juin 2023 à 19:33, Srikanth Jana  a
> écrit :
>
>> +1 from me
>>
>> On Mon, Jun 5, 2023 at 11:01 PM Alexander Brandes 
>> wrote:
>>
>>> +1 for Basil
>>>
>>> On Mon 5. Jun 2023 at 19:30, Mark Waite 
>>> wrote:
>>>


 On Monday, June 5, 2023 at 11:29:18 AM UTC-6 m Basil Crow wrote:

 I would like to become an organization administrator of the jenkinsci
 GitHub organization. This would facilitate various efforts I am
 involved with, such as repository transfers.


 +1 from 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/78809aba-d9ca-4d43-98bf-858811577121n%40googlegroups.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/CAP9joaGh28MKR0jSRptwGGhnAKNn_7C8W2aTQVgzpqmsyjtgeQ%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/CAJxAiNDnHRF5BRtESwKfdsmH9pi698V24TjXTMPXCTfOEUmK4Q%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/CANWgJS7QcnLsR4ZRR5tU9y6fWsQ2dKP2xdGCpx84V44ga3xhAg%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/CAKwJSvyFifUfdsmYxinNJcuawcyjOUE6uDEp70xYFOYh5ODq2A%40mail.gmail.com.

Re: Maven 3.9.2: ready to roll?

[Adrien Lecharpentier]

Same here, I've been using it locally with no problem.

Le mar. 23 mai 2023, 14:04, Mark Waite  a écrit :

>
>
> On Tuesday, May 23, 2023 at 1:57:48 AM UTC-6 Damien Duportal wrote:
>
> Hello dear maintainers,
>
> Is there any objection against the deployment of Maven 3.9.2 in the
> Jenkins infrastructure?
>
>
> No objection from me.  I've used it since shortly after it released and
> have found no blocking issues with it.
>
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/99da63b5-50ae-4f7a-aebc-a7e9aae94c88n%40googlegroups.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/CAKwJSvyrg%3Du%3DQDfgUaZhfK9fxzwE_1yFdU7fdfx1O9EzWbKv2g%40mail.gmail.com.

Re: Proposal to ensure new plugin hosting requests use Maven instead of Gradle

[Adrien Lecharpentier]

+1 as well from me.

Le jeu. 8 déc. 2022 à 17:19, Damien Duportal  a
écrit :

> +1
>
> Le mercredi 7 décembre 2022 à 15:49:42 UTC+1, bma...@gmail.com a écrit :
>
>> +1.
>>
>> At least such a move will make it very explicit for any new plugin that
>> only Maven really has /production/ support for Jenkins plugin dev.
>>
>> I think that we should still "allow" new plugins to use Gradle if they
>> wish so. But then they'll be very well aware that they got to be ready for
>> a lot of pain and much meta-work around the tooling itself for developing
>> their plugins.
>> Which right now might be overlooked by new developers joining the
>> community and thinking that choosing one or another is simply a matter of
>> taste and habits.
>>
>> Le mer. 7 déc. 2022 à 15:19, Basil Crow  a écrit :
>>
>>> +1
>>>
>>> On Wed, Dec 7, 2022 at 2:20 AM Alexander Brandes 
>>> wrote:
>>> >
>>> > Hey everyone,
>>> >
>>> > the Gradle JPI plugin lacks fundamental support of the jenkins.io
>>> infrastructure.
>>> > There's no support for automated releases (CD, JEP-229), missing
>>> metadata for the plugin page and a few other limitations, which don't make
>>> it a great experience using it.
>>> >
>>> > Additionally, worth to note, the components mentioned above aren't
>>> new. People are proactively switching away from Gradle to Maven for better
>>> support and acceptance of our tooling, see ivy-plugin/49 for example.
>>> >
>>> > For the reasons stated, I would like to propose, that new plugin
>>> hosting requests use Maven, to have better toolchain support.
>>> > I would be ready to lift this restriction again if the JPI plugin
>>> developers provide the same scope of tools like we have for Maven.
>>> >
>>> > Best,
>>> > Alexander Brandes, for the hosting team
>>> >
>>> > --
>>> > 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-de...@googlegroups.com.
>>> > To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/bb8f56d3-727b-481a-9132-17bf5eddbbcdn%40googlegroups.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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjq9xnyvJFoB33n07jORm7Hw6fSBf8FY5ho5FdGMDAiKug%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/5f43f822-37e4-45e2-85a2-3c60840ffcdfn%40googlegroups.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/CAKwJSvwL_u384_cXKACe_kcuOQ%2Ba%2BgSxHCqcGbooHri0eQB%2BxA%40mail.gmail.com.

Re: Hosting

[Adrien Lecharpentier]

I would also be happy to help on the hosting process.
Is there any room for me to help?

Le dim. 9 oct. 2022 à 20:11, 'Herve Le Meur' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Wiling to help too :)
> I'll take care of your request tomorrow morning NotMyFault.
>
> Le dim. 9 oct. 2022, 20:01, Alexander Brandes  a
> écrit :
>
>> Submitted https://github.com/jenkins-infra/helpdesk/issues/3163
>>
>> On Sunday, 9 October 2022 at 19:49:03 UTC+2 ga...@gavinmogan.com wrote:
>>
>>> I think you'll have to request via helpdesk permissions for
>>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>>
>>> On Sun, Oct 9, 2022 at 9:07 AM Alexander Brandes 
>>> wrote:
>>>
 Hey,

 I'd be up to assist with handling the RPU too.

 Best regards,
 Alex

 On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote:

> I can help with that. I know the process is different from when I was
> doing it before, but I can come up to speed.
>
> On Sat, Oct 8, 2022, 21:11 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> I'm looking for someone interested in replacing me. Right now it
>> seems to just be tim and myself. Tim's been amazing and processing all 
>> the
>> new plugin requests. Wrote tooling to help verify things, etc. He's 
>> already
>> doing a ton of other things, so I've been trying to help out with the
>> maintainer change request approvals, but the process is so fuzzy its just
>> draining me, which dumps more on him.
>>
>> The job entails monitoring PRs on
>> https://github.com/jenkins-infra/repository-permissions-updater
>> Making sure the request is either approved from an existing
>> maintainer, the plugin is labeled adopt this plugin, or the takeover
>> process has been followed.
>>
>> Gavin
>>
>> On Thu, Aug 26, 2021 at 2:24 AM Baptiste Mathus 
>> wrote:
>>
>>> I am ready to help again on hosting.
>>>
>>> Similar to how Gavin phrased it, I'll help move tickets through the
>>> pipe.
>>>
>>> Cheers
>>>
>>> Le jeu. 26 août 2021 à 08:23, Tim Jacomb  a
>>> écrit :
>>>
 You can just click leave team

 On Wed, 25 Aug 2021 at 22:33, Slide  wrote:

> I should probably be removed from that team as well.
>
> On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb 
> wrote:
>
>> Oleg has permissions on the team or Olivier:
>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>
>>
>> On Wed, 25 Aug 2021 at 21:03, Slide  wrote:
>>
>>> Those are the basics, just the bot checker (jenkins-admin: check
>>> HOSTING-) in the jenkins-hosting channel.
>>>
>>> On Wed, Aug 25, 2021 at 12:20 PM 'Gavin Mogan' via Jenkins
>>> Developers  wrote:
>>>
 Okay, making it official. If nobody else speaks up as wanting
 to take over as lead before end of week (Friday night pacific 
 time) I'll
 take over and make sure hosting requests get moving.

 I think i've fixed my irc client so I should stay in the
 channels now.
 Can I get invited to the hosting github teams as well?

 Is there anything else that might be needed for transition?

 Gavin

 On Wed, Aug 25, 2021 at 8:07 AM wfoll...@cloudbees.com <
 wfoll...@cloudbees.com> wrote:

> Thank you very much Alex for the effort you invested on this
> area. This is a really important piece of the process for the 
> security
> perspective. The fact that you did the preliminary security 
> checks and if
> something was weird, to ask the security team to make a more 
> complete
> audit, was of a great help for us.
>
> I cannot ask you Gavin to do more than what you are proposing
> to do as if you are not proposing this it will be mainly nothing 
> being
> done, so anything is better than nothing :-) In the case where 
> you are not
> sure about a plugin, if you are seeing something weird, do not 
> hesitate to
> ping Daniel Beck and me in the HOSTING ticket, requesting an 
> audit from us.
>
> Wadeck
>
> On Wednesday, August 25, 2021 at 5:58:20 AM UTC+2
> ga...@gavinmogan.com wrote:
>
>> If nobody else is able to step up, I can take it, but I won't
>> be code reviewing and as quickly as possible switch it from 
>> jira+irc to
>> 

Re: Request for access to YouTube account

[Adrien Lecharpentier]

+1

Le mer. 26 oct. 2022 à 15:16, Alexander Brandes  a
écrit :

> +1
>
> On Wednesday, 26 October 2022 at 15:09:53 UTC+2 damien@gmail.com
> wrote:
>
>> +1 for me!
>>
>> Bruno's work on the SIG is clearly an indicator of the trust we can put.
>> I'm also convinced that he'll have plenty of idea to
>> documente/describe/improve the SIG publication process
>>
>> Le mercredi 26 octobre 2022 à 15:07:33 UTC+2, ullrich...@gmail.com a
>> écrit :
>>
>>> +1
>>>
>>> Am 26.10.2022 um 14:42 schrieb timja...@gmail.com :
>>>
>>> +1
>>>
>>> On Wednesday, 26 October 2022 at 13:18:13 UTC+1 goun...@gmail.com wrote:
>>>
 Hi group,

 I sometimes run the Platform SIG meeting (like
 https://www.youtube.com/watch?v=R2322YxIciQ) and would like to be able
 to post the resulting video to YouTube when Mark is on PTO for example.
 Therefore I'm asking the authorization to be granted access to the
 Youtube account/channel (to upload the recording to the channel).

 Best wishes,

 Bruno Verachten

>>>
>>> --
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/77f08589-693b-46cd-96e4-cb665587b9a9n%40googlegroups.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/7b20bf94-250e-4815-a481-dcfbc27e4ed8n%40googlegroups.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/CAKwJSvxTx3sL6pCuJybnx6vhsX%2BsruVRmeTQj10S9csMBP7j%2Bg%40mail.gmail.com.

Marking plugins for adoption

[Adrien Lecharpentier]

Hello,

while I was updating some permissions I had on plugins deployment to
Artifactory, I noticed that a lot of plugins have no developers listed.
This means that no one is maintaining them.

So I proposed
https://github.com/jenkins-infra/repository-permissions-updater/pull/2891
to automatically mark plugins with no developers as up for adoption.

Currently, 104 plugins are mark as such, and only 92 are labelled with way
in the update center. However, I detect at least 327 plugins with no
developers. Probably more but some permission files have no `github` info.

It could be seen as harsh but I think it is just fair to users and us.

What do you think?
-- Adrien

-- 
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/CAKwJSvwQTNbASDLiV%3Df6ZfOO8%2Bawt-yUF6LDU-pPoPNT0znpxQ%40mail.gmail.com.

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

[Adrien Lecharpentier]

of course +1.


Le sam. 15 oct. 2022 à 18:31, Alexander Brandes  a
écrit :

> Thanks everyone, I'd be very happy to join the core team :)
>
> On Friday, 14 October 2022 at 13:48:48 UTC+2 hle...@cloudbees.com wrote:
>
>> +1
>>
>> On Fri, Oct 14, 2022 at 1:18 PM James Nord  wrote:
>>
>>> +1
>>>
>>> On Thu, 13 Oct 2022 at 20:16, Pedro Amaral  wrote:
>>>
 +1

 On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins Developers
  wrote:

> +1 from me too!
>
> On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> +1  :)
>>
>> On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins
>> Developers wrote:
>>
>> +1 for me too
>> good luck Alexander
>>
>> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>>
>>
>>
>> On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb 
>> wrote:
>>
>> I would like to propose Alexander Brandes (@NotMyFault
>> ) to join the Jenkins Core team.
>>
>>
>> +1
>>
>>
>> --
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO%2B-N1qxoBRFwKk4%3DJdVY%2B_gns%2BCaMd8J_DC9xuWnRqzEfYDZA%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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/b67d978b-bc39-4cb4-a2a3-3ad69cdf621c%40app.fastmail.com
>> 
>> .
>>
>
>
> --
> Kevin Martens
> Technical Content Developer
> CloudBees, Inc.
>
>
> E: kmar...@cloudbees.com
>
> Pronouns: He/Him/His
>
> --
> 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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAP92yNdJ5WrfjJith1bzawZiEsEJw%2BhG4SDv6GxLhVHT6fmjGA%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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAHnkEpkxT9pBagcAJszwL5Pw5RoSp26myuBC4sntO-GAq5J2sg%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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPzq3pf51chP_ZHkfGyxcBCFNtRAGAgxLMAqodCFom2r39VCNg%40mail.gmail.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups

Re: maven-jellydoc-plugin and maven-stapler-plugin

[Adrien Lecharpentier]

it makes sense to me. +1.

Le ven. 29 juil. 2022 à 07:48, Ullrich Hafner  a
écrit :

> +1
>
> > Am 29.07.2022 um 00:49 schrieb Basil Crow :
> >
> > I would like to request a transfer of
> > https://github.com/kohsuke/maven-jellydoc-plugin from the kohsuke
> > GitHub organization to the jenkinsci GitHub organization and
> > permissions for both that repository and
> > https://github.com/jenkinsci/maven-stapler-plugin in order to release
> > new versions that are compatible with current Maven APIs. If and when
> > a consensus is reached that we would like to proceed with this plan, I
> > will reach out to Kohsuke to begin the transfer.
> >
> > --
> > 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/CAFwNDjrRGSbTdSqZuD2VtkJPyELSqYostw4kZQz5tY9_pp9YZg%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/109CA0F9-DD72-4CBA-ADDC-6BEAC0D030A1%40gmail.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/CAKwJSvxzBudvxsm2NzB1UNwqLgh3y_a7KFxRS5KmwvXjcWTqhg%40mail.gmail.com.

Re: GSoC Project - Plugin Health Score Survey for Maintainers

[Adrien Lecharpentier]

Hello Ullrich,

this is a good point, we thought about it but for the moment, we wanted to
focus the project on the maintainers.
The idea was to give direction to maintainers to help them have the best
grade possible. Something like: "The plugin has a grade of 80%. Could gain
5% with dependabot." (just an example).

In the end, we would display those details to users (on plugins.jenkins.io
first) so we could help users decide if they want to install a plugin on
their controller(s) or not.
That is why we decided not to post our message on the user mailing list,
for now. We will probably revisit this decision.

Regards,

Le mar. 12 juil. 2022 à 22:03, Ullrich Hafner  a
écrit :

> Maybe it would help to post in https://community.jenkins.io as well?
>
> It would be also helpful to ask the users what they think, so the users
> mailing list may increase the number of return answers?
>
> Am 12.07.2022 um 17:24 schrieb Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com>:
>
> Hello everyone,
>
> just a reminder that the feedback that you can give us is really important
> for us. The idea is, when we will be in the "grading" phase of the project,
> to be fair to the community.
> By that I mean we don't want to say "Rule A is 90% of the grade" when in
> fact the community disagree with that.
>
> Here is the link to the survey: https://forms.gle/T6LLqQGYgKke2b8e9
>
> For the moment, we have 11 responses. Thank you for those who responded.
> Please be sure that it's really quick and your time is really important to
> us.
>
> Regards,
> -- Adrien
>
> Le jeu. 30 juin 2022 à 14:38, Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> a écrit :
>
>> Hello Wadeck,
>>
>> let me answer here for Dheeraj (as mentor of the GSoC project).
>>
>> At the moment, we don't have any probes in actions and we don't have a
>> lot of data. I know that we have for example, 52 plugins out of the 1872
>> currently in the update-center that don't have any SCM link. Out of the
>> others, some don't have a valid SCM link as well. We still haven't
>> implemented anything that could tell us which is the parent pom version
>> used by each plugin, but it is in the plan.
>>
>> The plan here, is to get a sense of what make sense for the community,
>> but the weight of each rule will have to evolve with time. For example, if
>> we say "having a Jenkinsfile" is very important, but in 6months we have all
>> plugins with one, then we can lower the rule (new plugins don't come often)
>> and just have a warning if / when the Jenkinsfile disappear.
>> Same thing, for new probes, we don't intend to have all the probes in
>> September and be done with it. We want this project to serve the community
>> for the years to come. So, the probes and weight will have to evolve with
>> the community.
>>
>> I know I haven't answered your question specifically, but that's the best
>> I can offer you.
>> -- Adrien
>>
>> Le jeu. 30 juin 2022 à 08:58, 'wfoll...@cloudbees.com' via Jenkins
>> Developers  a écrit :
>>
>>> Hello Dheeraj,
>>>
>>> Are you able to share the data distribution for the individual probes
>>> you already have in place? This will greatly help us understanding what
>>> should be done with the rules.
>>>
>>> E.g. if all plugins have a code coverage of 50%+, the weight should take
>>> that into consideration, in opposition to the situation where only the top
>>> 5% of the plugin have more than 5% of coverage.
>>> From my PoV the project has two goals, showing the current situation and
>>> also providing guidance about what to improve on a plugin, to follow the
>>> good practices.
>>>
>>> Thanks in advance,
>>>
>>> Wadeck
>>>
>>> On Wednesday, June 29, 2022 at 8:15:08 PM UTC+2 jodhadhe...@gmail.com
>>> wrote:
>>>
>>>> Hello Jenkins Contributors!
>>>>
>>>> My name is Dheeraj Singh Jodha and I'm selected as a Google Summer Of
>>>> Code 2022 student for the Jenkins project where I'm part of a group of 4
>>>> people currently working on the project that is titled Plugin Health
>>>> Scoring System
>>>> <https://www.jenkins.io/projects/gsoc/2022/projects/plugin-health-scoring-system/>
>>>> .
>>>>
>>>> Briefly, the Plugin Health Score is a composite score of various
>>>> different probes related to Jenkins Plugins. These different probes will
>>>> have different weights(value) and focus on different areas(think
>>>> admi

Re: GSoC Project - Plugin Health Score Survey for Maintainers

[Adrien Lecharpentier]

Hello everyone,

just a reminder that the feedback that you can give us is really important
for us. The idea is, when we will be in the "grading" phase of the project,
to be fair to the community.
By that I mean we don't want to say "Rule A is 90% of the grade" when in
fact the community disagree with that.

Here is the link to the survey: https://forms.gle/T6LLqQGYgKke2b8e9

For the moment, we have 11 responses. Thank you for those who responded.
Please be sure that it's really quick and your time is really important to
us.

Regards,
-- Adrien

Le jeu. 30 juin 2022 à 14:38, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> Hello Wadeck,
>
> let me answer here for Dheeraj (as mentor of the GSoC project).
>
> At the moment, we don't have any probes in actions and we don't have a lot
> of data. I know that we have for example, 52 plugins out of the 1872
> currently in the update-center that don't have any SCM link. Out of the
> others, some don't have a valid SCM link as well. We still haven't
> implemented anything that could tell us which is the parent pom version
> used by each plugin, but it is in the plan.
>
> The plan here, is to get a sense of what make sense for the community, but
> the weight of each rule will have to evolve with time. For example, if we
> say "having a Jenkinsfile" is very important, but in 6months we have all
> plugins with one, then we can lower the rule (new plugins don't come often)
> and just have a warning if / when the Jenkinsfile disappear.
> Same thing, for new probes, we don't intend to have all the probes in
> September and be done with it. We want this project to serve the community
> for the years to come. So, the probes and weight will have to evolve with
> the community.
>
> I know I haven't answered your question specifically, but that's the best
> I can offer you.
> -- Adrien
>
> Le jeu. 30 juin 2022 à 08:58, 'wfoll...@cloudbees.com' via Jenkins
> Developers  a écrit :
>
>> Hello Dheeraj,
>>
>> Are you able to share the data distribution for the individual probes you
>> already have in place? This will greatly help us understanding what should
>> be done with the rules.
>>
>> E.g. if all plugins have a code coverage of 50%+, the weight should take
>> that into consideration, in opposition to the situation where only the top
>> 5% of the plugin have more than 5% of coverage.
>> From my PoV the project has two goals, showing the current situation and
>> also providing guidance about what to improve on a plugin, to follow the
>> good practices.
>>
>> Thanks in advance,
>>
>> Wadeck
>>
>> On Wednesday, June 29, 2022 at 8:15:08 PM UTC+2 jodhadhe...@gmail.com
>> wrote:
>>
>>> Hello Jenkins Contributors!
>>>
>>> My name is Dheeraj Singh Jodha and I'm selected as a Google Summer Of
>>> Code 2022 student for the Jenkins project where I'm part of a group of 4
>>> people currently working on the project that is titled Plugin Health
>>> Scoring System
>>> <https://www.jenkins.io/projects/gsoc/2022/projects/plugin-health-scoring-system/>
>>> .
>>>
>>> Briefly, the Plugin Health Score is a composite score of various
>>> different probes related to Jenkins Plugins. These different probes will
>>> have different weights(value) and focus on different areas(think
>>> administrative metrics, code quality, best practices, and security) and we
>>> will generate a final score for each plugin within the Jenkins ecosystem.
>>>
>>> As communicated earlier in one of the previous emails, we're now very
>>> happy to share with you the Community-wide Survey link!
>>>
>>> Please find the link here: https://forms.gle/T6LLqQGYgKke2b8e9
>>>
>>> Your 5 mins spent on this survey would help us deliver the best results
>>> for our project. Thank you in advance!
>>>
>>> Regards,
>>> Dheeraj
>>>
>> --
>> 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/cc2dc61a-03a8-4695-8f6b-4436189f9690n%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/cc2dc61a-03a8-4695-8f6b-4436189f9690n%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/CAKwJSvxj3BYB7WcKtFpiU%2Big0B9kWBa-nmPFy7yeTO%2BGF8UCew%40mail.gmail.com.

Re: GSoC Project - Plugin Health Score Survey for Maintainers

[Adrien Lecharpentier]

Hello Wadeck,

let me answer here for Dheeraj (as mentor of the GSoC project).

At the moment, we don't have any probes in actions and we don't have a lot
of data. I know that we have for example, 52 plugins out of the 1872
currently in the update-center that don't have any SCM link. Out of the
others, some don't have a valid SCM link as well. We still haven't
implemented anything that could tell us which is the parent pom version
used by each plugin, but it is in the plan.

The plan here, is to get a sense of what make sense for the community, but
the weight of each rule will have to evolve with time. For example, if we
say "having a Jenkinsfile" is very important, but in 6months we have all
plugins with one, then we can lower the rule (new plugins don't come often)
and just have a warning if / when the Jenkinsfile disappear.
Same thing, for new probes, we don't intend to have all the probes in
September and be done with it. We want this project to serve the community
for the years to come. So, the probes and weight will have to evolve with
the community.

I know I haven't answered your question specifically, but that's the best I
can offer you.
-- Adrien

Le jeu. 30 juin 2022 à 08:58, 'wfoll...@cloudbees.com' via Jenkins
Developers  a écrit :

> Hello Dheeraj,
>
> Are you able to share the data distribution for the individual probes you
> already have in place? This will greatly help us understanding what should
> be done with the rules.
>
> E.g. if all plugins have a code coverage of 50%+, the weight should take
> that into consideration, in opposition to the situation where only the top
> 5% of the plugin have more than 5% of coverage.
> From my PoV the project has two goals, showing the current situation and
> also providing guidance about what to improve on a plugin, to follow the
> good practices.
>
> Thanks in advance,
>
> Wadeck
>
> On Wednesday, June 29, 2022 at 8:15:08 PM UTC+2 jodhadhe...@gmail.com
> wrote:
>
>> Hello Jenkins Contributors!
>>
>> My name is Dheeraj Singh Jodha and I'm selected as a Google Summer Of
>> Code 2022 student for the Jenkins project where I'm part of a group of 4
>> people currently working on the project that is titled Plugin Health
>> Scoring System
>> 
>> .
>>
>> Briefly, the Plugin Health Score is a composite score of various
>> different probes related to Jenkins Plugins. These different probes will
>> have different weights(value) and focus on different areas(think
>> administrative metrics, code quality, best practices, and security) and we
>> will generate a final score for each plugin within the Jenkins ecosystem.
>>
>> As communicated earlier in one of the previous emails, we're now very
>> happy to share with you the Community-wide Survey link!
>>
>> Please find the link here: https://forms.gle/T6LLqQGYgKke2b8e9
>>
>> Your 5 mins spent on this survey would help us deliver the best results
>> for our project. Thank you in advance!
>>
>> Regards,
>> Dheeraj
>>
> --
> 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/cc2dc61a-03a8-4695-8f6b-4436189f9690n%40googlegroups.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/CAKwJSvyCp_Opg%2BK_fjkX%2BdAd_PA%2BcAkBwrrHo4R7FqDmicWsBA%40mail.gmail.com.

Re: Looking for somebody who can run release of anything-goes-formatter-plugin

[Adrien Lecharpentier]

It seems that we need to update
https://github.com/jenkins-infra/repository-permissions-updater/blob/ace6411165c589f891d79d2ddd9f4044ba4a2954/permissions/plugin-anything-goes-formatter.yml#L8
to have someone with permissions on the repository manager first, no?

Le mer. 20 avr. 2022 à 21:08, Kohsuke Kawaguchi  a écrit :

> I don't seem to have the permission to run a plugin release any more,
> which is fine, so I'm looking for somebody who can do that to release
> https://github.com/jenkinsci/anything-goes-formatter-plugin/pull/5
>
> Any takers?
> --
> Kohsuke Kawaguchi
>
> --
> 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/CAN4CQ4yiK61RvJveb62y%2B2TRSA3dxzZPe8EDC71y8msLzWQa_g%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/CAKwJSvzzDCRujFah17HiYdvsc-NDs5yb7QtU-MpJxgDzws4daQ%40mail.gmail.com.

Re: [Question] Plugin Health Scores on Update Center?

[Adrien Lecharpentier]

I agree on the fact that the scoring shouldn't be added to the update
center file.
However, the details of the score shouldn't be added. My point is, if we
want the score to be visible on any controllers, only the score should be
added. Details of that score are should be left to the plugin site where
more details can be added than cryptic `isJenkinsfilePresent`.

On the service details, I don't know. The json file should be generated and
cached for sure, but the data on which the scoring is based could be stored.

Le jeu. 7 avr. 2022 à 07:45, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> Like update center, it can be a script that generates output and gets
> published to a server. Doesn't need to be a service. Actually
> shouldn't be a service, should be a once in a while generated json
> file so it can't be broken into or anything.
>
> On Wed, Apr 6, 2022 at 10:43 PM Dheeraj 
> wrote:
> >
> > I agree that there are just too many characters as the naming convention
> I've used is too descriptive, so maybe the character count can be decreased
> if we name them efficiently.
> >
> > The advantage of making the update center do it vs processing it
> elsewhere is that there will be one less service to maintain, but I agree,
> I didn't think of it from the character-count perspective.
> >
> > On Thu, Apr 7, 2022 at 9:07 AM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
> >>
> >> danielbeck is the owner of updatecenter, but my opinion is that is way
> >> too big for something jenkins won't use. the example you gave has 300+
> >> character, time 2000 plugins, thats 600+ megs of extra data that every
> >> jenkins would download
> >>
> >> What would be the advantage of making update center do it vs
> >> processing it elsewhere and then having plugin site pull it in?
> >>
> >> Gavin
> >>
> >> On Wed, Apr 6, 2022 at 8:28 PM Dheeraj 
> wrote:
> >> >
> >> > As per my understanding, for now, the data would only be used by
> Plugins Site. If in the future we want to show Plugin's health scores on
> Plugin Manager as well then I think every install of Jenkins would need the
> data.
> >> >
> >> >
> >> > An object full of values like this:
> >> > ```
> >> > "healthScore": 87,
> >> > “healthScoreParameters”: [
> >> >  {isParentPomLatest : 0.4},
> >> >  {isJenkinsfilePresent : 0.3},
> >> >  {checkJenkinsBaseVersion : -0.2},
> >> >  {checkDeprecatedLayouts : -0.1},
> >> >  {isSpotbugsEnabled : 0.3},
> >> >  {isScmUrlUpdated : 0.1},
> >> >  {isAutomatedDepCheckEnabled : 0.5},
> >> >  {isUsingPluginBom : 0.4},
> >> >  {isContributingGuidePresent : 0.2}
> >> >  .
> >> >  .
> >> >  .
> >> > ]
> >> > ```
> >> > The number of parameters can be expanded very easily and is yet to be
> decided specifically, but I think initially there can be around 30~ of them
> per plugin. This means 30*2000 = 6
> >> >
> >> >
> >> > That's weird, I specifically placed the link of the bookmark within
> my proposal which takes us to the exact section which answers your
> questions.
> >> >
> >> > Link:
> https://docs.google.com/document/d/1HTbcWh5C1KrCgEzgqeVEPyfr1H5fH5eTj8KpbWrWsSY/edit#bookmark=id.67e168tnirse
> >> >
> >> > Please let me know what you think about this, thanks!
> >> >
> >> >
> >> > On Wed, Apr 6, 2022 at 8:58 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
> >> >>
> >> >> Does every install for Jenkins need the data? Or would it be only
> for a single view?
> >> >>
> >> >>  How much data is it per plugin? A single number? Or an object full
> of values?
> >> >>
> >> >> Any data you'd want to add would need to be multiplied by like 2000
> plugins so it gets super expensive super quickly.
> >> >>
> >> >> I tried reading the proposal but after a couple pages or so I didn't
> feel like skimming any more to try and find this info.
> >> >>
> >> >> On Wed., Apr. 6, 2022, 5:14 a.m. Dheeraj, <
> jodhadheerajsi...@gmail.com> wrote:
> >> >>>
> >> >>> Hi everyone,
> >> >>>
> >> >>> Based on the project idea 'Plugin Health Score' for GSoC '22, I
> have a small question. Can we deliver each plugin's health score inside the
> JSON object published by the Update Center?
> >> >>>
> >> >>> More on this can be found in this proposal.
> >> >>>
> >> >>> --
> >> >>> 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/CAET3Cjcwrf_USC1tL-hRM0mDsd9gsa22bR5_rXbpNNj8aoJNGw%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 

Re: Automated plugin release

[Adrien Lecharpentier]

A good way would be to run

> mvn compile spotbugs:check || mvn spotbugs:gui

so that you can see the errors locally and work on them.

Le mar. 5 avr. 2022 à 13:40, Alexander Brandes  a
écrit :

> Various Spotbugs checks are failing. Take a look at
> https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/53/spotbugs/
> for the list of failures.
>
> Locally, you can run `mvn spotbugs:check` to highlight the failures with
> your IDE to address them.
>
> On Tuesday, 5 April 2022 at 13:31:00 UTC+2 mar...@gmail.com wrote:
>
>> I fixed the build errors and it's still failing, can you please help me
>> understand the root cause:
>>
>> https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/60/console
>>
>> *14:23:05* ERROR: Static analysis quality gates not passed; halting
>> early
>> *14:23:05* [GitHub Checks] GitHub check (name: Jenkins, status:
>> completed) has been published.
>> *14:23:05* Finished: FAILURE
>>
>> Thanks,
>> Marit.
>>
>> ב-יום שני, 4 באפריל 2022 בשעה 21:42:31 UTC+3, m...@basilcrow.com כתב/ה:
>>
>>> As Mark wrote in his previous message, it is because
>>> https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/ is
>>> failing.
>>>
>> --
> 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/fab3c8a1-36f7-4aed-aa59-009e033d8798n%40googlegroups.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/CAKwJSvwxaoestcU-Uyr5myZMQ5Fi2pTT11_CdSwXFDt6sHE_mA%40mail.gmail.com.

Re: Jenkins Core pull-requests management

[Adrien Lecharpentier]

Hello everyone,

I created https://github.com/jenkinsci/jenkins/pull/6413 to move this 
subject forward. 

Le mercredi 23 mars 2022 à 10:39:39 UTC+1, Adrien Lecharpentier a écrit :

> For everyone, to give data about why I started this discussion:
>  - we have 66 opens pull-requests, 5 of them are marked as ready-for-merge
>  - 10 out of 61 pull-requests are labeled proposed-for-close
>  - of the 10 oldest open pull-requests, 7 are labels proposed-for-close
>  - the 17 oldest open pull-requests were all created in 2020.
>
> Some of those old ones have been reviewed, approved but yet, because they 
> are old, now have merge conflicts. As some authors change focus with time, 
> which is perfectly normal to me, at some point we don't get any activities, 
> leading the pull-requests to be stalled. 
> I think having a clear closing policy will also help us prevent this 
> situation.
>
> Le mer. 23 mars 2022 à 09:43, Adrien Lecharpentier <
> adrien.lec...@gmail.com> a écrit :
>
>> Alex, I agree that we have the list of labels but even for 
>> `ready-for-merge`, we haven't document there what we tend to say when we 
>> put the label: the pr should be merge within 24hr (with no negative 
>> feedback). It is important that we have a clear guideline, like 
>>
>> >  * If you do not get feedback after 3 days, feel free to ping 
>> `@jenkinsci/core-pr-reviewers` in the comments.
>> -- (
>> https://github.com/jenkinsci/jenkins/blob/e3f8bc052d6065d3fcf6430f4c7c029c1fd25e54/CONTRIBUTING.md?plain=1#L107
>> )
>>
>> I think it's important to be clear, for the community and all 
>> contribution that everyone opening a PR should get a review and comments. 
>> But also that, to limit the time lost by anyone, when a PR is no where 
>> close to be merge, there is no consensus on it's content, there are 
>> concerns about its quality / justifications, we should close it, in a 
>> timely matter. 
>>
>> Again, I think this is to show respect to all contributors, to show that 
>> contributions are not going into a void, that we care about them. And I 
>> feel like we are lacking clarity about it for the moment. 
>>
>> Le mar. 22 mars 2022 à 23:41, Olivier Lamy  a écrit :
>>
>>>
>>>
>>> On Wed, 23 Mar 2022 at 02:07, Adrien Lecharpentier <
>>> adrien.lec...@gmail.com> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I've spent some time lately on looking at the pull-requests on 
>>>> jenkinsci/jenkins repository. For some old, inactive pull-requests I've 
>>>> pinged the authors and for some, added the proposed-for-close label. 
>>>>
>>>> However, the label description nor any prior discussion on the 
>>>> mailing-list are mentioning our policy about this (proposed-for-close) 
>>>> label. And I'd like to offer one: I'd like, as for the ready-for-merge 
>>>> label, to introduce a period of time, after which with no response from 
>>>> the 
>>>> author, we close the pull-request. I was thinking about 72 or 96hr.
>>>>
>>>
>>> Definitely sounds good to clean up some stale/dead PRs but I find 96h a 
>>> bit too short. (people can be off for few days/weeks and 1 or 2 weeks for 2 
>>> yo old PR will not hurt more)
>>> I have implemented something similar in some plugins using stale action 
>>> see configuration here 
>>> https://github.com/jenkinsci/maven-plugin/blob/master/.github/workflows/stale.yml
>>>   
>>> (tool here: https://github.com/actions/stale)
>>> with this configuration PRs 365 days old are marked stale then after 30 
>>> days they are closed.
>>>
>>  
>> A PR can always be reopen, the discussions and work put in it is not 
>> lost. 96hr with no activities seems long enough. It's not 96hr after the 
>> last message / commit, but 96hr after the label *with a message* is applied 
>> to the PR. We could definitively say that for PR with no activities in the 
>> last month, or less if some review comment were not addressed, we put a 
>> message and the label on the PR.
>>  
>>
>>>  This might seem a bit harsh, but my idea is to try to keep the 
>>> pull-requests list healthy. And when we have no consensus on the PR or no 
>>> response from the authors, it's healthier to close the pull-request. The 
>>> work done is not lost, the PR can be reopen later when the author is more 
>>> available to attend to it. 
>>>
>>>>
>>>> Also, in case the authors respond, we can simply put the label stalled 

Re: Jenkins Core pull-requests management

[Adrien Lecharpentier]

For everyone, to give data about why I started this discussion:
 - we have 66 opens pull-requests, 5 of them are marked as ready-for-merge
 - 10 out of 61 pull-requests are labeled proposed-for-close
 - of the 10 oldest open pull-requests, 7 are labels proposed-for-close
 - the 17 oldest open pull-requests were all created in 2020.

Some of those old ones have been reviewed, approved but yet, because they
are old, now have merge conflicts. As some authors change focus with time,
which is perfectly normal to me, at some point we don't get any activities,
leading the pull-requests to be stalled.
I think having a clear closing policy will also help us prevent this
situation.

Le mer. 23 mars 2022 à 09:43, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> Alex, I agree that we have the list of labels but even for
> `ready-for-merge`, we haven't document there what we tend to say when we
> put the label: the pr should be merge within 24hr (with no negative
> feedback). It is important that we have a clear guideline, like
>
> >  * If you do not get feedback after 3 days, feel free to ping
> `@jenkinsci/core-pr-reviewers` in the comments.
> -- (
> https://github.com/jenkinsci/jenkins/blob/e3f8bc052d6065d3fcf6430f4c7c029c1fd25e54/CONTRIBUTING.md?plain=1#L107
> )
>
> I think it's important to be clear, for the community and all contribution
> that everyone opening a PR should get a review and comments. But also that,
> to limit the time lost by anyone, when a PR is no where close to be merge,
> there is no consensus on it's content, there are concerns about its quality
> / justifications, we should close it, in a timely matter.
>
> Again, I think this is to show respect to all contributors, to show that
> contributions are not going into a void, that we care about them. And I
> feel like we are lacking clarity about it for the moment.
>
> Le mar. 22 mars 2022 à 23:41, Olivier Lamy  a
> écrit :
>
>>
>>
>> On Wed, 23 Mar 2022 at 02:07, Adrien Lecharpentier <
>> adrien.lecharpent...@gmail.com> wrote:
>>
>>> Hello everyone,
>>>
>>> I've spent some time lately on looking at the pull-requests on
>>> jenkinsci/jenkins repository. For some old, inactive pull-requests I've
>>> pinged the authors and for some, added the proposed-for-close label.
>>>
>>> However, the label description nor any prior discussion on the
>>> mailing-list are mentioning our policy about this (proposed-for-close)
>>> label. And I'd like to offer one: I'd like, as for the ready-for-merge
>>> label, to introduce a period of time, after which with no response from the
>>> author, we close the pull-request. I was thinking about 72 or 96hr.
>>>
>>
>> Definitely sounds good to clean up some stale/dead PRs but I find 96h a
>> bit too short. (people can be off for few days/weeks and 1 or 2 weeks for 2
>> yo old PR will not hurt more)
>> I have implemented something similar in some plugins using stale action
>> see configuration here
>> https://github.com/jenkinsci/maven-plugin/blob/master/.github/workflows/stale.yml
>> (tool here: https://github.com/actions/stale)
>> with this configuration PRs 365 days old are marked stale then after 30
>> days they are closed.
>>
>
> A PR can always be reopen, the discussions and work put in it is not lost.
> 96hr with no activities seems long enough. It's not 96hr after the last
> message / commit, but 96hr after the label *with a message* is applied to
> the PR. We could definitively say that for PR with no activities in the
> last month, or less if some review comment were not addressed, we put a
> message and the label on the PR.
>
>
>>  This might seem a bit harsh, but my idea is to try to keep the
>> pull-requests list healthy. And when we have no consensus on the PR or no
>> response from the authors, it's healthier to close the pull-request. The
>> work done is not lost, the PR can be reopen later when the author is more
>> available to attend to it.
>>
>>>
>>> Also, in case the authors respond, we can simply put the label stalled
>>> (for others to take over the PR). We could also put the PR back into draft,
>>> but all members have enough permission to do that on others pull-requests,
>>> but we could use the work-in-progress. Of course, after another period of
>>> time, with no more activities, we should close the PR anyway.
>>>
>>> Also, there is no mention of those labels, what they means and how we
>>> use it on our contribution guide [1]. Should we add a mention of those
>>> label on it?
>>>
>>> -- Adrien
>>>
>>>

Re: Jenkins Core pull-requests management

[Adrien Lecharpentier]

Alex, I agree that we have the list of labels but even for
`ready-for-merge`, we haven't document there what we tend to say when we
put the label: the pr should be merge within 24hr (with no negative
feedback). It is important that we have a clear guideline, like

>  * If you do not get feedback after 3 days, feel free to ping
`@jenkinsci/core-pr-reviewers` in the comments.
-- (
https://github.com/jenkinsci/jenkins/blob/e3f8bc052d6065d3fcf6430f4c7c029c1fd25e54/CONTRIBUTING.md?plain=1#L107
)

I think it's important to be clear, for the community and all contribution
that everyone opening a PR should get a review and comments. But also that,
to limit the time lost by anyone, when a PR is no where close to be merge,
there is no consensus on it's content, there are concerns about its quality
/ justifications, we should close it, in a timely matter.

Again, I think this is to show respect to all contributors, to show that
contributions are not going into a void, that we care about them. And I
feel like we are lacking clarity about it for the moment.

Le mar. 22 mars 2022 à 23:41, Olivier Lamy  a écrit :

>
>
> On Wed, 23 Mar 2022 at 02:07, Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I've spent some time lately on looking at the pull-requests on
>> jenkinsci/jenkins repository. For some old, inactive pull-requests I've
>> pinged the authors and for some, added the proposed-for-close label.
>>
>> However, the label description nor any prior discussion on the
>> mailing-list are mentioning our policy about this (proposed-for-close)
>> label. And I'd like to offer one: I'd like, as for the ready-for-merge
>> label, to introduce a period of time, after which with no response from the
>> author, we close the pull-request. I was thinking about 72 or 96hr.
>>
>
> Definitely sounds good to clean up some stale/dead PRs but I find 96h a
> bit too short. (people can be off for few days/weeks and 1 or 2 weeks for 2
> yo old PR will not hurt more)
> I have implemented something similar in some plugins using stale action
> see configuration here
> https://github.com/jenkinsci/maven-plugin/blob/master/.github/workflows/stale.yml
> (tool here: https://github.com/actions/stale)
> with this configuration PRs 365 days old are marked stale then after 30
> days they are closed.
>

A PR can always be reopen, the discussions and work put in it is not lost.
96hr with no activities seems long enough. It's not 96hr after the last
message / commit, but 96hr after the label *with a message* is applied to
the PR. We could definitively say that for PR with no activities in the
last month, or less if some review comment were not addressed, we put a
message and the label on the PR.


>  This might seem a bit harsh, but my idea is to try to keep the
> pull-requests list healthy. And when we have no consensus on the PR or no
> response from the authors, it's healthier to close the pull-request. The
> work done is not lost, the PR can be reopen later when the author is more
> available to attend to it.
>
>>
>> Also, in case the authors respond, we can simply put the label stalled
>> (for others to take over the PR). We could also put the PR back into draft,
>> but all members have enough permission to do that on others pull-requests,
>> but we could use the work-in-progress. Of course, after another period of
>> time, with no more activities, we should close the PR anyway.
>>
>> Also, there is no mention of those labels, what they means and how we use
>> it on our contribution guide [1]. Should we add a mention of those label on
>> it?
>>
>> -- Adrien
>>
>> [1]: https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md
>>
>> --
>> 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/CAKwJSvwTnxuwe1WZzs3eSJBgq783fMm8hkQ_-%3DFHS1u0%2B7GUAw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvwTnxuwe1WZzs3eSJBgq783fMm8hkQ_-%3DFHS1u0%2B7GUAw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> 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 discuss

Jenkins Core pull-requests management

[Adrien Lecharpentier]

Hello everyone,

I've spent some time lately on looking at the pull-requests on
jenkinsci/jenkins repository. For some old, inactive pull-requests I've
pinged the authors and for some, added the proposed-for-close label.

However, the label description nor any prior discussion on the mailing-list
are mentioning our policy about this (proposed-for-close) label. And I'd
like to offer one: I'd like, as for the ready-for-merge label, to introduce
a period of time, after which with no response from the author, we close
the pull-request. I was thinking about 72 or 96hr.

This might seem a bit harsh, but my idea is to try to keep the
pull-requests list healthy. And when we have no consensus on the PR or no
response from the authors, it's healthier to close the pull-request. The
work done is not lost, the PR can be reopen later when the author is more
available to attend to it.

Also, in case the authors respond, we can simply put the label stalled (for
others to take over the PR). We could also put the PR back into draft, but
all members have enough permission to do that on others pull-requests, but
we could use the work-in-progress. Of course, after another period of time,
with no more activities, we should close the PR anyway.

Also, there is no mention of those labels, what they means and how we use
it on our contribution guide [1]. Should we add a mention of those label on
it?

-- Adrien

[1]: https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md

-- 
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/CAKwJSvwTnxuwe1WZzs3eSJBgq783fMm8hkQ_-%3DFHS1u0%2B7GUAw%40mail.gmail.com.

Re: bitbucket-plugin - release is not published

[Adrien Lecharpentier]

You can also see the labels used in Release Drafter for the Jenkins project
here:
https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml

Le sam. 26 févr. 2022 à 19:00, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

> I used to have a little hackathon style tool that let you setup your repo
> with the standards, but at some point it broke
>
> https://github.com/halkeye/plugins-self-service/blob/master/labels.yaml
> is the list of official labels though, you might be able to use other ones,
> but that list worked once
>
> On Sat, Feb 26, 2022 at 9:50 AM tzach solomon 
> wrote:
>
>> Thank you Tim :)
>>
>> Is there a list of labels I need to choose from or I can label with
>> everything I want?
>>
>>
>>
>> On Sat, Feb 26, 2022, 6:15 PM Tim Jacomb  wrote:
>>
>>> Yes you need to label them
>>>
>>> On Sat, 26 Feb 2022 at 14:47, tzach solomon 
>>> wrote:
>>>
 I see now from
 https://www.jenkins.io/doc/developer/publishing/releasing-cd/ that I
 might have missed something? Do I need to label my PRs?

 *Now whenever Jenkins reports a successful build of your default
 branch, and at least one pull request had a label indicating it was of
 interest to users (e.g., enhancement rather than chore), your component
 will be released to Artifactory and release notes published in GitHub.*

 On Sat, Feb 26, 2022 at 4:42 PM tzach solomon 
 wrote:

> Daniel, thank you for trying to help. I really do appreciate it!
>
> I've tried again now to release a new version to fix
> https://issues.jenkins.io/browse/JENKINS-41635 but CI/CD does not
> seem to want to release my version.
>
> What have I done?
>
>1. Created a branch in my fork at
>https://github.com/tzachs/bitbucket-plugin
>2. Pushed the commit
>3. Merged back to https://github.com/jenkinsci/bitbucket-plugin
>
> At this point the CI started working and I followed it and saw the
> following failure,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/PR-83/1/pipeline
> BUT,
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fbitbucket-plugin/detail/master/88/pipeline
> passed.
>
> Also... from the Actions
>  tab, I've
> seen multiple CD runs (which I did not trigger), the last one is
> https://github.com/jenkinsci/bitbucket-plugin/actions/runs/1903327517
> .
> I don't know why release is not being performed? (shrugged)
>
> Can someone please help?
>
> On Tue, Feb 8, 2022 at 3:40 PM 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> On Tue, Feb 8, 2022 at 1:25 PM tzach solomon 
>> wrote:
>>
>>> Thanks Daniel (AGAIN! :)
>>>
>>> Can you please point me out what to read in order to fix these
>>> issues?
>>> On what did it fail?
>>> [image: image.png]
>>>
>>>
>>> This checks the "status" of the commit to be released as reported by
>> CI. It looks like if, at the time this action was run, something was 
>> wrong.
>> You can see the script doing this at
>> https://github.com/jenkins-infra/verify-ci-status-action/blob/master/run.sh
>> and I think we went into the block at line 42, so line 37 failed.
>>
>>
>> --
>> 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/CAMo7PtJXCuwu2i1nQJdRk%3DFDSgv7COuc1zeHPBGCKocJ5vQpHQ%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/CAC19wg%2BVb0PLs42fa5T7aNSsP4JgZut5%3DZh1ij%2Be1FGaUpdDsQ%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
>>> 

Re: Help maintaining "config-file-provider" plugin

[Adrien Lecharpentier]

Hello,

and I already approved the PR on RPU. Thank you for your help on this
plugin.
Regards,

Le mar. 30 nov. 2021 à 17:52, Jean-Marc Meessen 
a écrit :

> Hello
>
> I volunteer to actively maintain the "config-file-provider" plugin that is
> marked for adoption. I discussed this today with Adrien Lecharpentier as
> the plugin could do with some refreshing/modernisation work.
>
> Along this mail, I filed a pull request on the
> Repository-Permissions-Updater (RPU) for this purpose.
>
> Regards,
>
> /- Jmm
>
> --
> 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/CABLvyXzoCeB%3Di%2BUxh%2BQDfMKHyWswu5dvigaG_VrH%3D0ZMQHYOCA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CABLvyXzoCeB%3Di%2BUxh%2BQDfMKHyWswu5dvigaG_VrH%3D0ZMQHYOCA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
---
Adrien

-- 
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/CAKwJSvx%3DxEFgm--f9eGDQWjwELCsY_YGtZo2RcsBEHDJ_LR4Mw%40mail.gmail.com.

Re: Plugin documentation not showing on site

[Adrien Lecharpentier]

Hello Jean-Marc,

to my knowledge, the documentation generation requires a release and then
has some delay before showing up. This might still be the case and the
problem you are facing.


Le jeu. 18 nov. 2021 à 11:48, Jean-Marc Meessen 
a écrit :

> Hello,
>
> I am scratching my head with the plugin documentation. One day it shows on
> the site and the next day it doesn't (at least I am led to believe that).
>
> I have a README.md in the root of the workspace and the POM's  seems
> properly configured. Any ideas or explanations?
>
>- documentation page: https://plugins.jenkins.io/webhook-step/
>- github: https://github.com/jenkinsci/webhook-step-plugin
>- URL definition:
>https://github.com/jenkinsci/webhook-step-plugin/blob/master/pom.xml#L26
>
> /- Jmm
>
> --
> 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/CABLvyXysQM6TY%3D%2B%3DBN8kiBpgL2dF50EjggTk5fG1T3PWE%3DgJ0w%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/CAKwJSvy-ySejtVqTvjh%3Dpcj75sBASKyQPjJa7B%3DZjVU96My8RQ%40mail.gmail.com.

Re: Adopt a Jenkins Gitea plugin

[Adrien Lecharpentier]

+1.

Please open a PR on
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-gitea.yml
to add you as a maintainer.

Le mar. 26 oct. 2021 à 15:07, Mark Waite  a
écrit :

> +1 from me.  Thanks for being willing to adopt the plugin!
>
> On Tuesday, October 26, 2021 at 7:05:52 AM UTC-6 Lafriks wrote:
>
>> Hi,
>>
>>   I'm one of core Gitea maintainers and Gitea project would like to adopt
>> Jenkins Gitea plugin as it's has not been updated and for more than a year
>> already and is partially not functioning anymore because of API changes in
>> Gitea. All my attempts to contact plugin maintainer was not successful.
>>
>> Plugin Github URL: https://github.com/jenkinsci/gitea-plugin
>> My GitHub username: lafriks
>> Jenkins infrastructure account ID: lafriks
>>
>> Would be good if other Gitea maintainers could also be given access to
>> that plugin Github
>> repository or at least https://github.com/justusbunsi
>>
>> Best regards,
>> Lauris
>>
> --
> 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/1f07dbdc-e041-42bd-9989-5631049814e1n%40googlegroups.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/CAKwJSvzTj7bOWeXuA5wrZyAZ55DFruXdu%3DK%2BZr%3DDRpCpDpT90Q%40mail.gmail.com.

Re: Terminology Updates

[Adrien Lecharpentier]

I have to say that the music parallel from Angelique seems nice and has a
lot of sense in my opinion.
And the Jenkins butler is not that far from a music orchestrator as well.

Le lun. 15 juin 2020 à 22:47, Daniel Beck  a écrit :

>
>
> > On 15. Jun 2020, at 22:39, Markus Winter  wrote:
> >
> > Second the server is also just plain agent (more or less). For this we
> > could use the term "main"  as the default label.
>
> That's what I proposed earlier in the thread as well.
>
> 'main' seems reasonable, but still has the connotation that it's actually
> a good idea to use this node, when it rarely is.
>
> --
> 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/300611FD-062F-40B8-9292-8E16170ABDE6%40beckweb.net
> .
>

-- 
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/CAKwJSvwus_DLMT%3Dn2vxwpHya-Cn24qNRU%2B2bDbrKQBOyYL25yw%40mail.gmail.com.

Re: Proposal: New twitter contributors

[Adrien Lecharpentier]

of course +1!

Le mer. 11 déc. 2019 à 18:31, Arnaud Héritier  a
écrit :

> +1
>
> Le mer. 11 déc. 2019 à 17:44, Baptiste Mathus  a écrit :
>
>> +2, I mean. So very yey ;)
>>
>> Le mer. 11 déc. 2019 à 17:38, Kohsuke Kawaguchi  a
>> écrit :
>>
>>> Yay, +1
>>>
>>> On Wed, Dec 11, 2019 at 8:35 AM Tracy Miranda 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> As per the process outlined in JEP 10
>>>> <https://github.com/jenkinsci/jep/tree/master/jep/10>, I would like to
>>>> propose two new Twitter Contributors for the @jenkinsci account.
>>>>
>>>> 1. Oleg Nenashev - Oleg has been regularly proposing tweets/retweets
>>>> via the Advocacy gitter channel as well as tweeting community highlights
>>>> around hacktoberfest, gsoc, SIGs, elections etc. For example
>>>> https://twitter.com/oleg_nenashev/status/1202631389277032449
>>>> https://twitter.com/oleg_nenashev/status/1194982086521872384
>>>> https://twitter.com/oleg_nenashev/status/1176981880786313217
>>>>
>>>> 2. Mark Waite - Mark regularly tweets around Platform SIG &
>>>> Documentation SIG, Jenkins git plugin, Jenkins online meetups and other
>>>> community highlights. For example:
>>>> https://twitter.com/MarkEWaite/status/1190616140868808705
>>>> https://twitter.com/MarkEWaite/status/1180093593073045504
>>>> https://twitter.com/MarkEWaite/status/1192437176446812160
>>>>
>>>> By giving Oleg & Mark access to schedule tweets, etc it will help the
>>>> community with more timely and regular communication around the many
>>>> community activities and technical developments.
>>>>
>>>> Please go ahead and vote/comment on this proposal. I will also add to
>>>> an upcoming board meeting for approval there.
>>>>
>>>> Regards,
>>>> Tracy
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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/CACTaz6qfPKYm_5O4bW-%2Bnxhu2y6u-rf4C1eH7meTA2h2taXY-A%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qfPKYm_5O4bW-%2Bnxhu2y6u-rf4C1eH7meTA2h2taXY-A%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> --
>>> Kohsuke Kawaguchi
>>>
>>> --
>>> 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/CAN4CQ4xQQpfR_d2U3FPSNs3y_2nHX-4iZuFFT%3Dkc6DZq3mMrEg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xQQpfR_d2U3FPSNs3y_2nHX-4iZuFFT%3Dkc6DZq3mMrEg%40mail.gmail.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/CANWgJS5MLLKKWcyxc0LmKdsBe4y%2BBFKdbnnEKLGaxs66P-J2Ng%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5MLLKKWcyxc0LmKdsBe4y%2BBFKdbnnEKLGaxs66P-J2Ng%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> -
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_o9XdRj_TXALA_WbtJUBOP__Wh2AMpGjLWLQHf-dhhSA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_o9XdRj_TXALA_WbtJUBOP__Wh2AMpGjLWLQHf-dhhSA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvyepPmiYnsG3tJk86sKmqMPDdma2PBR3ej7P8Mx3df5EA%40mail.gmail.com.

Re: Adopting Google Metadata plugin

[Adrien Lecharpentier]

I'm sorry Matt, it seems that you are not the current maintainer of the
plugin based on
repository-permissions-updater#plugin-google-metadata-plugin.yml.
<https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-google-metadata-plugin.yml>

Nghia Tran, would you agree for me to help you on maintaining the plugin?
-- Adrien

Le mer. 20 nov. 2019 à 15:38, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> Hello,
>
> I came across the Google Metadata plugin [1] and saw that this plugin
> hasn't been touched in 5years. So I'd like to become maintainer of the
> plugin.
>
> Matt, would you agree for me to help you with this plugin?
>
> --
> Adrien
> [1]: https://github.com/jenkinsci/google-metadata-plugin
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvw45Anj63zJMc%3DXdOdSSs7cKOWcSfsSWBtaN-O_J9RSAg%40mail.gmail.com.

Adopting Google Metadata plugin

[Adrien Lecharpentier]

Hello,

I came across the Google Metadata plugin [1] and saw that this plugin
hasn't been touched in 5years. So I'd like to become maintainer of the
plugin.

Matt, would you agree for me to help you with this plugin?

-- 
Adrien
[1]: https://github.com/jenkinsci/google-metadata-plugin

-- 
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/CAKwJSvx1LgWdVF90x%2BcRsW-y8CEoQP%3D2FWrzWzh8pfz7GsWG-w%40mail.gmail.com.

Re: oauth-credentials plugin adoption

[Adrien Lecharpentier]

Thank you both, let me re-add Jenkins Dev List so that @Oleg Nenashev
 can see the answers you provided.
-- Adrien

Le lun. 11 nov. 2019 à 18:46, Craig Barber  a
écrit :

> Thanks Matt. I approved on the issue, but will also add my LGTM here :)
>
> On Mon, Nov 11, 2019 at 9:39 AM Matt Moore  wrote:
>
>> +Craig -list
>>
>>
>>
>> I can’t mail the list without being a member, but here’s what I replied
>> yesterday.
>>
>> -M
>>
>>
>>
>>
>>
>> *From: *Matt Moore 
>> *Date: *Sunday, November 10, 2019 at 7:25 AM
>> *To: *Adrien Lecharpentier , Jenkins
>> Developers 
>> *Cc: *"erjoh...@google.com" 
>> *Subject: *Re: oauth-credentials plugin adoption
>>
>>
>>
>> I’m adding Eric Johnson whose team at Google has taken on ownership of
>> other plugins my team developed (many) years ago.  It may also be worth
>> adding Vic Iglesias, as I believe he was involved in a related thread about
>> patching Google’s “source” plugin right before I left (I don’t have his
>> email handy).  They might be helpful for the “Google” side.
>>
>>
>>
>> From my perspective, I don’t mind.  I would like the owner to not be me
>> as I haven’t touched these in like 5-6 years. 
>>
>> -M
>>
>>
>>
>>
>>
>> *From: *Adrien Lecharpentier 
>> *Date: *Sunday, November 10, 2019 at 1:14 AM
>> *To: *Jenkins Developers , Matt Moore <
>> mattm...@vmware.com>
>> *Subject: *Re: oauth-credentials plugin adoption
>>
>>
>>
>> I re-add Matt Moor here then.
>>
>>
>>
>> Le dim. 10 nov. 2019 à 07:44, Oleg Nenashev  a
>> écrit :
>>
>> There is no company plugin ownership policy in Jenkins ATM. It is
>> something on my radars. Am explicit approval from Matt Moore is needed to
>> do the permission transfer. But indeed sign-off from Google is helpful
>> here, thanks Jeremy
>>
>>
>> Once there is am explicit +1 from Matt in this thread or in the GitHub
>> pill request, I will do the transfer
>>
>> --
>> 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/726cdbcf-c45c-4273-83ba-9f6027a63d28%40googlegroups.com
>> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2F726cdbcf-c45c-4273-83ba-9f6027a63d28%2540googlegroups.com=02%7C01%7Cmattmoor%40vmware.com%7C1fbaf59455224ffdcb8f08d765be74c1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637089740984710534=pNzhk2zKuMhYsIMui7UAIYOn3wVl9xIkvSxuapZz2Qs%3D=0>
>> .
>>
>>
>
> --
> Craig Barber
> Software Engineer
> Cloud Graphite: Platforms
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvxwdpsJbXZgyAR4KzOzsTn4h5BzgJz0gYBaQHBXeR3eLw%40mail.gmail.com.

Re: oauth-credentials plugin adoption

[Adrien Lecharpentier]

I re-add Matt Moor here then.

Le dim. 10 nov. 2019 à 07:44, Oleg Nenashev  a
écrit :

> There is no company plugin ownership policy in Jenkins ATM. It is
> something on my radars. Am explicit approval from Matt Moore is needed to
> do the permission transfer. But indeed sign-off from Google is helpful
> here, thanks Jeremy
>
>
> Once there is am explicit +1 from Matt in this thread or in the GitHub
> pill request, I will do the transfer
>
> --
> 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/726cdbcf-c45c-4273-83ba-9f6027a63d28%40googlegroups.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/CAKwJSvxxwuy5J_fm2cAiEmwqzMbW3Jjp1vUdouGdKCtofizj5A%40mail.gmail.com.

Re: oauth-credentials plugin adoption

[Adrien Lecharpentier]

Thank you for the heads up.

Le ven. 8 nov. 2019 à 15:47, Matt Moore  a écrit :

> I haven’t touched this in many years now, and am not sure who the best
> person at Google to talk to about this is.  Sorry!
>
>
>
> *From: *Adrien Lecharpentier 
> *Date: *Friday, November 8, 2019 at 1:29 AM
> *To: *Jenkins Developers , "
> mattm...@google.com" , Matt Moore <
> mattm...@vmware.com>
> *Subject: *Re: oauth-credentials plugin adoption
>
>
>
> Matt, I got your emails from your Github account and the one used on the
> Git commit. Sorry if it's not the email you used in the Jenkins community.
>
>
>
> Would you agree for Evaristo and I to help you maintain oauth-credentials
> plugin?
>
> Thanks in advance.
>
>
>
> Le jeu. 7 nov. 2019 à 17:19, Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> a écrit :
>
> Hello,
>
>
>
> Evaristo and I would like to adopt the plugin oauth-credentials (
> https://github.com/jenkinsci/oauth-credentials-plugin
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkinsci%2Foauth-credentials-plugin=02%7C01%7Cmattmoor%40vmware.com%7C0d1219285a4643c7a6e008d7642e37b7%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637088021978301285=wb%2B7eNtW1Eazvqcnz0r65OvexLs%2Fi16AJ39aUcFy%2BgY%3D=0>).
>
>
> I don't know the email for Matt Moore but I pinged him on the PR I opened
> on the repository-permission-updated [1].
>
>
> --
>
> Adrien Lecharpentier
>
>
>
> [1]:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1335
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2Fpull%2F1335=02%7C01%7Cmattmoor%40vmware.com%7C0d1219285a4643c7a6e008d7642e37b7%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C1%7C637088021978311275=RXbEcm3CMEnO7MIauqPaSyKNboxEyJEha8XJX0wkFgk%3D=0>
>
>
>
> --
>
> Adrien Lecharpentier
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvyLOi7CnG2kBK1Gxrz76KMco2ZBtfvVQX2MmaFM%2BWAD1Q%40mail.gmail.com.

Re: oauth-credentials plugin adoption

[Adrien Lecharpentier]

Matt, I got your emails from your Github account and the one used on the
Git commit. Sorry if it's not the email you used in the Jenkins community.

Would you agree for Evaristo and I to help you maintain oauth-credentials
plugin?
Thanks in advance.

Le jeu. 7 nov. 2019 à 17:19, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> Hello,
>
> Evaristo and I would like to adopt the plugin oauth-credentials (
> https://github.com/jenkinsci/oauth-credentials-plugin).
> I don't know the email for Matt Moore but I pinged him on the PR I opened
> on the repository-permission-updated [1].
>
> --
> Adrien Lecharpentier
>
> [1]:
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1335
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvw0ga1875P7jTrQqeJ%2BiO7hT6GhM3z%3DT%3Dr9ZhGdAgK-%2Bg%40mail.gmail.com.

oauth-credentials plugin adoption

[Adrien Lecharpentier]

Hello,

Evaristo and I would like to adopt the plugin oauth-credentials (
https://github.com/jenkinsci/oauth-credentials-plugin).
I don't know the email for Matt Moore but I pinged him on the PR I opened
on the repository-permission-updated [1].

-- 
Adrien Lecharpentier

[1]:
https://github.com/jenkins-infra/repository-permissions-updater/pull/1335

-- 
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/CAKwJSvznK_xkb-utdJfkeBu95nQZTw4nNa7egzs9%2BoZfTeZtOw%40mail.gmail.com.

Re: Maintenance Window - ci.jenkins.io - 2019/03/06 - 9AM UTC+2

[Adrien Lecharpentier]

Thank you Olivier.

A side note on the report of issues: please make sure to use the label
`java11` so it can popup in different filters.
BR,
-- Adrien

Le lun. 3 juin 2019 à 11:38, Olblak  a écrit :

> Hi Everybody,
>
> I am happy to announce that ci.jenkins.io is now running on Java 11.
>
> Thanks Adrien Lecharpentier and Baptiste Mathus for their help during the
> migration and more globally thanks to all the people
> involved in the platform-sig <https://jenkins.io/sigs/platform/> for
> their work on jenkins running on java 11.
>
> Excepted minor issues that we fixed  during the migration, upgrading from
> jdk8 to jdk11 was really easy.
>
> In short we executed following steps:
>
>- Set jenkins master in maintenance mode "Prepare for shutdown".
>- Backup jenkins home, yolo
>- Update JAVA_OPTS with options specific to java11 as defined here
>
> <https://github.com/jenkins-infra/jenkins-infra/blob/66337c3cbff1f5ab0cc773ba4a55825f01a6b5cb/hieradata/clients/azure.ci.jenkins.io.yaml#L12>
>  mainly
>related to the garbage collector
>- Move from the docker image jenkins/jenkins:lts-alpine to
>jenkins/jenkins:lts-jdk11
>- Restart Jenkins
>- Ensure linux/windows agents use the same major java version than
>master ( java 11 )
>
>
> For the windows agent we had to change the init script to use zulu11.31.11
> <https://cdn.azul.com/zulu/bin/zulu11.31.11-ca-jre11.0.3-win_x64.zip> instead
> of zulu8.28.0.1
> <https://cdn.azul.com/zulu/bin/zulu8.28.0.1-jdk8.0.163-win_x64.zip>
> And the linux agent was already using java11 anyway since we upgrade the
> agent to ubuntu 18.04
>
> As usual, feel free to report any issues that you may have about
> ci.jenkins.io, on issues.jenkins-ci.org using the 'infra' project.
>
> Remark, upgrading the other jenkins intances to java11 is not yet planned.
>
> Cheers
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
>
>
> On Mon, May 27, 2019, at 11:57 AM, Olblak wrote:
>
> Hi Everybody,
>
> The platform sig <https://jenkins.io/sigs/platform/> has been working
> hard on running jenkins with java11 and it's now time to use it in a real
> life scenario.
>
> Adrien Lecharpentier and I will upgrade ci.jenkins.io next Monday 3th of
> June at 9AM UTC+2.
>
> As usually with such maintenance, we'll communicate in different ways:
> * We'll be on a call using Google Meet
> <https://meet.google.com/hec-yjep-how> and on irc #jenkins-infra
> * We'll notify on this mail thread and update INFRA-2115
> <https://issues.jenkins-ci.org/browse/INFRA-2115> when the migration is
> done.
>
> In short we'll execute following steps:
> * Set jenkins master in maintenance mode "Prepare for shutdown"
> * Backup jenkins home
> * Update JAVA_OPTS with options specific to java11
> * Move from the docker image jenkins/jenkins:lts-alpine to
> jenkins/jenkins:jdk11
> * Ensure linux/windows agents use the same major java version than master
> ( java 11 )
>
> Remark: We won't (voluntarily ) modify the other jenkins instances, at
> least for this maintenance window.
>
> Cheers
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
> --
> 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/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/b0ec4765-ba06-4460-a832-c9522c1f796e%40www.fastmail.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/a94927d2-520c-4953-b666-50d9eb6ba10e%40www.fastmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/a94927d2-520c-4953-b666-50d9eb6ba10e%40www.fastmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvwWi59v5K8RjjXFU%3DcNOhibV%2B_v%3DVMxhPTeN4dZruPtag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Dependency plugin specifier in Pom.xml

[Adrien Lecharpentier]

What you are describing looks like an enforcer-rule report.
It's there to let you know that your plugin depends on a older version of
jenkins than what is required by one of your dependency.

So yes, you need to update your `jenkins.version` to match what the
dependency you added requires.

BR,
-- Adrien

Le sam. 18 mai 2019 à 18:25, selva vignesh  a
écrit :

> Yeah sure. I will upload in github and let you know
>
> On Sat, 18 May 2019 at 9:54 PM, Parichay Barpanda <
> parichay.barpa...@gmail.com> wrote:
>
>> I am not quite sure about this problem, maybe upgrade your Jenkins
>> version to Jenkins LTS beyond 2.6 like 2.60.3.
>>
>> And debugging on mailing list can be tedious and complicated. If you
>> upload your plugin to GitHub or any other SCM and share the link I can take
>> a look at it.
>>
>> On Sat 18 May, 2019, 21:49 selva vignesh, 
>> wrote:
>>
>>> Hi Parichay,
>>> Yes I have tried. I have given build var plugin as a dependency and
>>> scope as compile time.
>>> While packaging using mvn package, it’s asking me do check commons-Lang
>>> 2.1 and Jenkins expecting 2.6. Can you please explain how Can I resolve
>>> this kind of issue.
>>>
>>> On Sat, 18 May 2019 at 9:35 PM, Parichay Barpanda <
>>> parichay.barpa...@gmail.com> wrote:
>>>
>>>> Hi Vignesh,
>>>>
>>>> I am not quite sure I understand your problem but installing your
>>>> dependency plugins before installing your plugin should be pretty
>>>> straightforward:
>>>>
>>>> 1) Inside POM mention your dependency plugins within 'dependencies' tag
>>>>
>>>> 2) Run 'mvn clean install' then 'mvn hpi:run', your plugin should run a
>>>> pseudo Jenkins instance with your plugin and it's dependencies installed.
>>>>
>>>> Thanks,
>>>> Parichay (baymac)
>>>>
>>>> On Sat 18 May, 2019, 21:16 Jeff Pearce,  wrote:
>>>>
>>>>> I don’t quite get it. Can you describe the real world scenario you’re
>>>>> trying to implement?
>>>>>
>>>>> Best,
>>>>> Jeff
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On May 18, 2019, at 8:07 AM, selva vignesh 
>>>>> wrote:
>>>>>
>>>>> Hi Adrien,
>>>>> Thanks for replying.. my question is if I want to install my plugin it
>>>>> should ask me to mentioned plugin should be installed example pipeline
>>>>> plugin should be installed first and after that only allow to install my
>>>>> plugin.  Or else installation must be failed and showing warning message 
>>>>> as
>>>>> pipeline plugin install before install my plugin.
>>>>> Hope you understand now.. If not please let me know. I will explain
>>>>> again.
>>>>> On Sat, 18 May 2019 at 3:17 PM, Adrien Lecharpentier <
>>>>> adrien.lecharpent...@gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> all you need is to declare the plugins as dependencies of your
>>>>>> plugin.
>>>>>> You need to specify them in `compile` scope and not optional.
>>>>>>
>>>>>> However, you should only declare those plugins if you need their code
>>>>>> for your own plugin.
>>>>>> From your question, I'm not sure it's the case.
>>>>>>
>>>>>> BR,
>>>>>> -- Adrien
>>>>>>
>>>>>> Le sam. 18 mai 2019 à 08:40, selva vignesh 
>>>>>> a écrit :
>>>>>>
>>>>>>> HI,
>>>>>>>   How to make some dependency plugin to be installed while our
>>>>>>> plugin before installing.
>>>>>>> What are the changes need to be done at pom.xml.
>>>>>>> Thanks in advance
>>>>>>>
>>>>>>> --
>>>>>>> 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/f678a5d0-0ee5-4a76-b5f5-ed2b3

Re: Dependency plugin specifier in Pom.xml

[Adrien Lecharpentier]

Hello,

all you need is to declare the plugins as dependencies of your plugin.
You need to specify them in `compile` scope and not optional.

However, you should only declare those plugins if you need their code for
your own plugin.
>From your question, I'm not sure it's the case.

BR,
-- Adrien

Le sam. 18 mai 2019 à 08:40, selva vignesh  a
écrit :

> HI,
>   How to make some dependency plugin to be installed while our plugin
> before installing.
> What are the changes need to be done at pom.xml.
> Thanks in advance
>
> --
> 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/f678a5d0-0ee5-4a76-b5f5-ed2b395bc674%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/f678a5d0-0ee5-4a76-b5f5-ed2b395bc674%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvyFrXQFEfo_mCpvzZWiKc_rUZaz28r9Hx2mRg3S%2B0ACoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why don't disable DNS Multicast by default?

[Adrien Lecharpentier]

If we disable the feature by default (which I think is a good idea), maybe
we could rename the system property to "enabled". I have issues with double
negatives.

Le ven. 17 mai 2019 à 12:08, Francisco Javier Fernandez <
fjfernan...@cloudbees.com> a écrit :

> Hi all!
>
> There are many opened issues related to DNS Multicast. The version of
> JmDNS used by Jenkins is an old one. Many of them should be fixed updating
> it (PR already opened <https://github.com/jenkinsci/jenkins/pull/4021>),
> but also I'm wondering if it's worth to change the default behaviour and
> disable it, so anyone who wants this feature enabled should use
> the hudson.DNSMultiCast.disabled system property. It does not seem to be a
> widely used feature.
>
> Thoughts?
>
> Best regards,
>
> Francisco J. Fernandez
>
> --
> 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/401769a0-d616-4557-8079-f6ad26403d14%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/401769a0-d616-4557-8079-f6ad26403d14%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvxkYjP%3DF2Es9359bN_uwU9BTVbaZm%2Be2KvugTx8TUbo1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: PRs on jenkins-infra/repository-permissions-updater

[Adrien Lecharpentier]

Manuel,

did you try to ping a current maintainer?

Le lun. 10 déc. 2018 à 18:12, Manuel Vacelet  a
écrit :

> Hi there,
>
> I got a PR on jenkins-infra/repository-permissions-updater pending since
> 19 days without any info about why it's pending.
> I saw in a previous message that there was some infra issues in
> artifactory, is that related ?
>
> How can I move forward ?
>
> Thanks,
> Manuel
>
> --
> 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/b53d8a38-8e4c-4d66-a01f-681daec6d81c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/b53d8a38-8e4c-4d66-a01f-681daec6d81c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvy%2B7j9dGWQd34tB42sb1GhDjBX6Y9XmjCKGhdjvriG8%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins World 2018] - Graders wanted

[Adrien Lecharpentier]

I'd be happy to help as well. I submitted a subject to the French CFP, I
don't know if that makes me inadmissible for the review.

-- Adrien

Le ven. 13 avr. 2018 à 20:46, Michael Pailloncy 
a écrit :

> Hi Alyssa,
>
> I would be very happy to help.
>
> Cheers
> Michaël
>
>
> On Fri, Apr 13, 2018 at 6:09 PM, Alyssa Tong  wrote:
>
>> Hello,
>>
>> I am looking for additional graders to join the Jenkins World (JW) review
>> committee to help grade Jenkins World 2018 SF & EU proposals.
>>
>> Time commitment expected:
>>
>>- JW SF: 137 Jenkins submissions.
>>- JW EU: 76 Jenkins submissions at the moment but most likely will
>>increase after close of CFP this Sunday.
>>
>> What you get:
>>
>>- Pix, bio on the Committee webpage (part of JW website)
>>- JW swag
>>- Free conference ticket to JW
>>
>> Criteria:
>>
>>- You love to read and has a keen mind for the latest and greatest,
>>trendy technical topics
>>
>> Pls respond to this thread if you're interested.
>>
>> BR,
>> alyssa
>>
>> --
>> 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/CAC9wNaxGJ-r-Jz%3D1Nyx7otR0TsHEYDPR-V-sR%2B%3D5JRCTsZNbRw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c1Lu0C4zH%3D7dV1n%3DeDgixovk9LLWdhzGTB8N-HmYKpvdg%40mail.gmail.com
> 
> .
> 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/CAKwJSvxVSJm5vGb4Ls97TXPgHX%3DgBLWRqczL_sB5Wo29_%3DG92A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Artifact Deployer plugin

[Adrien Lecharpentier]

It has been a long time since I had a look at this plugin. I can help you
if you need but I'm OOO for the next week.

@Oleg: let's add Sean as a maintainer.
Best regards,
-- Adrien

Le dim. 16 juil. 2017 à 10:55, Oleg Nenashev <o.v.nenas...@gmail.com> a
écrit :

> Hi Sean,
>
> This plugin is up for adoption, hence we do not need extra confirmations,
>
> On the other hand, I see that Adrien Lecharpentier has done the release in
> the past. I doubt he wants to be a maintainer, but let's give him a chance
> to comment in this thread.
>
> Best regards,
> Oleg
>
>
>
> вторник, 11 июля 2017 г., 13:36:00 UTC+2 пользователь Sean Turner написал:
>>
>> Needed to join the group to send the message!
>>
>> On Tue, Jul 11, 2017 at 11:46 AM, Sean Turner <seantu...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> Current client is using this heavily, so could you please add me as a
>>> maintainer so I can sort out some of the security issues e.g.
>>> SECURITY-294 and "make this plugin great again". I'm not really a Java
>>> dev but can get my head around this I think.
>>>
>>> https://wiki.jenkins.io/display/JENKINS/ArtifactDeployer+Plugin
>>>
>>> github: seanturner83
>>> jenkins: seanturner83
>>>
>>> KR,
>>>
>>> Sean
>>>
>>
>>

-- 
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/CAKwJSvx9T1k%2B9_dKmtmAe%3Di39SSyb8_cinAe2T6AsF44ZMxZRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Plugin dev for Jenkins 2

[Adrien Lecharpentier]

Hi,

I have a question about plugin development which target Jenkins 2: when we
do `mvn hpi:run`, you are facing the security setup and the plugin wizard.
I don't have issues with the security but with the wizard.

Would it make sense to make the HPI plugin skip this wizard?

Best regards,
-- Adrien

-- 
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/CAKwJSvxf4_YiyPXf6YiS9C05WuNA7DZ-9zMFpC9K1Py0XmGYEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: combine multiple pipeline steps

[Adrien Lecharpentier]

Hi,

you could create a function take a clojure in parameter and use it. For
example:

def myenvironment(def body) {
  def label = configure()
  node(label) {
body.call()
  }
}

and use it like

myenvironment {
  sh "make"
}

Le mar. 2 août 2016 à 14:51, Ioannis Canellos  a écrit :

> Hi all,
>
> I have a couple of pipeline steps that I want to have the combined as one.
> For example I have the 'configure' step which returns a label and I want
> to combine it with the node step as follows:
>
> label = configure()
> node(label) {
> ...
> }
>
> So, what I want is to create an alternative of node, that encapsulates the
> above.
> Any hints on where I should look?
>
> --
> 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/4d77a7a6-1f1a-43b9-82f1-a73e5147f56b%40googlegroups.com
> 
> .
> 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/CAKwJSvxOybDVs5tWpN7p%2Bo%3DR4kKnkkc7-08iAdUovtsrnFXTUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

[Adrien Lecharpentier]

I agree with Robert. Moreover, Readme files across the repositories are not
containing the same details, are not written the same way and some
repositories don't have any. I'm all for KISS principle but I don't think
README.md is the place to old this but it should be on the repository so
the maintainers have full control on it and users can offer fix /
enhancement on the doc through PR.

Le ven. 17 juin 2016 à 11:24, Robert Sandell  a
écrit :

> No please, how many times do I have to plead my case here?
> The readme in the root of the repo is IMO aimed at describing the
> repository you are currently looking at; e.g. what it is, *how to build
> it*, who maintains it, links to additional resources (like user docs)
> etc. it is not the user documentation, it is developer documentation.
>
> You should sync with the GSoC project that is currently going on user
> docs:
> https://groups.google.com/forum/#!searchin/jenkinsci-dev/GSoC/jenkinsci-dev/kNZMOsF_ueA/15BWeTdXDQAJ
>
> /B
>
> On Tue, Jun 14, 2016 at 10:43 PM, Gus Reiber 
> wrote:
>
>> +1 to GitHub readme as well. Why put the same doc in 2 places.
>>
>>
>>
>> On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:
>>>
>>> +1 for the effort, ideally I'd like to see something that can pull
>>> information from the github README.md files and have people push updates to
>>> the descriptions that would be shown to their own plugin repositories.
>>> Perhaps some of the other information could be pulled from a metadata file
>>> that was also in the plugin repository.
>>>
>>> On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber  wrote:
>>>
 Hey all,
So I have on and off pushed the idea that the Jenkins community
 could benefit greatly from an overhaul of the wiki based plugins site. As
 an ultimate goal, I don't see any reason we couldn't build something that
 approach a modern app store, like https://play.google.com/store, but
 for the short run, it seems like we should be able to improove upon the
 browsing experience of the existing list page and detail view.

 Existing:

- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
- detail:
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

 I think as a minimum, we ought to be able to provide a reasonable
 search interface and means of filtering plugins by maintainer, Jenkins core
 requirement, plugins labels, and installation count. Plugins should also be
 assigned to categories that map to Jenkins user expectations a bit better
 than the current list of ~30ish maintainer assigned labels do today.
 Ideally the user ought to be able to manage the list of all plugins by
 specific features of the plugin and by some suggestion of quality or
 currentness of the plugin.

 At various points, my interest in bringing this value to the community
 has been great enough to assemble a couple of different prototypes and
 wireframes, attempting to generate interest. I have also had a chance to
 play with some prototypes from others all with what seems to me to be
 reasonable implementation paths. Attached are a few more recent sketches
 showing the gist of how we might handle searching and filtering as well as
 the plugin details.

 Anyway, at the moment, the plugin site is maintained by our
 representatives here in the community. So it is really the will of the
 community that should be reflected in any efforts that are actually
 deployed and later maintained by our community. Thus again, I am looking
 for grass roots support for the effort, support that potentially includes
 some avenue for long term hosting and support.

 So my questions are these: Is enhancing the plugin site really worth
 that degree of effort to the community? If you think it is, would you be
 willing to join the effort, both for the immediate development needs, but
 also for longer term support? Do you have any experience with other
 communities who manage to accomplish this sort of ends?

 ...and finally, could you help articulate a set of minimum requirements
 that would make overhauling the plugin site worth while?

 Thanks in advance,
 Gus

 --
 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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/33ab5051-e2b8-4684-8d9e-0d5aa6ab1284%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 

Re: Build failure when trying to generate hpi file [noob alert]

[Adrien Lecharpentier]

It seems that it's not a Jenkins plugin project. Are you sure it's the
correct one?
-- Adrien

Le ven. 15 avr. 2016 19:02, Telmo Cardoso <telmo.card...@gmail.com> a
écrit :

> I actually sent the wrong project, the one I'm trying to generate is
> https://github.com/damianszczepanik/cucumber-reporting
>
> But I'll give it a go on your suggestions
>
>
> On Friday, April 15, 2016 at 5:41:01 PM UTC+1, Adrien Lecharpentier wrote:
>
>> The version of Jenkins-core the plugin depends on is determine by the
>> parent-pom version:
>> https://github.com/jenkinsci/cucumber-reports-plugin/blob/master/pom.xml#L6
>>
>> However, to generate the `hpi`, you should use the classic `mvn package`
>> rather than calling the `hpi` plugin.
>> -- Adrien
>>
>> Le ven. 15 avr. 2016 à 18:05, Telmo Cardoso <telmo@gmail.com> a
>> écrit :
>>
> Hi,
>>>
>>> I checked out project from
>>> https://github.com/jenkinsci/cucumber-reports-plugin and I'm trying to
>>> generate hpi with command:
>>>
>>> mvn hpi:hpi
>>>
>>> I getting the error:
>>>
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 2.880 s
>>> [INFO] Finished at: 2016-04-15T15:07:56+01:00
>>> [INFO] Final Memory: 22M/220M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.jenkins-ci.tools:maven-hpi-plugin:1.117:hpi (default-cli) on project
>>> cucumber-reporting: Failed to determine Jenkins version this plugin depends
>>> on. -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:hpi (default-cli)
>>> on project cucumber-reporting: Failed to determine Jenkins version this
>>> plugin depends on.
>>>
>>> I have added dependency
>>>
>>> 
>>> org.jenkins-ci.main
>>> jenkins-war
>>> war
>>> 1.625.3
>>> 
>>>
>>>
>>> And I can see it downloaded on local maven repository
>>>
>>>
>>> Can anyone point me in the right direction?
>>>
>>>
>>> P.S. - If I create a new project from scratch I'm able to generate hpi file 
>>> or run it directly to jenkins.
>>>
>>>
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e27d78d4-a9dd-426e-ab85-2d7465018d4f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e27d78d4-a9dd-426e-ab85-2d7465018d4f%40googlegroups.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/f7c5e8d3-7c51-453f-b3f6-29f8813123a2%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/f7c5e8d3-7c51-453f-b3f6-29f8813123a2%40googlegroups.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/CAKwJSvzDKpY5KHB7Y-RNedpmN6BxGES5KOXsaBAPqRkxaY_GcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build failure when trying to generate hpi file [noob alert]

[Adrien Lecharpentier]

The version of Jenkins-core the plugin depends on is determine by the
parent-pom version:
https://github.com/jenkinsci/cucumber-reports-plugin/blob/master/pom.xml#L6

However, to generate the `hpi`, you should use the classic `mvn package`
rather than calling the `hpi` plugin.
-- Adrien

Le ven. 15 avr. 2016 à 18:05, Telmo Cardoso  a
écrit :

> Hi,
>
> I checked out project from
> https://github.com/jenkinsci/cucumber-reports-plugin and I'm trying to
> generate hpi with command:
>
> mvn hpi:hpi
>
> I getting the error:
>
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 2.880 s
> [INFO] Finished at: 2016-04-15T15:07:56+01:00
> [INFO] Final Memory: 22M/220M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.jenkins-ci.tools:maven-hpi-plugin:1.117:hpi (default-cli) on project
> cucumber-reporting: Failed to determine Jenkins version this plugin depends
> on. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:hpi (default-cli) on
> project cucumber-reporting: Failed to determine Jenkins version this plugin
> depends on.
>
> I have added dependency
>
> 
> org.jenkins-ci.main
> jenkins-war
> war
> 1.625.3
> 
>
>
> And I can see it downloaded on local maven repository
>
>
> Can anyone point me in the right direction?
>
>
> P.S. - If I create a new project from scratch I'm able to generate hpi file 
> or run it directly to jenkins.
>
>
>
> --
> 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/e27d78d4-a9dd-426e-ab85-2d7465018d4f%40googlegroups.com
> 
> .
> 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/CAKwJSvx6Lqxj-7jmufiJxD%2BnWdWqRgpDxHeb_h8kvKc1rw-3qQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Release not listed for download

[Adrien Lecharpentier]

Hello,

on https://github.com/jenkinsci/thin-backup-plugin/commits/master there is
no commits since 18days. How did you do the release?

-- Adrien

Le jeu. 3 mars 2016 à 17:05, Thomas Fürer  a
écrit :

> Hi,
>
> I have done a release of my plugin thinbackup the other day. On github
> it is marked as release as expected
> (https://github.com/jenkinsci/thin-backup-plugin). but in the
> updatecenter of jenkins it is not available. is there something I need
> to change in the release process?
>
> Thomas
>
> --
> 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/56D860D2.9070104%40googlemail.com
> .
> 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/CAKwJSvwFZ4RPMVFhP7gYvudxSxMW%2BFxCC%2BAFakjYdRPOVtJ86Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

s3-plugin

[Adrien Lecharpentier]

Hello,

I can see that in this s3 plugin, there is a lot of open PR. Maybe Michael
Watt might be overloaded on the subject. I'd like to offer my help to sort
the PR, merge and release the plugin.

For example, it is not possible for the moment to use it with copyartifact
more recent that 1.36. This makes the plugin unusable (JENKINS-32058 and
JENKINS-29582).

Also, it might need to refactoring to port the plugin to the latest Jenkins
version API (JENKINS-29533).

What do you think?
-- Adrien

-- 
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/CAKwJSvxfUFxWAWcPmWO3i3oxRJLMoe0QTWiA2kkC8QtrnfQSPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: s3-plugin

[Adrien Lecharpentier]

Baptiste,

yes if it can help having better plugins.
-- Adrien

Le jeu. 17 déc. 2015 à 16:35, Baptiste Mathus <m...@batmat.net> a écrit :

> Hi Adrien,
>
> Thanks for the proposal: the process is to ping the current maintainer(s)
> to get what they think.
> It's indeed up to each maintainer to provide approval (or consider the
> plugin unmaintained when no answer for some time).
>
> Not sure what should be done for plugins with PR, but w/o someone wanting
> to become maintainer in the general case.
>
> Do you want to become maintainer of that plugin if the current ones say
> they don't want to be anymore?
>
> Cheers
>
> 2015-12-17 13:44 GMT+01:00 Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com>:
>
>> Hello,
>>
>> I can see that in this s3 plugin, there is a lot of open PR. Maybe
>> Michael Watt might be overloaded on the subject. I'd like to offer my help
>> to sort the PR, merge and release the plugin.
>>
>> For example, it is not possible for the moment to use it with
>> copyartifact more recent that 1.36. This makes the plugin unusable
>> (JENKINS-32058 and JENKINS-29582).
>>
>> Also, it might need to refactoring to port the plugin to the latest
>> Jenkins version API (JENKINS-29533).
>>
>> What do you think?
>> -- Adrien
>>
> --
>> 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/CAKwJSvxfUFxWAWcPmWO3i3oxRJLMoe0QTWiA2kkC8QtrnfQSPg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvxfUFxWAWcPmWO3i3oxRJLMoe0QTWiA2kkC8QtrnfQSPg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> --
> 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/CANWgJS6Mh7Y9x84j8t6%2BrpeVeNQj%3DuDLRHE6S%2B23pvu_cvthCg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Mh7Y9x84j8t6%2BrpeVeNQj%3DuDLRHE6S%2B23pvu_cvthCg%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/CAKwJSvwk6kkSPQJdvzp0XNc_-hU21Xm_7SB8EotbXj5mKL3rxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices for integration of credentials in a plugin

[Adrien Lecharpentier]

Jean-Christophe,

so I would say use the Plain Credential plugin. A plain text password is
*never* the answer.

I agree that the field name can be vague, but we can discuss about it with
Jesse or create a quick PR.

-- Adrien

Le mar. 15 déc. 2015 à 14:58, jcsirot <jcsi...@gmail.com> a écrit :

> Hi Adrien,
>
> Well, there is no real issue with the Plain Credential Plugin but I find
> that the label "secret text" used by this plugin when creating a new
> credential entry is a little bit vague. Using a simple password field would
> also work but I prefer using a credential item in order to avoid password
> in plain text when the ansible plugin is used within a workflow job.
>
>
> Le lundi 14 décembre 2015 16:58:02 UTC+1, Adrien Lecharpentier a écrit :
>
>> Jean-Christophe,
>>
>> I would say using the Plain Credential Plugin if you only need a
>> "secured" field for the vault. What is the issue with it? Maybe it is
>> possible to improvement it?
>>
>> Best regards.
>>
>> Le lun. 14 déc. 2015 à 15:13, jcsirot <jcs...@gmail.com> a écrit :
>>
> Hello,
>>>
>>> I am working on the integration of the ansible vault feature (i.e.
>>> password protected configuration files) in the ansible plugin. I want to
>>> give the possibility to select the password from the credential plugin
>>> dropdown box. So I see 3 possibilities to do that :
>>>
>>> 1. Use the SSHUserPassword from the SSH Credential plugin. The username
>>> is then ignored. It works but I find this solution ugly.
>>>
>>> 2. Depend on a plugin which provides a password-only credential
>>> provider. For instance the Plain Credential plugin. But I think this
>>> provides a poor user experience.
>>>
>>> 3. Implement a dedicated credential provider in the Ansible plugin. This
>>> is probably the best solution regarding the user experience but it
>>> duplicates some code.
>>>
>>> Is there any solution I missed or is there some good practices to follow
>>> here.
>>>
>>> Thanks in advance for your feedback.
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.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/023fe378-f4fb-4e8c-b70a-f6870b971b10%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/023fe378-f4fb-4e8c-b70a-f6870b971b10%40googlegroups.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/CAKwJSvydr3-W2fWuNu%2BPGmMVfO6TvTkBWeruuE09MzBTG7PsTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Best practices for integration of credentials in a plugin

[Adrien Lecharpentier]

Jean-Christophe,

I would say using the Plain Credential Plugin if you only need a "secured"
field for the vault. What is the issue with it? Maybe it is possible to
improvement it?

Best regards.

Le lun. 14 déc. 2015 à 15:13, jcsirot  a écrit :

> Hello,
>
> I am working on the integration of the ansible vault feature (i.e.
> password protected configuration files) in the ansible plugin. I want to
> give the possibility to select the password from the credential plugin
> dropdown box. So I see 3 possibilities to do that :
>
> 1. Use the SSHUserPassword from the SSH Credential plugin. The username is
> then ignored. It works but I find this solution ugly.
>
> 2. Depend on a plugin which provides a password-only credential provider.
> For instance the Plain Credential plugin. But I think this provides a poor
> user experience.
>
> 3. Implement a dedicated credential provider in the Ansible plugin. This
> is probably the best solution regarding the user experience but it
> duplicates some code.
>
> Is there any solution I missed or is there some good practices to follow
> here.
>
> Thanks in advance for your feedback.
>
> --
> 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/524089f5-4005-4720-af20-9c7b0580e61f%40googlegroups.com
> 
> .
> 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/CAKwJSvzzhsTJRJz0SNt0gz0bHy_xamkdSsLLxYKaSHLVOiHhsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Variable substitution in Jenkins plugin

[Adrien Lecharpentier]

Hello,

You can also use the token macro plugin to do such things:
https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin

-- Adrien

Le dim. 31 mai 2015 20:29, Daniel Beck m...@beckweb.net a écrit :


 On 30.05.2015, at 17:41, p...@pholding.co.uk wrote:

  Does the Jenkins API provide a better solution that would allow my
 plugin to substitute a variable with a real value when the build job is
 executed?


 http://javadoc.jenkins-ci.org/hudson/EnvVars.html#expand%28java.lang.String%29

 --
 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/EA1537DF-CAEF-409F-8F07-36186DCB1535%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/CAKwJSvwH45bpTSrzHkba_Oi6Qy%2BM2SMx0t3CyotrnTH71h%2BfWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to programmatically get Jenkins Home from a plugin

[Adrien Lecharpentier]

Hello,

I think you can use `Jenkins.getInstance().getRootDir()` to get a
`java.io.File` of your JENKINS_HOME.

Best regards.
-- Adrien

Le mar. 12 mai 2015 à 06:50, Samith Dassanayake hisam...@gmail.com a
écrit :

 Hi all,
 I want to get Jenkins Home in my java code of the plugin. How can I access
 it?

 Thanks,
 Samith

 --
 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/d6f3a371-d3e8-45ac-9cdd-b307892fd3ae%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/d6f3a371-d3e8-45ac-9cdd-b307892fd3ae%40googlegroups.com?utm_medium=emailutm_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/CAKwJSvzHmLgGEfeemMT0-nqWLOgbMJcNyu%3D19BU2MCO9gy5BHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins plugin, only the old version shown in the update center

[Adrien Lecharpentier]

You can also add, in dependencyManagement, the maven-release-plugin in
version 2.5.1. That will do it to.

-- Adrien

Le mer. 6 mai 2015 à 08:27, Vincent Latombe vincent.lato...@gmail.com a
écrit :

 It's a known issue (too old maven-release-plugin, not compatible with
 recent gits), update your parent POM to 1.580 at least to get the fix.

 Vincent

 2015-05-06 2:45 GMT+02:00 Yuanbo Han yuanbo@gmail.com:

 Hi all,

 I'm using  mvn release:prepare release:perform to build and upload my
 jenkins plugin, it is successful when I first create my plugin and it
 appears in the update center (bearychat 1.0), but when I update it to 1.2
 or 1.3, it won't work, but my build process is successful. Can anyone help?

 attachments are 2 screen capture.


  --
 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/6cd128ce-ce1d-42b1-89e5-85e8709fd74d%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/6cd128ce-ce1d-42b1-89e5-85e8709fd74d%40googlegroups.com?utm_medium=emailutm_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/CAH-zGCjWo_N-_c2kWdFConpNy5FEKZXQv-hMzQzrByejveBUcg%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCjWo_N-_c2kWdFConpNy5FEKZXQv-hMzQzrByejveBUcg%40mail.gmail.com?utm_medium=emailutm_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/CAKwJSvzQ5xWhzzA1XrONyavS3R0ZnQPOpz7%3DNrsBjrJnuq1UoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

S3 plugin release

[Adrien Lecharpentier]

Hello,

I'd like to know if we could do a release of the plugin S3. The 0.7 version
has an issue about the link to download the managed artifact. The current
HEAD of the repository fixes that.

Is there any particular feature still in development that should be part of
the 0.8? Is so, maybe releasing a 0.7.1 with the download url fix should be
a good idea, what do you think?

Thanks in advance.

Best regards,
-- Adrien

-- 
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/CAKwJSvw7tB9mPuY--m4QaWkL0gL9%3D32P9YKDfFyn85qqDyRqWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Integration test against Jenkins

[Adrien Lecharpentier]

Hello,

I'm trying to contribute to a Jenkins client lib [1] but the integration
tests require a Jenkins instance on port 8080.
I'd like to change that to be able to run the integration tests against a
specific version of Jenkins.

For the moment, I managed to download Jenkins war (maven-dependency-plugin)
and unpack it in a specific directory. I tried maven-jetty-plugin to start
at pre-integration-test and stop it at post-integration-test but when
started, Jenkins doesn't let the integration-test processus go. I tried to
forked it or launch it as a daemon, but in those case, the integration-test
phase started before Jenkins to be up and ready.

My question is: how Jenkins injected tests are made so a Jenkins instance
is launch in parallel?

Thanks for your help,
Regards.

-- Adrien


[1]: https://github.com/RisingOak/jenkins-client

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Understanding extension point for plugin

[Adrien Lecharpentier]

Hi,

you should look at the Notifier class [1]. It's part of the post build
action that is responsible to interact with 3rd party tools.

Hope it helps,
-- Adrien

[1]: http://javadoc.jenkins-ci.org/?hudson/tasks/Notifier.html
Le 21 févr. 2014 16:29, Fabio Farronato fabio.farron...@lispa.it a
écrit :

  Hi all,
 I'm newbe on jenkins and in writing plugins. I have some trouble in
 understanding extension point.

 I have looked for in the wiki for an explanation of a job's workflow
 execution  without success.

 I have the need of notify to an external tool, calling an api, when a job
 start. I'm in trouble on choosing the extension point.

 Can anyone tell me where to look? or suggest me the extension point?

 Thanks in advance.


 --
 Fabio Farronato


   --
 You received this message because you are subscribed to the Google Groups
 Jenkins Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: NoClassDefFoundError: com/google/common/cache/CacheBuilder

[Adrien Lecharpentier]

(old topic but same issue, sorry)
Hi,

I have the same error with a new plugin, for which I wanted to use guava 
15.0. I understand you cannot embedded guava in core but maybe for the next 
jenkins' plugins parent pom we should use a dependencyManagement/ for 
both com.google.guava:guava and com.google.code.findbugs:jsr305.

If we do so, any IDE, developers could see that they are overriding the 
version for those dependencies.

Details: using maven 3.1.1 with org.jenkins-ci.plugins:plugin:1.509.4. My 
problem was that I couldn't test my plugin due to Guava API modification:

Results :
 Tests in error:
   
 org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyTestSuite(org.jvnet.hudson.test.junit.FailedTest):
  
 tried to access method 
 com.google.common.collect.MapMaker.makeComputingMap(Lcom/google/common/base/Function;)Ljava/util/concurrent/ConcurrentMap;
  
 from class com.google.inject.internal.Annotations$AnnotationChecker
   
 testCliSanity(org.jvnet.hudson.test.PluginAutomaticTestBuilder$CliSanityTest):
  
 Could not initialize class org.eclipse.sisu.wire.ParameterKeys


And using version 11.0.1 of guava and 1.3.9 of jsr305 fixed it.
 

Thanks.

Le mercredi 24 juillet 2013 11:46:59 UTC+2, David Mata Gorriz a écrit :

 You are right, as usual. Artifactory 2.1.6 depends on guava r08 and 
 jenkins depends on 1.0.1. 

  

 David Mata Górriz 
 Arquitectura Core Bancario 
 Carretera de Sierra Alhamilla S/N 
 Edificio Celulosa 2ª Planta Almería 
 950180360. Extensión: 12628 
 david...@tecnologia.cajamar.es javascript: 

 -Mensaje original- 
 De: jenkin...@googlegroups.com javascript: [mailto:
 jenkin...@googlegroups.com javascript:] En nombre de Kohsuke Kawaguchi 
 Enviado el: martes, 23 de julio de 2013 3:13 
 Para: jenkin...@googlegroups.com javascript: 
 CC: David Mata Gorriz 
 Asunto: Re: NoClassDefFoundError: com/google/common/cache/CacheBuilder 


 My guess is that your plugin depends on Guava directly or indirectly, 
 overwriting the version that Jenkins core uses. 

 Check mvn dependency:tree output and the path that leads to the guava. 

 On 07/18/2013 03:24 AM, David Mata Gorriz wrote: 
  Hi, everyone. 
  
  We have a plugin in our company to do some specific tasks. In the last 
  weeks, we had to add guava as a dependency to avoid 
  
  java.lang.NoClassDefFoundError: com/google/common/cache/CacheBuilder 
  
at hudson.model.Queue.init(Queue.java:188) 
  
at jenkins.model.Jenkins.init(Jenkins.java:764) 
  
at hudson.model.Hudson.init(Hudson.java:81) 
  
at 
  org.jvnet.hudson.test.HudsonTestCase.newHudson(HudsonTestCase.java:469) 
  
at 
  org.jvnet.hudson.test.HudsonTestCase.setUp(HudsonTestCase.java:312) 
  
at junit.framework.TestCase.runBare(TestCase.java:139) 
  
at 
  org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:290) 
  
at junit.framework.TestResult$1.protect(TestResult.java:122) 
  
  Do you know why is that? I think we shouldn't be required to do it. 
  
  Maybe I made a mistake, or some of the plugins I use (artifactory, 
  sonar, svn). 
  
  Thanks 
  
  
   
  AVISO DE CONFIDENCIALIDAD 
  Este correo electrónico y cualquier fichero con el transmitido son 
  confidenciales, contienen información privilegiada y son de conocimiento 
  y uso exclusivo de la persona o entidad a quienes han sido dirigidos. Su 
  contenido no puede ser modificado. En caso de recibir este mensaje por 
  error, le rogamos que informe de inmediato al remitente y proceda a 
  destruir dicho mensaje y cualquier copia que hubiese realizado. Como el 
  correo electrónico puede verse afectado por fallos técnicos u 
  operacionales, no se garantiza su recepción de forma adecuada y puede 
  estar sujeta a retrasos. Cualquier 
  comunicación que esté supeditada a una fecha u hora pactadas 
  previamente, también deberá ser enviada por correo convencional o fax. 
  El correo electrónico no garantiza la confidencialidad del contenido de 
  los mensajes. Si el destinatario de este mensaje tiene cualquier 
  objeción a la utilización de este medio, deberá ponerse en contacto de 
  inmediato con el remitente. Está estrictamente prohibido el uso, copia o 
  distribución por cualquier medio no autorizado de este mensaje y de 
  cualquier fichero en el contenido. 
  CONFIDENTIALITY WARNING 
  This e-mail and any files transmitted with it are confidential and 
  privileged, and are intented solely for the use of the individual or 
  entity to whom they are addressed. Their contents may not be altered. If 
  you are not the intended recipient of this communication please notify 
  the sender and delete and destroy all copies immediately. As e-mail can 
  be subject to operational or technical difficulties, the quality of 
  reception may be affected and it is subject to time delays. 

Re: [CPPTest] Compilation failed

[Adrien Lecharpentier]

Hello Olivier,

thanks for the reply. My problem wasn't about the compilation, but with
hpi:run. My bad for the ad explanation.

I made a pull-request this morning. The analysis-core and analysis-test,
via the analysis-pom, were using org.jvnet.hudson.main:maven-plugin:1.395
until the version 1.33 of the analysis-pom. I upgraded those versions to
remove this dependency and it works. I didn't upgrade to the latest as the
plugin is made to be built against jenkins 1.410.

Thanks!
-- Adrien


2013/8/9 Olivier Dagenais olivier.dagen...@gmail.com

 Bonjour Adrien,

 I just tried it and although I couldn't compile with JRE 1.7.0-11 (due to 
 java.lang.NoClassDefFoundError:
 com/sun/mirror/apt/AnnotationProcessorFactory, which I think is fixed in
 later versions of the parent project), I was able to build cpptest-plugin
 with JDK 1.6.39-x64.  This is with Maven 3.0.4 on Windows 7 SP1.

 I noticed that analysis-core version 1.50 was released less than a month
 ago, maybe you could try upgrading that?

 HTH,
 - Olivier

 On Thursday, August 8, 2013 12:12:16 PM UTC-4, Adrien Lecharpentier wrote:

 Hello,

 I'm trying to give an improvement to cpptest-plugin but I can't compiled
 it out of the box due to :

 Version of org.jvnet.hudson.main:maven-**plugin:jar:1.395 is
 inconsistent with org.jenkins-ci.main:maven-**plugin:jar:1.410


 I've tried maven 2.2.1 and 3.0.5 as well as jdk 1.6 and 1.7.

 From a `dependency:tree`, I saw that 
 `org.jvnet.hudson.plugins:**analysis-core:jar:1.21`
 try to use `org.jvnet.hudson.main:maven-**plugin:jar:1.395` and
 `org.jenkins-ci.main:maven-**plugin:jar:1.410`. Can't figure out how to
 fix it. Exclusions has no effect on this issue.

 Thanks for your help.

 --
 Adrien Lecharpentier

  --
 You received this message because you are subscribed to the Google Groups
 Jenkins Developers group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.






-- 
Adrien Lecharpentier

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[CPPTest] Compilation failed

[Adrien Lecharpentier]

Hello,

I'm trying to give an improvement to cpptest-plugin but I can't compiled it
out of the box due to :

 Version of org.jvnet.hudson.main:maven-plugin:jar:1.395 is inconsistent
 with org.jenkins-ci.main:maven-plugin:jar:1.410


I've tried maven 2.2.1 and 3.0.5 as well as jdk 1.6 and 1.7.

From a `dependency:tree`, I saw that
`org.jvnet.hudson.plugins:analysis-core:jar:1.21` try to use
`org.jvnet.hudson.main:maven-plugin:jar:1.395` and
`org.jenkins-ci.main:maven-plugin:jar:1.410`. Can't figure out how to fix
it. Exclusions has no effect on this issue.

Thanks for your help.

-- 
Adrien Lecharpentier

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.