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

Internal knowledge about release steps required. #199

Closed
gsvgit opened this issue Aug 3, 2015 · 3 comments
Closed

Internal knowledge about release steps required. #199

gsvgit opened this issue Aug 3, 2015 · 3 comments

Comments

@gsvgit
Copy link
Member

gsvgit commented Aug 3, 2015

Hi

Does any information about Scaffold working process exist? I have a problem with release and seems that I do not understand all steps of Scaffold. For example, I have the next error:

Finished Target: ReleaseDocs
Starting Target: NuGet (==> All)
C:\gsv\projects\YC\YC.PrettyPrinter\.paket\paket.exe pack output bin version  0.0.1-beta releaseNotes  "Initial release"
Paket failed with:
        Could not find a part of the path 'C:\gsv\projects\YC\YC.PrettyPrinter\temp\gh-pages\src\YC.PrettyPrinter\bin\Release\YC.PrettyPrinter.dll'.
Running build failed.

Whether packaging really should be performed on gh-pages branch? (why binaries should be in temp\gh-pages\src\ ?) If so, then compilation step is missed. If no, then switching back to master does not perform correctly.

@gsvgit
Copy link
Member Author

gsvgit commented Aug 5, 2015

Seems that I have problems because my gh-pages branch is not clear. It was branched from master and contains src folder. So, packet.template also exists here and Packed try to process it while process all subfolders recursively. May be short note about gh-pages branch should by included to Scaffold getting started manual? Just to remind user of necessity to clean directories in gh-pages.

@forki
Copy link
Member

forki commented Aug 5, 2015

Yes. Or even better: try to automate things in the init script

@gsvgit
Copy link
Member Author

gsvgit commented Aug 5, 2015

Issue #201 created. Seems, that this issue can be closed.

@forki forki closed this as completed Aug 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants