Skip to content

Instantly share code, notes, and snippets.

@bethesque

bethesque/current.txt

Last active October 5, 2020 09:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save bethesque/2d4a538b6efd80ec41ddec35eed7d068 to your computer and use it in GitHub Desktop.
Save bethesque/2d4a538b6efd80ec41ddec35eed7d068 to your computer and use it in GitHub Desktop.
Download ZIP
WIP
Raw
current.txt
Current definition of WIP:
No successful verifications exist for the pact content by a provider version with the specified tag.
main ref1, basePact
create branchA refA, basePact+integrationA
create branchB refB, basePact+integrationB
main provider build runs, configured to verify main pacts, and WIP pacts.
basePact (explicit), basePact+integrationA (wip), basePact+integrationB (wip) all verified successfully
basePact+integrationA and basePact+integrationB no longer WIP
can-i-deploy refA --to master => true
can-i-deploy refB --to master => true
main provider build runs
basePact (explict) verified successfully,
can-i-deploy refA --to master => false
can-i-deploy refB --to master => false
Raw
potential.txt
Potential new definition of WIP:
No successful verification by a provider version with the specified tag AND also never verified as an explicitly included pact.
main ref1, basePact
create branchA refA, basePact+integrationA
create branchB refB, basePact+integrationB
main provider build runs, configured to verify main pacts, and WIP pacts.
basePact (explicit), basePact+integrationA (wip), basePact+integrationB (wip) all verified successfully
basePact+integrationA and basePact+integrationB still WIP because their content was explicitly selected
can-i-deploy refA --to master => true
can-i-deploy refB --to master => true
main provider build runs, configured to verify main pacts, and WIP pacts.
basePact (explicit), basePact+integrationA (wip), basePact+integrationB (wip) all verified successfully
basePact+integrationA and basePact+integrationB still WIP because their content was explicitly selected
merge refA into main (provider build triggered by webhook because new tag has been applied to existing content), no longer WIP
merge refB into main (provider build triggered by webhook because new tag has been applied to existing content), no longer WIP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment