Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: Nightly builds or way to produce own build #5453

Closed
outcoldman opened this issue Apr 18, 2016 · 13 comments
Closed

Suggestion: Nightly builds or way to produce own build #5453

outcoldman opened this issue Apr 18, 2016 · 13 comments
Assignees

Comments

@outcoldman
Copy link
Contributor

To help contributing - we, contributors, need to have a way to get the latest builds. Will be good to have an option, something like "update.channel": "nightly".
If this is not possible - at least have a way to build own VSCode package, which we can use for development.

@bgse
Copy link
Contributor

bgse commented Apr 18, 2016

You can build vscode yourself, just clone the repo and follow the instructions here:

https://github.com/Microsoft/vscode/blob/master/wiki/contributing/how-to-contribute.md#build-and-run-from-source

@outcoldman
Copy link
Contributor Author

@bgse sorry, by "building" I meant "packaging". I want to be able to produce a package which I can use to replace Visual Studio Code.app.

@dbaeumer
Copy link
Member

You can only build the OSS version of code using gulp vscode-win32 (or other platforms). There is no public command to build the identical MS VS Code version due to product specific settings.

@chrisdias can you provide more details?

@outcoldman
Copy link
Contributor Author

What about publicly available Nightly builds?

@outcoldman
Copy link
Contributor Author

Also does gulp vscode-win32 produces actually a package, like "OSS Version Code.app" or just set of files which I need to package inside Electron on my own?

@dbaeumer why have you closed this issue? My question has not been answered yet.

@outcoldman
Copy link
Contributor Author

Ok, I have found that gulp vscode-darwin outputs VSCode-darwin/ outside of the source folder (which is not great), but understandable. Please document these steps.

@dbaeumer
Copy link
Member

I thought my explanation was good enough on how to build VSCode yourself. Obviously not :-(. We also discussed making nightly builds available but haven't reached a conclusion yet.

@outcoldman
Copy link
Contributor Author

Yes, it was a little bit confusing how to produce own build. I believe that gulp vscode-darwin is not documented anywhere. But this gave me some idea where to look, so I finally made my own build (using it for my unmerged PR).

@dbaeumer Could you please keep this feature request open to track "nightly builds" status?

Honestly I do not see a reason why I (or anybody else) cannot setup "nightly builds" on their own, but in that case you (Microsoft) will loose telemetry and statistics, which you probably want to have.

@dbaeumer
Copy link
Member

Reopening.

@chrisdias I assign to you because of the request of public nightly builds and the request of being able to run their own full VSCode builds

@chrisdias
Copy link
Member

Nightly builds are on their way, please see: http://code.visualstudio.com/blogs/2016/05/23/evolution-of-insiders

@petebytes
Copy link

@outcoldman This is a memory test :)

I am trying to create a vscode package using gulp vscode-darwin which from what I can tell needs modifications to the build script.
You mentioned "I finally made my own build (using it for my unmerged PR)" which I was hoping to find and learn from, but no luck.

Any chance you can point me in the right direction so I can gulp vscode-darwin successfully?

Thanks

@outcoldman
Copy link
Contributor Author

@peteoliveira sorry, I do not remember what required to do that. I only remember that I took some json file from official package and used it as an example.

@petebytes
Copy link

@outcoldman thanks for the response and hopefully pointing me in the right direction.
Stay warm

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants