Skip to content
This repository has been archived by the owner on Jul 12, 2022. It is now read-only.

Commit

Permalink
Text for azure devops (#720)
Browse files Browse the repository at this point in the history
* add website

* enable Emojis!

* remove footer

* Add azure devops platform

* typo
  • Loading branch information
MarcBruins authored Apr 13, 2019
1 parent 484c066 commit 0cea1cc
Show file tree
Hide file tree
Showing 4 changed files with 80 additions and 5 deletions.
2 changes: 1 addition & 1 deletion site/content/_index.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@

# NuKeeper
Nukeeper is a tool to Automagically update NuGet packages in all .NET projects. It has command for local usage and for making PR's to a repostiory on all kinds of git hosting platforms. It supports .NET framework and .NET Core.
Nukeeper is a tool to `automagically` update NuGet packages in all .NET projects. It has command for local usage and for making PR's to a repository on all kinds of git hosting platforms. It supports .NET framework and .NET Core.

### Quick install

Expand Down
79 changes: 79 additions & 0 deletions site/content/platform/azure-devops.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,3 +2,82 @@
title: "Azure Devops"
---

{{% notice tip %}}
NuKeeper supports Azure Devops, VSTS and TFS on premise. The same instruction apply for all these platforms!
{{% /notice %}}

NuKeeper supports intergration with Azure Devops in two ways. One of them is to use the `repo` command and the other one is through the `extension`. The benefit of the extension is that you can make a build pipeline with the extension and schedule your pipeline. This way you can automate your updating flow.

## Extension

The NuKeeper extension is available in the [marketplace](https://marketplace.visualstudio.com/items?itemName=nukeeper.nukeeper#overview). In order to install it you need to add it to your organisation click the `Get it free` button and follow the installation. Once that is done you can create a new pipeline and use the extension.

### Installation
Azure Devops gives us the option to do it either in editor mode, or in yaml.

#### Yaml
1. Add a new build pipeline and select yaml.
1. Add the following `yml` file and adjust where necessary:

<pre>
<code class="language-yml">resources:
- repo: self #point to its own repo, change it if you don't want that
pool:
name: Hosted VS2017 # can be anything you want
steps:
- task: nukeeper.nukeeper.nukeeper.NuKeeper@0
displayName: NuKeeper</code><span class="copy-to-clipboard" title="Copy to clipboard"></span>
</pre>

1. Optionally add extra arguments, The extension just call the `repo` command, so any arguments extra for your repo command can be added here.
<pre>
<code class="language-yml">resources:
steps:
- task: nukeeper.nukeeper.nukeeper.NuKeeper@0
displayName: NuKeeper
inputs:
arguments: '-m 3 -v d'</code><span class="copy-to-clipboard" title="Copy to clipboard"></span>
</pre>
1. Go to triggers and click the <i class="fas fa-plus"></i> Add button to add your schedule. [This cannot be done in yml yet.](https://github.com/Microsoft/azure-pipelines-yaml/issues/39)
1. Finally give the `build service user` the required *[Permissions](#permissions)* and take it for a spin by qeueing a new build!

#### Editor mode
1. Create a new build pipeline for editor mode.
1. Select your repository and select the master branch.
1. Add a new task to your pipeline and select NuKeeper.
1. Optionally, click on the task and add additional arguments to the `Arguments` field. For help on the arguments checkout the [Configuration](/basics/configuration.md) page. The extension just call the `repo` command, so any arguments extra for your repo command can be added here.
1. Go to triggers and click the <i class="fas fa-plus"></i> Add button to add your schedule.
1. Enable your agent to access the oauth token:
![Oauth checkmark](/img/oauth_checkmark.png)

1. Finally give the `build service user` the required *[Permissions](#permissions)* and take it for a spin by qeueing a new build!

#### Permissions
The extensions uses the `build service user` to make a PR. By default this user is not allowed to do that. We have to give it the permissions to do so:

1. Go to "Project settings" in your AzureDevops home screen.
2. Click repositories
3. Click Git repositories
4. Click the build service User(the bottom one, something like: Project collection build service)

Give it the following rights:

- Contribute `Allow`
- Contribute to pull requests `Allow`
- Create branch `Allow`

## Repo command

The repo command works for azure-devops & vsts they same as for the other platforms. You will need a [personal access token](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops) to use the repo command.

```batch
nukeeper repo "https://dev.azure.com/{org}/{project}/_git/{repo}/" <PAT>
```

### Additional arguments
Add any additional arguments that are available for the repo command

```batch
nukeeper repo "https://dev.azure.com/{org}/{project}/_git/{repo}/" <PAT> -m 10
```
The `-m 10` tells NuKeeper that it may update 10 packages. For more parameters checkout the [Configuration](/basics/configuration.md) page.
4 changes: 0 additions & 4 deletions site/content/platform/vsts.md

This file was deleted.

Binary file added site/static/img/oauth_checkmark.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 0cea1cc

Please sign in to comment.