Re: AppCenter Plugin up for adoption

l 2021 at 18:09:12 UTC+1 Mez Pahlan wrote: > Hi everyone > > Sadly I can no longer continue to maintain the AppCenter Plugin for > Jenkins. :(. In line with the guidance > <https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#how-can-i-mark-a-plugin-for-adoptio

AppCenter Plugin up for adoption

Hi everyone Sadly I can no longer continue to maintain the AppCenter Plugin for Jenkins. :(. In line with the guidance I am announcing this decision here. If anyone is interested

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

...@cloudbees.com wrote: > On Sat, Nov 7, 2020 at 4:35 PM Mez Pahlan wrote: > >> Without the mirrors section I was getting the following error: Could not >> find artifact org.jenkins-ci.tools:maven-hpi-plugin:pom in central ( >> https://repo.maven.apache.org/maven2). That plugin is clearl

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

t 18:55:21 UTC+1 db...@cloudbees.com wrote: > On Mon, Oct 12, 2020 at 7:19 PM Jesse Glick wrote: > >> On Mon, Oct 12, 2020 at 7:36 AM Mez Pahlan wrote: >> > I am still curious as to what I should be putting in my settings.xml >> >> You do not really need one at all, as all J

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

and that was years ago. On Monday, 12 October 2020 at 12:05:57 UTC+1 Mez Pahlan wrote: > Hi everyone > > I'm getting the following error whilst trying to build a PR branch from a > contributor. They've bumped the parent POM version and minimum supported > Jenkins version and tho

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

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

Re: Adopt / co-maintain AppCenter plugin

PM UTC+5:30, Mez Pahlan wrote: >> >> Brilliant! Thanks Nitin. I'll try and figure out how to add you as a >> maintainer. >> >> On Wednesday, 5 August 2020 at 16:00:11 UTC+1 snit...@gmail.com wrote: >> >>> Hello, Im interested. My github handle is sniti

Re: Adopt / co-maintain AppCenter plugin

Brilliant! Thanks Nitin. I'll try and figure out how to add you as a maintainer. On Wednesday, 5 August 2020 at 16:00:11 UTC+1 snit...@gmail.com wrote: > Hello, Im interested. My github handle is snitin315 ( > https://github.com/snitin315) -- You received this message because you are

Adopt / co-maintain AppCenter plugin

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

Re: Terminology Updates

Why not extend the butler analogy? Majordomo. Or MD for short? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com.

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

I'm glad I checked here first! Same thing happened to me. My user id is: mezpahlan I registered more than 3 months ago but I *have* changed my password in the last 3 months and don't remember the old one any more. Do I need to password reset? Thanks On Wednesday, 3 June 2020 16:30:10 UTC+1,

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

>though if your instructions do fix the issue then jenkins documentation is >incorrect: "Log in to Artifactory, and from your profile, obtain the encrypted >password." I've recently changed laptops and have had to re setup my environment and obtained the encrypted password correctly using

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

2020 20:31:17 UTC+1, Gavin Mogan wrote: > > Is it just those two PRs? - i don't know sorry > or any PRs in general? - did you enable the app or github actions? > > On Sat, May 16, 2020 at 9:07 AM Mez Pahlan > wrote: > >> Hi Jenkins Developers! >> >> Just a qui

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

Settings best practice > <https://support.cloudbees.com/hc/en-us/articles/204859670-Java-Heap-settings-best-practice> > and > the Maven manual <http://maven.apache.org/configure.html>): > > *export MAVEN_OPTS="-Xms4g -Xmx4g"* > > > On Sat

Allocate more memory to Jenkins whilst running hpi:run

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

Re: Lock JIRA issues

it's clearly abusive behavior, you could file an infra issue requesting > that the offending account be destroyed. > > (Note that Jira's keyboard shortcuts make it extremely easy to > accidentally perform certain actions like assign-to-self.) > > > On 31. Oct 2019, a

Lock JIRA issues

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

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

Many thanks Baptiste for picking this up. When you say provide a status check here do you mean to add your stack traces to this forum thread or to the INFRA ticket you linked to or something else? Cheers. On Thursday, 31 October 2019 10:28:42 UTC, Baptiste Mathus wrote: > > I filed

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

Thanks for the reply Oleg > I am sure it is a massive task maintaining the infra side of things and more contributors will hopefully help. We all *do* appreciate the hard work and my comments were mostly out of frustration last night. I tend to do my plugin development on the weekend so maybe

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

Am I doing something wrong here? I *constantly* get failures with ci.jenkins.io typically with agents not working when I expect them to. Not build failures with my plugin but infra issues before the plugin even gets built. Typically out of memory issues when the build doesn't even start. At

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

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

Re: Rechecking Pull Requests

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

Re: Proxy details

If you get an instance of Jenkins via Jenkins.get() then you have access to a field that contains the proxy details jenkins.proxy. If you access this object you should be able to get the details you need. On Thursday, 19 September 2019 07:13:06 UTC+1, selva vignesh wrote: > > Hi, > How to get

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

now everything works as I expect. Fantastic. Thanks for the help Jesse! And thanks everyone else too! On Wednesday, 11 September 2019 21:46:15 UTC+1, Jesse Glick wrote: > > On Wed, Sep 11, 2019 at 4:19 PM Mez Pahlan > wrote: > > I tried removing the following from my POM wh

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

s down the cause of the missing plugin. Unfortunately I need this included in some form or the other. Are there any special settings I can add to this to ensure that the dagger-compiler runs but doesn't break the packaging of the plugin? Thanks On Wednesday, 11 September 2019 20:54:01 UTC+1, Mez

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

oticed you had several items > marked as test scope in the pom.xml. > > On Wed, Sep 11, 2019, 12:17 Mez Pahlan > > wrote: > >> Thanks for the answers Jesse! >> >> > Try specifically: mvn clean hpi:run >> >> Same issue. Builds fine no obvious erro

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

like, are handled at > compile time? > > On Wed, Sep 11, 2019 at 2:17 PM Mez Pahlan > wrote: > > > > Thanks for the answers Jesse! > > > > > Try specifically: mvn clean hpi:run > > > > Same issue. Builds fine no obvious errors in the termina

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

happy to be corrected on this). Any further tips on attempting to track down the cause of this? On Wednesday, 11 September 2019 14:38:04 UTC+1, Jesse Glick wrote: > > On Wed, Sep 11, 2019 at 3:20 AM Mez Pahlan > wrote: > > I've looked at the local work directory in my IDE that is cr

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

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

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

Thanks Gavin, great explanation and insight. I'm likely worrying about nothing. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

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

Hi again. I'm probably worrying about nothing but this looked strange to me. https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fappcenter-plugin/activity/ During a release:prepare release:perform maven will request two builds from the CI server due to two commits to master. The first

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

Thanks both. Great suggestions. I'll give them a go. On Monday, 8 July 2019 17:57:51 UTC+1, Jesse Glick wrote: > > On Sat, Jul 6, 2019 at 9:32 AM Mez Pahlan > > wrote: > > 1. hpi:run > > 2. Configure Jeknins -> Manage Nodes -> Add additional slave > > 3. Do

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

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

Testing a master-slave setup when developing a plugin

Hi everyone! Whilst developing a plugin I find it really useful to be able to run hpi:run and quickly get an instance of Jenkins with my plugin that I can test. However this only creates a single Master setup. Is there a better / easier way to quickly get a master-slave setup so I can test how

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

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

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

A lot of those points resonated with me. I started using Jenkins (well Hudson) years ago to simplify manual builds and quickly discovered the power it brings. This was really exciting. I am a mobile developer and I also maintain a plugin on Jenkins. All the issues I had to struggle with

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

> The plain text tokens are already potentially compromised and need to > be regenerated and stored encrypted anyways. This is specific to each > plugin on how to go about regenerating keys and whatnot. > Yes, when you put it like that it makes more sense not to worry about migration. Thank you

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

> > There is not any good way that I know of. I would just ignore it. > I could ignore it, for sure. But that was the reason I received a security bug that I'm looking to fix. That the tokens in my plugin were being stored in plain text. If I leave them in plain text what am I actually fixing?

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

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

Re: How to safely upgrade the minimum Jenkins version

Thanks James Version 3.11 is a weird one. It always existed on the stats before I joined the project and to be best of my knowledge it isn't a plugin version we've released. No idea how it got onto the stats page. I think I am reading the stats incorrectly, thanks for the sense check. In that

How to safely upgrade the minimum Jenkins version

I'm looking to bump the minimum version of Jenkins for the plugin I maintain. Currently it is 1.625.3 which is a really old version of Jenkins. I want to move over to the 2.x line but was wondering what sort of strategy people recommend? I've checked out the stats for my plugin

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

8 at 3:20 PM Mez Pahlan > wrote: > > Notice that the parent POM has a Java level set to 8 so I remove my java > version tag from my POM > > You must be using an old version of the parent POM. All recent > versions treat `java.level` as mandatory (no default). > > >

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

Hello all As it says in the title. I'm working with a PR for the HockeyApp Plugin and after making some changes I dutifully run all tests locally using the verify maven goal before I push changes to the PR. All checks pass I'm happy, computer is happy, I push. BAM! it fails on the Jenkins CI

Re: Wiki plugin labels

That's perfect thank you. PR filed. :) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion

Wiki plugin labels

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

Maintaining a dormant plugin

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

Re: Request to become a maintainer for hockeyapp

> P.S: would also appreciate a merge of > https://github.com/jenkinsci/hockeyapp-plugin/pull/45 > > > On Wednesday, May 23, 2018 at 8:59:53 AM UTC+2, Mez Pahlan wrote: >> >> Morning all >> >> It has been two weeks since the request. Can we kick off the proc

Re: Request to become a maintainer for hockeyapp

Morning all It has been two weeks since the request. Can we kick off the process for me to join the maintenance team for the HockeyApp plugin please? Thank you. Mez -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Request to become a maintainer for hockeyapp

Hi everyone I would like to formally request to become a maintainer for the hockeyapp plugin, please. I have started a PR and a thread discussion detailing why and

Re: HockeyApp plugin maintainers

May 2018 09:43:19 UTC+1, Oleg Nenashev wrote: > > Responded to the PR. > IIUC we have 4 days before the response timeout, right? > > On Tue, May 1, 2018 at 8:43 AM, Mez Pahlan <mez.p...@gmail.com > > wrote: > >> Trying one last time to reach the existing plugin m

Re: HockeyApp plugin maintainers

Trying one last time to reach the existing plugin maintainers. Hello could you review this thread please and give me your thoughts on the existing PRs please. Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: HockeyApp plugin maintainers

). Automated notifications are too easy to > miss. > > > On 18. Apr 2018, at 08:24, Mez Pahlan <mez.pah...@gmail.com> wrote: > > > > Thank you, you've been great! I'll wait for a reply on Github for two > weeks and then kick off the explicit request after that. Ho

Re: HockeyApp plugin maintainers

response earlier. > > Hopefully it helps, > Oleg > > > On Tuesday, April 17, 2018 at 9:53:35 PM UTC+2, Mez Pahlan wrote: >> >> Hello Jenkins Devs! >> >> I'm interested in contributing to the HockeyApp >> <https://www.google.com/url?q=https%3A%

HockeyApp plugin maintainers

Hello Jenkins Devs! I'm interested in contributing to the HockeyApp plugin and want to reach out to the plugin maintainers to see if they can help resolve some PRs. My immediate interest is in the PR#48