You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Michael Nielsen (JIRA)" <ji...@apache.org> on 2012/06/03 11:34:22 UTC
[jira] [Created] (BUILDR-642) individual repositories for snapshots
and releases
Michael Nielsen created BUILDR-642:
--------------------------------------
Summary: individual repositories for snapshots and releases
Key: BUILDR-642
URL: https://issues.apache.org/jira/browse/BUILDR-642
Project: Buildr
Issue Type: Improvement
Reporter: Michael Nielsen
We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
My understanding is that buildr use the same URL for both upload (snapshots) and release:
repositories.release_to[:url]
Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
repositories.release_to[:url]
repositories.upload_to[:url]
including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413236#comment-13413236 ]
Tan Quach commented on BUILDR-642:
----------------------------------
Yep, that's correct.
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (BUILDR-642) individual repositories for snapshots
and releases
Posted by "Peter Donald (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald updated BUILDR-642:
--------------------------------
Fix Version/s: 1.5
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
> Fix For: 1.5
>
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412985#comment-13412985 ]
Alex Boisvert commented on BUILDR-642:
--------------------------------------
This is probably obvious but I'll just confirm your suspicion that it can't be done through YAML alone at the moment.
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Damian Monogue (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416426#comment-13416426 ]
Damian Monogue edited comment on BUILDR-642 at 7/17/12 6:24 PM:
----------------------------------------------------------------
We use ~/.buildr/buildr.rb for this, in combination with the buildr environment. For release builds we pass -e release, and for nonrelease builds we pass -e integration . Then in ~/.buildr/buildr.rb we case Buildr.environment and set repositories.release_to accordingly.
ETA: this is less of a hassle for us than those invoking manually because we using a continuous integration server to run nearly all of our builds. I do still agree that being able to set a release url and a snapshot url separately would be quite handy
was (Author: dmonogue):
We use ~/.buildr/buildr.rb for this, in combination with the buildr environment. For release builds we pass -e release, and for nonrelease builds we pass -e integration . Then in ~/.buildr/buildr.rb we case Buildr.environment and set repositories.release_to accordingly.
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Tan Quach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412876#comment-13412876 ]
Tan Quach commented on BUILDR-642:
----------------------------------
Since it is recommended to put repository settings in build.yaml or .buildr/settings.yaml, how would one do #2 in a YAML way?
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288305#comment-13288305 ]
Alex Boisvert commented on BUILDR-642:
--------------------------------------
Two comments,
1) Just for reference, this has been discussed before (though not implemented yet) here:
http://buildr.markmail.org/thread/ihf4nlomzluyfds5
2) Remember that you have full access to Ruby language in your buildfile so in the mean time you can do things like,
if VERSION =~ /SNAPSHOT/
repositories.release_to[:url] = ...
else
repositories.release_to[:url] = ...
end
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BUILDR-642) individual repositories for
snapshots and releases
Posted by "Damian Monogue (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416426#comment-13416426 ]
Damian Monogue commented on BUILDR-642:
---------------------------------------
We use ~/.buildr/buildr.rb for this, in combination with the buildr environment. For release builds we pass -e release, and for nonrelease builds we pass -e integration . Then in ~/.buildr/buildr.rb we case Buildr.environment and set repositories.release_to accordingly.
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots) and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira