Skip to content

Bundles with 'noname' when running on build server #26

@steve-gray

Description

@steve-gray

When running on a build server, the workflow is:

-- Pull project
git clone <path>
cd <path>
Create freight definition if not exists, otherwise just freight.
freight create 
freight
npm install

However I find very often that 'noname-' is the bundle name. Is there something specific that freight is looking for in my paths that I'm not supplying? Or can I set a command-line argument to create the bundle with a name?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions