Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Artifact questions

    Scheduled Pinned Locked Moved Support
    artifactsnetbuildmaster
    3 Posts 1 Posters 8 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      1. As far as I understood, when you create Artifact it only packages directory content into a Zip file and moves it into Artifact library? Is that correct?

      2. When deploying artifacts, you have a chance of choosing "Deploy as zip file" option. What does that do? Does it just copy a zip file or does it do the same as msdeploy?

      3. Is it at all possible to deploy a packaged .NET web application using artifacts?

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        Hello Vladimir,

        1. Yes, that's correct; these artifacts are stored on disk, under the path `Artifacts\AppId\RelNo\BldNo\DepId\ArtifactName.zip

        2. The Deploy Artifact action will find the appropriate artifact (Based on Build/Rel No), inspect the contents, and transfer the changed files to the target folder. This option skips the last two steps, and simply deploys the zip file.

        3. Maybe? But you may just want to use msbuild with the msdeploy step if you're looking to do that...

        1 Reply Last reply Reply Quote 0
        • ? This user is from outside of this forum
          Guest
          last edited by

          [3] – yes; I'm currently doing the following:

          1. Create an application package (by using the standard "Package" target in my "Build .NET MSBuild Project" action)
          2. Create a BuildMaster build artifact (i.e. create an archive file containing the application package and ancillary files)
          3. Deploy the build artifact to a folder on the build server.
          4. Run Web Deploy (msdeploy.exe) via a "Execute Command Line" action to deploy the application package (in the folder to which the artifact was deployed in [3]) to the relevant server(s) for the environment.
          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation