Removing the continue on error. #1273
dotnet-core-docker.yml
on: push
frontend-build
3m 56s
backend-pn-build
9m 16s
items-planning-test-dotnet
55s
greatebelt-dotnet-test
1m 4s
workflow-dotnet-test
49s
backend-pn-test-dotnet
1m 19s
timeplanning-pn-dotnet-test
56s
service-build
20s
timeplanning-service-build
3m 10s
items-planning-service-build
3m 4s
workflow-service-build
2m 45s
backend-configuration-service-build
8m 44s
greate-belt-pn-build
4m 33s
items-planning-build
8m 20s
timeplanning-pn-build
4m 32s
workflow-build
4m 12s
Matrix: frontend-test
frontend-test-dotnet
1m 5s
Matrix: backend-pn-test
Matrix: items-planning-test
Matrix: timeplanning-pn-test
Annotations
154 warnings
service-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
service-build
The variable 'ex' is declared but never used
|
service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
service-build
The variable 'ex' is declared but never used
|
service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
workflow-dotnet-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-test-dotnet
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-test-dotnet
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
items-planning-test-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
items-planning-test-dotnet
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
items-planning-test-dotnet
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
timeplanning-pn-dotnet-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
timeplanning-pn-dotnet-test
Non-nullable property 'Date' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'YesterDay' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'Worker' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'PlanText' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'SumFlexStart' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'SumFlexEnd' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'Message' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'CommentWorker' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
Non-nullable property 'CommentOffice' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
timeplanning-pn-dotnet-test
'SentryOptions.EnableTracing' is obsolete: 'Use TracesSampleRate or TracesSampler instead'
|
greatebelt-dotnet-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test-dotnet
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
backend-pn-test-dotnet
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
workflow-service-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
workflow-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
workflow-service-build
The variable 'ex' is declared but never used
|
workflow-service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
workflow-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
workflow-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
workflow-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
workflow-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
items-planning-service-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
items-planning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
items-planning-service-build
The variable 'pattern' is assigned but its value is never used
|
items-planning-service-build
The variable 'pattern' is assigned but its value is never used
|
items-planning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
items-planning-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
items-planning-service-build
The variable 'ex' is declared but never used
|
items-planning-service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
items-planning-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
items-planning-service-build
The variable 'pattern' is assigned but its value is never used
|
timeplanning-service-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
timeplanning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
timeplanning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
timeplanning-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
timeplanning-service-build
The variable 'ex' is declared but never used
|
timeplanning-service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
timeplanning-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
timeplanning-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
frontend-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
workflow-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
workflow-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
workflow-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
workflow-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
greate-belt-pn-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
timeplanning-pn-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test-dotnet
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test-dotnet
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
frontend-test-dotnet
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
frontend-test-dotnet
Non-nullable property 'GroupUid' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
frontend-test-dotnet
Non-nullable property 'Description' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
frontend-test-dotnet
'SentryOptions.EnableTracing' is obsolete: 'Use TracesSampleRate or TracesSampler instead'
|
frontend-test-dotnet
Use IHeaderDictionary.Append or the indexer to append or set headers. IDictionary.Add will throw an ArgumentException when attempting to add a duplicate key. (https://aka.ms/aspnet/analyzers)
|
frontend-test-dotnet
Use IHeaderDictionary.Append or the indexer to append or set headers. IDictionary.Add will throw an ArgumentException when attempting to add a duplicate key. (https://aka.ms/aspnet/analyzers)
|
frontend-test-dotnet
Use IHeaderDictionary.Append or the indexer to append or set headers. IDictionary.Add will throw an ArgumentException when attempting to add a duplicate key. (https://aka.ms/aspnet/analyzers)
|
frontend-test-dotnet
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
frontend-test-dotnet
Non-nullable property 'Name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
|
items-planning-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-configuration-service-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-dotnet@v3, docker/login-action@v2, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-configuration-service-build
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
backend-configuration-service-build
Unreachable code detected
|
backend-configuration-service-build
The variable 'hasCompliances' is assigned but its value is never used
|
backend-configuration-service-build
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
backend-configuration-service-build
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
backend-configuration-service-build
Unreachable code detected
|
backend-configuration-service-build
The variable 'hasCompliances' is assigned but its value is never used
|
backend-configuration-service-build
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-configuration-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
backend-configuration-service-build
The variable 'ex' is declared but never used
|
backend-configuration-service-build
Field 'ServiceLogic._eventHandlers' is never assigned to, and will always have its default value null
|
backend-configuration-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
backend-configuration-service-build
The variable 'pattern' is assigned but its value is never used
|
backend-configuration-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
backend-configuration-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
backend-configuration-service-build
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
|
backend-configuration-service-build
'HtmlConverter.ParseHtml(string, CancellationToken)' is obsolete: 'Use ParseBody instead for output clarification'
|
backend-configuration-service-build
The variable 'hasCompliances' is assigned but its value is never used
|
backend-configuration-service-build
The type 'RebusHandlerInstaller' in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusHandlerInstaller.cs' conflicts with the imported type 'RebusHandlerInstaller' in 'Microting.eForm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusHandlerInstaller.cs'.
|
backend-configuration-service-build
The type 'RebusInstaller' in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusInstaller.cs' conflicts with the imported type 'RebusInstaller' in 'Microting.eForm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusInstaller.cs'.
|
backend-configuration-service-build
Non-nullable field '_container' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
Non-nullable field '_bus' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
Non-nullable field '_dbContext' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
The type 'RebusHandlerInstaller' in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusHandlerInstaller.cs' conflicts with the imported type 'RebusHandlerInstaller' in 'Microting.eForm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusHandlerInstaller.cs'.
|
backend-configuration-service-build
The type 'RebusInstaller' in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusInstaller.cs' conflicts with the imported type 'RebusInstaller' in 'Microting.eForm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. Using the type defined in '/home/runner/work/work-items-planning-container/work-items-planning-container/eform-service-backendconfiguration-plugin/ci/eformparsed/Installers/RebusInstaller.cs'.
|
backend-configuration-service-build
Non-nullable field '_container' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
Non-nullable field '_bus' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
Non-nullable field '_dbContext' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-configuration-service-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
greate-belt-pn-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
backend-pn-build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
frontend-test (e)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (f)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (d)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
workflow-test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (j)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (c)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (b)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (a)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (i)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
timeplanning-pn-test (a)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-test (b)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-test (a)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (g)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
frontend-test (h)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
items-planning-test (c)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (e)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (f)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (a)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (b)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (d)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (c)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (j)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (g)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (h)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
backend-pn-test (i)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, actions/setup-node@v3, cypress-io/github-action@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
deploy-service
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
deploy-service
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
deploy
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/download-artifact@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
deploy
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "container", "greate-belt-container", "items-planning-container", "time-planning-container", "workflow-container", "work-items-planning-container", "work-items-planning-service-container".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
container
|
305 MB |
|
greate-belt-container
|
463 MB |
|
items-planning-container
|
2.26 GB |
|
time-planning-container
|
371 MB |
|
work-items-planning-container
|
2.26 GB |
|
work-items-planning-service-container
|
2.17 GB |
|
workflow-container
|
390 MB |
|