tag:help.appveyor.com,2012-11-13:/discussions/problems/11613-latest-appveyor-update-causing-vc-projects-to-failAppVeyor: Discussion 2018-10-19T08:18:39Ztag:help.appveyor.com,2012-11-13:Comment/446239002018-01-31T00:24:51Z2018-01-31T00:24:51ZLatest Appveyor Update causing VC++ projects to fail<div><p>For the record, here is the project:<br>
<a href="https://ci.appveyor.com/project/BinCrafters/conan-lz4">https://ci.appveyor.com/project/BinCrafters/conan-lz4</a></p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-01T03:54:12Z2018-02-01T03:54:12ZLatest Appveyor Update causing VC++ projects to fail<div><p>We did not get any other similar reports and I could not repro it with <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/conan-lz4/build/1.0.1#L198">in my fork</a>. Seems that some secure variable is required. Please create repo we could fork and investigate.</p>
<p>Note that after next update current image will become "previous" so we need to understand what happened before. So public repo and any idea how you could manually fix this with current image will not hurt.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-02-10T04:05:00Z2018-02-10T04:06:13ZLatest Appveyor Update causing VC++ projects to fail<div><p>I just tried switching back to the current images, same problem.</p>
<p><a href="https://ci.appveyor.com/project/BinCrafters/conan-lz4/build/job/luxmigyubk7wdbo1">https://ci.appveyor.com/project/BinCrafters/conan-lz4/build/job/lux...</a></p>
<p>Here's the repository:<br>
<a href="https://github.com/bincrafters/conan-lz4">https://github.com/bincrafters/conan-lz4</a></p>
<p>Again, if I just change back to previous, it works :(</p>
<p>I guess I don't understand what you mean about secure variable being required. Can you provide any more detail about this statement?</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-10T04:36:34Z2018-02-10T04:36:34ZLatest Appveyor Update causing VC++ projects to fail<div><p>Let me explain what I mean... I forked your repo, simplified matrix (not needed all that variants for simple repro), set default branch to <code>stable/1.8.0</code> and started the build. <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/conan-lz4/build/1.0.1#L198">Error</a> I got is 'Exception: Upload not possible, 'password' is missing!'. I did not look deep, but I suspect that this 'password' is taken from some variable entered in UI (as I do not see anything in YAML).</p>
<p>Generally it would be great to have a repro as much in "hello word" style as possible. We should be able to clone it and have the same error without any knowledge of your build specifics.</p>
<p>I created <a href="https://github.com/appveyor/ci/issues/2072">this issue</a> to track this, because next image update will make current image to be "Previous" and what you use now as "Previous" will be gone.</p>
<p>Let me please stress once again that we need as simple and generic repro as possible, this will help us to narrow down the problem. This is especially important in this case where we have other reports of this issue.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-02-10T04:54:47Z2018-02-10T04:54:47ZLatest Appveyor Update causing VC++ projects to fail<div><p>I see, yes, I forgot conan checks to make sure you have credentials in place to upload the binaries before trying to compile them. However, it doesnt use them until after successful build. Thus, please just add the following environment variables to your appveyor project and it should satisfy the check, and then proceed to error during build:</p>
<p>CONAN_LOGIN_USERNAME<br>
CONAN_PASSWORD</p>
<p>yes, obviously, would be nice to have generic repro, but all our other builds are working on the current image. can't begin to imagine what's causing, so can't think of good way to isolate.</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-10T04:59:41Z2018-02-10T04:59:41ZLatest Appveyor Update causing VC++ projects to fail<div><p>You mean just add those variables with any values?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-02-10T05:01:27Z2018-02-10T05:01:27ZLatest Appveyor Update causing VC++ projects to fail<div><p>Yes, any values should do.</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-12T19:45:21Z2018-02-12T19:45:21ZLatest Appveyor Update causing VC++ projects to fail<div><p>Hi Ilya , were you able to reproduce with those variables populated?</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-12T22:47:29Z2018-02-12T22:48:08ZLatest Appveyor Update causing VC++ projects to fail<div><p>Just tried that. It <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/conan-lz4/build/1.0.5#L188">says</a>: <code>ERROR: Wrong user or password. [Remote: upload_repo]</code></p>
<p>Maybe you need to create some temporary restricted credentials for me. Ping me over email ilyaf at our company dot com, if you decide to do so.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-02-12T23:04:21Z2018-02-12T23:04:21ZLatest Appveyor Update causing VC++ projects to fail<div><p>Can you link me to your build log?</p>
<p>Gerald R. Wiltse<br>
<a href="mailto:jerrywiltse@gmail.com">jerrywiltse@gmail.com</a></p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-02-12T23:06:33Z2018-02-12T23:06:33ZLatest Appveyor Update causing VC++ projects to fail<div><p>Sure <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/conan-lz4/build/1.0.5#L188">https://ci.appveyor.com/project/IlyaFinkelshteyn/conan-lz4/build/1....</a></p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-02-17T21:55:14Z2018-02-17T21:55:14ZLatest Appveyor Update causing VC++ projects to fail<div><p>Thanks. Sorry for the back/forth. If you are still willing to spend time on this, please try to build the <code>testing/1.8.0</code> branch instead. The testing branch does not require credentials, and does not attempt to upload.</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-03-02T01:29:25Z2018-03-02T01:29:25ZLatest Appveyor Update causing VC++ projects to fail<div><p>Hi Gerald,<br>
I did some poking around in the project in question. I can’t say I fully understand your build tools but RDP’d into the build machine and ran devenv (visual studio 12.0) /upgrade manually and got the same error but then tried to use devenv (visual studio 14.0) and the upgrade worked.<br>
I'm not sure if your build matrix variable 'CONAN_VISUAL_VERSIONS' is set for any other reasons but i was able to successfully <a href="https://ci.appveyor.com/project/britzkopf/conan-lz4/build/1.0.42">build</a> by changing that variable from 12 to 14.</p>
<p>Would that solution work for you?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/446239002018-03-02T14:01:08Z2018-03-02T14:01:08ZLatest Appveyor Update causing VC++ projects to fail<div><p>Owen,</p>
<p>Thanks for poking around :)</p>
<p>Sadly no. Our build tools compile for all 3 VS versions, 12, 14, and 15,<br>
and upload them to a package manager. Then, the "conan client" downloads<br>
the appropriate binary based on the MSVC version the user defines. In<br>
summary, we need to build all three versions.</p>
<p>Again, it works on the previous image, and doesn't work on the new image.<br>
Just trying to figure out what parts of the change might have affected<br>
MSVC12.</p>
<p>Regards,<br>
Jerry</p>
<p>Gerald R. Wiltse<br>
<a href="mailto:jerrywiltse@gmail.com">jerrywiltse@gmail.com</a></p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-03-02T17:30:50Z2018-03-02T17:30:50ZLatest Appveyor Update causing VC++ projects to fail<div><p>Interestingly, I tried with APPVEYOR_BUILD_WORKER_IMAGE set to 2013 (which is what Visual studio 12 is) and it also worked. Though that doesn't answer why it worked on previous image but not on current, I wonder if it might also address your issue?</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/446239002018-03-02T21:07:39Z2018-03-02T21:07:39ZLatest Appveyor Update causing VC++ projects to fail<div><p>We're not going to change the setting, we need to isolate and understand<br>
the breaking change that was made. I know, it might be really hard, but<br>
that's what we need right now.</p>
<p>Gerald R. Wiltse<br>
<a href="mailto:jerrywiltse@gmail.com">jerrywiltse@gmail.com</a></p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-03-02T21:15:57Z2018-03-02T21:15:57ZLatest Appveyor Update causing VC++ projects to fail<div><p>Can you please elaborate why <code>devenv /upgrade</code> from Visual Studio 2013 should be called on <code>Visual Studio 2015</code> image?</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/446239002018-03-03T23:15:55Z2018-03-03T23:15:55ZLatest Appveyor Update causing VC++ projects to fail<div><p>I don't know why that is. It was that way on the templates provided by the team that provides our build tools.</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-03-03T23:50:48Z2018-03-03T23:50:48ZLatest Appveyor Update causing VC++ projects to fail<div><p>I switched the image to the current 2013 image for the MSVC12 build. It worked.</p>
<p>I'll close this ticket due to this particular workaround, and because this is the only package we've had it happen on so far. However, I'm still very uneasy about the fact that nobody seems to have a clue why the recent change may have caused a "working configuration" to "stop working". Even if it "should not have been working in the first place"... somebody should be able to explain what change in the environment was "corrected"</p>
<p>Please let me know if you come up with anything.</p>
<p>Thanks again for sticking with this and helping us find this workaround. You guys really are great!</p></div>jerrywiltsetag:help.appveyor.com,2012-11-13:Comment/446239002018-03-06T07:17:14Z2018-03-06T07:17:14ZLatest Appveyor Update causing VC++ projects to fail<div><p>No problem, it's what we do...<br>
We're not comfortable with the breaking change either but its likely buried somewhere in recent updates which are needed by other customers. We'll leave it for now as long as you are not totally stuck, but keep our eyes peeled for any other possible manifestation of this unexpected behaviour.</p></div>Owen McDonnelltag:help.appveyor.com,2012-11-13:Comment/446239002018-06-15T12:37:18Z2018-06-15T12:37:18ZLatest Appveyor Update causing VC++ projects to fail<div><p>For future ref, I don't know how this was fixed, but it seems to have just gone away and our builds work now.</p></div>jerrywiltse