"Subscription has web workers, but no website was found in build" when merging PR, but PR have website detected

laedit's Avatar

laedit

19 Aug, 2017 06:06 AM

Hi,

I was working on a PR for dotliquid and the build was fine and propose to deploy, but when I merged the PR back in master, the build doesn't found the website.
Is this normal?
Do I need to add some missing configuration or other?

Thanks.

  1. Support Staff 1 Posted by rune on 23 Aug, 2017 09:52 PM

    rune's Avatar

    Hi,

    Sorry about the delay -- I took a look at this app, but it seems like you figured out a solution in the meantime? Otherwise let me know and I'll be happy to take a closer look!

    Best,
    Rune

  2. 2 Posted by laedit on 24 Aug, 2017 05:07 AM

    laedit's Avatar

    Thanks for the reply.

    Sadly I didn't find a solution, but since I am new to AppHarbor I was wondering if the website not found only on master is normal, like if the deploy is meant to be from the PRs only?

  3. Support Staff 3 Posted by rune on 01 Sep, 2017 02:38 PM

    rune's Avatar

    Hi,

    The branch used to build the application doesn't influence the way the application is built although the deployment may/may not be deployed based on which branch is currently being "tracked" for automatic deployments. You can read more about tracking branches in this KB article under "Deploy from non-default branch".

    The issue in this case seems to be related to the .NET framework used. In particular, the last build you referenced appears to be a .NET Core app, which currently requires a bit of project file configuration to properly publish the website to the build output directory. Currently you'll need to trigger the Publish build target and set the PublishDir project property yourself. That's pretty straightforward as you can see in this sample csproj using a default ASP.NET Core (Core FX) template app created created with VS017:

    <Project Sdk="Microsoft.NET.Sdk.Web" DefaultTargets="Publish">
        <PropertyGroup>
            <TargetFramework>netcoreapp1.1</TargetFramework>
            <PublishDir>$(OutDir)_PublishedWebsites\NetCoreApp\</PublishDir>
        </PropertyGroup>
        <PropertyGroup>
            <PackageTargetFallback>$(PackageTargetFallback);portable-net45+win8+wp8+wpa81;</PackageTargetFallback>
        </PropertyGroup>
        <ItemGroup>
            <PackageReference Include="Microsoft.ApplicationInsights.AspNetCore" Version="2.0.0" />
            <PackageReference Include="Microsoft.AspNetCore" Version="1.1.2" />
            <PackageReference Include="Microsoft.AspNetCore.Mvc" Version="1.1.3" />
            <PackageReference Include="Microsoft.AspNetCore.StaticFiles" Version="1.1.2" />
            <PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="1.1.2" />
            <PackageReference Include="Microsoft.VisualStudio.Web.BrowserLink" Version="1.1.2" />
        </ItemGroup>
        <ItemGroup>
            <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="1.0.1" />
        </ItemGroup>
    </Project>
    

    The same changes are required for ASP.NET Core apps that use the regular .NET Framework, which also works today! This will ensure that your website is published to the directory structure supported by AppHarbor, and the website will be detected and deployable with these changes.

    We should have this configuration automated on the build servers in the next couple of weeks, but in the meantime please don't hesitate to reach out with any feedback or questions!

    Best,
    Rune

  4. rune closed this discussion on 01 Sep, 2017 02:38 PM.

  5. laedit re-opened this discussion on 02 Sep, 2017 07:11 AM

  6. 4 Posted by laedit on 02 Sep, 2017 07:11 AM

    laedit's Avatar

    Thanks for the tips, but the publication of the website fails the website tests build, even on a newly created dotnet core website + unit test projects.

    I think I will wait for the publish part to be integrated to the AppHarbor workflow.

  7. Support Staff 5 Posted by rune on 08 Sep, 2017 03:03 AM

    rune's Avatar

    Hi,

    Ok great -- the publish integration is currently planned for release as part of next week's regular maintenance, so assuming goes well this should work around Wednesday/Thursday.

    Best,
    Rune

  8. rune closed this discussion on 08 Sep, 2017 03:03 AM.

  9. laedit re-opened this discussion on 25 Oct, 2017 03:44 AM

  10. 6 Posted by laedit on 25 Oct, 2017 03:44 AM

    laedit's Avatar

    It's seems that there is still an error or am I missing something on this build?
    https://appharbor.com/applications/dotliquid/builds/2008286

  11. Support Staff 7 Posted by rune on 26 Oct, 2017 05:10 AM

    rune's Avatar

    Hi,

    I took a look at the NuGet package restore and build logs, and as far as I can tell there are some assembly/dependency version mismatches that are likely causing this issue (e.g. some rc2 and rc3 builds of certain libraries that are not consistent across all projects.

    Try upgrading your NuGet packages and the .NET Core version to the latest available on the 1.x branch! Also make sure your projects rely on the same versions of the dependencies across the projects.

    Best,
    Rune

  12. 8 Posted by laedit on 26 Oct, 2017 05:56 PM

    laedit's Avatar

    Oh sorry, since it's worked elsewhere I was thinking of a AppHarbor specific, I will fix that.
    Thanks!

  13. 9 Posted by laedit on 26 Oct, 2017 07:16 PM

    laedit's Avatar

    So, as far as I can understand it seems that it's coming from an issue in dotnet core 1.0 so I am trying to upgrade to 1.1.1.
    I've got a successful build but the following, which updates only the .travis.yml file fails.

    I must say that I am lost about that, do you have an idea about why the last build is failing when nothing related to AppHarbor has been modified?

    Thanks.

  14. 10 Posted by laedit on 26 Oct, 2017 07:49 PM

    laedit's Avatar

    After some more tests it seems that it was the .sln which only add the travis file, but even if the PR build pass, the master's still didn't find a website.

    Have I missed a step or a setting?

    Thanks.

  15. Support Staff 11 Posted by rune on 31 Oct, 2017 02:20 AM

    rune's Avatar

    Hi,

    Yep I took a look at the repository and it seems the website isn't being published -- this should work automatically soon but has been delayed a bit. Take a look at my initial response for information on how to do this yourself!

    Best,
    Rune

  16. rune closed this discussion on 31 Oct, 2017 02:20 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac