I was working on Artifactory Pro version but thought of upgrading due to its limitations. I was confused which version of artifactory to use such that I get XRay license as well. I was more into buying the Artifactory Enterprise version but as I can see the pricing on this page, xray-pricing, I am a bit confused.
It shows JFrog XRay HA(Add-on option). Correct me if I am wrong, does this mean that JFrog XRay will come with the enterprise edition but for the HA version of XRay, I will have to pay?
Related
Can JFrog Artifactory be used to store deployment artifacts for promotion, for applications developed with Visual Studio ?
Also, can JFrog Artifactory be used for API deployment and DataBase deployment?
If the requirement is to have the .NET projects perform build and store artifacts from Visual Studio against the Artifactory, please follow the instructions here. Additionally, if the query regarding API deployment is around the programmatic access against the Artifactory instance, please refer to Artifactory REST API wiki.
I'm a little confused over the latest released versions of Azure DevOps Server 2020 on 17th May.
What is the difference between 2020.0.2 and 2020.1.2 and why are two versions of 2020 being maintained?
Currently running 2020.0.1 and looking to move to latest version.
The main difference should between Server Version RC and RTW. The data migration tool doesn't support imports from Azure DevOps Server release candidates (RC). If you're planning on importing your collection database to Azure DevOps Services using this service, it's important that you don't upgrade your production database to an RC release. If you do upgrade, then you will need to wait and upgrade to the release to web (RTW) version when it's available or restore a backup copy of your database from a previous Azure DevOps Server version to import.
From the Release on May 17, 2022, along with several fixes, the Data Migration tool will be available for both Sever 2020.0.2 and 2020.1.2
Before preparing for upgrade, check this official doc: Upgrade your deployment - Azure DevOps Server & TFS | Microsoft Docs
In my project, there is a requirement to create Azure artifacts feed automatically.
For this I used REST API mentioned in this doc: https://learn.microsoft.com/en-us/rest/api/azure/devops/artifacts/feed%20%20management/create%20feed?view=azure-devops-rest-5.0
and used python to create feed.
POST https://feeds.dev.azure.com/{organization}/_apis/packaging/feeds?api-version=5.0-preview.1
It worked fine.
Later I saw that a new version of API was available.
It is not easy to change the code every time there is a new API version.
So the question is how to identify/use the latest stable working version of API always?
Sorry, there wasn't a hint if there is a new Rest API version released. But just like Matt commented, the old version will not stop working in general. It's quite stable.
Azure DevOps and Team Foundation Server REST APIs are versioned to ensure applications and services continue to work as APIs evolve.
Major API version releases align with Team Foundation Server RTM releases. For example, the 3.0 API set was introduced with Team Foundation Server 2017.
You'll find a quick mapping of REST API versions and their corresponding TFS releases here. All API versions will work on the server version mentioned as well as later versions.
Unlike Azure DevOps Server/TFS, if you are working on Azure DevOps Service, you do not have to pay too much attention which version you are using. It's supported on 1.0~6.0.
Hope it is clearly.
GitHub released this nice feature to create PR templates[1]. Me and my team wanted to leverage that. However,I couldn't get it to work in enterprise git.
Is the new feature not available in GitHub Enterprise yet?
[1]https://github.com/blog/2111-issue-and-pull-request-templates
The pull request template feature is not available in GitHub Enterprise as of March 12, 2016. The latest releases of GitHub Enterprise are 2.5.1, 2.4.5, 2.3.9, 2.2.15, and 2.1.20. Features introduced at GitHub.com may make their way into GitHub Enterprise, but it is not guaranteed. For instance, Jupiter notebook support was added to GitHub.com on May 7, 2015, but has not yet made its way into GitHub Enterprise.
GitHub Enterprise release notes can be found here
I have been looking at self hosting NuGet, having a hard time understanding how to set it up and how it would help support our development process.
Does anyone have any recommendations as to which to use, how to set it up?
Or should I just use a hosted service?
After looking around at various solutions--self-hosted and hosted service--we chose to go with ProGet.
ProGet Summary
ProGet has a standard "free" license and nominal licensing fees (single year and perpetual) for the enterprise version. We currently use the standard "free" version and have no real complaints. You can create as many feeds as you want, add as many users as you want, etc. (We created "Testing", "Staging", and "Production" feeds to be part of our quality assurance process.) The only real limit in the free version is the inability to filter external feeds for specific packages you want included in your ProGet feeds. This filtering feature is managed with "connectors". With the enterprise version--when you create a feed--you can optionally add a "connector" to pull in packages from other feeds (external or internal).
ProGet With Nuget Package Management and Creation
The steps for creating a nuget package itself I'll leave to David Ebbo's popular blog post, http://blog.davidebbo.com/2011/04/easy-way-to-publish-nuget-packages-with.html. However, know that for uploading packages you can upload via the ProGet packages administration web UI, command-line nuget.exe, or the Nuget Package Explorer.
ProGet Installation, Configuration, and Activation
Installing, configuring and activating ProGet was the least intuitive part. It can install backed by a regular SQL Server database or a SQL Server Express db. Furthermore, it can also be a self-hosted app or run under IIS. If you need to perform offline activation or want to request different license keys go to my.inedo.com and create an account and you can do everything from there.
Proget Quality Control & CI
CI with TeamCity is something we are going to need so we are looking at creating a nuget package build process using TeamCity's Nuget server. There's a how-to for creating the packages I'll post in a comment. The next step would be to automatically publish the TeamCity-created nuget packages over to the appropriate ProGet feeds (ie. "Testing", "Staging", "Production") perhaps utilizing command-line Nuget with an API key.
Further Information
We looked at MyGet as a hosted service but it seemed to trip up on simple scenarios like adding another contributor/user. It also jumped quite a bit in price when needing more than just two contributor accounts. Whereas with ProGet you get unlimited user accounts with the free version alone.
One more side note: For publishing OSS type projects/packages, I'd take a look at Chocolatey as a solution.
Another option for self hosting is using the NuGet.Server package and creating an IIS website to host it on your internal network, although it won't scale very well if you plan to publish more than a handful of packages.
I've created a fork of NuGet.Server that uses a Lucene.Net index to fix these performance issues. Downloads are available from https://github.com/themotleyfool/Klondike/releases.
To keep this thread up-to-date, Visual Studio Team Services also has a package manager in preview. See the marketplace: Package Management
You can create an empty Asp.Net Web Application and install Nuget.Server from Nuget Gallery. This is a free option of self hosting your own Nuget packages on IIS. Check the documentation