Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions lib/graphs/discovery-mgmtsku-graph.js
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,14 @@ module.exports = {
},
taskName: 'Task.Catalog.GenerateSku'
},
{
label: 'generate-enclosure',
waitOn: {
'discovery-mgmt-graph': 'succeeded'
},
taskName: 'Task.Catalog.GenerateEnclosure',
ignoreFailure: true
},
{
label: 'create-mgmt-default-pollers',
taskDefinition: {
Expand Down
8 changes: 8 additions & 0 deletions lib/graphs/discovery-sku-graph.js
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,14 @@ module.exports = {
},
taskName: 'Task.Catalog.GenerateSku'
},
{
label: 'generate-enclosure',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SKU generation failure will not impact the enclosure generation, so it requires to add "ignoreFailure: true" in generate-sku task, or move generate-enclosure to be before generate-sku.

In future we may need to define the SKU rule for enclosure.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The enclosure generation job will be run after discovery succeeded (see waitOn options), parallel with sku generation. So the sku generation doesn't impact enclosure generation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it.

waitOn: {
'discovery-graph': 'succeeded'
},
taskName: 'Task.Catalog.GenerateEnclosure',
ignoreFailure: true
},
{
label: 'create-default-pollers',
taskDefinition: {
Expand Down