Re: New plugin

Thanks for all those suggestions. I will apply them and will return to you for further guidance. piątek, 22 marca 2024 o 11:53:49 UTC+1 db...@cloudbees.com napisał(a): > On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote: > >> My work environment requires from me to give users privileges to create

Re: New plugin

On Fri, Mar 22, 2024 at 11:12 AM DuMaM wrote: > My work environment requires from me to give users privileges to create > new jobs, but I need to lock creation of non pipeline jobs. > I could take a solution proposed a long time ago by Daniel Beck, but I > fought that maybe it's a good place for

RE: New plugin

On Behalf Of DuMaM Sent: Freitag, 22. März 2024 11:12 To: Jenkins Developers Subject: New plugin You don't often get email from nowak.bartos...@gmail.com<mailto:nowak.bartos...@gmail.com>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi, I'm look

New plugin

Hi, I'm looking for some answers to questions which pop out during plugin development. https://github.com/DuMaM/lock-project-plugin My work environment requires from me to give users privileges to create new jobs, but I need to lock creation of non pipeline jobs. I could take a solution

Re: Error in Javadoc when attempting to publish a new plugin version

Hi Basil! Great, thanks, I will try that  -- Stéphane Le mar. 5 mars 2024 à 18:09, Basil Crow a écrit : > You can reproduce locally by running mvn clean verify -Pjenkins-release > and on CI by enabling incrementals > . >

Re: Error in Javadoc when attempting to publish a new plugin version

You can reproduce locally by running mvn clean verify -Pjenkins-release and on CI by enabling incrementals . Be sure to use the same version of Java you intend to use when doing the release, as different Java versions produce

Error in Javadoc when attempting to publish a new plugin version

Hi all! Sorry, it is probably a newbie question. I was just attempting to publish a new version of my plugin (mvn release:prepare release:perform) and I got plenty of errors in the Javadoc I recently added in my code. I didn't have these errors while building and testing (mvn clean install).

Re: New plugin - Support for Azure credentials via the Kubernetes Credentials Provider

ci/kubernetes-credentials-provider-plugin/pull/94#issuecomment-1867550472>, >> >> this is best supported by a separate plugin. >> >> >> >> Can’t find any existing support for this. I therefore believe the best >> way forward are to implement a new plu

Re: New plugin - Support for Azure credentials via the Kubernetes Credentials Provider

> this is best supported by a separate plugin. > > > > Can’t find any existing support for this. I therefore believe the best way > forward are to implement a new plugin to handle this – just as is the case > with for example > https://plugins.jenkins.io/bitbucket-kubernet

New plugin - Support for Azure credentials via the Kubernetes Credentials Provider

the managed identity, but as indicated here<https://github.com/jenkinsci/kubernetes-credentials-provider-plugin/pull/94#issuecomment-1867550472>, this is best supported by a separate plugin. Can't find any existing support for this. I therefore believe the best way forward are to impl

Re: New Plugin version not updated on Jenkins IO Plugin page

OK. Thanks! On Thursday, July 13, 2023 at 12:07:48 AM UTC-4 Mark Waite wrote: > On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote: > > Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have > send you the previous email. It is all set now. > > Just for

Re: New Plugin version not updated on Jenkins IO Plugin page

On Wednesday, July 12, 2023 at 10:04:55 PM UTC-6 Ricardo DeLemos wrote: Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now. Just for reference on the next update: the 1.2.0 version took over 6hr to show up on

Re: New Plugin version not updated on Jenkins IO Plugin page

Yes. The 2 versions (1.2.0 and 1.2.1) showed up 15 minutes after I have send you the previous email. It is all set now. Just for reference on the next update: the 1.2.0 version took over 6hr to show up on https://plugins.jenkins.io/, while 1.2.1 showed up after 1 hr. It is just the time that

Re: New Plugin version not updated on Jenkins IO Plugin page

On Wednesday, July 12, 2023 at 8:57:48 PM UTC-6 Ricardo DeLemos wrote: Hi Mark, I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/

Re: New Plugin version not updated on Jenkins IO Plugin page

Hi Mark, I have created a new release (1.20) following your recommendation, but I still do not see the new release in https://plugins.jenkins.io/crowdstrike-security/releases/ . I have created a version 1.2.0, which I see on

Re: New Plugin version not updated on Jenkins IO Plugin page

The 1.1.0 release is not available on repo.jenkins-ci.org. https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/crowdstrike-security/ shows a 1.0.0 release that was delivered in 2022. Since a tag has been created in the repository, I recommend that you declare the 1.1.0

New Plugin version not updated on Jenkins IO Plugin page

Hello, I have released a new version of the plugin in GitHub (https://github.com/jenkinsci/crowdstrike-security-plugin) and I can see the new release there, but after waiting more than 6hr, I could not see the new release version in https://plugins.jenkins.io/crowdstrike-security/releases/

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

ent Jenkins core > baseline and an ancient plugin Bill of Materials (BOM), which does not > speak to the viability of the gradle-jpi-plugin toolchain. > > In general the gradle-jpi-plugin toolchain needs to be at feature > parity with the maven-hpi-plugin toolchain before we could accept

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

core baseline and an ancient plugin Bill of Materials (BOM), which does not speak to the viability of the gradle-jpi-plugin toolchain. In general the gradle-jpi-plugin toolchain needs to be at feature parity with the maven-hpi-plugin toolchain before we could accept new plugin hosting requests

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

On Thursday, May 25, 2023 at 9:07:41 AM UTC-6 at...@gradle.com wrote: Thanks for the quick answer! On Thursday, May 25, 2023 at 3:16:30 PM UTC+2 Mark Waite wrote: On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for

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

Thanks for the quick answer! On Thursday, May 25, 2023 at 3:16:30 PM UTC+2 Mark Waite wrote: On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see

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

On Thursday, May 25, 2023 at 6:09:42 AM UTC-6 you wrote: Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see https://github.com/jenkinsci/gradle-jpi-plugin/issues/213 for more details Thanks for doing that. The latest JPI plugin release 0.49.0

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

Hi, lately I've been working on improving the Gradle support for building Jenkins plugins, see https://github.com/jenkinsci/gradle-jpi-plugin/issues/213 for more details The latest JPI plugin release 0.49.0 and recent changes on the pipeline-library

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

On Mon, Mar 27, 2023 at 7:27 AM 'Herve Le Meur' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > For those using buildPluginWithGradle() from the shared pipeline library, we could add a note about it in the logs. This was done in jenkins-infra/pipeline-library#629

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

For those using buildPluginWithGradle() from the shared pipeline library, we could add a note about it in the logs. On Wed, Mar 22, 2023 at 6:38 PM Basil Crow wrote: > Here are the most popular plugins still using Gradle for their build: > > gradle 232,746 > multiple-scms 22,241 >

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

Here are the most popular plugins still using Gradle for their build: gradle 232,746 multiple-scms 22,241 allure-jenkins-plugin 17,121 terraform 5,046 checkmarx 4,502 jira-trigger 3,996 blackduck-detect 2,838 npm-yarn-wrapper-steps 2,152 ez-templates 2,145 templating-engine 1,742

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

On Fri, Dec 16, 2022 at 7:43 PM sghil...@gmail.com wrote: > > Last I checked, generated poms were also invalid, which is a problem for > any consumers of these artifacts that do more than just download the hpi. > > I believe this was fixed in 2019 as v0.31.0 >

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

Hi all, I've been maintaining the gradle-jpi-plugin for the last several years. I'm in support of this decision. My most recent OSS plugin used maven as well to take advantage of the excellent tooling the community has put together. I elaborated a bit more on the mentioned issues in the

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

I submitted a dedicated issue on the plugin's repository outlining the TODOs and linking to this discussion. On Thursday, 8 December 2022 at 21:53:36 UTC+1 db...@cloudbees.com wrote: > On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes

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

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > 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. > … > I would be ready to lift this restriction again if the

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

t; >>> +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

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

+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 M

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

+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&quo

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

+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

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

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.

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

On Wed, Dec 7, 2022 at 11:20 AM Alexander Brandes wrote: > 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. > Last I checked, generated poms were also invalid, which is

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

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 <https://github.com/jenkinsci/ivy-plugin/pull/49> for example. For the reasons stated, I would like to propose, th

Re: Releasing a new plugin fails due to 'Check interesting categories' failure

Can you let us know what you did to resolve the issue? I am facing the same problem. Thanks, Karl On Tuesday, July 19, 2022 at 8:48:32 AM UTC-5 jgl...@cloudbees.com wrote: > https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/releases > seems to be working now? > -- You received

Re: Releasing a new plugin fails due to 'Check interesting categories' failure

https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/releases seems to be working now? -- 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: Releasing a new plugin fails due to 'Check interesting categories' failure

gh api /repos/jenkinsci/bmc-change-manager-imstm-plugin/releases 10++ jq -e -r '.[] | select(.draft == true and .name == "next") | .body' 11++ egrep '[⚠]|:(boom|tada|construction_worker):' Seems like it gets "releases" for the plugin, looks for a draft named "next" and then checks for any

Releasing a new plugin fails due to 'Check interesting categories' failure

https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/runs/7396269153?check_suite_focus=true Though I added *an appropriate category label* ( enhancement) to the PR before merging.https://github.com/jenkinsci/bmc-change-manager-imstm-plugin/pull/2 Please advise how to proceed. Thanks,

Re: New plugin for showing dynamic header across Jenkins

Hey Gavin, Thanks for sharing your thoughts. *Easier than the existing system notice box? What does dynamic mean in this case* - I felt the existing system notice box content gets unnoticed and my way of showing the header at the top has more visibility. - By dynamic I mean we can have the

Re: New plugin for showing dynamic header across Jenkins

- Header content will be dynamic and easy to update for administrators. Easier than the existing system notice box? What does dynamic mean in this case [image: image.png] - Header content will have an expiry date and post expiry it would not be shown. I could potentially see that

Re: New Plugin With Multiple Components Hosting Question

On Thu, Jun 30, 2022 at 8:55 PM Mark Diesburg wrote: > We could submit just the source for the test-management plugin portion > with reference to the other two components on GitHub since they can be used > independently for other purposes. > > Would this be acceptable? > > Or would we have to

Re: New Plugin With Multiple Components Hosting Question

Hi All libraries used in a plugin must be published publicly, open source approved license, and to an artifact repository that anyone can pull from normally either maven central or Jenkins repository. Basically we can host it or you can push it to maven central if it makes sense outside of

New Plugin With Multiple Components Hosting Question

We will be submitting a new Jenkins plugin very shortly to integrate Jenkins into one of our products. Before pushing the plugin source to GitHub and starting the process we have a question on what should be submitted to the jenkinsci for hosting Our Jenkins plugin is comprised of three

Re: Submission process of a new plugin

The pattern I saw was that both GitHub and Bitbucket had separate plugins for Kubernetes Credential Provider so I assumed it has to be a separate plugin. I am also not aware how optional dependencies are managed and what impact it would have on the Gitea plugin if we add this functionality

Re: Submission process of a new plugin

Is it worth submitting a PR to add the functionality to the gitea plugin? its an optional dependency on the kubernetes secrets plugin anyways. On Tue, Apr 5, 2022 at 12:29 PM Qasim Mehmood wrote: > > Hi Alexander, > > Thank you for pointing me to the right direction. I have create the hosting >

Re: Submission process of a new plugin

Hi Alexander, Thank you for pointing me to the right direction. I have create the hosting request issue . > Though I'm unsure if there's a guideline how to deal with forks of existing > plugins on the jenkinsci

Re: Submission process of a new plugin

Heyo, there is this guide that outlines how to open a hosting request alongside the general information for publishing plugins . Though I'm unsure if there's a guideline how

Submission process of a new plugin

Hi, I have written a plugin for creating a Gitea Personal Access Token Credential from a Kubernetes Secret. I am not a Java developer so I forked a similar plugin for creating a Github App credential and basically brute

Re: Not able to release new plugin changes

You need to reset the credentials. See https://groups.google.com/g/jenkinsci-dev/c/1-46eS41y6I and Details: https://www.jenkins.io/blog/2021/09/04/wiki-attacked/ nikhil...@gmail.com schrieb am Montag, 13. September 2021 um 09:43:33 UTC+2: > Hi , > > I am from MathWorks official CI team we

Not able to release new plugin changes

Hi , I am from MathWorks official CI team we are trying to release of new pluing changes for MATLAB however we see the Jenkins artifact repo user name and password stopped working suddenly our orgs official user name registered with Jenkins is *mathworks_ci_team * Please let me know if we

Re: Issues releasing new plugin

This seems to be solved? https://github.com/jenkins-infra/repository-permissions-updater/pull/1679 > Am 30.09.2020 um 14:22 schrieb Pontus Rydin : > > Hi fellow Jenkins coders! > > I just finished up a plugin for VMware vRealize Automation and got permission > to push it to Artifactory.

Issues releasing new plugin

Hi fellow Jenkins coders! I just finished up a plugin for VMware vRealize Automation and got permission to push it to Artifactory. However, I'm getting a 403 error while pushing the POM, but the HPI seems to go through. I have an approved write access request here:

Re: Add New plugin request: kubesphere-token-auth-plugin

On Sun, Jun 14, 2020 at 11:52 PM SW C wrote: > In the upcoming 3.0，oauth authority authentication is realized. The > plugins of kubesphere-token-auth-plugin will complete the docking with oauth. I know nothing about Kubesphere but offhand it sounds like this could be a PR to

Re: Add New plugin request: kubesphere-token-auth-plugin

dy have an account you'll have to wait for infra issues > to be over. > > Gavin > > On Sun., Jun. 14, 2020, 8:52 p.m. SW C, > > wrote: > >> Hi，I need to create a new plugin repository >> >> >> id: kubesphere-token-auth-plugin >> >> in

Re: Add New plugin request: kubesphere-token-auth-plugin

https://www.jenkins.io/doc/developer/publishing/requesting-hosting/ You need to make an HOSTING ticket to get it processed. If you don't already have an account you'll have to wait for infra issues to be over. Gavin On Sun., Jun. 14, 2020, 8:52 p.m. SW C, wrote: > Hi，I need to create a

Add New plugin request: kubesphere-token-auth-plugin

Hi，I need to create a new plugin repository id: kubesphere-token-auth-plugin introduction: https://github.com/kubesphere is a Kubernetes platform tailored to the DevOps teams. DevOps uses Jenkins as its engine. In the upcoming 3.0，oauth authority authentication is realized

Re: regarding issues publishing new plugin, but publishing works when publishing a snapshot

io/jenkins/plugin io/jenkins/plugins > On 23. May 2020, at 02:26, john rowley wrote: > > -- 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: regarding issues publishing new plugin, but publishing works when publishing a snapshot

According to https://www.jenkins.io/doc/developer/publishing/releasing/ 403 means the permissions are not setup. It's possible you just need to wait a little bit and try again. On Fri, May 22, 2020, 18:15 john rowley wrote: > Hello, > > > > I recently went through the process of developing a

regarding issues publishing new plugin, but publishing works when publishing a snapshot

Hello, I recently went through the process of developing a Jenkins plugin, getting it hosted, getting permissions for publishing to artifactory, etc. Everything was working correctly until I attempted to release the plugin. I was able to release a snapshot of the plugin, and this

Re: I'm working on a new plugin and when I try to run it I get the following error

Adopt OpenJDK is widely used in the Jenkins project. You're also welcome to use other OpenJDK implementations. Licensing restrictions on recent Oracle JDK 8 versions have made it very rarely used in the Jenkins project. On Mon, Feb 24, 2020 at 11:38 AM Daniel Anechitoaie wrote: > Will do. Is

Re: I'm working on a new plugin and when I try to run it I get the following error

Will do. Is OpenJDK ok? Or i need Oracle JDK? On Monday, February 24, 2020 at 8:35:39 PM UTC+2, Jesse Glick wrote: > > On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie > > wrote: > > I'm compiling on OpenJDK 11. > > Best to use JDK 8 for all purposes related to Jenkins. > -- You received

Re: I'm working on a new plugin and when I try to run it I get the following error

On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie wrote: > I'm compiling on OpenJDK 11. Best to use JDK 8 for all purposes related to Jenkins. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: I'm working on a new plugin and when I try to run it I get the following error

Yes, that was it. I'm compiling on OpenJDK 11. Using 2.164.1 works now even with parent POM 3.56 Thank you. On Monday, February 24, 2020 at 6:30:39 PM UTC+2, Mark Waite wrote: > > > > On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie > wrote: > >> Hmm, yeah, I had a small brainfart. For some

Re: I'm working on a new plugin and when I try to run it I get the following error

On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie wrote: > Hmm, yeah, I had a small brainfart. For some reason I was thinking in > decimal and was seeing 3.6 as 3.60 which in my mind was more recent than > 3.56 (which is the latest 3.x version)/ > > So now with > > > org.jenkins-ci.plugins

Re: I'm working on a new plugin and when I try to run it I get the following error

Hmm, yeah, I had a small brainfart. For some reason I was thinking in decimal and was seeing 3.6 as 3.60 which in my mind was more recent than 3.56 (which is the latest 3.x version)/ So now with org.jenkins-ci.plugins plugin 3.56 And 1.8 8 2.121.1 I

Re: I'm working on a new plugin and when I try to run it I get the following error

On Mon, Feb 24, 2020 at 10:29 AM Daniel Anechitoaie wrote: > > org.jenkins-ci.plugins > plugin > 3.6 This is very old. Try using the latest 3.x, and for the newer LTS line you may need to use a 4.0 beta. -- You received this message because you are subscribed to

I'm working on a new plugin and when I try to run it I get the following error

Hi, I just started working on a new plugin and when I run mvn hpi:run I get the following error: Failed while enforcing RequireUpperBoundDeps. The error(s) are [ Require upper bound dependencies error for org.slf4j:jcl-over-slf4j:1.7.25 paths to dependency are: +-io.jenkins.plugins:my-plugin

Re: New plugin: global-pre-script-plugin

You need to make a HOSTING jira ticket - https://jenkins.io/doc/developer/publishing/requesting-hosting/ On Sat, Feb 1, 2020 at 1:53 PM Orekaria N wrote: > Hello > > > I have created a plugin that may interest > youhttps://github.com/Orekaria/global-pre-script-plugin > > Please, let me know if

New plugin: global-pre-script-plugin

Hello I have created a plugin that may interest you https://github.com/Orekaria/global-pre-script-plugin Please, let me know if it can be added to official repositories / list of missing requirements jenkins id: orekaria Regards -- You received this message because you are subscribed to

Do not use the new plugin-pom with the BOM profile.

Hi all, There are issues using the jenkins-bom for dependency versioning in the plugin pom. Whilst it works for a single plugin, any plugins that are deployed using this also force any plugins that depend on them to enable the profile (as it can not be enabled per module). likewise the other

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

> On 7. Sep 2019, at 03:52, Jesse Glick wrote: > > I tried this, but it does not do what I need: it just sends, say, a > daily list of all issues matching that filter. To replace the > notification function of default assignee, I would want something that > only send me _changes_ in issues

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

On Thu, Sep 5, 2019 at 7:01 PM Oleg Nenashev wrote: > create a filter (or to use a public one), go to "Details" and then to > subscribe to notifications there. I tried this, but it does not do what I need: it just sends, say, a daily list of all issues matching that filter. To replace the

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Filterers can be saved and shared, and so a default search could be setup with https://confluence.atlassian.com/jira063/advanced-searching-functions-683542527.html#AdvancedSearchingFunctions-componentsLeadByUser() and then any custom requirements could be forked and tweaked per user. On Fri.,

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

I totally agree with the general opinion that an issue should only be assigned to someone if that person is effectively ready to work on it otherwise it just bring confusion about either the assignee will effectively works on it or not. And I also understand that people use default assignee to

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

My first thought was that I would like to keep the default assignee - but after reading all the comments, I have to agree, that my only reason for this is so that I get notified by new issues. Although Oleg shoed it is possible to create a filter and get notified about this things, It seems

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Making it an optional field in the HOSTING report seems to be a good compromise, so +1 from me for such a change. (I understand that developers do not want to be assignee for issues they are never going to fix. On the other hands, for a user that reports an issue it is somewhat disappointing

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

On Thu, Sep 5, 2019 at 2:36 PM Gavin wrote: > Does jira have a concept of auto watch like GitHub does? So an issue could > still notify people but not be claimed? Good question. That would be very useful. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

Does jira have a concept of auto watch like GitHub does? So an issue could still notify people but not be claimed? On Thu., Sep. 5, 2019, 11:35 a.m. Matt Sicker, wrote: > That makes tons of sense to me. You should only assign tickets to > yourself that you're currently working on or at least

Re: [DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

That makes tons of sense to me. You should only assign tickets to yourself that you're currently working on or at least intend to work on in the near future. On Thu, Sep 5, 2019 at 4:31 AM Baptiste Mathus wrote: > > I fully agree with Jesse's take. IMO for most plugins where the maintainer is >

[DISCUSS] Default assignee on new plugin JIRA issues (was: Re: Request to be made maintainer of ant-plugin)

I fully agree with Jesse's take. IMO for most plugins where the maintainer is not going to have time to jump on new reports right away, this sends a wrong message that issues will be analyzed and fixed by the assignee. This sends a second bad message: that an issue being already assigned, this is

Re: new plugin/option to deploy on staging

Thanks Oleg I will test those. best regards Reinaldo El jueves, 22 de agosto de 2019, 16:00:43 (UTC-5), Oleg Nenashev escribió: > > Hi, > > These page is being controlled by summary.jelly/groovy pages in Actions > which you can attach to the build. > > One of examples (maybe abit too heavy,

Re: new plugin/option to deploy on staging

Hi, These page is being controlled by summary.jelly/groovy pages in Actions which you can attach to the build. One of examples (maybe abit too heavy, but you can get an idea there): -

Re: How to introduce new plugin variable with default value without breaking compatibility

On Tue, Jul 30, 2019 at 10:03 AM 'Robin Jansohn' via Jenkins Developers wrote: > Can this sort of problem be avoided/fixed? You can replace uses of `path` with a getter returning `path != null ? path : "/manager/text"`. Or you can add a private Object readResolve() { if (path == null) {

How to introduce new plugin variable with default value without breaking compatibility

://github.com/jenkinsci/deploy-plugin/commit/db254d7c8c70214c7da91308c50bedb25fbf4eb8#diff-b2a541c8af2e6626b795634cc9d7143dR48 The problem is that this caused a breaking change for users using the new plugin with their existing freestyle jobs: https://issues.jenkins-ci.org/browse/JENKINS-58667

Planning for contributing a New Plugin for Discarding Builds

d problems here <https://docs.google.com/document/d/15LWsnNyZU2eDG56Zl4HW1_fgUSxuazujBypfAGVLrz8/edit#> suggested by Martin D'Anjou and where improvement is needed. So I am planning to make a new plugin which includes solution to some of the problems. I had made my GSoC Proposal <http

Re: filtering on io.jenkins does not find any archetype causing inability to create a new plugin

018, at 22:29, Bassam Khouri wrote: > > Hi, > > I'm a complete newbie to Jenkins plugin development, and I'm attempting to > create a new plugin. I'm following the instructions here: > > https://jenkins.io/doc/developer/tutorial/prepare/ > > I have the following jav

filtering on io.jenkins does not find any archetype causing inability to create a new plugin

Hi, I'm a complete newbie to Jenkins plugin development, and I'm attempting to create a new plugin. I'm following the instructions here: https://jenkins.io/doc/developer/tutorial/prepare/ I have the following java and maven versions installed $ java -version java version "1.8.0_144&q

Re: propose a new plugin

You can follow the process outlined here: https://jenkins.io/doc/developer/publishing/requesting-hosting/ On Mon, Oct 29, 2018 at 6:48 AM wrote: > During the DW|JW in Nice, I half-heard someone talk about proposing a new > plugin. > Also, during the conference I got Daniel Beck to qui

propose a new plugin

During the DW|JW in Nice, I half-heard someone talk about proposing a new plugin. Also, during the conference I got Daniel Beck to quickly hack together a prototype of a plugin we have the need for. https://github.com/daniel-beck/quiet-down-endpoint-plugin After a bit of tweaking

Re: New Plugin - Dependency-Track

Hi Steve, Please see https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins for information on how to get a plugin hosted. Regards, Alex On Wed, Sep 12, 2018 at 4:36 PM Steve Springett wrote: > Hello, > > I’m the author of a few Jenkins plugins and I’m working on another. > > The plugin is

New Plugin - Dependency-Track

Hello, I’m the author of a few Jenkins plugins and I’m working on another. The plugin is for Dependency-Track, an open source platform that allows organizations to track the use of third-party and open source components, determine if they are out-of-date, or have publicly disclosed

Re: New plugin developer: A View Plugin

On Fri, Apr 20, 2018 at 2:27 PM, Sverre Moe wrote: > This made me suspect that I was using OpenJDK and Java 9. Oh, well Jenkins does not run on Java 9. At all. So there is that. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: New plugin developer: A View Plugin

target/surefire-reports/TEST-InjectedTest.xml WARNING: Failed to instantiate Key[type=org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error

Re: New plugin developer: A View Plugin

On Wed, Apr 18, 2018 at 5:18 PM, Sverre Moe wrote: > What kind of test is this? There is nothing in my newly created project. The Jenkins plugin build harness generates a synthetic test to verify basic sanity aspects of your plugin. I am not sure what specifically the

New plugin developer: A View Plugin

Let me begin starting with I have never written a plugin to Jenkins before. I have plenty of insight into the Jenkins API for Groovy scripting in script console and scripting Pipeline scripts. I am a Java developer for over 10 years (API/Spring, Swing/JavaFX), and have been using Jenkins for

Re: Start in creating a new plugin

Thanks alot now i want to debugs the hello world plugin to jenkins using eclipse i run this command as in documentation mvnDebug hpi:run this error message appear in the command line Listening for transport dt_socket at address: 8000 Debugger failed to attach: handshake failed - received >GET /

Re: Start in creating a new plugin

If you haven't executed maven before, then the .m2 directory probably won't exist. You can create the .m2 directory in the %USERPROFILE% directory, %USERPROFILE% is a variable, you can put it into Windows Explorer or the command line and it will resolve to the correct location (e.g., in the

  1   2   3   4   5   6   7   8   9   10   >