Download ebooks file (Ebook) Azure DevOps for Web Developers: Streamlined Application Development Using Azure DevOps Features by Ambily K K ISBN 9781484264119, 9781484264126, 1484264118, 1484264126 all chapters
Download ebooks file (Ebook) Azure DevOps for Web Developers: Streamlined Application Development Using Azure DevOps Features by Ambily K K ISBN 9781484264119, 9781484264126, 1484264118, 1484264126 all chapters
com
OR CLICK HERE
DOWLOAD EBOOK
(Ebook) Biota Grow 2C gather 2C cook by Loucas, Jason; Viles, James ISBN
9781459699816, 9781743365571, 9781925268492, 1459699815, 1743365578, 1925268497
https://ebooknice.com/product/biota-grow-2c-gather-2c-cook-6661374
ebooknice.com
(Ebook) DevOps for Azure Applications: Deploy Web Applications on Azure by Suren
Machiraju, Suraj Gaurav ISBN 9781484236420, 9781484236437, 1484236424, 1484236432
https://ebooknice.com/product/devops-for-azure-applications-deploy-web-
applications-on-azure-7146742
ebooknice.com
(Ebook) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right
Way by Jeffrey Palermo ISBN 9781484253434, 1484253434
https://ebooknice.com/product/net-devops-for-azure-a-developer-s-guide-to-
devops-architecture-the-right-way-50195174
ebooknice.com
(Ebook) Implementing Devops with Microsoft Azure by Mitesh Soni ISBN 9781787127029,
1787127028
https://ebooknice.com/product/implementing-devops-with-microsoft-azure-7164892
ebooknice.com
(Ebook) Hands-on Azure Pipelines: Understanding Continuous Integration and
Deployment in Azure DevOps by Chaminda Chandrasekara, Pushpa Herath ISBN
9781484259016, 1484259017
https://ebooknice.com/product/hands-on-azure-pipelines-understanding-continuous-
integration-and-deployment-in-azure-devops-11295326
ebooknice.com
(Ebook) Matematik 5000+ Kurs 2c Lärobok by Lena Alfredsson, Hans Heikne, Sanna
Bodemyr ISBN 9789127456600, 9127456609
https://ebooknice.com/product/matematik-5000-kurs-2c-larobok-23848312
ebooknice.com
https://ebooknice.com/product/hands-on-azure-repos-understanding-centralized-
and-distributed-version-control-in-azure-devops-services-50195564
ebooknice.com
https://ebooknice.com/product/hands-on-azure-repos-understanding-centralized-
and-distributed-version-control-in-azure-devops-services-53001822
ebooknice.com
(Ebook) SAT II Success MATH 1C and 2C 2002 (Peterson's SAT II Success) by Peterson's
ISBN 9780768906677, 0768906679
https://ebooknice.com/product/sat-ii-success-math-1c-and-2c-2002-peterson-s-sat-
ii-success-1722018
ebooknice.com
Azure DevOps
for Web
Developers
Streamlined Application Development
Using Azure DevOps Features
—
Ambily K K
Azure DevOps for
Web Developers
Streamlined Application Development
Using Azure DevOps Features
Ambily K K
Azure DevOps for Web Developers: Streamlined Application Development Using
Azure DevOps Features
Ambily K K
Hyderabad, India
Introduction�����������������������������������������������������������������������������������������������������������xvii
v
Table of Contents
vi
Table of Contents
vii
Table of Contents
Releases����������������������������������������������������������������������������������������������������������������������������������� 204
Creating a Release Pipeline������������������������������������������������������������������������������������������������� 205
Library��������������������������������������������������������������������������������������������������������������������������������������� 215
Variable Groups������������������������������������������������������������������������������������������������������������������� 215
Secure Files������������������������������������������������������������������������������������������������������������������������� 216
Task Groups������������������������������������������������������������������������������������������������������������������������������ 217
Deployment Groups������������������������������������������������������������������������������������������������������������������� 220
Sample Build and Release Implementation������������������������������������������������������������������������������ 220
Build and Release of an Angular Application����������������������������������������������������������������������� 221
Build and Release of a .NET Application������������������������������������������������������������������������������ 224
Summary���������������������������������������������������������������������������������������������������������������������������������� 226
viii
Table of Contents
Index��������������������������������������������������������������������������������������������������������������������� 257
ix
About the Author
For more than a dozen years Ambily has worked on cloud
adoption and accelerating software delivery through DevOps.
As the head of Azure, DevOps, and UI practices at TCS
HiTech Industry, she supports major public- and private-
sector companies across the globe in their cloud journeys
and DevOps implementations. Ambily blogs about her
experiences and speaks at conferences to share what she has
learned. You can find her blog at https://ambilykk.com/.
xi
About the Technical Reviewer
Swapneelkumar Deshpande is a software engineer. He is
a Microsoft Certified Professional and Microsoft Certified
Trainer. Swapneel has been working and leading teams in
various aspects of the software development life cycle for
more than 20 years.
xiii
Acknowledgments
Writing a book is harder than I thought and more rewarding than I could have ever
imagined. I’m grateful to my teachers, and I’ve been lucky enough to have a lot of great
teachers, but one in particular shaped the person I am today: Minu K K. My heartfelt
thanks to him for being an inspiration throughout my life.
I am grateful to my loving husband, Rajeev, for all his support and caring. To my little
children, Pranav and Pavitra: thank you for letting me spend time on writing.
A very special thanks to my mentor, Bala Peddigari, who inspired me to write articles
and books.
Finally, to all those who have been part of my getting there: Smriti Srivastava,
Matthew Moodie, Shrikant Vishwakarma, and Swapneelkumar Deshpande.
xv
Introduction
DevOps is one of the mandatory elements of the entire IT spectrum, which integrates
people, process, and technology with an objective of delivering value faster. At the same
time, DevOps comes in many varieties with varying levels of understanding, which
can be an obstacle for many implementations. In this book, we will explore the various
concepts of DevOps and take you on a DevOps journey using Azure DevOps. We’ll look
at the end-to-end process of DevOps implementation using Azure DevOps.
Specifically, the following are the topics covered:
• Requirement management
• Test management
• Test management
• Continuous feedback
Also, we will discuss the current IT landscape and how we can leverage the benefits
of DevOps in various areas such as support projects. Every concept will be covered from
different perspectives, including a novice view, a DevOps developer view, a DevOps
architect view, and a business view.
This book is intended for novices in DevOps who want to learn the concepts of
DevOps across a modern application spectrum. Also, it provides enough information for
DevOps engineers to fine-tune their skills in various aspects of DevOps.
xvii
CHAPTER 1
DevOps Basics
and Variations
Software development processes and the release requirements can change over time
in order to continue bringing value to customers and gaining market adoption. To
scale up and get some early feedback, many organizations have adopted a frequent
release methodology for new features or defect fixes. These releases are deployed to the
production system as often as once a week, and sometimes they are even once a day,
once an hour, or even every ten seconds. To maintain this edge in the market or gain this
quick feedback cycle, companies are adopting DevOps practices such as continuous
delivery and continuous deployment. In this chapter, you will get an introduction to
DevOps concepts and practices.
S
oftware Development
The software development industry gradually adopted the agile model after many
years of following the waterfall model. The agile development model provides the
ability to adapt to changing requirements, and it offers better collaboration between
teams and improved productivity. In a waterfall model, application development is
done as a sequential operation, and the application is released at the end of the project.
Sometimes, though, the development process takes a long time to complete, and the
relevance of lot of features envisioned at the start may not be useful anymore. Moreover,
this approach lacks the end-user feedback loop, the expectations of the end user and any
feedback will be received only after the entire development/deployment is complete.
The agile process demands the release of finished features (production-ready) more
frequently to receive early feedback from customers and respond accordingly. Agile
without DevOps takes more cycle time and manual involvement. DevOps addresses the
1
© Ambily K K 2020
A. K K, Azure DevOps for Web Developers, https://doi.org/10.1007/978-1-4842-6412-6_1
Chapter 1 DevOps Basics and Variations
D
evOps
DevOps is one of the hottest topics in the IT field, but it has many different variations. If
ten people started discussing DevOps, they would have ten different explanations for it.
Here is a popular definition of DevOps from https://en.wikipedia.org/wiki/DevOps
shows the process angle of DevOps, in other words, how we can use the single process
across the development and operations teams:
DevOps is a software development methodology that combines software
development (Dev) with information technology operations (Ops).
The following definition from https://searchitoperations.techtarget.com/
definition/DevOps. DevOps is defined from a person’s perspective, specifying how the
team culture changes and enables more collaborative working environments.
DevOps is the blending of the terms development and operations, meant to
represent a collaborative or shared approach to the tasks performed by a
company's application development and IT operations teams.
In the following definition, defines DevOps from a technical perspective, where DevOps
is for automating end-to-end development processes (www.atlassian.com/devops):
DevOps is a set of practices that automates the processes between software
development and IT teams, in order that they can build, test, and release
software faster and more reliably.
2
Chapter 1 DevOps Basics and Variations
Considering the importance of DevOps in the IT industry and the fact that DevOps is
an integral part of software development, let’s discuss these different possibilities of what
it encompasses.
DevOps is a combination of cultural elements, practices, and tools for delivering
value at a higher velocity. DevOps consists of people, process, and technology.
Technology enables the automation of an end-to-end pipeline for delivery. Moreover,
using the proper tools increases a team’s collaboration. The agile process provides agility
in execution, collaboration between teams, management of end-to-end activities, and
an innovative team culture. DevOps culture means people are trained on multiple skills
to improve the breadth of understanding on the overall process, a proper handshake
between the teams, a single team mindset, and multiskilled team members.
As part of DevOps adoption, most companies start with or focus on the technology
and process implementation. Agile is the de facto development methodology for many
companies, and automation is the driving force for DevOps adoption. DevOps Culture
adoption is complex, and it requires that changes in organizational structure and that
people’s mindsets change.
D
evOps Team
If DevOps is a mixture of development and operations, then what about the test
department and other stakeholders?
All the stakeholders have their own importance and roles in DevOps. The Dev in
DevOps includes the scrum masters, developers, testers, project managers, subject-
matter experts (SMEs), business analysts, domain experts, security architects, solution
architects, performance engineers, and so on. The roles and responsibilities differ from
project to project based on the size, complexity, and business impact of the solution.
The Ops in DevOps includes the operational members such as the build engineers,
production support, monitoring, and so on.
Remember that the goal of DevOps is to deliver value to the customer, not to reduce
the cost or automate the process; these are the by-products of enabling proper DevOps
practices. Team structure plays a major role in driving the DevOps practice in an
organization. Based on various parameters, we can identify a matching team topology
for our project. Identify whether you are following an anti-type or a correct DevOps team
type by reading the article by Matthew Skelton https://web.devopstopologies.com/.
3
Chapter 1 DevOps Basics and Variations
DevOps Practices
DevOps involves different components to establish an end-to-end DevOps workflow.
These are some of the main practices:
There are many more areas such as collaboration, knowledge management, identity/
access management, portfolio management, artifacts repositories, performance testing,
security test, backlog management, and so on.
DevOps Variations
DevOps is an integral part of software development. Most projects implement at least
the technical and process parts of DevOps, even though this may not result in the actual
benefits of DevOps. Culture changes really help you to realize the real benefit of DevOps.
4
Chapter 1 DevOps Basics and Variations
But, most of the time, we end up with limiting our DevOps scope to automation and cost
reduction instead of releasing value.
Currently, many variations of DevOps exist based on the implementation. Some of
the main variants are as follows:
5
Chapter 1 DevOps Basics and Variations
The DevOps process has evolved over time from DevOps 1.0 to intelligent DevOps.
D
evOps 1.0
In DevOps 1.0, the main focus is to resolve the conflict and increase the collaboration
between various stakeholders such as the development team, QA, and operations, as
shown in Figure 1-2. Bridging the gap in understanding the priority of the other team
played a major role here.
6
Chapter 1 DevOps Basics and Variations
In this scenario, mainly the development team focuses on new features to improve the
business, whereas the Ops team looks for stability in the production environment. Figure 1-3
shows some of the conflict or deviations between the dev team and the ops team.
D
evOps 2.0
DevOps 2.0 focused on the user-centric deployments, as shown in Figure 1-4. This is
especially true for SaaS or products where the preview features are released to a set of
users who give feedback. Based on the feedback, the team incorporates the changes and
releases a final version to all the users.
7
Chapter 1 DevOps Basics and Variations
This kind of DevOps implementation is handled using feature flags. Feature flags are
the implementation of labeling the features and releasing them to selected users only.
S
ecDevOps
Security has become one of the main focuses in a DevOps implementation because of
the recent remote work culture and cloud adoption. More and more DevOps tools are
moving to a cloud-based subscription model to address the growing demand of cloud
adoption. Another reason for security by design is the adoption of open source libraries
in application development. For example, most modern web UI development is based
on Angular or React, JavaScript frameworks are based on npm packages. Lots of npm
packages are used along with the base package to design the rich UI. Deploying all these
dependent libraries without proper screening will lead to security threats.
I ntelligent DevOps
In intelligent DevOps, the team will look into implementing different intelligent models
to derive proper insights from the data collected throughout the DevOps life cycle. Here,
data will be added as a fourth element to the DevOps ecosystem. Figure 1-5 shows an
example of intelligent DevOps.
8
Chapter 1 DevOps Basics and Variations
Benefits
The benefits of DevOps include building and shipping software changes faster to the
market, from idea to release and through automation, orchestration of software delivery
processes, and continuous customer feedback. DevOps continuously delivers value
to end customers with lots of added benefits in terms of fewer test cycles, increased
9
Chapter 1 DevOps Basics and Variations
ticket resolutions, reduced end-to-end effort, and so on. The transition from traditional
DevOps to intelligent DevOps will bring exponential value to end users and businesses
by combining the power of DevOps and AI.
The following are some of the DevOps benefits in the business area:
• Increased sales
• Lower risk
• Reduced complexity
• Collaborative culture
• Productive teams
• Higher team engagements
Azure DevOps
Azure DevOps provides two offerings: Azure DevOps Server and Azure DevOps Services.
Azure DevOps Server, previously known as Team Foundation Server (TFS), is the
on-premise offering from Microsoft. Azure DevOps Services, formerly known as Visual
Studio Team Services (VSTS), provides a SaaS-based offering to manage the end-to-end
DevOps life cycle. This book will focus on Azure DevOps Services only.
10
Chapter 1 DevOps Basics and Variations
Azure DevOps Services provides a platform for implementing the DevOps process
across different IT segments. This tool supports the various practices under DevOps such
as continuous planning, continuous development, continuous integration, continuous
testing, continuous deployment/delivery, and continuous monitoring/feedback.
Moreover, this tool supports integration with various tools such as code analysis tools to
verify the quality of code, security tools to scan the vulnerabilities in code, infrastructure
provisioning tools to automatically provision infrastructure components, and so on.
Summary
DevOps is an integral part of modern application development irrespective of
commercial off-the-shelf (COTS) products or bespoke applications, machine learning
models or web applications, and database or serverless models. This book will take you
through the DevOps implementation journey using Azure DevOps. It will also address
some of the high-level DevOps blueprints at the end.
11
CHAPTER 2
Project Management
Using Azure DevOps
The field of project management has evolved over the years from the management
of resources to include areas such as optimization and productivity boosters. Project
managers have always managed resources and maintained schedules, but today’s
project managers add multiple dimensions such as agility and technology to these
regular duties. Technical managers are the new norm to handle the growing adoption of
agile and DevOps practices and automation. The collaborative and self-driven culture
of the modern workforce provides more room for project managers to optimize their
activities.
Azure DevOps complements project management activities by facilitating more
automated features for the managers to track the work, optimize areas, and tightly
control and maintain schedule. Project execution means creating a project, managing
the end-to-end development cycle of the project, and onboarding teams with the proper
permissions. In Azure DevOps, projects related to the same domain or business unit are
grouped under an organization. Therefore, an organization is a collection of projects. In
earlier versions, this was called a project collection.
As discussed in Chapter 1, an enterprise can have multiple Azure DevOps
subscriptions to keep the billing related to each business unit separate, as shown in
Figure 2-1. Multiple organizations can be configured using one subscription to capture
the billing on a granular level or sub-business unit level. Organizations host related
projects under that, which supports the execution of a project from requirements
gathering until the deployment.
13
© Ambily K K 2020
A. K K, Azure DevOps for Web Developers, https://doi.org/10.1007/978-1-4842-6412-6_2
Chapter 2 Project Management Using Azure DevOps
Each project can have multiple repositories to hold the codebase in separate
areas. For example, a project handling the microservices will have one repo for each
microservice. The repos will be further divided into branches to manage the code
versioning and collaborative work. This chapter covers the high-level features of
organizations and projects and touches upon a few configurations related to repos and
branches. Repos and branches will be covered in more detail in Chapter 4. Also, most of
the configurations discussed in this chapter will be revisited in later chapters based on
their importance when setting up the end-to-date DevOps configuration.
Organizations
Organizations are the highest level of aggregation in Azure DevOps. From an enterprise
perspective, organizations can be used to group the user licenses, the billings for a set
of related projects, connections to an enterprise Azure AD, and global notifications and
policies. More features of organizations will be discussed later in this book.
14
Chapter 2 Project Management Using Azure DevOps
C
reating an Organization
You can create a free organization by navigating to the Azure DevOps site: https://
azure.microsoft.com/en-us/services/devops/.
Select the option “Start free” to activate a free instance of Azure DevOps. Azure
DevOps supports using a Microsoft ID for login, where you can provide an existing live
email address (@hotmail.com, @outlook.com, @live.com, etc.) or create one to proceed.
Once the login completes, Azure DevOps prompts you to continue with organization
creation.
Provide an organization name to continue the journey. Once the organization is
created, the system will prompt you to create a project, as shown in Figure 2-2. Create a
new project with the minimum details.
O
rganization Settings
The organization home page shows the list of existing projects in the organization,
“My work items” tab, and “My pull requests” tab as shown in Figure 2-3. Hovering the
cursor over each of the project tiles allows users to navigate to the selected project’s
components such as the repo, board, pipeline, etc. The “My work items” tab displays all
15
Chapter 2 Project Management Using Azure DevOps
the work items assigned to that user irrespective of the project. If a user contributes to
multiple projects, this view provides a unified look at all the work items assigned to the
user. Also, this view lists the activities related to the user. The “My pull requests” tab lists
the pull requests (PRs) created by the user. More about the work items and PRs will be
covered in subsequent chapters.
The organization settings allow you to configure a set of features required for the
organization. Click the “Organization settings” option in the lower-left corner of the
organization’s home page to view the settings, as shown in Figure 2-3.
Briefly take a look at the different settings available in the organization settings.
These settings are used as part of project execution. For example, the settings under
Boards ➤ Process will be used to customize the project template when setting up the
execution process. Similarly, the settings under Security help us to define organizational
policies as part of the build and deployment operations.
G
eneral ➤ Overview
The Overview section allows you to manage the general properties associated with
an organization such as the name of the organization, privacy URL, time zone, and
description.
16
Chapter 2 Project Management Using Azure DevOps
Scroll down in the Overview section to view the two main activities you can perform:
changing the owner and deleting the organization, as shown in Figure 2-4.
G
eneral ➤ Projects
This section lists the projects associated with the organization. In this section, we can
create a new project, delete a project, or rename an existing project, as shown in Figure 2-5.
17
Discovering Diverse Content Through
Random Scribd Documents
Hagenin seurueeseen liittymisen, oli ollut tavattoman suurilukuinen,
suurempi kuin koskaan ennen. Siihen kyllä oli osaltansa vaikuttanut
ihmisten tavaton huvitteluhalukin tänä epävarmana sota-aikana,
mutta se ei mitenkään vähentänyt neiti Hagenin ansioita. Myöskin
toveripiirinsä sydämet hän oli voittanut vaatimattomalla,
sydämellisellä esiintymisellään. Hän ehdotti, että kaikki
saapuvillaolijat joisivat Martta Hagenin, taiteilijan ja ihmisen maljan…
Isäntä itse oli jo niin hyvällä tuulella, että hän tahtoi näyttää
taitoansa aseiden heittelemisessä. Ville otti hänen käskystään esille
tikareja, miekkoja, puukkoja ja pistimiä ja toi ne hänelle. Sitten hän
alkoi huoneen perältä heitellä niitä ateljeerin oveen, ja joka kerta
kun joku näistä teräkaluista kolahtaen tarttui oveen kiinni, kirkuivat
naiset ihastuksesta. Tämä heitteleminen oli taiteilija Hertellin
erikoisurheilua, ja hänen tavoistaan tiedettiin kertoa monenlaisia
juttuja. Toisinaan, kun hän oli juonut hiukan liiemmälti, saattoi hän
käydä tässä urheilussaan hengenvaaralliseksikin, sillä hän heitteli
puukkoja myöskin kattoon, ja jos ne sattuivat tarttumaan huonosti
kiinni, niin ne helposti saattoivat putoilla ihmisten päähän.
Kun taiteilija oli heitellyt kaikki käsillä olevat aseet kiinni oveen,
joka oli täynnä reikiä niinkuin lihanmyyjän lihatukki, väsyi hän tähän
leikkiin, ja laulu ja soitto alkoivat uudestaan. Ilon ollessa ylimmillään
soitettiin ovikelloa rajusti. Ville meni aukaisemaan, ja ateljeeriin
ilmestyi tuomari Katajisto.
Nytkin hän oli hiukan humalassa ja pahalla päällä, kun näki Martan
täällä taiteilija Hertellin luona. Hertell oli kiivasluontoinen ja tappeli
mielellänsä, ja vaikeata hänen oli nytkin hillitä itseänsä, kun tuomari
Katajisto soimasi Marttaa siitä, että tämä oli hänet muka taaskin
pettänyt. Mutta koska nyt oli jouluaatto, rauhanjuhla, päätti taiteilija
olla ystävällinen tuomarille ja koetti rauhoittaa häntä. Muutamalla,
ystävällisellä sanalla sai Martta tuomarin rauhoittumaan, ja niin oli
mieliala jälleen palautettu.
*****
Minä tiedän, että ne ovat taas tulossa, ei vielä, älä pelkää, mutta
vasta jonkun päivän päästä. Aah, se on kauheata. Jospa edes
ymmärtäisi, silloin kun ne pahimmillansa ovat, surmata itsensä,
mutta silloin kaikki järjellinen toiminta on mahdotonta…
— Ei, älä sano niin. Sinä olet niin hyvä ihminen, sinä olet kärsinyt
ihminen, ja kärsimykset tekevät ihmiset hyviksi. Minä rakastan
kärsineitä ihmisiä…
— Rakas!
*****
— Me olemme onnettomuussisaruksia.
— Älä Jumalan nimessä suutele minua! Etkö sinä tiedä, että minun
rintaani syö Kamelianaisen kuluttava tauti…
*****
Äidille oli tämä ollut pettymys, eikä Albert kehdannut kertoa, että
taiteilija Hertell oli Martan pauloissa, sillä Martan nimenkin
mainitseminen olisi tuonut heidän kotiinsa niin paljon ikäviä ja
surullisia muistoja…
Annikki olikin iloinen kuten aina, sillä hän oli saanut uudeksikin
vuodeksi muutamia lahjoja. Liisa ja hän olivat
tinojenvalamishommissa.
— Äiti, kuka nyt valaa tinoja, kun isä on poissa? Mihinkä isä oikein
meni? — kysyi Annikki.
*****
Se sitten oli kummallista, kuinka puku teki paljon asiaan. Jos vain
panit päällesi »formun» ja satuit istumaan jonkun puiston penkille,
niin kyllä siihen kosijoita ilmestyi jos jonkinkarvaisia. Aivanhan ne
tytöt olivat hulluina ja tahtoivat viedä väkisten, ja olisi sitä saanut
pitää seuraa oikein hienoille fröökynöillekin, vaikka ties mitä ne
olivat… Oikein häntä nauratti, kun ajatteli mitä kaikkea hän olisi
saanut seuraansa, jos vain olisi huolinut..
*****
Vähän sen jälkeen kuin palokunta oli saapunut paikalle, tuli tohtori
Hakalakin hevosella ajaen. Liisa oli soittanut ensin paloasemalle.
Sitten hän oli yrittänyt palata palavaan huoneeseen, mutta kun tuli
ja savu löivät häntä ovessa vastaan, oli hän hätääntynyt ja juossut
alakertaan ja soittanut alakerroksessa olevalla puhelimella vanhalle
ylioppilastalolle, jossa hän tiesi tohtorin olevan juhlapuhujana.
Tohtori oli tullut jonkun ajan kuluttua puhelimeen, eikä hän siinä
paljoa puhunut, vaan syöksyi ulos ilman päällysvaatteita ja otti
ensimäisen ajurin.
Kun hän saapui palopaikalle, oli talo ilmitulessa. Hän riehui kuin
mielipuoli ja koetti heti hyökätä yläkertaan, mutta vastaan tuleva tuli
ja savu ehkäisivät hänen yrityksensä. Kaikeksi onnettomuudeksi oli
sähkökin sammunut.
Mitä hän sieltä oli hakenut? Tietysti sitä ainaista Marttaa. Minkä
hän mahtoi tunteellensa ja onnettomuudelleen. Mutta sitten hän
alkoi muistella, mitenkä hän oikeastaan oli tutustunut Marttaan. Hän
vihasi sitä henkilöä, joka oli hänet esittänyt tuolle sybariitille, tuolle
viheliäiselle velholle. Mutta sitten hän muistikin, ettei siinä ollut
tapahtunut mitään esittelyä, itsestäänhän se oli käynyt, ja sinne oli
hänet hommannut ajuri….
Mutta hänen leukaansa kivisti yhä, niin että hänen täytyi hiljaa
itseksensä kiroilla.
Jos edes olisi saanut todistetuksi, että Martta oli yleinen nainen,
niin olisi saanut hänet poliisin kirjoihin. Mutta miten? — Silloin
muistui hänen mieleensä ajuri, joka oli tutustuttanut hänet Marttaan.
Hän päätti heti lähteä ottamaan asiasta selvää.
— Kyllä, kiitoksia!
— Olen.
— Olen.
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
ebooknice.com