Issue #579 - Creating project before uploading allure results

[PatStLouis]

Signed-off-by: Patrick St-Louis patrick.st-louis@idlab.org

This PR adds a call to the /allure-docker-service/projects api endpoint before uploading the results. If the project already exists, it will simply upload the results to the existing project.

[PatStLouis]

@swcurran here is a signed PR. The afgo agent is still having a hard time building, with the following errors.

# github.com/hyperledger/aries-framework-go/pkg/didcomm/protocol/didexchange
../../pkg/didcomm/protocol/didexchange/didex_interop.go:62:17: undefined: didcommutil
note: module requires Go 1.19
make: *** [Makefile:135: agent-rest-acapy-interop] Error 2
The command "/bin/sh -c GO_TAGS=${GO_TAGS} GOPROXY=${GOPROXY} make agent-rest-acapy-interop" returned a non-zero code: 2
Docker image build failed.
Error: Process completed with exit code 1.

Would bumping the version of ARG GO_VER=1.16 to ARG GO_VER=1.19 in the Dockerfile.afgo-interop and Dockerfile.afgo-master fix this? Not sure if this would break other stuff

[swcurran]

Aware of the AF-Go issue -- I've created this issue for it in the AF-Go repo: hyperledger-archives/aries-framework-go#3396

Thanks for the fix! @nodlesh -- can you please review?

[nodlesh]

This is great @PatStLouis.

So the call to create the project doesn't do anything if it finds it already there? If so, this is much simpler than I thought, and absolutely meets the criteria for #579.

[PatStLouis]

This is what we are using internally and what you describe is the observed behavior. It makes a post request to create the project, if the project already exists it will simply carry on and append the results to the existing project.

In case the project already exists, it will return a 400 {"message": "project_id '<project_id>' is existent"}