No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    quasar build error piping

    CLI
    3
    6
    442
    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.
    • M
      marka last edited by

      Hello,

      I’m trying to build quasar CI pipeline, but it seems cli error output stream on windows 10 does not get any messages, all messages are put to default output stream. I tried searching info, but not found any info on how to do it.

      Example output from CMD when I run commands:

      D:\GitLab-Runner\builds\msNW1ix4\0\xx-projects\yy-project
      λ quasar build 2> $null
      
       Error Unknown command "build"
      
      
        ___
       / _ \ _   _  __ _ ___  __ _ _ __
      | | | | | | |/ _` / __|/ _` | '__|
      | |_| | |_| | (_| \__ \ (_| | |
       \__\_\\__,_|\__,_|___/\__,_|_|
      
      
        Running @quasar/cli v1.1.3
      
        Example usage
          $ quasar <command> <options>
      
        Help for a command
          $ quasar <command> --help
          $ quasar <command> -h
      
        Options
          --version, -v Print Quasar CLI version
      
        Commands
          create    Create a project folder
          info      Display info about your machine
                         (and your App if in a project folder)
          upgrade   Check (and optionally) upgrade Quasar packages
                         from a Quasar project folder
          serve     Create an ad-hoc server on App's distributables
          help, -h  Displays this message
      
        --------------
        => IMPORTANT !
        => Trigger this inside of a Quasar project (and npm/yarn install) for more commands.
        --------------
      
      D:\GitLab-Runner\builds\msNW1ix4\0\xx-projects\yy-project
      λ quasar build 1> $null
      
      D:\GitLab-Runner\builds\msNW1ix4\0\xx-projects\yy-project
      λ
      

      quasar -v
      1.1.3

      beets 1 Reply Last reply Reply Quote 0
      • beets
        beets @marka last edited by

        @marka Does the folder D:\GitLab-Runner\builds\msNW1ix4\0\xx-projects\yy-project contain a quasar.conf.js ?

        1 Reply Last reply Reply Quote 0
        • M
          marka last edited by

          yes

          node_modules are missing, so it throws error on build, but this is not problem. I want to detect error with the help of error output, if it prints something, CI halts next steps.

          metalsadman 1 Reply Last reply Reply Quote 0
          • metalsadman
            metalsadman @marka last edited by metalsadman

            @marka maybe catch the first message Error Unknown command "build". or

            --------------
              => IMPORTANT !
              => Trigger this inside of a Quasar project (and npm/yarn install) for more commands.
              --------------```
            1 Reply Last reply Reply Quote 0
            • M
              marka last edited by

              @metalsadman yes I was thinking about it, but this solution will need to enumurate all possible errors, I just wanted to know if running cli command produces any errors so I do not need to worry about parsing each “quasar xx” command for success messages.

              I think I will just look for “Build succeeded,” for now, if it does not exists I will print to error output.

              Would be nice to have quasar print to error output, as at least gitlab CI detects those messages and stops executing pipeline 🙂

              Thanks for help

              metalsadman 1 Reply Last reply Reply Quote 0
              • metalsadman
                metalsadman @marka last edited by

                @marka you should issue a feature request at quasar’s github repo.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post