{"id":42805,"date":"2018-04-27T15:06:14","date_gmt":"2018-04-27T15:06:14","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/devops\/?p=42805"},"modified":"2019-02-14T15:50:05","modified_gmt":"2019-02-14T23:50:05","slug":"vsts-public-projects-limited-preview","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/vsts-public-projects-limited-preview\/","title":{"rendered":"VSTS Public Projects Limited Preview"},"content":{"rendered":"

Visual Studio Team Services (VSTS)<\/span><\/a> offer<\/span>s<\/span> a suite of <\/span>DevOps capabilities to developers including Source control, Agile planning, Build, Release, Test and more<\/span>. B<\/span>ut <\/span>until now <\/span>all these <\/span>features<\/span> require the user to first login using a Microsoft Account<\/span> before <\/span>they<\/span> can<\/span> be used<\/span>.<\/span>\u00a0<\/span><\/p>\n

Today<\/span>, we\u2019re<\/span> starting <\/span>a <\/span>limited <\/span>preview of a new capability that will<\/span> eventually <\/span>extend the powerful features of VSTS to <\/span>the <\/span>open source <\/span>community<\/span>. <\/span>Starting <\/span>today, we\u2019re<\/span> working with a small number of\u00a0<\/span>open source projects to <\/span>begin<\/span> testing this experience in beta before rolling <\/span>it <\/span>out to a wider <\/span>set of projects.<\/span> I<\/span>n this blog post<\/span>,<\/span> we <\/span>want to give you a<\/span>n early look into <\/span>what this new feature<\/span> does and why we\u2019re building it.<\/span>\u00a0<\/span><\/p>\n

Introducing Public Project<\/span><\/b>s<\/span><\/b> in VSTS<\/span><\/b>\u00a0<\/span><\/h5>\n

With <\/span>p<\/span>ublic <\/span>p<\/span>rojects<\/span>,<\/span> users <\/span>will for the first time be able to mark<\/span> a <\/span>VSTS <\/span>T<\/span>eam <\/span>P<\/span>rojec<\/span>t<\/span><\/a> as public<\/span>. This <\/span>will <\/span>enable<\/span> anonymous users to <\/span>be able to <\/span>view the contents of that project<\/span> in a read-only state<\/span> enabling <\/span>collaboration with <\/span>anonymous (un-authenticated) users<\/span> that wasn\u2019t possible before<\/span>.<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

\"Control<\/a><\/p>\n

A<\/span>nonymous user<\/span>s<\/span> will largely see<\/span> the same <\/span>views <\/span>as authenticated <\/span>users<\/span>,<\/span> with non-public <\/span>functionality<\/span> such as<\/span> settings, or actions <\/span>(such as <\/span>queue build<\/span>) <\/span>hidden<\/span> or <\/span>disabled. <\/span>As we <\/span>continue to work<\/span> on <\/span>public <\/span>project support we <\/span>will <\/span>be <\/span>improving the views<\/span>, especially<\/span> for <\/span>un-authenticated <\/span>users<\/span>.<\/span>\u00a0<\/span><\/p>\n

\"Authenticated<\/a><\/h5>\n
How does it work?<\/span><\/b>\u00a0<\/span><\/h5>\n

In this initial preview, when you mark a project public, the <\/span>B<\/span>uild, <\/span>R<\/span>elease, <\/span>Git repos<\/span>, <\/span>D<\/span>ashboard<\/span>s<\/span> and<\/span> a subset of <\/span>W<\/span>ork will appear visible to the anonymous user<\/span>s visiting your project through a publicly accessible URL that does not require any authentication<\/span>.\u00a0 <\/span>After <\/span>working with some projects to get <\/span>early feedback, we plan to <\/span>hopefully <\/span>make the<\/span> full contents of <\/span>a public <\/span>project visible, including<\/span> additional<\/span> areas such as <\/span>Test and <\/span>Package<\/span> Management,<\/span> allowing <\/span>users<\/span> to host NuGet, Maven and <\/span>npm<\/span> feeds for <\/span>their<\/span> projects<\/span>\u2019<\/span> CI builds<\/span>.<\/span>\u00a0<\/span><\/p>\n

Public projects <\/span>are <\/span>an entirely opt-in experience<\/span> in whic<\/span>h account a<\/span>dministrators <\/span>have <\/span>full control over <\/span>who can enable this functionality<\/span>. <\/span>The default for<\/span> existing VSTS account<\/span>s<\/span> will be <\/span>private; the a<\/span>ccount <\/span>administrator will need to <\/span>first<\/span> enable <\/span>P<\/span>ublic <\/span>P<\/span>roject<\/span> su<\/span>pport for the account<\/span> and then specially set a<\/span>n individual<\/span> project to be public.<\/span>\u00a0<\/span><\/p>\n

A p<\/span><\/b>ractical <\/span><\/b>example: <\/span><\/b>.NET Core CLI<\/span><\/b>\u00a0<\/span><\/h5>\n

Supporting <\/span>open source <\/span>development is one of the most <\/span>compelling<\/span> scenarios for <\/span>p<\/span>ublic <\/span>p<\/span>rojects.\u00a0 A good example is the <\/span>.N<\/span>ET<\/span> Core CLI<\/span><\/a>.\u00a0 Their source is hosted on GitHub <\/span>and <\/span>they use VSTS for their CI builds. However<\/span>,<\/span> today <\/span>if you click on the build badges in their <\/span>readme<\/span><\/a>, unless you <\/span>were one of the maintainers of that <\/span>project<\/span>, you will not be able to see the build results.\u00a0 Since this is an open source project, <\/span>everybody<\/span> should be able to view th<\/span>e<\/span> full <\/span>results<\/span> so they can see why a build failed and maybe even send a pull request to help fix it<\/span>.\u00a0<\/span>\u00a0<\/span><\/p>\n

Thanks to <\/span>p<\/span>ublic <\/span>p<\/span>rojects capabilities<\/span>, <\/span>the team<\/span> will<\/span> be able to<\/span> enable just that<\/span> experience<\/span> and <\/span>everyone in the community will have access to the same build results, regardless of if they are a maintainer on the project or not<\/span>.<\/span>\u00a0<\/span><\/p>\n

Road Ahead<\/span><\/b>\u00a0<\/span><\/h5>\n

We are incredibly excited to be able to offer the power of our cloud hosted Mac, Linux and Windows build servers to the world<\/span>,<\/span> and make it easier for developers to create an automated build pipeline for their projects.<\/span> For open source projects<\/span>, <\/span>the build and release capabilities of <\/span>VSTS\u2019s <\/span>and <\/span>support for<\/span> p<\/span>ublic <\/span>p<\/span>r<\/span>ojects<\/span> will be<\/span> a <\/span>great <\/span>complement to <\/span>functionality in <\/span>GitHub<\/span>, where many <\/span>community developers<\/span> collaborate on projects<\/span>.<\/span>\u00a0<\/span><\/p>\n

As we strive <\/span>to<\/span> get the experience right <\/span>for <\/span>the community, we’ll be<\/span> working with a small group of <\/span>open source project maintainers <\/span>b<\/span>efore <\/span>mak<\/span>ing<\/span> this functionality <\/span>available <\/span>to the rest of our community<\/span>. <\/span>Following <\/span>this initial <\/span>testing, we\u2019ll share more details<\/span> which will include <\/span>update<\/span>s to<\/span> our license<\/span> and pricing<\/span> to enable project members working on <\/span>open source<\/span> projects<\/span> to <\/span>use VSTS for<\/span> free<\/span>.<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

To <\/span>apply to <\/span>sign up<\/span> to the early <\/span>preview<\/span>,<\/span> tell us about which projects you want to use this for by emailing our team at:<\/span> vsts-public@microsoft.com<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

\n<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Visual Studio Team Services (VSTS) offers a suite of DevOps capabilities to developers including Source control, Agile planning, Build, Release, Test and more. But until now all these features require the user to first login using a Microsoft Account before they can be used.\u00a0 Today, we\u2019re starting a limited preview of a new capability that […]<\/p>\n","protected":false},"author":253,"featured_media":45953,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[228,226,1,230,249,251],"tags":[],"class_list":["post-42805","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-admin-licensing","category-ci","category-devops","category-directions","category-open-source","category-security"],"acf":[],"blog_post_summary":"

Visual Studio Team Services (VSTS) offers a suite of DevOps capabilities to developers including Source control, Agile planning, Build, Release, Test and more. But until now all these features require the user to first login using a Microsoft Account before they can be used.\u00a0 Today, we\u2019re starting a limited preview of a new capability that […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/42805","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/253"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=42805"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/42805\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/45953"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=42805"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=42805"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=42805"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}