Allow plugin artifact to be created in same job
Issue #38
wontfix
At the moment the Deploy Plugin task expects the deployed artifact to be a subscription to one defined by another job. We're trying to do stuff in one job to keep things simple and that means we can't use this task. :(
Please add an option to use a local artifact.
Comments (5)
-
-
We're going to try and work around this issue by using Manifesto to upgrade the test instance instead, avoiding the use of this task altogether.
-
- marked as minor
-
Ok, sounds good. I'm going to Close: Won't Fix this issue then, since it will add a lot of complexity without a direct use case. If you decide to go back down this path again, just re-open it or or re-create it.
-
- Log in to comment
This was created by me (didn't realise I wasn't logged in).