Deploying CI/CD infrastructure using Jenkins.

• Installing a Jenkins master on a remote Linux server that had two slave agents on build machines in the server room in the office. These machines ran on Windows and Mac operating systems. The product was also tested on an Android phone connected to a Windows machine and an iPad that was launched via Apple silicone. Testing included many stages. Such as working with the file system and compiling the product, for this I created bash, powershell and shell scripts. Creating screenshots of a running product and collecting performance metrics, since it was a Unity application, I used C# for this. Uploading test files to Google Drive using Python. Sending alerts to Slack with test results. I deployed this infrastructure from scratch and maintained it alone.
• Creation of scripts in PowerShell for parallel compilation of the product.
• Created several Jenkins pipelines for different products and repositories to fully test them. The pipelines had about 30 steps that simultaneously worked on two slave agents and interacted with each other. I also used parallel running steps.
• Created a multibranch pipeline that triggered pull requests. This was how basic testing of the product’s performance took place. At the end of testing, the committer received a message in Slack about the test results. Also, until the end of testing and if testing failed, it was impossible to push this branch into the main. The testing status was displayed in Github.
• A pipeline was created communicating with Jira. To launch this pipeline, I created automation in Jira and a button to start testing on a ticket. When this button was clicked, the Jenkins pipeline was launched and a subticket was created for this ticket and assigned the “testing” status. At the end of testing, the subticket received the Done or Fail status, and a link to the Jenkins build and a link to Google Drive with the test results appeared in the comments.

Working with the product on Unity.

• Creation of scripts for analytics, product pop-ups, automatic testing in C#.
• Creating projects and scenes on Unity for product testing.

Working with the Backend.

• Created Web applications for internal use by product managers for quick and secure access to the MongoDB database. The application was written using the Django framework.
• I was involved in product management support (before I proposed and created the web application described above). I use Postman and the API available on the backend interacted with the MongoDB database.

Another coding using Python.

• Creating scripts for archiving test data using shutil.
• Creating scripts for working with GoogleDisk and the file system using argparse and pydrive.
• Worked with images using the Pillow library.

Tech stack: Python, Django, Djongo, PyMongo, PyDrive, Pillow MongoDB, Postman, Jenkins, python-jenkins, HTML, CSS, Git, Windows, Linux, Mac, Bash, Shell, PowerShell, Unity, C#, Scrum.

• Development of internal API in Django to improve the functionality of the platform.
• Support and optimization of the existing web platform, including the implementation of new features.
• Creation and support of telegram bots integrated with the web platform.
• Creating an asynchronous telegram bot and a parser for it.
• Creation of telegram parsers.

Tech stack: Python, Django, Django REST, Postman, Postgres, SQLite, Unittest, Sentry, Git, Linux, HTML, CSS, JS, python-telegram-bot, pyTelegramBot, Telethon, Pillow, asyncio.

• Development and configuration of a telegram bot in Python, integrated with the Django framework.

Tech stack: Python, Django, Django REST, Postman, SQLite, python-telegram-bot, Git, Linux.