Settings and activity
13 results found
-
1 vote
Jason Hess
shared this idea
·
-
1 voteJason Hess
shared this idea
·
-
1 voteJason Hess
shared this idea
·
-
4 votes
An error occurred while saving the comment Jason Hess
supported this idea
·
-
6 votesJason Hess
shared this idea
·
-
27 votesJason Hess
supported this idea
·
-
15 votesJason Hess
shared this idea
·
-
3 votesJason Hess
shared this idea
·
-
25 votesJason Hess
supported this idea
·
-
1 voteJason Hess
shared this idea
·
-
4 votesJason Hess
shared this idea
·
-
152 votesJason Hess
supported this idea
·
-
40 votes
An error occurred while saving the comment Jason Hess
commented
I no longer need this since the restart was related to adding a WIndows feature. I now run boxstarter manually on the machine before deploying from Octopus (manual isn't ideal but it's good enough for me for now). So I basically have a Boxstarter script that I manually manage in hand with the Octopus scripts - both under source control.
Jason Hess
shared this idea
·
Agreed. The only work around is to trigger the create release from octo.exe or the API once the packages have been uploaded. It would be more ideal if when each package is uploaded, Octopus would create the release if all packages with the same version have been uploaded.