Bamboo step plugin?

We have a custom Bamboo step plugin that we're using in our Jenkinsfile to call build plans on our Bamboo server from Jenkins. I'm wondering if I should try to get hosting for it in the community repositories, as there doesn't seem to be anything else out there. There's the Bamboo Notifier

Re: Build class does not invoke get invoked

Thanks Oleg , could not share my code due to organizational policies however . My moto is to create one top level Item (new project type) which is similar to freestyle project & whenever a job is created using this project it should get invoked . i have referred to jenkins freestyle project &

Re: "One or more fields in this block have been edited." is always displayed.

On Mon, Aug 7, 2017 at 3:54 PM, Daniel Anechitoaie wrote: > So it seems that this is normal, and this is to show that the data has been > changed and it's no longer the default value. Yes. I am not sure if this is well tested with repeatable sections. Definitely you should

Re: Build class does not invoke get invoked

I think you should still prefer trying to extract the gist of your code and create a PR or something reviewable online to maximize your chances to get feedback, ideally on GitHub where it's easy to do. Reviewing code in emails is a quite a bit cumbersome. After a quick glance at the code, aren't

Re: Request for commit access

I believe they're not supposed to be rejected, simply queued up for moderation isn't it? Indeed I had checked it and never found/saw any email from Christoph there. And I guess the moderators wouldn't have deleted it... Another weird case of Google groups (Is there any audit log for this in

Re: "One or more fields in this block have been edited." is always displayed.

Hi, I have replaced now the with and seems to be working fine. Thank you. On Tuesday, August 8, 2017 at 3:30:41 PM UTC+3, Jesse Glick wrote: > > On Mon, Aug 7, 2017 at 3:54 PM, Daniel Anechitoaie > wrote: > > So it seems that this is

Securely storing secrets

(This is discussing a class of potential security issues -- if you want to mention how it's a problem in a specific plugin, please report to our secure tracker instead. Thanks!) Hi everyone, I've just posted another security advisory: https://jenkins.io/security/advisory/2017-08-08/ This

Re: Securely storing secrets

On Tue, Aug 8, 2017 at 10:44 AM, Daniel Beck wrote: > Backups that exclude the secrets/ directory don't compromise secrets even if > the backups are made accessible to unauthorized people. To clarify, it is just `secrets/master.key` which should be excluded from backups. The

Re: Securely storing secrets

On Tue, Aug 8, 2017 at 10:44 AM, Daniel Beck wrote: > Backups that exclude the secrets/ directory don't compromise secrets even if > the backups are made accessible to unauthorized people. To clarify, it is just `secrets/master.key` which should be excluded from backups. The

Re: Securely storing secrets

> On 8. Aug 2017, at 16:55, Jesse Glick wrote: > > The rest of the `secrets/` directory is (at least in theory) initialAdminPassword remains from the 2.0 install wizard if you don't customize the admin user. -- You received this message because you are subscribed to