StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You <em>can</em> use the same feed, with the following caveats:</p> <p>The nugets built from the two branches obviously have to have different (non-colliding) versions. I add the 'dev' suffix to the package built from the 'dev' branch (eg 1.2.3.4-dev), and leave my 'stable' branch bare.</p> <p>You have to be explicit when you 'create release', because by default Octopus will pick up the highest version nuget available, and that might not be the release you want (stable presumably lags dev). Pick the version of the package you want (and set the deployment version appropriately). If you are creating your release via TeamCity, ensure you use the --packageVersion argument as well as set the release number. </p> <p><del>Since the above only works if there's only one package in the release, your deployment process does (unfortunately) have to produce one monolithic nuget, or you will get version-mismatches.</del></p> <p>The advantage of this kind of arrangement, of course, is that at a pinch you <em>could</em> push your dev build to QA (or Prod) if the need ever arose.</p> <p>All this assumes both branches <strong>build as the same package</strong> of course. You <em>could</em> build different packages between the dev and stable branches (but I don't think I'd recommend this because of duplicating all the Octopus config).</p> <p>Update: apparently you <em>can</em> use Octo.exe to specify different version numbers across different packages - see <a href="https://github.com/OctopusDeploy/Octopus-Tools">https://github.com/OctopusDeploy/Octopus-Tools</a>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload