Skip to content

Separate publish to npmjs from container-related operations #358

Description

@nepalevov

Name and Version

ai-dial-ci up to current version

What is the problem this feature will solve?

Currently, building and publishing JS code as a package to npmjs comes in line with building, scanning, and publishing container images. It's slow

What is the feature you are proposing to solve the problem?

Seems no build artifacts are shared, container build is completely autonomous.

We need to extract it into a separate job to speed up execution.

What alternatives have you considered?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    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