Implement Pact support in FOLIO modules and CI/CD pipeline
(FOLIO-1477)
|
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Implement Pact support in FOLIO modules and CI/CD pipeline |
| Type: | Story | Priority: | P3 |
| Reporter: | Anton Emelianov (Inactive) | Assignee: | Matt Reno |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | Pact | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Story Points: | 3 |
| Epic Link: | Implement Pact support in FOLIO modules and CI/CD pipeline |
| Comments |
| Comment by Matt Reno [ 14/Sep/18 ] |
|
The story thus far... implemented Pact verification in mod-users driven by ui-checkin. Regressions with the latest version of pact-jvm have caused slowed broker integration (the solution was to downgrade). However, we still need to figure out the best way to deal with dev builds that are not configured to use the hosted pact broker. Requiring devs to deploy the docker based Pact broker may be an option. If there are no pacts in the broker, the verification test will pass, which will allow the build to continue. Being unable to communicate with the broker will fail the build. Currently, Pact broker configuration is defined by environment variables. |
| Comment by Anton Emelianov (Inactive) [ 19/Mar/19 ] |
| Comment by Marc Johnson [ 21/Mar/19 ] |
|
Matt Reno Is this something you are still actively working on? |
| Comment by Matt Reno [ 21/Mar/19 ] |
|
No, but I told Anton I'd put what I had done into a branch in mod-users. I haven't had a chance yet. |