mendersoftware / mender-mcu

26%

main: 61%

LAST BUILD ON BRANCH pr_143

branch: pr_143

CHANGE BRANCH

x

Reset

• pr_143
• HEAD
• main
• pr_100
• pr_101
• pr_102
• pr_103
• pr_104
• pr_105
• pr_106
• pr_107
• pr_108
• pr_109
• pr_110
• pr_111
• pr_112
• pr_113
• pr_114
• pr_115
• pr_117
• pr_118
• pr_119
• pr_120
• pr_121
• pr_122
• pr_123
• pr_124
• pr_125
• pr_126
• pr_127
• pr_128
• pr_129
• pr_130
• pr_131
• pr_134
• pr_136
• pr_137
• pr_138
• pr_139
• pr_140
• pr_141
• pr_142
• pr_144
• pr_145
• pr_146
• pr_147
• pr_148
• pr_149
• pr_150
• pr_152
• pr_153
• pr_154
• pr_155
• pr_156
• pr_157
• pr_158
• pr_159
• pr_160
• pr_161
• pr_162
• pr_163
• pr_164
• pr_165
• pr_166
• pr_167
• pr_168
• pr_169
• pr_170
• pr_172
• pr_173
• pr_175
• pr_176
• pr_177
• pr_178
• pr_179
• pr_180
• pr_181
• pr_182
• pr_183
• pr_184
• pr_185
• pr_186
• pr_187
• pr_188
• pr_189
• pr_190
• pr_191
• pr_192
• pr_193
• pr_194
• pr_195
• pr_196
• pr_197
• pr_198
• pr_199
• pr_200
• pr_201
• pr_205
• pr_206
• pr_207
• pr_209
• pr_210
• pr_212
• pr_213
• pr_214
• pr_215
• pr_216
• pr_62
• pr_65
• pr_93
• pr_97
• pr_98
• pr_99
• test-coverage

Build # 1659047404

Build Type

push

gitlab-ci

Committed by vpodzime

Commit Message

fix: Allow `null` values in deployment data

Some of the fields in deployment data are initialized to `null`
because they are populated later from other places. Not allowing
`null` values in such fields thus means that freshly created and
initialized deployment data is not valid until those fields are
populated. The data is validated every time we try to store it in
non-volatile memory so it either needs to never be saved until
being fully populated or we need to consider not-fully-populated
deployment data valid. However, since the state of the client is
saved as part of the deployment data, the latter approach is
required because otherwise we can't even save the client's state
in some cases.

Ticket: MEN-7934
Changelog: none
Signed-off-by: Vratislav Podzimek <vratislav.podzimek@northern.tech>

Run Details

0 of 2 new or added lines in 1 file covered. (0.0%)

739 of 2851 relevant lines covered (25.92%)

8.55 hits per line