Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for multiple artifact extensions #11

Open
scottTomaszewski opened this issue Jan 22, 2016 · 4 comments
Open

Add support for multiple artifact extensions #11

scottTomaszewski opened this issue Jan 22, 2016 · 4 comments

Comments

@scottTomaszewski
Copy link

In configuration, it would be nice to be able to promote multiple artifacts with the same groupId, artifactId, version, etc. For example, to promote a pom and jar:

job {
    steps {
        artifactPromotion {
          groupId("foo")
          artifactId("bar")
          version("1.2.3")
          extension(["pom", "jar"])
          stagingRepository("nexus", "foo", "bar")
          releaseRepository("nexus", "foo", "bar")
          debug(false)
        }
    }
}
@hcguersoy
Copy link
Contributor

Thank you, I'll take a look on it how this can be implemented.
Feel free to implement it by your own and open a pull request :-)

@stahloss
Copy link

stahloss commented Jul 10, 2020

@hcguersoy Why not simply promote all artifacts for the specified version? And optionally an exclusion matcher or something?

Now I need to call artifactPromotion separately for every type of extension :(
And then the same for every classifier :(

@hcguersoy
Copy link
Contributor

@hcguersoy Why not simply promote all artifacts for the specified version? And optionally an exclusion matcher or something?

Now I need to call artifactPromotion separately for every type of extension :(
And then the same for every classifier :(

@D0rmouse yes, would be a possibility and usable for most of the projects.
Can you provide a PR?

@stahloss
Copy link

stahloss commented Jul 10, 2020

@hcguersoy Not sure my company will give me more time to spend on this. I may have to drop it or find alternate solutions.

It would be nice to put in the README that this is a serious limitation of the plugin for any future users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants