Re: Managing maven credentials on a shared build server
Nice, didn't know it's available. On 2014/01/21 10:16 AM, Stephen Connolly wrote: I work for CloudBees... I can assure you that it is free and open source... look here: https://github.com/jenkinsci/cloudbees-folder-plugin. -Stephen. Open Frickin Source == Fecking Open Source Baby == Open source and not something else. Prior to 4.0 it was Closed Source but Free as in "tell me your email address and I will give you a free beer" Since 4.0 it is Open Source and free as in "here is how you can make beer you are free to tell this or modify however/whatever way you want" On 21 January 2014 15:04, Naumenko, Roman mailto:roman.naume...@rbccm.com>> wrote: You mean folders plugin from cloudbees? As far as I know it's not free. PS What's Open Frickin Source? On 2014/01/17 12:13 PM, Stephen Connolly wrote: There is actually a layered set of credential stores... if you use the folders plugin (which as of version 4.0 is free as in Open Frickin Source) then you can tie credentials to within a specific folder. imod has been working on trying to integrate credentials into the maven settings.xml provider... but after we made him a committer over at Maven we've been keeping him busy with his OSS time ;-) On 17 January 2014 15:20, Naumenko, Roman mailto:roman.naume...@rbccm.com>> wrote: Hi, Are there any known best practices for managing credentials for maven on a shared build server? Only way I see it is to have store them in a workspace in custom setting xml, but for that users should be able to upload the file from somewhere. And only option is to get it from version control system. Which is not really working, maven credentials should be separated for snapshots and releases repositories. E.g different persons make builds and other prepare releases. Obviosly it's not applicable if credentials are stored in the same repository. Rephrasing it: is there a way to separate maven credentials per job while manage it somewhere on jenkins? There is a plugin credential-store that provides a nice interface for managing password. But again, this is for global definitions. --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Managing maven credentials on a shared build server
On 21 January 2014 15:27, Daniel Beck wrote: > > On 21.01.2014, at 16:16, Stephen Connolly > wrote: > > > 4.0 > > Also worth noting is that the major changes in 4.0 were removal of several > of the nicer features as described here: > > > http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-source.html > > I should note that it was not Engineering's decision to move the features, but this was the basis on which we got approval to make the core functionality open source, so we took the battle we had won and accepted that, for now, the second battle we did not win > > This 4.0 release is fully functional on its own, but some of the > advanced features have been retained in Jenkins Enterprise (in the Folders > Plus plugin): the Move action, some health reports and icons, the > Environment variables property, the Pull information from nested job list > view column, and the Restrict the kind of children in this folder option. > The core folder functionality and all of the APIs and extension points are > available in the open-source plugin. > > > > Are you already running the Folders plugin? If so, you may upgrade to > 4.0 today, but if you are using it via the free license, be aware that you > would lose access to the advanced functions. You can do without them, stay > on 3.15 or earlier, or upgrade to Jenkins Enterprise. > > > http://release-notes.cloudbees.com/release/Folders/4.0 > > > some functions were moved out of the core plugin into these plugins. If > you were using the Folders plugin under the Free license, not as part of > Jenkins Enterprise, you may update to 4.0 but you will lose some advanced > features; otherwise you may continue to run up to version 3.15 under the > Free license. > > > So users without Jenkins Enterprise license have the choice between > folders 3.x (closed source, all features, dead end) and 4.x (open source, > basic features, continued development). > It would not be too hard for somebody in the community to add health reports and icons... just a question of implementing the correct extension points... if you do decide to implement some health reports I highly recommend getting Señor Beck to test them for you as it can be quite easy to inadvertently kill the view performance if you don't think about safe iteration... hence the Reporter helper class/interface that forces you to do things mostly the right way. The moving of folders and items in folders is coming back (already checked in https://github.com/jenkinsci/cloudbees-folder-plugin/commit/efac1d2625bd9b58eb6841e632389306d97a9a4a) but the OSS version does not have the passivation fancy logic in the JE version, so will only move folders when it is absolutely safe to do so... the JE version will try a lot harder and block builds that would stall progress. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Managing maven credentials on a shared build server
On 21.01.2014, at 16:16, Stephen Connolly wrote: > 4.0 Also worth noting is that the major changes in 4.0 were removal of several of the nicer features as described here: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-source.html > This 4.0 release is fully functional on its own, but some of the advanced > features have been retained in Jenkins Enterprise (in the Folders Plus > plugin): the Move action, some health reports and icons, the Environment > variables property, the Pull information from nested job list view column, > and the Restrict the kind of children in this folder option. The core folder > functionality and all of the APIs and extension points are available in the > open-source plugin. > > Are you already running the Folders plugin? If so, you may upgrade to 4.0 > today, but if you are using it via the free license, be aware that you would > lose access to the advanced functions. You can do without them, stay on 3.15 > or earlier, or upgrade to Jenkins Enterprise. http://release-notes.cloudbees.com/release/Folders/4.0 > some functions were moved out of the core plugin into these plugins. If you > were using the Folders plugin under the Free license, not as part of Jenkins > Enterprise, you may update to 4.0 but you will lose some advanced features; > otherwise you may continue to run up to version 3.15 under the Free license. So users without Jenkins Enterprise license have the choice between folders 3.x (closed source, all features, dead end) and 4.x (open source, basic features, continued development). -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Managing maven credentials on a shared build server
I work for CloudBees... I can assure you that it is free and open source... look here: https://github.com/jenkinsci/cloudbees-folder-plugin. -Stephen. Open Frickin Source == Fecking Open Source Baby == Open source and not something else. Prior to 4.0 it was Closed Source but Free as in "tell me your email address and I will give you a free beer" Since 4.0 it is Open Source and free as in "here is how you can make beer you are free to tell this or modify however/whatever way you want" On 21 January 2014 15:04, Naumenko, Roman wrote: > > You mean folders plugin from cloudbees? As far as I know it's not free. > > PS > What's Open Frickin Source? > > > On 2014/01/17 12:13 PM, Stephen Connolly wrote: > > There is actually a layered set of credential stores... if you use the > folders plugin (which as of version 4.0 is free as in Open Frickin Source) > then you can tie credentials to within a specific folder. > > imod has been working on trying to integrate credentials into the maven > settings.xml provider... but after we made him a committer over at Maven > we've been keeping him busy with his OSS time ;-) > > On 17 January 2014 15:20, Naumenko, Roman wrote: > >> Hi, >> >> Are there any known best practices for managing credentials for maven on >> a shared build server? >> >> Only way I see it is to have store them in a workspace in custom setting >> xml, but for that users should be able to upload the file from somewhere. >> And only option is to get it from version control system. Which is not >> really working, maven credentials should be separated for snapshots and >> releases repositories. E.g different persons make builds and other prepare >> releases. Obviosly it's not applicable if credentials are stored in the >> same repository. >> >> Rephrasing it: is there a way to separate maven credentials per job while >> manage it somewhere on jenkins? >> There is a plugin credential-store that provides a nice interface for >> managing password. But again, this is for global definitions. >> >> --Roman >> >> ___ >> >> This email is intended only for the use of the individual(s) to whom it >> is addressed and may be privileged and confidential. >> Unauthorised use or disclosure is prohibited. If you receive This e-mail >> in error, please advise immediately and delete the original message. >> This message may have been altered without your or our knowledge and the >> sender does not accept any liability for any errors or omissions in the >> message. >> >> Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux >> droits et obligations qui s'y rapportent. >> Toute diffusion, utilisation ou copie de ce message ou des renseignements >> qu'il contient par une personne autre que le (les) destinataire(s) >> désigné(s) est interdite. >> Si vous recevez ce courriel par erreur, veuillez m'en aviser >> immédiatement, par retour de courriel ou par un autre moyen. >> -- >> > > > ___ > > This email is intended only for the use of the individual(s) to whom it is > addressed and may be privileged and confidential. > Unauthorised use or disclosure is prohibited. If you receive This e-mail > in error, please advise immediately and delete the original message. > This message may have been altered without your or our knowledge and the > sender does not accept any liability for any errors or omissions in the > message. > > Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux > droits et obligations qui s'y rapportent. > Toute diffusion, utilisation ou copie de ce message ou des renseignements > qu'il contient par une personne autre que le (les) destinataire(s) > désigné(s) est interdite. > Si vous recevez ce courriel par erreur, veuillez m'en aviser > immédiatement, par retour de courriel ou par un autre moyen. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Managing maven credentials on a shared build server
You mean folders plugin from cloudbees? As far as I know it's not free. PS What's Open Frickin Source? On 2014/01/17 12:13 PM, Stephen Connolly wrote: There is actually a layered set of credential stores... if you use the folders plugin (which as of version 4.0 is free as in Open Frickin Source) then you can tie credentials to within a specific folder. imod has been working on trying to integrate credentials into the maven settings.xml provider... but after we made him a committer over at Maven we've been keeping him busy with his OSS time ;-) On 17 January 2014 15:20, Naumenko, Roman mailto:roman.naume...@rbccm.com>> wrote: Hi, Are there any known best practices for managing credentials for maven on a shared build server? Only way I see it is to have store them in a workspace in custom setting xml, but for that users should be able to upload the file from somewhere. And only option is to get it from version control system. Which is not really working, maven credentials should be separated for snapshots and releases repositories. E.g different persons make builds and other prepare releases. Obviosly it's not applicable if credentials are stored in the same repository. Rephrasing it: is there a way to separate maven credentials per job while manage it somewhere on jenkins? There is a plugin credential-store that provides a nice interface for managing password. But again, this is for global definitions. --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Managing maven credentials on a shared build server
There is actually a layered set of credential stores... if you use the folders plugin (which as of version 4.0 is free as in Open Frickin Source) then you can tie credentials to within a specific folder. imod has been working on trying to integrate credentials into the maven settings.xml provider... but after we made him a committer over at Maven we've been keeping him busy with his OSS time ;-) On 17 January 2014 15:20, Naumenko, Roman wrote: > Hi, > > Are there any known best practices for managing credentials for maven on a > shared build server? > > Only way I see it is to have store them in a workspace in custom setting > xml, but for that users should be able to upload the file from somewhere. > And only option is to get it from version control system. Which is not > really working, maven credentials should be separated for snapshots and > releases repositories. E.g different persons make builds and other prepare > releases. Obviosly it's not applicable if credentials are stored in the > same repository. > > Rephrasing it: is there a way to separate maven credentials per job while > manage it somewhere on jenkins? > There is a plugin credential-store that provides a nice interface for > managing password. But again, this is for global definitions. > > --Roman > > ___ > > This email is intended only for the use of the individual(s) to whom it is > addressed and may be privileged and confidential. > Unauthorised use or disclosure is prohibited. If you receive This e-mail > in error, please advise immediately and delete the original message. > This message may have been altered without your or our knowledge and the > sender does not accept any liability for any errors or omissions in the > message. > > Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux > droits et obligations qui s'y rapportent. > Toute diffusion, utilisation ou copie de ce message ou des renseignements > qu'il contient par une personne autre que le (les) destinataire(s) > désigné(s) est interdite. > Si vous recevez ce courriel par erreur, veuillez m'en aviser > immédiatement, par retour de courriel ou par un autre moyen. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Managing maven credentials on a shared build server
Hi, Are there any known best practices for managing credentials for maven on a shared build server? Only way I see it is to have store them in a workspace in custom setting xml, but for that users should be able to upload the file from somewhere. And only option is to get it from version control system. Which is not really working, maven credentials should be separated for snapshots and releases repositories. E.g different persons make builds and other prepare releases. Obviosly it's not applicable if credentials are stored in the same repository. Rephrasing it: is there a way to separate maven credentials per job while manage it somewhere on jenkins? There is a plugin credential-store that provides a nice interface for managing password. But again, this is for global definitions. --Roman ___ This email is intended only for the use of the individual(s) to whom it is addressed and may be privileged and confidential. Unauthorised use or disclosure is prohibited. If you receive This e-mail in error, please advise immediately and delete the original message. This message may have been altered without your or our knowledge and the sender does not accept any liability for any errors or omissions in the message. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
