Use unique bucket names in scenarios where the name is not random

[williamlardier]

Issue: ZENKO-4932

We had a scenario using the same (fixed) bucket name. In these kind of scenarios, this is required.
But then if they run in parallel we might have the same bucket being deleted / re-created, and eventually the hook at the end, cleaning up the existing buckets, will fail because of this concurrency problem. The solution is to use unique bucket names.

[bert-e]

Hello williamlardier,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[KillianG]

Should be great to be able to pass variables generated during the test in the examples, so that the given an existing bucket ... will create an bucket named randomly and in the examples we put something like {bucketName} and it takes the one generated in the beginning
Not sure if it is feasable tho..

[williamlardier]

We do that in most scenarios, but here we need to specify the resource name, and we actually want to have control over it because sometimes we alter it, so we want to keep it... Still possible to have it fully automatic but we still need to keep support for static bucket names. For example, the bucket used for website must be named "website".

[KillianG]

I know we do that in most scenario, what I suggest here is to be able to use it in example, so here for example we could do ${bucketName}/* in the ressource name
But ofc we need to keep support for creating static bucket names

[williamlardier]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge bugfix/ZENKO-4932 into
  development/2.6
• w/2.7/bugfix/ZENKO-4932 will be merged into development/2.7
• w/2.8/bugfix/ZENKO-4932 will be merged into development/2.8
• w/2.9/bugfix/ZENKO-4932 will be merged into development/2.9
• w/2.10/bugfix/ZENKO-4932 will be merged into development/2.10

The following branches will NOT be impacted:

• development/2.5

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

Build failed

The build for commit did not succeed in branch bugfix/ZENKO-4932.

The following options are set: approve

[bert-e]

Build failed

The build for commit did not succeed in branch w/2.9/bugfix/ZENKO-4932.

The following options are set: approve