update name #11016
sinehomeglobal-ci.yml
on: push
flex-ci
/
lint
3m 58s
flex-ci
/
unit-test
5m 25s
flex-ci
/
ui-test
6m 15s
flex-ci
/
upload-plugin
4m 59s
webchat-ci
/
build
58s
webchat-ci
/
lint
31s
webchat-ci
/
test
32s
aselo-webchat-react-app-ci
/
lint
1m 13s
aselo-webchat-react-app-ci
/
unit-test
1m 28s
aselo-webchat-react-app-ci
/
upload-aselo-webchat-react-app
2m 32s
twilio-lambda-ci
/
Run Tests
2m 56s
Matrix: twilio-lambda-ci / Build Lambda Image
Annotations
49 warnings
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L20
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
Legacy key/value format with whitespace separator should not be used:
lambdas/Dockerfile#L18
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format
More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
|
|
The 'as' keyword should match the case of the 'from' keyword:
lambdas/Dockerfile#L15
FromAsCasing: 'as' and 'FROM' keywords' casing do not match
More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
|
|
flex-ci / lint:
lambdas/account-scoped/src/integrations/iwf/reportToIWF.ts#L64
Returning an awaited value that is not a promise is not allowed
|
|
flex-ci / lint:
lambdas/account-scoped/src/conversation/chatChannelJanitor.ts#L57
Returning an awaited value that is not a promise is not allowed
|
|
flex-ci / lint:
plugin-hrm-form/src/components/search/ConnectDialog.tsx#L80
Expected the depth of nested jsx elements to be <= 5, but found 6
|
|
flex-ci / lint:
plugin-hrm-form/src/components/search/ConnectDialog.tsx#L79
Expected the depth of nested jsx elements to be <= 5, but found 6
|
|
flex-ci / lint:
plugin-hrm-form/src/components/search/ConnectDialog.tsx#L69
Expected the depth of nested jsx elements to be <= 5, but found 6
|
|
flex-ci / lint:
plugin-hrm-form/src/components/case/CloseCaseDialog.tsx#L59
Expected the depth of nested jsx elements to be <= 5, but found 6
|
|
flex-ci / lint:
plugin-hrm-form/src/components/case/CloseCaseDialog.tsx#L54
Expected the depth of nested jsx elements to be <= 5, but found 6
|
|
flex-ci / ui-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v1, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
flex-ci / ui-test
No files were found with the provided path: ./e2e-tests/temp. No artifacts will be uploaded.
|
|
flex-ci / ui-test
No files were found with the provided path: ./e2e-tests/test-results. No artifacts will be uploaded.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
techmatters~flex-plugins~18LVN4.dockerbuild
|
41.2 KB |
sha256:a780d08c49bba08d938e9169ab3363089d5fa41607583f99695a3a28534de633
|
|
|
techmatters~flex-plugins~2H23AQ.dockerbuild
|
32 KB |
sha256:ded44ca98bbad0f86345083a2dd298a73cd91abd507711f67f7bba0bc8ab6923
|
|
|
techmatters~flex-plugins~HA2TBA.dockerbuild
|
38.5 KB |
sha256:caf0f9d24e565395e4d9d80cc864463656e27c07bc77b84201cdc80febca409f
|
|
|
techmatters~flex-plugins~IDOZUM.dockerbuild
|
41.1 KB |
sha256:054dcf84808c21aec3060b1cc4169b6c66661cc57c5bb3c2714db270e64356db
|
|
|
techmatters~flex-plugins~IH10MZ.dockerbuild
|
39.6 KB |
sha256:add9ca5fada7ad95999f6c51169371d81b4f7657b823561015e7f2e46e08a174
|
|
|
techmatters~flex-plugins~JJ6PLB.dockerbuild
|
40.2 KB |
sha256:b00eb15a821a8f9365108f13ede552a6007df8934fddc2524349b48acbb988d8
|
|
|
techmatters~flex-plugins~JNOTN7.dockerbuild
|
39.7 KB |
sha256:c4f8db627d44cf312478719a82346edafa2a1a8f71be839a73914c65533c70b5
|
|
|
techmatters~flex-plugins~KX0TCN.dockerbuild
|
97 KB |
sha256:bec0940d74a4b8ecc6108cc8713f7ae4fd0714a1deff86935e376aa053bdc8f4
|
|
|
techmatters~flex-plugins~PBXZWC.dockerbuild
|
32.7 KB |
sha256:c99031b4018fd9e2834b0eee913f08bd133adb1b8090441d7f8ffb7f66125379
|
|
|
techmatters~flex-plugins~R23XBW.dockerbuild
|
63.3 KB |
sha256:914445c1b4211ae959ab80da07b73bbac3de2e1bc74256a651f9948ddf2dccc3
|
|
|
techmatters~flex-plugins~T29SP3.dockerbuild
|
26.8 KB |
sha256:785c9ca42dc8245013ccb0834e83966b57a63fee2eb924f229bfcc3d8dfc2829
|
|
|
techmatters~flex-plugins~VLQBCA.dockerbuild
|
31.2 KB |
sha256:48824894bb08dc4fd83f2811f2be06349a3ee0cd493408fa8e1682caec374ef4
|
|
|
techmatters~flex-plugins~Z53GTC.dockerbuild
|
37 KB |
sha256:be8ff37ac18ab41a7ce42f5145e104011791591f11008c7b9b788d26a2ee5e9c
|
|