distribute private package to my customers - distribution license now available #285
-
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 2 replies
-
I'm in the same situation. Your documentation is great, but several things do not seem to be available yet, the CI role for example is not visible |
Beta Was this translation helpful? Give feedback.
-
Sorry for the late response on this one, we are in the final days of moving out of beta so it's been a bit hectic, to say the least. If the final testing doesn't reveal any issues we will be moving out of Beta on Monday. Firstly to the simple issues: The CICD role does exist but there is a known bug that results in the Role not being visible. As to the distribution question. So the documentation isn't quite right, I'm in the process of updating it and it should be ready next week. So the requirements are:
We haven't actually released the Distribution License publicly but it will be live by the end of the week (10th of March). We would be rather keen to have you both on board as the first live users.
If you are interested post a response and I will get you set up. Brett |
Beta Was this translation helpful? Give feedback.
-
A couple of missing points
You can add any no. of customers.
Each customer developer should be given their own account.
…On Fri, 3 Mar 2023, 10:20 pm Jérémy CARBONNE, ***@***.***> wrote:
I'm in the same situation.
I will share a private git repo to my customer 😢
Your documentation is great, but several things do not seem to be
available yet, the CI role for example is not visible
—
Reply to this email directly, view it on GitHub
<#285 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OF3AH55HTYYR6YZVLLW2HHXHANCNFSM6AAAAAAVKSEMNI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
- Should I invite my customer by "Member Invitation"?
Yes, on Monday the will be an updated member invite that lets you invite a
member to a specific team. Create a team Pet customer
- Do they count towards my no. of members?
No.
- How do I add "Distribution License"?
We do that manually
- If my customer has a group of developers, can they share the same
Distribution license?
Only single distribution licence for all your customers
- Is "External user" actually a "Member"
Yes
- How can I view "Distribution License" in my OnePub portal?
There is a new product tab that shows your licence. Coming Monday
…On Sat, 4 Mar 2023, 9:25 am Brett Sutton, ***@***.***> wrote:
A couple of missing points
You can add any no. of customers.
Each customer developer should be given their own account.
On Fri, 3 Mar 2023, 10:20 pm Jérémy CARBONNE, ***@***.***>
wrote:
> I'm in the same situation.
> I will share a private git repo to my customer 😢
>
> Your documentation is great, but several things do not seem to be
> available yet, the CI role for example is not visible
>
> —
> Reply to this email directly, view it on GitHub
> <#285 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAG32OF3AH55HTYYR6YZVLLW2HHXHANCNFSM6AAAAAAVKSEMNI>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
Beta Was this translation helpful? Give feedback.
-
Customer are unlimited.
Developers of customers are unlimited.
You need at a team or enterprise seat licence for each of the developers
that work for your company.
…On Sat, 4 Mar 2023, 3:57 pm isaac-gofa, ***@***.***> wrote:
Interested. Thanks for your help!
And I would like to pay, just it's still unclear about the specific cost
increase if I have more developers or more customers.
—
Reply to this email directly, view it on GitHub
<#285 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32OE4KLIG3ZTYOXDTLJDW2LDUTANCNFSM6AAAAAAVKSEMNI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
We have a release planned for tomorrow which include the required changes.
Will update you once it has been pushed.
…On Wed, 8 Mar 2023, 8:52 pm isaac-gofa, ***@***.***> wrote:
Hello @bsutton <https://github.com/bsutton>, any updates?
—
Reply to this email directly, view it on GitHub
<#285 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG32ODS57XYHBYTT36G37DW3BJEJANCNFSM6AAAAAAVKSEMNI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Just thought I should give you an update.
I will keep you posted as we progress. |
Beta Was this translation helpful? Give feedback.
-
Just letting you know that we have finally released the distribution license and reworked the CI/CD model. To enable the distribution license, you start by Inviting a Customer from the 'Invite' link on the home page. We have also updated the doco: CICD Distribution license Any issues, please let me know. |
Beta Was this translation helpful? Give feedback.
Sorry for the late response on this one, we are in the final days of moving out of beta so it's been a bit hectic, to say the least.
If the final testing doesn't reveal any issues we will be moving out of Beta on Monday.
Firstly to the simple issues:
@jeremy-carbonne
The CICD role does exist but there is a known bug that results in the Role not being visible.
We have a fix for this and if all goes well it will be rolled by the end of next week.
In the meant time, you can just create another account with the Member role and achieve most of the core objectives (the CICD role is more restricted than a normal Member, otherwise there is no difference).
As to the distribution question.
So the d…