Progetによって.NETライブラリーのCIとビルド管理
チームの人数が少なすぎますとビルドとテストの時間が減ってしまいます。Progetを使えば簡単に数個のフィードを立て、社内でも社外でもNugetパケージを提供することができます。それによって、どのビルドがどうなっているかすぐ解ることができます。しかも、Nugetパケージ自体を使ってテストすれば、nuget.orgにそのままリリースできます。Couchbaseではこの方法を使って1週間おきにデベロッパー版を出すことができます。Progetを効果的に使いましょう!
If your team is too small, it can lead to time loss for build and testing . With Proget, you can set up several feeds and offer Nuget package builds both inside and outside the company. Using this, it is easy to determine what is happening with every build. Furthermore, if you test with the actual Nuget package, you can release it as-is to nuget.org. At Couchbase, I use this process to release a developer build every other week. Let's learn some ways to use Proget effectively!
Outline/Structure of the Lightning Talk
Lightning Talkなので、数個のスライドと基本的な解説になります。
This is a lightning talk, so just a few slides and some short explanation.
Learning Outcome
Progetを使えば、.NETライブラリーのCIがどんなに楽になるか解ります。
Learn how much less hectic .NET library CI can be with Proget.
Target Audience
ビルド管理者、QE部、開発者
Links
https://inedo.com/proget
schedule Submitted 3 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Alex Papadimoulis / Tsuyoshi Ushio - DevOpsDays Tokyo Opening
Alex PapadimoulisPresident and FounderInedoTsuyoshi UshioSenior Software EngineerMicrosoft Corporationschedule 3 years ago
30 Mins
Keynote
Beginner
We will open the DevOpsDays Tokyo conference by giving a brief introduction of DevOps, the purpose and goals of the conference, as well as giving some of the sponsors an opportunity to introduce themselves.
-
keyboard_arrow_down
Alex Papadimoulis - DevOps for Japan
45 Mins
Talk
Beginner
DevOps represents a simple idea: increase collaboration across teams while automating processes. Although the concept is relatively new to Japan, American IT organizations have been trying to implement DevOps in recent years: many have found success, while others have seen failure.
One of main causes of failure is adopting the wrong culture. Although companies like Netflix and Etsy dominate the DevOps conversation, most enterprises do not have the same problems to solve, nor do they employee the same types of engineers. Thus simply, attempting to emulate Netflix will often yield failure.
It’s similar in Japan; the culture of Japanese IT organizations are quite different from western companies, and attempting to emulate western DevOps practices will often result in failure and other setbacks. Thus, in order to be successful with adopting DevOps practices, those practices must first be adapted for Japan.
In this talk, I’ll compare and contrast the unique cultural differences in Japanese IT organizations and discuss how you can adopt DevOps practices that specifically address those.
-
keyboard_arrow_down
Alex Papadimoulis - WinOps: A DevOps tool roundup for Windows
20 Mins
Talk
Intermediate
Windows and Linux are very different; not just technologically, but philosophically. Tools are a major component to establishing DevOps, and the lack of Windows-centric tools limited early Windows DevOps adoptions as most initial supporting technologies emerged from Linux and open-source communities. WinOps strives to address the same challenges as DevOps, using different tools with a Windows approach.
This talk will be tool-focused, and give an overview of the major tools used in Windows DevOps environments.
-
keyboard_arrow_down
Alex Papadimoulis - Building a DevOps Culture in a Windows Environment
45 Mins
Talk
Beginner
DevOps tools and practices have traditionally been Linux-focused, which has presented a significant adoption hurdle in Windows-based organizations. Windows sysadmins rarely need to use a command line to do their job, let alone Ruby, Git, or other tools. Although tool vendors have tried to make “Windows versions” of their Linux tools, and Microsoft has tried adding “Linux features” to the Windows, many organizations still view DevOps as a square peg in a round hole.
To bring DevOps to Windows-based organizations, it’s important to not only understand the cultural differences between Windows and Linux, but learn how you can build a process that truly crosses development and operation silos, and doesn’t just become “the DevOps team”.