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

Added Nuget example cli-for-jfrog-artifactory.md #75

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions jfrog-applications/jfrog-cli/cli-for-jfrog-artifactory/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2094,6 +2094,17 @@ jf dotnet restore --build-name=my-build-name --build-number=1

In addition, record the build-info as part of build **my-build-name/1**. The build-info can later be published to Artifactory using the [build-publish](https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-artifactory#publishing-build-info) command.

##### Example 4

To incorporate both the build artifacts and the dependencies within the same module in the published build-info, utilize the --module option with the following commands:

```
jf rt dotnet build <PACKAGE_NAME> --module my-module-name --build-name=my-build-name --build-number=1
jf rt u example.1.0.0.nupkg <LOCAL_REPOSITORY_NAME> --module my-module-name --build-name=my-build-name --build-number=1

jf rt bp --build-name=my-build-name --build-number=1
```
Keep in mind that the resulting build will be published under a single module, and it's important to note that the module type will be generic.

### Packaging and Publishing Terraform Modules

Expand Down
Loading