Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] conan config reset #5935

Open
1 task done
monsdar opened this issue Oct 18, 2019 · 4 comments · May be fixed by #17514
Open
1 task done

[feature] conan config reset #5935

monsdar opened this issue Oct 18, 2019 · 4 comments · May be fixed by #17514

Comments

@monsdar
Copy link
Contributor

monsdar commented Oct 18, 2019

We're using conan config install <git-repo> within our CI environment. For our Windows builds we do not use Docker yet, they're just VMs and work like so:

  1. Developer pushes changes to a repo
  2. CI connects to one of the Windows VMs
  3. CI uses conan config install to get the latest profiles and configuration for Conan
  4. CI builds and tests the repo
  5. CI uploads the Conan package
  6. CI disconnects. Windows VM waits for the next job.

As you can see Windows jobs are not running within a sandboxed environment. That means when we do conan config install and install profileA it will remain there also for future jobs. To work around this we can clear the profiles directory before doing conan config install, but this is not as clean as it could be.

Therefore this feature request is to implement something like conan config reset or conan config uninstall. The command should reset the Conan config to its original state. It would help to have CI mechanisms a bit cleaner and would avoid us to implement any workarounds that may or may not work as intended and with future versions.

@czoido
Copy link
Contributor

czoido commented Oct 18, 2019

Hi @monsdar,
Thank's a lot for the feedback, we'll give a thought at the feature for future developments :)

@sbudenkov
Copy link

Hi,
Do you have a plan for this feature? Will be very useful.

@memsharded
Copy link
Member

@sbudenkov

I think that is conan config init, that was added some time ago. It seems that this issue was not correctly closed, please check it and let us know.

@sbudenkov
Copy link

Hi @memsharded,

Looks like no.
Cmd: conan config init --force doesn't clean files and folders in .conan directory.
Please check the original post out:

That means when we do conan config install and install profileA it will remain there also for future jobs. To work around this we can clear the profiles directory before doing conan config install, but this is not as clean as it could be.

@memsharded memsharded linked a pull request Dec 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants