hi we are moving to `deployedOrReleased` and i want to clari Pact Foundation #general

hi! we are moving to `deployedOrReleased` and i wa...

Dmitry Munda

12/07/2022, 12:16 PM

hi! we are moving to

deployedOrReleased

and i want to clarify one more stuff • we deploy FE app( lets say twice a week ) , which has some support time and is marked as released • we deploy BE ( lets say twice a week ) both FE and BE parts could be consumers and providers current BE has

deployedOrReleased

selectors, so it verifies all FE in the wiled -thats ok 🙂 at which point / how FE part ( marked as released , lets say 2 months ago ) will be verified against upcoming BE part ?

Matt (pactflow.io / pact-js / pact-go)

12/12/2022, 12:21 PM

When the FE makes a new change it will publish a new contract. At this point can I deploy will fail until the provider has implemented and deployed the change. If the FE makes a change that doesn't modify the contract it's preverifed and can I deploy will pass.

👍 1

Matt (pactflow.io / pact-js / pact-go)

12/12/2022, 12:22 PM

It's the same as tags, am I missing something?

Dmitry Munda

12/12/2022, 12:42 PM

when MR is being merged its being tested against deployed and released versions • provider is compliant with all version • consumer updates or not pact

Dmitry Munda

12/12/2022, 12:43 PM

if half year old FE provider will be not ok with current BE - BE consumer will be not allowed to be merged/deployed - this will be detected on c-i-d stage

Dmitry Munda

12/12/2022, 12:45 PM

if half year old FE consumer will be not ok with current BE - BE provider tests will fail on tests stage ( as

deployedOrReleased

selector is there )

Dmitry Munda

12/12/2022, 12:45 PM

am i correct ?

Dmitry Munda

12/12/2022, 12:46 PM

looks like i finally managed to formulate this 😄

Dmitry Munda

12/12/2022, 12:50 PM

message has been deleted

😆 1

Open in Slack

Previous Next