Made Smart Publish and Revert Workflow

[anantakumarghosh]

This workflow triggers 4 workflows sequentially
All workflows are dependent in chaining way.
If current workflow runs successfully, then only next workflow will be triggered.
If any of the workflow fails, published packages by the workflow run are deleted, and version gets decremented
Here is a screenshot :)

[samhere17]

This is a good one... will be very helpful.

Can we extend it to pass parameters to cherry-pick the repos we want to publish?
@anantakumarghosh let me know your thoughts.

@techoneel @sumanta-m

[techoneel]

Well cherry pick the repos will be a great idea.

But in terms of sequencing I'd suggest the below structure:

• styles
  • sc-web
  • sc-mobile
    • core

Explanation:

• Publish stylespackage
  If success
• Publish sc-web & sc-mobile package together
  If success
• Publish core package

[anantakumarghosh]

If you are thinking of a dynamic approach, based on my current knowledge, I don't know yet. As for passing repos as arguments, I think it should be possible, number of repos will need to be maintained. Current workflow can do only 4 repos, not more or less. It is possible to make separate workflows for specified number of repos that will take repo name as argument.

Or if I'm not understanding you, lets do a meet after my internals are over and when you are available.

[samhere17]

@techoneel I agree and I think @anantakumarghosh has followed steps as mentioned by you.

@anantakumarghosh You understood correct. I suggest to pass repo name(s) as argument. It should be a list of repos with dependencies. Lets discuss in details when we are available next.

[anantakumarghosh]

Smart publish is not used anymore. Fast Publish is used.
Hence, closing this discussion.