slnodejs 6.1.361 → 6.1.372

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (50) hide show
  1. package/README.md +0 -23
  2. package/browser-agent/dist/browser-agent-all.js +376 -280
  3. package/browser-agent/dist/browser-agent-all.min.js +3 -3
  4. package/browser-agent/package.json +1 -1
  5. package/package.json +1 -1
  6. package/tsOutputs/cli-parse/cli.js +10 -9
  7. package/tsOutputs/cli-parse/cli.js.map +1 -1
  8. package/tsOutputs/cli-parse/executors/base-executor.js +2 -2
  9. package/tsOutputs/cli-parse/executors/base-executor.js.map +1 -1
  10. package/tsOutputs/cli-parse/executors/build-end-executor.js +2 -2
  11. package/tsOutputs/cli-parse/executors/build-end-executor.js.map +1 -1
  12. package/tsOutputs/cli-parse/executors/build-executor.js +6 -6
  13. package/tsOutputs/cli-parse/executors/build-executor.js.map +1 -1
  14. package/tsOutputs/cli-parse/executors/config-executor.js +5 -4
  15. package/tsOutputs/cli-parse/executors/config-executor.js.map +1 -1
  16. package/tsOutputs/cli-parse/executors/integration-build-components-executor.js +4 -4
  17. package/tsOutputs/cli-parse/executors/integration-build-components-executor.js.map +1 -1
  18. package/tsOutputs/cli-parse/executors/start-execution-executor.js +1 -0
  19. package/tsOutputs/cli-parse/executors/start-execution-executor.js.map +1 -1
  20. package/tsOutputs/cli-parse/executors/test-listener-executor.js +1 -1
  21. package/tsOutputs/cli-parse/executors/test-listener-executor.js.map +1 -1
  22. package/tsOutputs/cli-parse/executors/upload-report-executor.js +1 -1
  23. package/tsOutputs/cli-parse/executors/upload-report-executor.js.map +1 -1
  24. package/tsOutputs/common/agent-events/agent-events-conracts.d.ts +1 -0
  25. package/tsOutputs/common/agent-events/agent-events-conracts.js +1 -0
  26. package/tsOutputs/common/agent-events/agent-events-conracts.js.map +1 -1
  27. package/tsOutputs/common/config-process/config.d.ts +2 -0
  28. package/tsOutputs/common/config-process/config.js +2 -0
  29. package/tsOutputs/common/config-process/config.js.map +1 -1
  30. package/tsOutputs/common/contracts.d.ts +1 -0
  31. package/tsOutputs/common/http/backend-proxy.d.ts +1 -1
  32. package/tsOutputs/common/http/backend-proxy.js +2 -2
  33. package/tsOutputs/common/http/backend-proxy.js.map +1 -1
  34. package/tsOutputs/common/http/contracts.d.ts +2 -0
  35. package/tsOutputs/common/http/contracts.js.map +1 -1
  36. package/tsOutputs/common/http/sl-routes.d.ts +1 -1
  37. package/tsOutputs/common/http/sl-routes.js +5 -3
  38. package/tsOutputs/common/http/sl-routes.js.map +1 -1
  39. package/tsOutputs/common/state-tracker.js +3 -0
  40. package/tsOutputs/common/state-tracker.js.map +1 -1
  41. package/tsOutputs/test-listener/contracts.d.ts +7 -0
  42. package/tsOutputs/test-listener/execution-process/execution-service-proxy.js +3 -0
  43. package/tsOutputs/test-listener/execution-process/execution-service-proxy.js.map +1 -1
  44. package/tsOutputs/test-listener/factory.js +3 -1
  45. package/tsOutputs/test-listener/factory.js.map +1 -1
  46. package/tsOutputs/test-listener/nyc-report-executor.js +2 -2
  47. package/tsOutputs/test-listener/nyc-report-executor.js.map +1 -1
  48. package/tsOutputs/test-listener/test-recommendation-handler.d.ts +3 -1
  49. package/tsOutputs/test-listener/test-recommendation-handler.js +14 -10
  50. package/tsOutputs/test-listener/test-recommendation-handler.js.map +1 -1
package/README.md CHANGED
@@ -1,24 +1 @@
1
1
  # SL.OnPremise.Agent.JavaScript
2
- ## Publish
3
- ### Node agent
4
-
5
- 1. Check the latest public version `run npm view slnodejs time`
6
- 2. Go to main [build job](http://jenkins2.dev.sealights.co:8080/view/AGENTS/job/SL.OnPremise.Agent.JavaScript/job/main) and get latest successful build number (6.1.278 for example)
7
- - **IMPORTANT**: if by any case the build version you want to publish is failed please start investigate and make sure it fixed, do not leave the main branch dirty
8
- 3. Trigger the [publish job](http://jenkins2.dev.sealights.co:8080/view/AGENTS/job/Deploy%20node%20agent%20mono%20repo) and provide the build number
9
-
10
- - **Note**: please make sure to separate between base and minor version
11
- 4. Verify agent published by running again `npm view slnodejs time`
12
- 5. Collect the Jira tickets included in each build
13
- - **Note**: ideally should be in the commit message which included in the changes section in the top build details page
14
- 6. Update the [release notes file](https://sealights.atlassian.net/wiki/spaces/DEV/pages/559415316/Node+Agent+Releases) and include links to jira tickets in the relevant column
15
- - **IMPORTANT**: in case of changes affects the browser agent add browser-agent in Changed components and follow a [browser agent publish guide](#browser-agent)
16
- 7. For each ticket update status to Deployed and set the version in the Handle in version field
17
-
18
- ### Browser agent
19
-
20
- If you need to publish new version of browser agent you need to publish node agent first and then:
21
-
22
- 1. Ask someone from DevOps team (currently [Jason](https://sealights.slack.com/archives/D04NBJD0RB7)) to publish js bundle in S3. Just provide them a version number.
23
- 2. Check that version accessible by link `https://agents.sealights.co/browser/{version-number}/browser-agent-all.min.js`
24
- 3. Check that recommended version for customers updated. You can check [here](https://sealights.slack.com/archives/CL4AQKXEY) or by executing `/api/v1/agents/browser/recommended?customerId={customerId}`