Skip to content

Deployment rules allow possibly invalid invocations #404

Open
@jamesreprise

Description

Problem

We have a pattern of requiring the specification of 'snapshot' and 'release' repositories for deployment rules. This is true for the following.

  • deploy_apt
  • deploy_brew
  • deploy_crate
  • deploy_npm
  • deploy_maven
  • deploy_pip
  • deploy_helm

This is troublesome when we want to have a target using this rule point to another target that is specifically a 'snapshot' or 'release' artefact as we've now introduced the possibility of an invalid invocation; our deployment target can make a 'release' deployment for a 'snapshot' artefact or vice versa.

Suggestion

Instead of requiring the specification of both 'snapshot' and 'release' repositories we could require that just one 'repository' is specified. This allows us to create multiple targets (manually or through macros, list comprehensions) for our desired workflows.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions