Visual Studio Community Continuous Deployment Jenkins

The Continuous Delivery Tools for Visual Studio extension makes it simple to automate and stay up to date on your DevOps pipeline for ASP.NET and other projects targeting Azure. The tools also allow to improve your code quality and security.

This version of the extension is only available for Visual Studio 2017 RC.3 and above. A previous version of the extension was automatically installed as part of the .NET Core preview workload in RC.2.

The Continuous Delivery Tools for Visual Studio is a Technology Preview DevLabs extension.

Automatically detect secret settings in project source code
You can now detect secret settings in project source code to prevent them from being checked in to source control. Suppose you have an Azure credential, such as a SQL Azure connection string saved in a project file. Open the file. You will see squiggly on the line containing the secret, and an entry in the Error List. This is helpful to prevent secret settings from being checked in to source control for security purposes.

To learn more about how to securely persist secret settings, checkout the How to fix the secrets detected by the CredScan code analyzer

NOTE: the analyzer only works on project files opened in Visual Studio. If you close a file, the detected result will disappear.

Heads-up information on Build and Code Analysis Results on Commit

Early remediation of issues in your code is a key way to drive quality and improve your team's productivity. With the new Build and Code Analysis Results panel, you get a heads-up reminder at commit-time of issues detected by any code analysis tool that puts results in the error list. This means you can take care of those issues before they propagate into your team's CI/CD process, and commit with confidence.

The panel shows results both for live edit-time analysis (e.g. C#/VB Analyzers) and, via the Refresh Analysis button, for batch-style static analysis (e.g. C43;43; Static Analysis tools). It is supported on Visual Studio 2017 Enterprise. At present it supports code being committed to a Git Repo.

In response to your feedback, the panel now shows issue counts only for files that are changed in the set of files you are committing, so that you can focus only on the issues related to your changes. View Issues will let you see a view of the Error List filtered to just the changed files too.

You can tell us more about what you think about this new feature by filling out a short survey.

Build notifications for any CI run on Visual Studio Team Services

Things move fast when you have an automated DevOps pipeline that ships code to your customers several times a day. However, thanks to new build notifications feature, you can now learn about build issues as soon as they occur without having to switch context away from your development environment.

Build notifications are scoped to build events requested on behalf of accounts on your keychain and associated with the solution that's currently open. As such, you don't have to worry about getting flooded with notifications or even with notifications that are not contextual or relevant to you.

Work item notifications for any work item that is assigned to you

You can also stay on top of important VSTS work items assignments, thanks to the new work item notifications feature. With this feature you'll learn about new work items as soon as they are assigned to you without having to switch context away from your development environment.

You will not be bothered with multiple notifications of several items are being updated at the same time. Notifications will be batched and you will only be presented with a single notification.

Open any of your VSTS hosted solutions on the Visual Studio IDE, and you will be automatically notified via the new Toast notification mechanism.

Notifications tool window integration

The new toast notification appears in the top right corner of the IDE, and whenever not acted upon or dismissed by you, it retracts to the notification flag, indicating it can be found inside the Notifications tool window.

Automate the build and deployment of any ASP.NET project

From the ASPNET project menu click "Configure Continuous Delivery..." to setup an automated Build and Release definition that can deploy your ASP.NET project to an Azure App Service or Azure Container Service.

Use it to quickly setup an automated 'Dev' or 'Test' environment. Then add additional steps like "manual checks" to configure staging and production deployments from Visual Studio Team Services. Visual Studio Team Services will trigger a build and deployment for the source repository after every Git Push operation.

To learn more about how to setup and benefit from a CI/CD pipeline, checkout the get started guide.

The extension allows you to configure Continuous Delivery to Azure App Services, Web Containers and Service Fabric Clusters for ASP.NET and ASP.NET Core projects under source control on GitHub or VSTS. It supports both TFVC and Git repos.

Release Notes:

Version: 0.4.211.1649

1. The extension is not compatible with Visual Studio 2019. This update fixes an issue where the extension would try to install to Visual Studio 2019, then fail. With this update, installation to Visual Studio 2019 is blocked.

Version: 0.4.210.44124

1. Azure Devops compatibility
2. Assorted bug fixes

Version: 0.4.174.2830

1. Assorted bug fixes

Version: 0.4.173.6850

1. Added support for CICD on Azure function apps
2. Assorted bug fixes

Version: 0.4.132.17223

1. Build and Work Item notifications now support TFVC repos

Version: 0.4.122.16101

1. Fixes an issue where the extension would fail to load
2. Assorted bug fixes

Version: 0.4.66.9081

1. New toast notification mechanism
2. Added button to provide feedback from toast notifications
3. Notification integration with the Notifications tool window
4. Assorted bug fixes

Version: 0.4.28.54201

1. Assorted bug fixes.

Version: 0.4.9.4324

1. Credential scanner crash fixed.
2. Assorted bug fixes.

Version: 0.3.510.42958

1. Assorted bug fixes.

Version: 0.3.493.58515

1. Fixed an issue that would cause notifications from VSTS to be shown twice
   2. Added CredScan Code Analyzer to detect secret settings. Known issue: the analyzer only works on project files opened in Visual Studio. If you close a file, the detected result will disappear

Version: 0.3.439.12417

1. Fixed an issue preventing auto-update of the extension for some users

Version: 0.3.438.6810

1. Added support for configuring continuous delivery to TFVC repos hosted on visualstudio.com
2. Added new notifications for Work Items from VSTS assigned to you
3. Fixed a variety of bugs around SSH remotes for VSTS and GitHub
4. Assorted other bug fixes and polish

Version: 0.3.387.64656

1. Fixes a bug when configuring CICD on a solution not under source control
2. Other assorted bug fixes

Version: 0.3.360.58237

1. Enables creation of new Azure Container Registry when configuring CICD to App Service (Linux) or Service Fabric Cluster
2. Bug fixes and reliability improvements

Version: 0.3.275.25451

1. Sorts the App Service Host selection list to display "App Service (Linux)" as the default

Version: 0.3.274.54004

1. Fixes a bug when configuring CICD on a solution not under source control
2. Switches the name of the release environment created for CICD from 'Production' to 'Dev'

Version: 0.3.271.47084

1. Enables filtering Build and Code Analysis on changed files

Version: 0.3.269.62949

1. Fixes a bug where App Services on Linux were not being configured correctly to use the selected Azure Container Registry.

Version: 0.3.268.17844

1. Assorted bug fixes, reliability fixes, and performance improvements.
2. Enable creation of new App Services on Linux.
3. Set the Docker image name from the docker-compose file.

Version: 0.3.216.5157

1. Assorted bug fixes, reliability fixes, and performance improvements.
2. Show only valid location choices for app service creation.
3. Select matching ACR by default for app services that are already configured with one.
4. Minor UI tweaks.

Version: 0.3.168.56876

1. Assorted bug fixes and usability improvements.

Version: 0.3.112.7525

1. Fixed a bug where spaces in a repo name would cause CICD setup to fail.

Version: 0.3.111.7525

1. Fixed a bug preventing CICD setup to an existing App Service
2. Fixed a bug when pasting a GitHub PAT with leading or trailing whitespace
3. Fixed a bug where all available Azure Container Registries in a subscription were not listed

Version: 0.3.105.11995

1. Static Analysis on Commit to ensure better product quality
2. Success and failure build notification for all your CI and manual builds
3. Status bar button changes to highlight the state of the last received build notification
4. Support for configure CD of solutions containing ASP.NET and ASP.NET Core projects.
5. Configure CD of solutions with Docker Compose to App Service Linux.
6. Configure CD of solutions with Docker Compose to Service Fabric Cluster.

Version: 0.3.29.47597

1. Adds support for CICD configuration to App Service for ASP.NET Core projects
2. Minor bug fixes

Version: 0.3.18.52138

1. Fixed an permissions issue related to using a Microsoft account to configure CICD to an AAD-backed VSTS account
2. Minor fixes for usability and reliability

Version: 0.2.235.55646

1. Bug fixes and minor improvements.

Version: 0.2.189.9278

1. Added support for configuring CI/CD on repos hosted on GitHub
2. Build notifications now listen across all definitions in your Team Project and will appear for CI, Manual or PR builds requested by you.
3. Many bug fixes and usability improvements.

Version: 0.2.109.18451

1. Hot fix for a change in AppService CI/CD configuration.

Version: 0.2.108.1548

1. Removed the dependency on Team Explorer for build failure notification.
2. Added support for independent user account selection for VSTS Accounts and Azure Subscription in the Configure Continuous Delivery dialog.
3. Other bug fixes and minor improvements.

It's all about feedback…

Over the coming days, weeks, and months we'll update the extension with improvements based on your feedback, new experiences to try, and of course bug fixes.

We're interested in hearing how we can help improve the speed of delivering software to customers. If you are interested in sharing your feedback ping us at vsDevOps@microsoft.com.

gravesflefted.blogspot.com

Source: https://marketplace.visualstudio.com/items?itemName=VSIDEDevOpsMSFT.ContinuousDeliveryToolsforVisualStudio

Share this post