No, you should have these rights already. 

Am 04.01.2014 um 18:29 schrieb Mark Adamcin <[email protected]>:

> Thanks, Ulli! Do I also need to request additional permissions for my 
> "madamcin" jenkins-ci.org account, in order to create/maintain the plugin 
> wiki page, and to execute releases?
> 
> Thanks,
> 
> Mark Adamcin
> http://adamcin.net/
> 
> 
> On Sat, Jan 4, 2014 at 2:15 AM, Ulli Hafner <[email protected]> wrote:
> Created https://github.com/jenkinsci/crx-content-package-deployer-plugin
> 
> Welcome aboard!
> 
> Ulli
> 
> Am 03.01.2014 um 22:41 schrieb Mark Adamcin <[email protected]>:
> 
>> In case this got overlooked because of the holidays, I'd like to request 
>> hosting for my jenkins plugin project, CRX Content Package Deployer Plugin ( 
>> https://github.com/adamcin/crx-content-package-deployer ). My github ID for 
>> commit access is "adamcin". 
>> 
>> Thanks,
>> 
>> Mark Adamcin
>> http://adamcin.net/
>> 
>> 
>> On Mon, Dec 23, 2013 at 8:49 AM, Mark Adamcin <[email protected]> wrote:
>> Hi Georg,
>> 
>> I don't mind renaming the project to reflect its more specific focus on CRX 
>> package deployment, since I don't foresee features being added in the near 
>> future which don't relate to that. I've renamed the project to 
>> https://github.com/adamcin/crx-content-package-deployer .
>> 
>> Here are the main features of the Jenkins plugin that differentiate it from 
>> the content-package-maven-plugin. I have added them to the README.md, and I 
>> will add it to the wiki page once that is set up.
>> 
>> 1. Supports password-less HTTP Signature authentication using your 
>> configured SSH Private Keys, eliminating the need to coordinate password 
>> exchange between developers, devops, and operations teams. 
>> 2. Downloads and/or deploys 1-to-many CRX packages per execution, and 
>> deploys each CRX package to 1-to-many servers per execution
>> 3. The multiselect-enabled Package Choice Parameter allows for execution of 
>> parameterized builds using a selection widget populated with a list of 
>> packages retrieved from a CRX server.
>> 
>> Thanks,
>> 
>> Mark Adamcin
>> http://adamcin.net/
>> 
>> 
>> On Sun, Dec 22, 2013 at 11:45 PM, Georg Henzler 
>> <[email protected]> wrote:
>> Hi Mark, 
>> 
>> There seems to be very little documentation about the plugin... the pom that 
>> states "Deploys content packages to Adobe Granite applications, like Adobe 
>> CQ 5.4, CQ 5.5 and AEM 5.6" and index.jelly says "Provides build steps and 
>> other magic to support package deployment and configuration management for 
>> Adobe Granite applications (CQ5.4+, AEM 5.6.1+, CRX 2.1+)". 
>> 
>> So what exactly does the plugin better than a simple maven job + simple pom 
>> with content-package-maven-plugin [1] would do? Would something like 
>> crx-content-package-deploy-plugin be a better name? 
>> 
>> -Georg
>> 
>> [1]
>> http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html
>> 
>> On Saturday, December 21, 2013 7:36:07 PM UTC+3, Mark Adamcin wrote:
>> Hello!
>> 
>> I would like to host a Jenkins Plugin on https://github.com/jenkinsci. My 
>> GitHub ID is "adamcin". Please fork from 
>> https://github.com/adamcin/granite-client.git.
>> 
>> Thanks,
>> 
>> Mark Adamcin
>> http://adamcin.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 [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> 
>> 
>> -- 
>> 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].
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> 
> -- 
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to