Details
Description
For example, if A and B both working for same project go through the same onboarding process, then this will duplicate or overwrite things like:
- CONAN_USER
- CONAN_PASS
- JFROG_USER
- JFROG_PASS
So, we should probably ask the user:
- My project already uses Qt cloud.
- I am reinstalling (or installing) the plugin
- I will have to setup Qt cloud for my project from scratch
Some more discussion is required around this.
We should also consider - if user A has configured the Gitlab project to use his CONAN credentials and then is it OK for the whole team to use the same credentials or then, we should find some other way of using the conan credentials? Or should there be a "team conan credentials"?
Some changes in onboarding steps:
- Ask Qt account
- Get token
- Check licence
- Gitlab info prompt
- My project already uses Qt cloud
- I need to setup Qt cloud for my project
Conclusion or closure
**At this point, all the variables are just overwritten. However, at the soonest, we should do the following:
- Show all the variables that may be overwritten to the user and ask them if they want to overwrite it or not?
- Create an API for writing (or overwriting) one CI variable to the Gitlab Project
Another approach could be:
- Create variables with prefix or suffix, for example:
- QTCLOUD_CONAN_USER_${GITLAB_USER_ID}
- QTCLOUD_CONAN_PASS_${GITLAB_USER_ID}
Then, in the .gitlab-ci.yml, we should refer the variables with the above notation. We have to find if this is actually possible or not? If yes, then this is the best method.