Skip to content
This repository has been archived by the owner on Mar 7, 2019. It is now read-only.

Continuous integration of the sdk #42

Open
baywet opened this issue Dec 31, 2017 · 18 comments
Open

Continuous integration of the sdk #42

baywet opened this issue Dec 31, 2017 · 18 comments

Comments

@baywet
Copy link
Collaborator

baywet commented Dec 31, 2017

Hey @kenakamu here is some of the follow up of #39
Currently the SDK is not being continuously integrated.
That means we're not checking if PR's are even build (automatically) before reviewing those.
The goal of this thread is to identify which technology we will set up to build the project + PR's automatically.
I have a lot of experience with VSTS and could get us up to speed fairly quick. However VSTS is more of a corporate solution (private, no public access) and doesn't support yet build definitions being part of the repo (which means if we set it up on my vsts tenant and I disappear, maintainers will have to rebuild it)
Do you have and CI/CD experience with other technologies? And opinion on that?

@lazaromenezes
Copy link
Contributor

What about Travis-CI ?

https://travis-ci.org/

I can spend a few hours trying to get it built from there.

@baywet
Copy link
Collaborator Author

baywet commented Mar 20, 2018

I'm not super familiar with this one or AppVeyor but I know they are pretty standard in OpenSource projects. I don't have much time to spend on this project lately but if you can get CI running with Travis and share the ownership of the "build definition" with @kenakamu and I, that'd be greatly appreciated!

@lazaromenezes
Copy link
Contributor

I'll try that until the end of the week :)

@lazaromenezes
Copy link
Contributor

Hi all, got a preview using AppVeyor, since Travis-CI is linux/osx only and I'm still struggling to get Portable Net45 dependency working there.

Here's the preview: https://ci.appveyor.com/project/lazaromenezes/ucwa2-0-cs
Source: https://github.com/lazaromenezes/UCWA2.0-CS/tree/appveyor

I'll improve this as soon as I got more time

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

Nice work! keep us posted.
Yeah we have a separate issue to migrate to dotnet core 2, maybe we should do that first then? #29

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

also, could you give @kenakamu and myself permissions on that build definition so we can take a look please?

@lazaromenezes
Copy link
Contributor

Sure!!

I could add you, @baywet, as a collaborator for my account but it didn't work for any of @kenakamu emails I got into git log. Can you check if you have access to the build project?

I'll try adding you both as collaborators to my github fork later as it seems appveyor can import it.

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

I received a notification from appveyor, however I can't see any appveyor project at the moment.
I think this is because I need some rights on your forked repos as well. Very new to appveyor :)

@lazaromenezes
Copy link
Contributor

So am I!!

LoL...I used Travis CI before for some personal stuff, but it's my first time with AppVeyor. I'll add you both to my fork.

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

Accepted github permissions, still can't see the project on my appveyor dashboard and I don't seem to have any permission when I access the project directly through url... this is confusing. Maybe try to share the project again now that I have github permissions as well?

@lazaromenezes
Copy link
Contributor

I removed and added the project again. Is it showing for you now? Into the project settings I couldn't find how to add someone, only deals with role permissions (You're an administrator for the account itself).

I'll have to stop for while but I'll be back to this later if it doesn't work right now

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

Still not showing up. I took a look at stack and their documentation and couldn't find a clear answer. Created a stack question to hopefully get an answer. We must be missing out something. https://stackoverflow.com/questions/49451544/appveyor-share-project-between-users

@baywet
Copy link
Collaborator Author

baywet commented Mar 23, 2018

I can access the build! There is a sign in/out dance you have to do I didn't get. And people answered the question on SO. Thanks!

@lazaromenezes
Copy link
Contributor

Hi @kenakamu, i started a prototype for the CI but for continue it I'd like to know the process you have been using for generate the sdk nupkg, could you please describe it so I can try apply the same steps into AppVeyor?

@kenakamu
Copy link
Owner

kenakamu commented May 4, 2018

At this moment, it is very manual process. Sync in Visual Studio, compile, then create package for nuget and upload.

@lazaromenezes
Copy link
Contributor

lazaromenezes commented Aug 27, 2018

This is a proof of concept I was working for enable CI with AppVeyor. Unfortunatelly I'm not having enough time to continue working on this right now, so if anyone wants to pickup and continue please feel free to do it: https://github.com/lazaromenezes/UCWA2.0-CS/tree/appveyor

@baywet
Copy link
Collaborator Author

baywet commented Sep 12, 2018

Update on the matter now that vsts became azure devops and is free for open source project we maybe could rely on that https://azure.microsoft.com/en-us/blog/announcing-azure-pipelines-with-unlimited-ci-cd-minutes-for-open-source/

@baywet
Copy link
Collaborator Author

baywet commented Sep 21, 2018

Hey @kenakamu Azure DevOps being really easy to set up and being free for open source project I think we should set it up. However it requires admin permissions on the repos to register the webhooks/install successfully.
If you don't have time to set it up yourself, could you at least create the pipeline and give me permissions to edit it on my hotmail address please? https://github.com/marketplace/azure-pipelines

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants