Currently the feature/nuget_package branch of the MHC can be built as a Nuget package and pushed to Nuget.org (see the README.md in that branch). However I'm struggling to work out the best thing to do wrt automation.
How to push a new version to Nuget.org from Jenkins? Should we even bother with doing this? Issues / todos are:
nuget push nupkg\Jncc.MhcMicrosite.Plugin.0.0.1.nupkg -Source https://api.nuget.org/v3/index.json requires you to give the nuget package that you just packed (created). But how do we know in Jenkins what file this is? We don't have easy access to the package version. We could extract it out of the XML or perhaps do a directory listing to see what filename was just put into the nupkg folder.
nuget push will fail if the package version already exists, which it will if we make this run on every build. What best to do to avoid this getting even more complicated? A separate Jenkins job just for publishing which is manually triggered? Or potentially do curl or something to check if the package version already exists on Nuget, and if so then skip it.
Main website
The jncc-website feature/mhc-integration branch needs to be updated. It currently has a dependency on MarineHabitatClassification.1.0.0 but it needs to be updated so that it uses the package on Nuget.org now called Jncc.MhcMicrosite.Plugin.0.0.1.
Then it needs a straightforward automatic deployment set up so that a push to master automatically publishes via Jenkins and Octopus to the jncc-website.latest website on the jncc-dev machine. A push to release should do the same but publish to jncc live umbraco
Example microsite (MHC)
Currently the
feature/nuget_packagebranch of the MHC can be built as a Nuget package and pushed to Nuget.org (see the README.md in that branch). However I'm struggling to work out the best thing to do wrt automation.How to push a new version to Nuget.org from Jenkins? Should we even bother with doing this? Issues / todos are:
nuget push nupkg\Jncc.MhcMicrosite.Plugin.0.0.1.nupkg -Source https://api.nuget.org/v3/index.jsonrequires you to give the nuget package that you justpacked (created). But how do we know in Jenkins what file this is? We don't have easy access to the package version. We could extract it out of the XML or perhaps do a directory listing to see what filename was just put into the nupkg folder.nuget pushwill fail if the package version already exists, which it will if we make this run on every build. What best to do to avoid this getting even more complicated? A separate Jenkins job just for publishing which is manually triggered? Or potentially docurlor something to check if the package version already exists on Nuget, and if so then skip it.Main website
The jncc-website
feature/mhc-integrationbranch needs to be updated. It currently has a dependency onMarineHabitatClassification.1.0.0but it needs to be updated so that it uses the package on Nuget.org now calledJncc.MhcMicrosite.Plugin.0.0.1.Then it needs a straightforward automatic deployment set up so that a push to
masterautomatically publishes via Jenkins and Octopus to thejncc-website.latestwebsite on the jncc-dev machine. A push toreleaseshould do the same but publish to jncc live umbraco