I got AppVeyor setup to run windows builds for RSpec. However, the builds are currently running under the "myronmarston" user as that's my github login:
https://ci.appveyor.com/project/myronmarston/rspec-core
Given that we have a github RSpec org I'd prefer if our builds
could be at /project/rspec/<repo> -- it's more
clear that way that they are the official RSpec windows builds.
More practically speaking the other members of the RSpec github org
aren't able to retry builds when they have transient failures. I
saw the team page:
...but it feels wrong to add the other RSpec team members to the "myronmarston" team.
Is there a way to make an RSpec team on AppVeyor? I can't figure out how since my github login is myronmarston.
Thanks!
#1 Posted by Feodor Fitsner Support staff on 29 Nov, 2014 06:36 PM
Just rename your AppVeyor account at https://ci.appveyor.com/account
-Feodor
#2 Posted by Myron Marston on 29 Nov, 2014 06:40 PM
Thanks. I couldn't find that for some reason.
On the team page it has a spot to add users and a spot to add collaborators. What's the difference?
Also, is their any way to make the team automatically grant permissions to everyone who has commit access as part of the github org? That's how travis works...
#3 Posted by Feodor Fitsner Support staff on 29 Nov, 2014 06:48 PM
Use "GitHub Teams" to add your colleagues. You can associate GitHub team with AppVeyor role.
#4 Posted by Myron Marston on 29 Nov, 2014 10:24 PM
Thanks. It looks like the rspec/RSpec team has already been added, although I don't remember doing that. Kinda odd!
Anyhow, is there anything else that needs to be done so that other members of the rspec/RSpec github org can retry failed AppVeyor builds? They've reported they're unable to do that.
#5 Posted by Feodor Fitsner Support staff on 29 Nov, 2014 10:36 PM
Make sure that team assosiated with Administrator group.
-Feodor
#6 Posted by Arlo on 20 Dec, 2015 07:37 PM
Now is there a way to do that without renaming the Appveyor account? I do work with multiple organizations & on my own, all using the same github login.
I'd like to have the option to use Appveyor with each. But that would mean that I'd need to be able to have /projects/arlobelshee/*, /projects/Minions/*, /projects/InnovatingTeams/*, and so on.
Is there a good way to support this, all from one GH login?
#7 Posted by Feodor Fitsner Support staff on 20 Dec, 2015 07:41 PM
Add those projects under the same AppVeyor account.
#8 Posted by Arlo on 20 Dec, 2015 08:09 PM
That doesn't work. It creates /projects/Minions/Minions, /projects/Minions/presentationkaraoke, and /projects/Minions/innovatingteams-github-io. Instead, I want /projects/Minions/Minions, /projects/arlobelshee/presentationkaraoke, and /projects/InnovatingTeams/innovatingteams-github-io.
My multiple GH orgs are really distinct entities. I'm the organizer for each of them. I'd like them to appear as distinct entities on AppVeyor as well.
#9 Posted by Feodor Fitsner Support staff on 20 Dec, 2015 08:12 PM
Register several AppVeyor accounts then.
#10 Posted by Arlo Belshee on 20 Dec, 2015 08:25 PM
How do I associate them all with the same GitHub credentials? In GH, I’m logged in as arlobelshee. The others are organizations, without any credentials (just members). I’d prefer not to have to create AppVeyor accounts with separate passwords and everything just to manage my organizations.
Arlo
#11 Posted by matham on 30 Dec, 2015 12:24 AM
I'm kinda wondering about the same thing. I'd rather not rename because then it'd affect all the other projects I will create builds for. Creating multiple accounts doesn't work because first, it doesn't allow to associate multiple accounts with one email. And I'd rather not create multiple emails accounts that I have to manage.
Travis resolves this by allowing I think one travis project for each github project and anyone with access to that project on gh will be able to modify that same project using their travis account. Then, the project is accessible from a url using that projects name and org.
However, I do like the appveyor model better where you can have independent builds. However, having a single global version for the project which once created by someone with access, everyone with gh access to that project will also have access maybe worth adding as an additional option. Then, that global project can take the url of the org/project_name which would solve this problem.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:03 AM.