Remote Host Build using Jenkins
Is it possible to build the remote host file using jenkins? If possible means can anyone suggest me,how to proceed the steps for build the remote host files using jenkins? -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b265c330-a236-4b80-abad-1ce148ae1e0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Creating a Jenkins android build using HTTP URL.
Have to build the Jenkins android build using HTTP URL? Is this possible, if it is can you provide me steps to build the android app using HTTP URL? -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e6368fcd-0372-4d92-9920-d8eb5b2f64a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: INFRA-240 is fixed / post-mortem
2015-02-16 15:23 GMT-08:00 Christopher Orr ch...@orr.me.uk: - Identify and remove single-point-of-failure in our infra. Off the top of my head: - I think I'm currently the only one who has the private key to sign update center root CA. - jenkins-ci.org domain name still appears to be registered under Tyler's personal account. These kind of things sound like good INFRA tickets; can we create a new spof component/tag? :) Created spof component and filed INFRA-243 https://issues.jenkins-ci.org/browse/INFRA-243 for domain names and INFRA-244 https://issues.jenkins-ci.org/browse/INFRA-244 for root CA private key. INFRA-75 https://issues.jenkins-ci.org/browse/INFRA-75 is another SPoF. As the ops lead, I'd like the project to consider Adam Papai https://github.com/woohgit. He's been a long time user of Jenkins and he is a member of the CloudBees ops team. I'm sensitive to the fact that he works for CloudBees and how that can come across, but OTOH this will be a part of his day job, and I think that ensures that he can allocate necessary time to the effort. Since i've got a couple of real-world things consuming a boatload of my time, I don't have any objections to Adam joining the infra team. I'm not sure I like the term ops lead as I've never thought of there being a leadership structure around our infrastructure so much as a steaming pile of JIRAs and not enough people to tackle them :-P I was under the same impression regarding a leadership structure, but I guess creating this position is reasonable. As for adding infra team members — since I've been responsible in the past for lots of nagging, waiting for people in the US to wake up, asking about SPoFs, and adding a bunch of tickets to the INFRA pile — I'd be keen to help solve some of these things, and I have a fair amount of sysadmin and Puppet experience. Great, thanks. Aside from the obvious infrastructure/server-access roles, we also have accumulated various moderator roles, which (I think) a very short list of people have, usually to varying degrees. e.g. wiki moderation, wiki user deletion, LDAP account authorisation, account deletion, mailing list banning. There are probably a couple other systems like that. It would be nice to define/document the various roles and who has them, and how people can join that role. Yes, I agree. I suppose I need to revisit the permissions of https://wiki.jenkins-ci.org/display/infra/ so that it has some publicly visible parts to capture this kind of information. I've spent a lot of time in the past deleting wiki spam (moreso when the daily wiki email actually gets sent), and would love to help delete the various spammers on the mailing lists, JIRA and the wiki. I would suggest ramping Adam up in the following ways to mitigate some of our current risk: * Documenting and migrating backend crawlers into the jenkins-infra GH organization. This is one of the places where I think we have a seriously low bus factor * Helping KostySha where I have failed, with feedback on this PR: https://github.com/jenkins-infra/jenkins-infra/pull/66 * Drive migration of JIRA and Confluence onto the newer hardware and newer versions we've not been able to complete due to time There's a long tail of other smaller projects, but in terms of our current infra health and its affect on the project's continued growth and success, I think those are the areas of most need. There is indeed always a lot to be done, but it's also worth pointing out how well a lot of the stuff runs, and how much automation we have. Thanks to you and Kohsuke for keeping the bulk of this stuff under control. And of course to the other infra contributors :) Regards, Chris -- 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 on the web visit https://groups.google.com/d/ msgid/jenkinsci-dev/54E27BFD.8080101%40orr.me.uk. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4zTig%2BD0KyBpGYEm0_OgOJmXdNDbXYgDKU2JYpu24vMWw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Jira Account verification
Done. You should have gotten an email. On Tue, Feb 17, 2015 at 9:15 AM, Amedee Van Gasse amedee.vanga...@gmail.com wrote: Hi, same question here. I signed up with amedee.vangasse (at) itextpdf (dot) com -- Amedee Van Gasse QA Engineer iText Software On Saturday, February 14, 2015 at 1:30:12 PM UTC+1, Nikolaus Demmel wrote: Hi, I just wanted to sign up for an account on the Jenkins Jira. I was told that “due to the spam problem” there was need for additional verification and that I should contact this group. Can someone please enable my account? Email I signed up with: nikolaus (at) nikolaus-demmel (dot) de Thanks everyone! Kind regards, Nikolaus Demmel -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/569dd9e5-7280-48de-897e-c33bd5bfeaf6%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/569dd9e5-7280-48de-897e-c33bd5bfeaf6%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPr6TnSkfT5ivvh%3D4thXMXkB1HQM04FE2Ku5Qa8-5KiXZ8U%2BJw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
New plug-in: Uno Choice Plug-in for dynamic parameters
Hello all, We developed a plug-in in the BioUno project [1], initially based on the Dynamic Parameter Plug-in [2], but that followed a different approach for dynamic parameters. It provides parameters that are also rendered from Groovy scripts (per job script or via Scriptler integration) **but that can be related to other parameters**. It utilizes JavaScript (FWIW dynamicparameter-plugin code is 2.8% JavaScript according to GitHub interface and uno-choice's is 43.9%) to monitor the HTML elements of one parameter, and trigger changes in other parameters. This way, you can easily create many parameters, like Maven Group ID, Artifact ID and Versions, that are dynamically updated. Quick example: The Maven group ID could be a Uno Choice Dynamic Choice Parameter that returns a list of maven group IDs in some Maven repo using Groovy. Once the user selects a group ID, the artifact ID (a Uno Choice Cascade Dynamic Choice Parameter) would automatically get updated, and its Groovy script rendered. The selected group ID would be available to the artifact id Groovy script as a variable. This way your script can load only the artifacts related to the selected group ID. Attached is a GIF file with another example with a State parameter that dynamically updates the City parameter accordingly. The following Wiki page has been created and contains further information and examples: https://wiki.jenkins-ci.org/display/JENKINS/Uno+Choice+Plugin There are other features that were added to the plug-in such as hidden parameters, parameter filtering, self-referenced parameters and more, that I believe Ioannis could explain much better if necessary. GitHub repository: https://github.com/biouno/uno-choice-plugin/GitHub user IDS: @kinow and @imoutsatsos If the plug-in gets accepted, I'll adjust the pom.xml, and will cut a 1.0 release. Thank you!Bruno [1] http://biouno.org/[2] https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/50262896.2043921.1424179818746.JavaMail.yahoo%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
Plugin Hosting Requests
Hi I was just going through a bunch of dev-list items and came across quite a few instances of plugin hosting requests that haven't been answered or are awaiting more information from the requestor etc. It made me wonder about whether it would be a good idea or not to use Jira tickets for the requests. This way its easy to see outstanding requests and the outcome of them. For instance, was the plugin request denied for some reason, is it waiting for further info, or has it been completed etc. I'm not a Jira guru but perhaps there's a way of having a set of fields that people fill out to try and capture the correct information up front rather than having to keep going back for more info. Just an idea and feel free to say if its a bad idea for some reason :) Richard. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947b-gFXN7Dj_c8agaNcPC6jyp6O5H5mzKGs2gLWOmXaFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin Hosting Requests
Hi Richard, I think the good thing with using the dev-list is that this definitely gives more visibility for people to comment/suggest, which I'm afraid you'd lose by switching to JIRA. Vincent 2015-02-17 21:51 GMT+01:00 Richard Bywater rich...@byh2o.com: Hi I was just going through a bunch of dev-list items and came across quite a few instances of plugin hosting requests that haven't been answered or are awaiting more information from the requestor etc. It made me wonder about whether it would be a good idea or not to use Jira tickets for the requests. This way its easy to see outstanding requests and the outcome of them. For instance, was the plugin request denied for some reason, is it waiting for further info, or has it been completed etc. I'm not a Jira guru but perhaps there's a way of having a set of fields that people fill out to try and capture the correct information up front rather than having to keep going back for more info. Just an idea and feel free to say if its a bad idea for some reason :) Richard. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947b-gFXN7Dj_c8agaNcPC6jyp6O5H5mzKGs2gLWOmXaFQ%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947b-gFXN7Dj_c8agaNcPC6jyp6O5H5mzKGs2gLWOmXaFQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCho%2BwcmthOSWG_%2Bxu_UBb%2BwzN9GKRg8-ipEKoDtpkoguw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: INFRA-240 is fixed / post-mortem
I can spare time to help with infrastructure problems. I know pretty much nobody knows me, but i try to be on IRC as much as i can and help other people with issues. If you are interested in a young fellow(version 3.0 :) ) like me just mail me and tell me what you need me to do and have experience with. You never know, maybe I am the guy to help you ;) n Monday, February 16, 2015 at 4:56:34 PM UTC+2, Kohsuke Kawaguchi wrote: My apologies for a delay in handling INFRA-240 https://issues.jenkins-ci.org/browse/INFRA-240. As the ticket indicates now, I've resolved the problem. The issue was that ldap daemon wasn't restarted when I installed a new certificate last week. So it continued running with the old certificate, and when it expired, Artifactory started refusing to talk to it. Local apps on cucumber weren't affected because it was using unsecured communication. I need to figure out why JIRA and Confluence were unaffected by this. Perhaps they have the password locally cached, perhaps they have LDAP connections pooled and long-running, or perhaps they don't properly check the certificate. The next thing I want to talk about is that I think this is a symptom of a deeper issue, which is that the infra ops coverage has fallen way behind. Tyler isn't spending time on this project as he used to be, and the time I spend on Jenkins infra is not as much as it needs to be, too. In the last 6 months or so, we've handed out infra acecss right to a few more people (Daniel Beck and Oleg Nanoshev, IIRC), and that was good for better time zone coverage and what not. But the problem still remains that there is a leadership vacuum, that no one sufficiently owns the infra, and that's difficult to solve by adding more hands alone. So here's what I'd like to propose: - Formalize our ops team more by designating the lead that reports to the board. The lead shall be chosen in the discussion during the project meeting. - Under the new lead, accept another round of ops team members to help spread the workload. I know for example Kostasya is interested in helping. - Kohsuke (and Tyler if he can join) and the ops team will schedule a series of transfer of information sessions to bring the new ops lead and the team up to speed about how things are put together today. - Identify and remove single-point-of-failure in our infra. Off the top of my head: - I think I'm currently the only one who has the private key to sign update center root CA. - jenkins-ci.org domain name still appears to be registered under Tyler's personal account. As the ops lead, I'd like the project to consider Adam Papai https://github.com/woohgit. He's been a long time user of Jenkins and he is a member of the CloudBees ops team. I'm sensitive to the fact that he works for CloudBees and how that can come across, but OTOH this will be a part of his day job, and I think that ensures that he can allocate necessary time to the effort. What do people think? -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1173c59a-d050-49d7-b43c-c408e4cbdfda%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin Hosting Requests
Surely there's a way to make JIRA tickets which can notify the devlist any time they're created. A plugin of some sort, perhaps? Or maybe it's already built in. Regardless, I think we should have JIRA tickets for hosting requests to more formally track said requests. On Tuesday, February 17, 2015 1:27 PM, Vincent Latombe vincent.lato...@gmail.com wrote: Hi Richard, I think the good thing with using the dev-list is that this definitely gives more visibility for people to comment/suggest, which I'm afraid you'd lose by switching to JIRA. Vincent 2015-02-17 21:51 GMT+01:00 Richard Bywater rich...@byh2o.com: Hi I was just going through a bunch of dev-list items and came across quite a few instances of plugin hosting requests that haven't been answered or are awaiting more information from the requestor etc. It made me wonder about whether it would be a good idea or not to use Jira tickets for the requests. This way its easy to see outstanding requests and the outcome of them. For instance, was the plugin request denied for some reason, is it waiting for further info, or has it been completed etc. I'm not a Jira guru but perhaps there's a way of having a set of fields that people fill out to try and capture the correct information up front rather than having to keep going back for more info. Just an idea and feel free to say if its a bad idea for some reason :) Richard. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMui947b-gFXN7Dj_c8agaNcPC6jyp6O5H5mzKGs2gLWOmXaFQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCho%2BwcmthOSWG_%2Bxu_UBb%2BwzN9GKRg8-ipEKoDtpkoguw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1445943671.5727714.1424212102306.JavaMail.yahoo%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
Re: new plugin - jenkins-lockdown-fullcontrol-auth-plugin
It's usually a good idea to provide a short descriptive readme.md file in the root of your repository with a short description / statement of the purpose your plugin serves. On Tue, Feb 17, 2015 at 11:35 AM, Nitzan Raz nitz@gmail.com wrote: Hi All I developed a new plugin and wanted to contribute it, according to this https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins Plugin is based on standard procedure, pom file is complete because I didn't know how to fill the @jenkinsci part. My plugin name: jenkins-lockdown-fullcontrol-auth-plugin (Lockdown Logged-in Authorization Startegy) Personal github ID: BackSlasher Existing repo: https://github.com/BackSlasher/jenkins-lockdown-fullcontrol-auth-plugin.git If some info is missing / the plugin sucks and cannot be possibly accepted please LMK Thanks *Nitzan Raz* http://backslasher.net -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROA0LDFn_6FOgEjaoZQvPSsHZEHKcSzOj%2B%2Bq0vqyCKCT%2BQ%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROA0LDFn_6FOgEjaoZQvPSsHZEHKcSzOj%2B%2Bq0vqyCKCT%2BQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- [image: ] Mads Nielsen Consultant m...@praqma.net +45 50 98 18 09 Skype: inkspot Praqma www.praqma.com Allerød Stationsvej 4 DK-3450 Allerød +45 36 77 27 62 -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFariutZpAjN5QYwnk1fz5v-817d4BFyZ_ZNa9iKp%3DxKpdyZ7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: new plugin - jenkins-lockdown-fullcontrol-auth-plugin
I don't think it's mandatory, just good practice. Although i have a general idea of what your plugin does by looking at the code. If your codebase grew and the complexity was higher, having a short descriptive readme file makes it easier for the folks responsible for forking it on jenkinsci to determine whether the plugins functionality could be merged into existing plugins. On Tue, Feb 17, 2015 at 11:41 AM, Nitzan Raz nitz@gmail.com wrote: I'm going to. Didn't see it on my inspiration plugin https://github.com/jenkinsci/matrix-auth-plugin, so I assumed it was not-mandatory. *Nitzan Raz* http://backslasher.net On Tue, Feb 17, 2015 at 12:40 PM, Mads Nielsen m...@praqma.net wrote: It's usually a good idea to provide a short descriptive readme.md file in the root of your repository with a short description / statement of the purpose your plugin serves. On Tue, Feb 17, 2015 at 11:35 AM, Nitzan Raz nitz@gmail.com wrote: Hi All I developed a new plugin and wanted to contribute it, according to this https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins Plugin is based on standard procedure, pom file is complete because I didn't know how to fill the @jenkinsci part. My plugin name: jenkins-lockdown-fullcontrol-auth-plugin (Lockdown Logged-in Authorization Startegy) Personal github ID: BackSlasher Existing repo: https://github.com/BackSlasher/jenkins-lockdown-fullcontrol-auth-plugin.git If some info is missing / the plugin sucks and cannot be possibly accepted please LMK Thanks *Nitzan Raz* http://backslasher.net -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROA0LDFn_6FOgEjaoZQvPSsHZEHKcSzOj%2B%2Bq0vqyCKCT%2BQ%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROA0LDFn_6FOgEjaoZQvPSsHZEHKcSzOj%2B%2Bq0vqyCKCT%2BQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- [image: ] Mads Nielsen Consultant m...@praqma.net +45 50 98 18 09 Skype: inkspot Praqma www.praqma.com Allerød Stationsvej 4 DK-3450 Allerød +45 36 77 27 62 -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFariutZpAjN5QYwnk1fz5v-817d4BFyZ_ZNa9iKp%3DxKpdyZ7A%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAFariutZpAjN5QYwnk1fz5v-817d4BFyZ_ZNa9iKp%3DxKpdyZ7A%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROBvtCgyctb%3Dh-TQ9v9Zo_DKA7839P9RL%3Dc2Hy0b9HXT0Q%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROBvtCgyctb%3Dh-TQ9v9Zo_DKA7839P9RL%3Dc2Hy0b9HXT0Q%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- [image: ] Mads Nielsen Consultant m...@praqma.net +45 50 98 18 09 Skype: inkspot Praqma www.praqma.com Allerød Stationsvej 4 DK-3450 Allerød +45 36 77 27 62 -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFariuv9fw7OCWg8VfrSk0JCYo6c2%3DygtG0fecWAs1-apRZssw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Validation or default values for repeatableHeteroProperty
Hi, I created a new plugin: https://github.com/jenkinsci/jgiven-plugin I am using a repeatableHeteroProperty to configure a list of reports to generate. Now I want to validate in the UI that this list is not empty. Is this possible? An alternative would be to start with a default entry in the list when the publisher is newly added. How can I achieve this? Currently I am adding the default element in the DataBoundConstructor. This is somewhat unexpected, since the UI does not show this entry on saving. Any help is welcome... Regards, Stefan -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8695d132-8eaa-4634-ae61-6d4b4466514f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
new plugin - jenkins-lockdown-fullcontrol-auth-plugin
Hi All I developed a new plugin and wanted to contribute it, according to this https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins Plugin is based on standard procedure, pom file is complete because I didn't know how to fill the @jenkinsci part. My plugin name: jenkins-lockdown-fullcontrol-auth-plugin (Lockdown Logged-in Authorization Startegy) Personal github ID: BackSlasher Existing repo: https://github.com/BackSlasher/jenkins-lockdown-fullcontrol-auth-plugin.git If some info is missing / the plugin sucks and cannot be possibly accepted please LMK Thanks *Nitzan Raz* http://backslasher.net -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD%2BnROA0LDFn_6FOgEjaoZQvPSsHZEHKcSzOj%2B%2Bq0vqyCKCT%2BQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Gradle JPI Plugin
Hi, I'm the maintainer of the Gradle JPI plugin [1] (the Gradle equivalent of the maven-hpi-plugin) and I would like to get the plugin listed on the Gradle Plugin Portal [2]. To get the plugin included, some steps [3] need to be accomplished. The Gradle JPI plugin already fulfills all but step #4: add a 'gradle-plugin' attribute to each version in your plugin package. That needs to be done on the Jenkins Bintray account [4] for each version of the gradle-jpi-plugin package [5]. The attribute name is 'gradle-plugin' with a value of 'org.jenkins-ci.jpi:org.jenkins-ci.tools:gradle-jpi-plugin'. Can someone with access to the Bintray account do that? Or shall I post this on the infra list or create an INFRA ticket? There is also RTFACT-6860 [6] in the Artifactory JIRA to sync attributes from Artifactory to Bintray. But that's not implemented yet, so for now it needs to be set directly in Bintray. Daniel [1] https://github.com/jenkinsci/gradle-jpi-plugin [2] https://plugins.gradle.org/ [3] https://plugins.gradle.org/submit [4] https://bintray.com/jenkins [5] https://bintray.com/jenkins/maven/tools%3Agradle-jpi-plugin/view [6] https://www.jfrog.com/jira/browse/RTFACT-6860 -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5cd7645d-937b-4bd6-a42b-60896286ce8b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
