homework 9.5: complete all tasks

readme.md

@@ -45,3 +45,4 @@
 * [9.1. Жизненный цикл ПО](/src/homework/09-ci/9.1)
 * [9.3. CI\CD](/src/homework/09-ci/9.3)
 * [9.4 Jenkins](/src/homework/09-ci/9.4)
+* [9.5. Teamcity](/src/homework/09-ci/9.5)

src/homework/09-ci/9.4/readme.md

@@ -1,5 +1,5 @@
 Выполнение [домашнего задания](https://github.com/netology-code/mnt-homeworks/blob/MNT-13/09-ci-04-jenkins/README.md)
-по теме "9.3. Jenkins".
+по теме "9.4. Jenkins".
 
 ## Q/A
 

src/homework/09-ci/9.5/infrastructure/.gitignore

@@ -0,0 +1,3 @@
+files/*.pub
+inventory/hosts.yml
+roles/*

src/homework/09-ci/9.5/infrastructure/inventory/group_vars/nexus.yml

@@ -0,0 +1,22 @@
+---
+nexus_user_group: nexus
+nexus_user_name: nexus
+nexus_directory_data: "/home/{{ nexus_user_name }}/sonatype-work/nexus3"
+nexus_directory_home: "/home/{{ nexus_user_name }}/nexus"
+nexus_directory_log: "/home/{{ nexus_user_name }}/log"
+nexus_directory_package: "/home/{{ nexus_user_name }}/pkg"
+nexus_directory_tmp: "/home/{{ nexus_user_name }}/tmp"
+nexus_version: 3.14.0-04
+nexus_download_url: https://download.sonatype.com/nexus/3
+nexus_service_enabled: true
+nexus_ulimit: 65536
+nexus_context_path: /
+nexus_host: 0.0.0.0
+nexus_port: 8081
+nexus_port_check_timeout: 600
+nexus_edition: nexus-oss-edition
+nexus_features: nexus-oss-feature
+nexus_java_heap_size: 1200M
+nexus_java_max_direct_memory: 2G
+nexus_service_start_on_boot: true
+nexus_configuration_disk_free_space_limit: ~

src/homework/09-ci/9.5/infrastructure/inventory/hosts.yml.example

@@ -0,0 +1,12 @@
+---
+all:
+  hosts:
+    nexus-01:
+      ansible_host: <nexushost>
+  children:
+    nexus:
+      hosts:
+        nexus-01:
+  vars:
+    ansible_connection_type: paramiko
+    ansible_user: <user>

src/homework/09-ci/9.5/infrastructure/site.yml

@@ -0,0 +1,158 @@
+---
+- name: Get Nexus installed
+  hosts: nexus
+  pre_tasks:
+    - name: Create Nexus group
+      become: true
+      group:
+        name: "{{ nexus_user_group }}"
+        state: present
+    - name: Create Nexus user
+      become: true
+      user:
+        name: "{{ nexus_user_name }}"
+    - name: Install JDK
+      become: true
+      package:
+        name: [java-1.8.0-openjdk, java-1.8.0-openjdk-devel]
+        state: present
+  tasks:
+    - name: Create Nexus directories
+      become: true
+      file:
+        group: "{{ nexus_user_group }}"
+        owner: "{{ nexus_user_name }}"
+        path: "{{ item }}"
+        state: directory
+      with_items:
+        - "{{ nexus_directory_log }}"
+        - "{{ nexus_directory_data }}"
+        - "{{ nexus_directory_data }}/etc"
+        - "{{ nexus_directory_package }}"
+        - "{{ nexus_directory_tmp }}"
+
+    - name: Download Nexus
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      get_url:
+        dest: "{{ nexus_directory_package }}/nexus-{{ nexus_version }}.tar.gz"
+        url: "{{ nexus_download_url }}/nexus-{{ nexus_version }}-unix.tar.gz"
+
+    - name: Unpack Nexus
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      unarchive:
+        copy: no
+        creates: "{{ nexus_directory_package }}/nexus-{{ nexus_version }}"
+        dest: "{{ nexus_directory_package }}"
+        src: "{{ nexus_directory_package }}/nexus-{{ nexus_version }}.tar.gz"
+
+    - name: Link to Nexus Directory
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      file:
+        dest: "{{ nexus_directory_home }}"
+        src: "{{ nexus_directory_package }}/nexus-{{ nexus_version }}"
+        state: link
+
+    - name: Add NEXUS_HOME for Nexus user
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      lineinfile:
+        create: yes
+        dest: "/home/{{ nexus_user_name }}/.bashrc"
+        insertafter: EOF
+        line: "export NEXUS_HOME={{ nexus_directory_home }}"
+
+    - name: Add run_as_user to Nexus.rc
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      lineinfile:
+        create: yes
+        dest: "{{ nexus_directory_home }}/bin/nexus.rc"
+        insertafter: EOF
+        line: "run_as_user=\"{{ nexus_user_name }}\""
+        regexp: "^run_as_user"
+
+    - name: Raise nofile limit for Nexus user
+      become: true
+      pam_limits:
+        domain: "{{ nexus_user_name }}"
+        limit_type: "-"
+        limit_item: nofile
+        value: "{{ nexus_ulimit }}"
+
+    - name: Create Nexus service for SystemD
+      become: true
+      template:
+        dest: /lib/systemd/system/nexus.service
+        mode: 0644
+        src: nexus.systemd.j2
+
+    - name: Ensure Nexus service is enabled for SystemD
+      become: true
+      systemd:
+        daemon_reload: yes
+        enabled: yes
+        name: nexus
+      when:
+        - nexus_service_enabled
+
+    - name: Create Nexus vmoptions
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      template:
+        dest: "{{ nexus_directory_home }}/bin/nexus.vmoptions"
+        src: nexus.vmoptions.j2
+      register: nexus_config_changed
+
+    - name: Create Nexus properties
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      template:
+        dest: "{{ nexus_directory_data }}/etc/nexus.properties"
+        src: nexus.properties.j2
+      register: nexus_config_changed
+
+    - name: Lower Nexus disk space threshold
+      become: true
+      become_user: "{{ nexus_user_name }}"
+      lineinfile:
+        backrefs: yes
+        dest: "{{ nexus_directory_home }}/etc/karaf/system.properties"
+        insertafter: EOF
+        line: "storage.diskCache.diskFreeSpaceLimit={{ nexus_configuration_disk_free_space_limit }}"
+        regexp: ^storage\.diskCache\.diskFreeSpaceLimit
+      when: nexus_configuration_disk_free_space_limit is not none
+      register: nexus_config_changed
+
+    - name: Start Nexus service if enabled
+      become: true
+      service:
+        enabled: yes
+        name: nexus
+        state: started
+      when:
+        - nexus_service_start_on_boot
+        - not nexus_config_changed.changed
+      tags:
+        - skip_ansible_lint
+
+    - name: Ensure Nexus service is restarted
+      become: true
+      service:
+        name: nexus
+        state: restarted
+      when:
+        - nexus_service_start_on_boot
+        - nexus_config_changed.changed
+      tags:
+        - skip_ansible_lint
+
+    - name: Wait for Nexus port if started
+      wait_for:
+        port: "{{ nexus_port }}"
+        state: started
+        timeout: "{{ nexus_port_check_timeout }}"
+      when:
+        - nexus_service_start_on_boot

src/homework/09-ci/9.5/infrastructure/templates/nexus.properties.j2

@@ -0,0 +1,12 @@
+#
+#
+
+# Jetty section
+application-host={{ nexus_host }}
+application-port={{ nexus_port }}
+nexus-context-path={{ nexus_context_path }}
+
+# Nexus section
+nexus-edition={{ nexus_edition }}
+nexus-features=\
+  {{ nexus_features }}

src/homework/09-ci/9.5/infrastructure/templates/nexus.systemd.j2

@@ -0,0 +1,15 @@
+[Unit]
+Description=nexus service
+After=network.target
+
+[Service]
+Type=forking
+User={{ nexus_user_name }}
+Group={{ nexus_user_group }}
+LimitNOFILE={{ nexus_ulimit }}
+ExecStart={{ nexus_directory_home }}/bin/nexus start
+ExecStop={{ nexus_directory_home }}/bin/nexus stop
+Restart=on-abort
+
+[Install]
+WantedBy=multi-user.target

src/homework/09-ci/9.5/infrastructure/templates/nexus.vmoptions.j2

@@ -0,0 +1,16 @@
+-Xms{{ nexus_java_heap_size }}
+-Xmx{{ nexus_java_heap_size }}
+-XX:MaxDirectMemorySize={{ nexus_java_max_direct_memory }}
+-XX:+UnlockDiagnosticVMOptions
+-XX:+UnsyncloadClass
+-XX:+LogVMOutput
+-XX:LogFile={{ nexus_directory_log }}/jvm.log
+-XX:-OmitStackTraceInFastThrow
+-Djava.net.preferIPv4Stack=true
+-Dkaraf.home=.
+-Dkaraf.base=.
+-Dkaraf.etc=etc/karaf
+-Djava.util.logging.config.file=etc/karaf/java.util.logging.properties
+-Dkaraf.data={{ nexus_directory_data }}
+-Djava.io.tmpdir={{ nexus_directory_tmp }}
+-Dkaraf.startLocalConsole=false

src/homework/09-ci/9.5/readme.md

@@ -0,0 +1,83 @@
+Выполнение [домашнего задания](https://github.com/netology-code/mnt-homeworks/blob/MNT-13/09-ci-05-teamcity/README.md)
+по теме "9.5. Teamcity"
+
+## Q/A
+
+### Задание 1
+
+> Подготовка к выполнению
+> 1. В Ya.Cloud создайте новый инстанс (4CPU4RAM) на основе образа `jetbrains/teamcity-server`
+> 2. Дождитесь запуска teamcity, выполните первоначальную настройку
+> 3. Создайте ещё один инстанс(2CPU4RAM) на основе образа `jetbrains/teamcity-agent`. Пропишите к нему переменную окружения `SERVER_URL: "http://<teamcity_url>:8111"`
+> 4. Авторизуйте агент
+> 5. Сделайте fork [репозитория](https://github.com/aragastmatb/example-teamcity)
+> 6. Создать VM (2CPU4RAM) и запустить [playbook](./infrastructure)
+
+Форк репозитория: [netology-devops-teamcity-example](https://github.com/Dannecron/netology-devops-teamcity-example).
+
+![teamcity_dashboard](./img/teamcity_dashboard.png)
+
+### Задание 2
+
+> Основная часть
+> 1. Создайте новый проект в teamcity на основе fork
+
+![teamcity_new_project](./img/teamcity_new_project.png)
+
+> 2. Сделайте autodetect конфигурации
+> 3. Сохраните необходимые шаги, запустите первую сборку master'a
+
+![teamcity_project_build](./img/teamcity_project_build.png)
+
+![teamcity_build_success](./img/teamcity_build_success.png)
+
+> 4. Поменяйте условия сборки: если сборка по ветке `master`, то должен происходит `mvn clean deploy`, иначе `mvn clean test`
+
+![teamcity_build_config](./img/teamcity_build_config.png)
+
+> 5. Для deploy будет необходимо загрузить [settings.xml](./teamcity/settings.xml) в набор конфигураций maven у teamcity, предварительно записав туда креды для подключения к nexus
+> 6. В pom.xml необходимо поменять ссылки на репозиторий и nexus
+
+![teamcity_maven_config](./img/teamcity_maven_config.png)
+
+> 7. Запустите сборку по master, убедитесь что всё прошло успешно, артефакт появился в nexus
+
+![teamcity_deploy_success](./img/teamcity_deploy_success.png)
+
+![nexus_release](./img/nexus_release.png)
+
+> 8. Мигрируйте `build configuration` в репозиторий
+
+![teamcity_build_config_sync](./img/teamcity_build_config_sync.png)
+
+> 9. Создайте отдельную ветку `feature/add_reply` в репозитории
+
+```shell
+git branch -C feature/add_reply && git switch feature/add_reply
+```
+
+> 10. Напишите новый метод для класса Welcomer: метод должен возвращать произвольную реплику, содержащую слово `hunter`
+> 11. Дополните тест для нового метода на поиск слова `hunter` в новой реплике
+> 12. Сделайте push всех изменений в новую ветку в репозиторий
+
+Ветка с изменениями: [feature/add_reply](https://github.com/Dannecron/netology-devops-teamcity-example/tree/feature/add_reply)
+
+> 13. Убедитесь что сборка самостоятельно запустилась, тесты прошли успешно
+
+![teamcity_build_branch_success](./img/teamcity_build_branch_success.png)
+
+> 14. Внесите изменения из произвольной ветки `feature/add_reply` в `master` через `Merge`
+> 15. Убедитесь, что нет собранного артефакта в сборке по ветке `master`
+> 16. Настройте конфигурацию так, чтобы она собирала `.jar` в артефакты сборки
+
+Конфигурация уже настроена на сборку `jar`. При мерже в мастер сборка запустилась автоматически,
+так как изначально кофигурация проверяет все изменения всех веток в репозитории.
+
+> 17. Проведите повторную сборку мастера, убедитесь, что сбора прошла успешно и артефакты собраны
+
+Поменяли `pom.xml`, вписав новую версию. Сборка запустилась автоматически и успешно опубликовала артефакты в `nexus`.
+
+> 18. Проверьте, что конфигурация в репозитории содержит все настройки конфигурации из teamcity
+> 19. В ответ предоставьте ссылку на репозиторий
+
+[netology-devops-teamcity-example](https://github.com/Dannecron/netology-devops-teamcity-example)

src/homework/09-ci/9.5/teamcity/settings.xml

@@ -0,0 +1,261 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+<!--
+ | This is the configuration file for Maven. It can be specified at two levels:
+ |
+ |  1. User Level. This settings.xml file provides configuration for a single user,
+ |                 and is normally provided in ${user.home}/.m2/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the CLI option:
+ |
+ |                 -s /path/to/user/settings.xml
+ |
+ |  2. Global Level. This settings.xml file provides configuration for all Maven
+ |                 users on a machine (assuming they're all using the same Maven
+ |                 installation). It's normally provided in
+ |                 ${maven.conf}/settings.xml.
+ |
+ |                 NOTE: This location can be overridden with the CLI option:
+ |
+ |                 -gs /path/to/global/settings.xml
+ |
+ | The sections in this sample file are intended to give you a running start at
+ | getting the most out of your Maven installation. Where appropriate, the default
+ | values (values used when the setting is not specified) are provided.
+ |
+ |-->
+<settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
+          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 http://maven.apache.org/xsd/settings-1.2.0.xsd">
+    <!-- localRepository
+     | The path to the local repository maven will use to store artifacts.
+     |
+     | Default: ${user.home}/.m2/repository
+    <localRepository>/path/to/local/repo</localRepository>
+    -->
+
+    <!-- interactiveMode
+     | This will determine whether maven prompts you when it needs input. If set to false,
+     | maven will use a sensible default value, perhaps based on some other setting, for
+     | the parameter in question.
+     |
+     | Default: true
+    <interactiveMode>true</interactiveMode>
+    -->
+
+    <!-- offline
+     | Determines whether maven should attempt to connect to the network when executing a build.
+     | This will have an effect on artifact downloads, artifact deployment, and others.
+     |
+     | Default: false
+    <offline>false</offline>
+    -->
+
+    <!-- pluginGroups
+     | This is a list of additional group identifiers that will be searched when resolving plugins by their prefix, i.e.
+     | when invoking a command line like "mvn prefix:goal". Maven will automatically add the group identifiers
+     | "org.apache.maven.plugins" and "org.codehaus.mojo" if these are not already contained in the list.
+     |-->
+    <pluginGroups>
+        <!-- pluginGroup
+         | Specifies a further group identifier to use for plugin lookup.
+        <pluginGroup>com.your.plugins</pluginGroup>
+        -->
+    </pluginGroups>
+
+    <!-- proxies
+     | This is a list of proxies which can be used on this machine to connect to the network.
+     | Unless otherwise specified (by system property or command-line switch), the first proxy
+     | specification in this list marked as active will be used.
+     |-->
+    <proxies>
+        <!-- proxy
+         | Specification for one proxy, to be used in connecting to the network.
+         |
+        <proxy>
+          <id>optional</id>
+          <active>true</active>
+          <protocol>http</protocol>
+          <username>proxyuser</username>
+          <password>proxypass</password>
+          <host>proxy.host.net</host>
+          <port>80</port>
+          <nonProxyHosts>local.net|some.host.com</nonProxyHosts>
+        </proxy>
+        -->
+    </proxies>
+
+    <!-- servers
+     | This is a list of authentication profiles, keyed by the server-id used within the system.
+     | Authentication profiles can be used whenever maven must make a connection to a remote server.
+     |-->
+    <servers>
+        <!-- server
+         | Specifies the authentication information to use when connecting to a particular server, identified by
+         | a unique name within the system (referred to by the 'id' attribute below).
+         |
+         | NOTE: You should either specify username/password OR privateKey/passphrase, since these pairings are
+         |       used together.
+         |
+        <server>
+          <id>deploymentRepo</id>
+          <username>repouser</username>
+          <password>repopwd</password>
+        </server>
+        -->
+        <server>
+            <id>nexus</id>
+            <username>admin</username>
+            <password>admin123</password>
+        </server>
+        <!-- Another sample, using keys to authenticate.
+        <server>
+          <id>siteServer</id>
+          <privateKey>/path/to/private/key</privateKey>
+          <passphrase>optional; leave empty if not used.</passphrase>
+        </server>
+        -->
+    </servers>
+
+    <!-- mirrors
+     | This is a list of mirrors to be used in downloading artifacts from remote repositories.
+     |
+     | It works like this: a POM may declare a repository to use in resolving certain artifacts.
+     | However, this repository may have problems with heavy traffic at times, so people have mirrored
+     | it to several places.
+     |
+     | That repository definition will have a unique id, so we can create a mirror reference for that
+     | repository, to be used as an alternate download site. The mirror site will be the preferred
+     | server for that repository.
+     |-->
+    <mirrors>
+        <!-- mirror
+         | Specifies a repository mirror site to use instead of a given repository. The repository that
+         | this mirror serves has an ID that matches the mirrorOf element of this mirror. IDs are used
+         | for inheritance and direct lookup purposes, and must be unique across the set of mirrors.
+         |
+        <mirror>
+          <id>mirrorId</id>
+          <mirrorOf>repositoryId</mirrorOf>
+          <name>Human Readable Name for this Mirror.</name>
+          <url>http://my.repository.com/repo/path</url>
+        </mirror>
+         -->
+    </mirrors>
+
+    <!-- profiles
+     | This is a list of profiles which can be activated in a variety of ways, and which can modify
+     | the build process. Profiles provided in the settings.xml are intended to provide local machine-
+     | specific paths and repository locations which allow the build to work in the local environment.
+     |
+     | For example, if you have an integration testing plugin - like cactus - that needs to know where
+     | your Tomcat instance is installed, you can provide a variable here such that the variable is
+     | dereferenced during the build process to configure the cactus plugin.
+     |
+     | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
+     | section of this document (settings.xml) - will be discussed later. Another way essentially
+     | relies on the detection of a system property, either matching a particular value for the property,
+     | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
+     | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.
+     | Finally, the list of active profiles can be specified directly from the command line.
+     |
+     | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
+     |       repositories, plugin repositories, and free-form properties to be used as configuration
+     |       variables for plugins in the POM.
+     |
+     |-->
+    <profiles>
+        <!-- profile
+         | Specifies a set of introductions to the build process, to be activated using one or more of the
+         | mechanisms described above. For inheritance purposes, and to activate profiles via <activatedProfiles/>
+         | or the command line, profiles have to have an ID that is unique.
+         |
+         | An encouraged best practice for profile identification is to use a consistent naming convention
+         | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc.
+         | This will make it more intuitive to understand what the set of introduced profiles is attempting
+         | to accomplish, particularly when you only have a list of profile id's for debug.
+         |
+         | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo.
+        <profile>
+          <id>jdk-1.4</id>
+
+          <activation>
+            <jdk>1.4</jdk>
+          </activation>
+
+          <repositories>
+            <repository>
+              <id>jdk14</id>
+              <name>Repository for JDK 1.4 builds</name>
+              <url>http://www.myhost.com/maven/jdk14</url>
+              <layout>default</layout>
+              <snapshotPolicy>always</snapshotPolicy>
+            </repository>
+          </repositories>
+        </profile>
+        -->
+
+        <!--
+         | Here is another profile, activated by the system property 'target-env' with a value of 'dev',
+         | which provides a specific path to the Tomcat instance. To use this, your plugin configuration
+         | might hypothetically look like:
+         |
+         | ...
+         | <plugin>
+         |   <groupId>org.myco.myplugins</groupId>
+         |   <artifactId>myplugin</artifactId>
+         |
+         |   <configuration>
+         |     <tomcatLocation>${tomcatPath}</tomcatLocation>
+         |   </configuration>
+         | </plugin>
+         | ...
+         |
+         | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
+         |       anything, you could just leave off the <value/> inside the activation-property.
+         |
+        <profile>
+          <id>env-dev</id>
+
+          <activation>
+            <property>
+              <name>target-env</name>
+              <value>dev</value>
+            </property>
+          </activation>
+
+          <properties>
+            <tomcatPath>/path/to/tomcat/instance</tomcatPath>
+          </properties>
+        </profile>
+        -->
+    </profiles>
+
+    <!-- activeProfiles
+     | List of profiles that are active for all builds.
+     |
+    <activeProfiles>
+      <activeProfile>alwaysActiveProfile</activeProfile>
+      <activeProfile>anotherAlwaysActiveProfile</activeProfile>
+    </activeProfiles>
+    -->
+</settings>