[FORGE-52] Can't deploy to magnolia.forge.releases Created: 11/Apr/14 Updated: 05/May/14 Resolved: 05/May/14 |
|
| Status: | Closed |
| Project: | Forge |
| Type: | Support Request | Priority: | Neutral |
| Reporter: | Richard Unger | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
I've just committed the 1.0.0 release of my scss module, but jenkins is denied by nexus on attempting to deploy it... Can I be authorized to write to that repository, or how does that work? Thanks, and regards from Vienna, Richard Jenkins output, for full output see: http://hudson.magnolia-cms.com/job/forge_magnolia-module-resources-scss/12/console [INFO] [deploy:deploy {execution: default-deploy}] |
| Comments |
| Comment by Magnolia International [ 17/Apr/14 ] |
|
Jenkins is only allowed to deploy to snapshot repositories. You need to do the release from your machine. I'd recommend using the Maven release plugin rather than manually changing versions, tagging etc. |
| Comment by Richard Unger [ 29/Apr/14 ] |
|
Thanks greg, this bug can be closed... I can't seem to do that myself. |