Atlantis is pretty liberal giving away accounts for open source, so I don't know for crowd specifically, but you can probably just ask for one.
> I also need a place where we can store such data. Does jenkins devs have any > shared vault? In general plugin authors have managed their own test environments. Jenkins project does have a sponsored 1password account, but we (board? infra?) never really decided on how things should be managed. We have a jenkins governance meeting this week, so it might be worth discussing it. Gavin On Mon, Apr 4, 2022 at 4:47 PM DuMaM <[email protected]> wrote: > > Thanks Mark for fast response. > I was expecting such answer, but It's never hurts to ask. :) > > Right now I'm working on preparing some testing environment for this plugin. > mvn hpi:run is good tool, but for this plugin we need also an crowd instance. > My target for now is to deliver easy setup for myself and feature devs. > > I'm wondering if there is any option to acquire testing licence. > I also need a place where we can store such data. Does jenkins devs have any > shared vault? > > Thanks, > Bartosz > poniedziałek, 4 kwietnia 2022 o 23:07:29 UTC+2 Mark Waite napisał(a): >> >> On Monday, April 4, 2022 at 2:37:17 PM UTC-6 nowak wrote: >> >>> I'm only wondering if I would be allowed to change plugin id or name in >>> such case? >> >> >> Description is easy to update by changing the contents of the >> src/resources/main/index.jelly file. Can be done at any time. >> >> I believe that name change is allowed and relatively low impact by changing >> the <name></name> in the pom.xml. Others may be able to give more guidance >> on name changing. >> >> Changing the plugin ID is strongly discouraged. The plugin ID is used to >> identify upgrades. When you change the plugin ID, you disconnect from your >> existing users. They won't be notified of new releases of the new plugin ID >> because they haven't installed it yet. They will need to remove the >> previous plugin with the original plugin ID and install the plugin with the >> new plugin ID. It is rarely valuable enough to users to change the plugin >> id. >> >> There are several examples of poorly chosen plugin IDs that are kept >> unchanged so that users are not disrupted. The TestNG plugin (as one >> example) uses the id 'testng-plugin-plugin'. Yes, that's redundant. No, we >> won't change it because that will disrupt users. >> >> 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/aa834bcb-51b9-44f8-9b3a-442ed6a58fa9n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dutr0e6fg3geHT8tnCSMqb6QhJiPb_V9HeDBToAeV3%2B_wQ%40mail.gmail.com.
