Skip to content

Commit c146c59

Browse files
author
Abhishek Kumar Singh
committed
2 parents 5fdbd3b + 23fbd7e commit c146c59

File tree

2 files changed

+9
-13
lines changed

2 files changed

+9
-13
lines changed

PromoteToView-Extension/PromoteToView/PromoteNuGetPackages.ps1

Lines changed: 1 addition & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,3 @@
1-
#===================================================================================================================================================#
2-
# The script retrieves package versions from the installation path and promotes them to a specific view in an Azure DevOps feed via the REST API. #
3-
# #
4-
# Author: Abhishek Kumar Singh #
5-
# Date: 11.04.2025 #
6-
#===================================================================================================================================================#
7-
8-
# Debugging
9-
# .\PromoteNuGetPackages.ps1 -feedName "TestPromote" -feedScoped "Organization" -view "Release" -nugetPackageMappingFilePath "D:\Extensions\Inputs to Extensions\NugetPackageMapping.psd1"
10-
# $devBaseUrl = "https://pkgs.dev.azure.com/AbhishekORG"
11-
# $SYSTEM_ACCESSTOKEN = "DDum5iuo3u19wZkj3F5Ed59GI58bPi8nNBe5mH0dBHvlImgjqPiOJQQJ99BGACAAAAAsmWmDAAASAZDO4fei"
12-
131
[CmdletBinding()]
142

153
param (
@@ -66,4 +54,4 @@ foreach ($package in $nugetPackageVersionMapping.GetEnumerator()) {
6654
$packageVersion = $package.Value
6755

6856
PromoteNuGetPackageToFeed -packageName $packageName -packageVersion $packageVersion
69-
}
57+
}

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# 🚀 Built Custom Azure DevOps Pipeline Extension! 🚀
2+
🔧 Powering CI/CD with Flexibility, Automation, and Control
3+
4+
Building a custom Azure DevOps extension from the ground up and publishing it to use in internal and potentially public pipelines.
5+
This wasn’t just about code — it was about understanding the internals of Azure DevOps pipelines, YAML tasks, custom inputs, PowerShell/Node handlers, and packaging them for scale and reuse.
6+
7+
💡 Why a custom extension?
8+
Because sometimes, the built-in tasks just don’t cut it, and custom automation is the key to unlocking consistency across complex deployments.

0 commit comments

Comments
 (0)