geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Deppe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-1817) Disable artifact signing by default
Date Thu, 25 Aug 2016 14:49:20 GMT

     [ https://issues.apache.org/jira/browse/GEODE-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jens Deppe updated GEODE-1817:
------------------------------
    Description: 
Currently our CI pipeline is generating -SNAPSHOT releases. The nexus build plugin, we are
using, automatically detects `SNAPSHOT` in the version string and does not attempt to sign
those artifacts.

We intend to change the pipeline to always be building 'release candidate' versions and so
signing would be required. As signing is currently a manual process, this will be disabled
by default.

As an aside, the CI pipeline will still produce `SNAPSHOT` releases for each successful build,
however this step will be a rebuild with a `-SNAPSHOT` version string against the SHA of the
code passing the build.

  was:
Currently our CI pipeline is generating -SNAPSHOT releases. The nexus build plugin, we are
using, automatically detects `SNAPSHOT` in the version string and does not attempt to sign
those artifacts.

We intend to change the pipeline to always be building 'release candidate' versions and so
signing would be required. As signing is currently a manual process, this will be disabled
by default.

(As an aside, the CI pipeline will still produce `SNAPSHOT` releases for each successful build.)


> Disable artifact signing by default
> -----------------------------------
>
>                 Key: GEODE-1817
>                 URL: https://issues.apache.org/jira/browse/GEODE-1817
>             Project: Geode
>          Issue Type: Improvement
>          Components: build
>            Reporter: Jens Deppe
>
> Currently our CI pipeline is generating -SNAPSHOT releases. The nexus build plugin, we
are using, automatically detects `SNAPSHOT` in the version string and does not attempt to
sign those artifacts.
> We intend to change the pipeline to always be building 'release candidate' versions and
so signing would be required. As signing is currently a manual process, this will be disabled
by default.
> As an aside, the CI pipeline will still produce `SNAPSHOT` releases for each successful
build, however this step will be a rebuild with a `-SNAPSHOT` version string against the SHA
of the code passing the build.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message