virtocommerce / jenkins-pipeline-scripts Goto Github PK

• use any commit in https://github.com/VirtoCommerce/vc-content deploy branch as trigger for run CI/CD pipeline
• The CI process should be the same as we have for vc-default-theme. (gulp build task, sonar validation, prepare temporary env for the latest Storefront and Platform versions with default modules, install only this vc-content theme, run special E2E tests for virtocommerce.com (ask @blazemachine where to get them)
• The all changes after successfully passing CI pipeline should automatically published on the Azure production environment

Problem:
Now it's very hard to work with the Jenkinse log, because no all messages with any severity don't highlighted, and this increase complexity of log analyse.

Problem:
CI cannot build the solution targeting .NET Core 2.2: example branch.

Error:
The current .NET SDK does not support targeting .NET Core 2.2. Either target .NET Core 2.1 or lower, or use a version of the .NET SDK that supports .NET Core 2.2.

Current msbuild version: "Microsoft (R) Build Engine version 15.7.179.6572 for .NET Framework".

Proposed changes:
Install .NET Core SDK 2.2.

https://github.com/VirtoCommerce/jenkins-pipeline-scripts/blob/master/src/jobs/scripts/Modules.groovy#L64
VIRTO_CONN_STR_VirtoCommerce=Data Source=http://ci.virtocommerce.com:${sqlPort};Initial Catalog=VirtoCommerce2;Persist Security Info=True;User ID=sa;Password=v!rto_Labs!;MultipleActiveResultSets=True;Connect Timeout=30

http://ci.virtocommerce.com:1433 (34, 35, etc...) is not available. SQL Server Management Studio can't connect to it as well as VirtoCommerce module integration tests.

Problem
It is necessary to monitor the performance dynamics for solutions based on VC platform.

Functional requirements

• See the key performance indicators, such as response time and throughput for the storefront and platform API, obtained during stress tests on specially prepared sample data that are almost entirely consistent with the typical solution built on the VC platform.
  https://github.com/VirtoCommerce/vc-benchmark
• Do all tests on Azure environments
• Regular run at scheduled time or depending on event
• Allow to see benchmark report online with dynamic over time
• Allow to receive reports by email.

Need to execute all E2E tests taken from https://github.com/VirtoCommerce/vc-platform-qg on the temporary environment (Docker) for each commit in master/ dev branches of all observed repositories.

Problem
Currently not all CI/CD actions that we performed in pipeline defined as separated step, and this face complicates understanding and usage of current pipeline process for end-user.

Would be nice to see all steps described in https://github.com/VirtoCommerce/jenkins-pipeline-scripts/blob/master/README.md in Jenkinse pipeline web interface too.

This function: https://github.com/VirtoCommerce/jenkins-pipeline-scripts/blob/master/src/jobs/scripts/Utilities.groovy#L74 take release notes from .NET Core project and tries to pass it to github-release, but does not escape quotes in this string, so you may get construction like this:
github-release release --user VirtoCommerce --repo vc-storefront-core --tag v3.0.3 --description "[PRE-RELEASE]<br>- Load a user-defined settings from the special section.<br>- Correct display of the "Access Denied" page"
Here we have "[PRE-RELEASE] ... display of the "Access Denied" page".
Look at http://ci.virtocommerce.com/blue/organizations/jenkins/vc-2-org%2Fvc-storefront-core/detail/master/66/pipeline for details.

Problem
All changes with these themes (https://github.com/VirtoCommerce/vc-theme-default, https://github.com/VirtoCommerce/vc-theme-b2b, https://github.com/VirtoCommerce/vc-theme-material) get on production only with sample data, it is the manual process that takes a more time.

Solution
Need to establish deployment process of all theme releases into demo.virtocommerce.com after successfully passed CI