Again, purely generally speaking, ci.jenkins.io doesn't really do integration tests. I think the general assumption is that if it is on the public install, it is compromised (just to be safe), so we don't put any real secrets or anything else there.
Not saying it can't be done, but generally speaking not done. On Mon, Apr 4, 2022 at 5:06 PM DuMaM <[email protected]> wrote: > > That's great news. > I think the best place it would be a Jenkins Instance used in Jenkins Plugins > CI. > I will try to play with `mvn hpi:run` if there is any possibility to lunch > other services alongside. > Otherwise git-secrets? > > Thanks, > Bartosz > > wtorek, 5 kwietnia 2022 o 01:52:31 UTC+2 [email protected] napisał(a): >> >> 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/4150dee5-9d98-4eed-b7d7-c9b34fbf938dn%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_DuvCEjFLH-cP%3DinOfUvcZO4WbG9TYnNHYqdy_X3zm16QUA%40mail.gmail.com.
