[jira] [Comment Edited] (OAK-9500) Automatically deploy snapshot artifacts to Maven repo through Jenkins

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383906#comment-17383906 ] 

Konrad Windszus edited comment on OAK-9500 at 7/20/21, 8:55 AM:
----------------------------------------------------------------

bq. Do you mean testing before performing a release? If yes, then this should be covered by CI without the need to deploy.

I am talking about testing it in the real application (not about executing unit and integration tests). Without a SNAPSHOT deployment it is hard to reference temporarily in downstream consumers.

bq. It saves some time, yes. My machine builds all modules in two minutes. 

With running tests it is much longer for me. The idea of having SNAPSHOTs available is that they represent the latest state where all tests have been performed successfully!

bq.  But then it may also add trouble because maven detects a more recent snapshot dependency on a remote and overwrites your locally built module that contains your pending changes.

Granted but that should rarely happen as Maven by default only checks on a daily basis for newer SNAPSHOTs on remotes and when you work on a module you compile (and maybe even install) that on a more regular basis.


was (Author: kwin):
> Do you mean testing before performing a release? If yes, then this should be covered by CI without the need to deploy.

I am talking about testing it in the real application (not about executing unit and integration tests). Without a SNAPSHOT deployment it is hard to reference temporarily in downstream consumers.

> It saves some time, yes. My machine builds all modules in two minutes. 

With running tests it is much longer for me. The idea of having SNAPSHOTs available is that they represent the latest state where all tests have been performed successfully!

>  But then it may also add trouble because maven detects a more recent snapshot dependency on a remote and overwrites your locally built module that contains your pending changes.

Granted but that should rarely happen as Maven by default only checks on a daily basis for newer SNAPSHOTs on remotes and when you work on a module you compile (and maybe even install) that on a more regular basis.

> Automatically deploy snapshot artifacts to Maven repo through Jenkins
> ---------------------------------------------------------------------
>
>                 Key: OAK-9500
>                 URL: https://issues.apache.org/jira/browse/OAK-9500
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: continuous integration
>            Reporter: Konrad Windszus
>            Priority: Minor
>
> With the addition from OAK-9486 it should be fairly simple to deploy the build artifacts to the Apache Snapshot repository whenever the branch {{trunk}} is build. 
> There are some hints about deployment in multibranch builds in https://cwiki.apache.org/confluence/display/INFRA/Multibranch+Pipeline+recipes#MultibranchPipelinerecipes-DeployingArtifacts.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)