1

I'm trying to update a solution from vs10 to vs 2017 by line command devenv /upgrade from a job gitlab.

The weird thing is that it works fine by launching it locally with powershell but fail with gitlab job

Example

devenv.exe "Src\GenATC.sln" /upgrade

the job at gitlab :

code-migration:
  stage: migration
  allow_failure: true
  tags:
    - WINDOWS
    - VS2013
  only:
    - "master"
  artifacts:
    name: Executable
    when: on_success
    expire_in: 1 week
  script:
    - '& "path to devenv\devenv.exe" "Src\GenATC.sln" /upgrade'
jessehouwing
  • 106,458
  • 22
  • 256
  • 341
Raz Ysn
  • 11
  • 1
  • I think the `/upgrade` commands requires an interactive session to start Visual Studio and show UI. It's also not guaranteed to not block... So it's not the ideal thing to do in a pipeline. What are you trying to do that requires this, generally one-time action? – jessehouwing Jul 24 '20 at 12:33
  • Thank you but locally we don't have to have interraction with the UI – Raz Ysn Jul 24 '20 at 12:52
  • But visual studio likely still depends on the message pump and an active windows session to work. – jessehouwing Jul 24 '20 at 16:19

0 Answers0