[
https://issues.apache.org/jira/browse/MESOS-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844858#comment-16844858
]
Benno Evers edited comment on MESOS-9697 at 5/21/19 1:55 PM:
-------------------------------------------------------------
{noformat}
commit 35fa8420762f1e8cf8df211ddcdaa0cc77104bc2
Author: Benno Evers <bev...@mesosphere.com>
Date: Fri May 17 11:24:23 2019 +0200
Updated bintray upload scripts to remove hard-coded accounts.
This updates the Jenkinsfile used in the ASF Jenkins as well
as the associated upload script for bintray to make the
used credential id configurable and to upload the built packages
to the official `apache/mesos` bintray account.
Review: https://reviews.apache.org/r/70573/
{noformat}
{noformat}
commit ae23ded11116b9b2ec3b2b6ec494408dc3d6e1df (bevers/apache-jenkins-bintray)
Author: Benno Evers <bev...@mesosphere.com>
Date: Fri May 17 18:46:34 2019 +0200
Rearranged 'Downloads' page and updated bintray URL.
Updated the bintray link on the `Downloads` page to point
to the `apache/mesos` account instead of the `mesos`
account.
In addition, several minor formatting changes were done:
* Added a space after the colon in the `Getting older
Mesos binaries` section.
* Moved links to the getting started guide to the top
of the document.
* Used a list to present the download links to the latest
stable release.
* Used `<pre>` instead of `<code>` tags for the link to the
ASF git repository.
Review: https://reviews.apache.org/r/70526/
{noformat}
The changes in the commit above did return the Apache CI to a state where
packages are built succesfully, however the bintray upload is still failing
without any error message.
was (Author: bennoe):
{noformat}
commit 35fa8420762f1e8cf8df211ddcdaa0cc77104bc2
Author: Benno Evers <bev...@mesosphere.com>
Date: Fri May 17 11:24:23 2019 +0200
Updated bintray upload scripts to remove hard-coded accounts.
This updates the Jenkinsfile used in the ASF Jenkins as well
as the associated upload script for bintray to make the
used credential id configurable and to upload the built packages
to the official `apache/mesos` bintray account.
Review: https://reviews.apache.org/r/70573/
{noformat}
The changes in the commit above did return the Apache CI to a state where
packages are built succesfully, however the bintray upload is still failing
without any error message.
> Release RPMs are not uploaded to bintray
> ----------------------------------------
>
> Key: MESOS-9697
> URL: https://issues.apache.org/jira/browse/MESOS-9697
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 1.6.2, 1.7.2, 1.8.0
> Reporter: Benjamin Bannier
> Assignee: Benno Evers
> Priority: Critical
> Labels: foundations, integration, jenkins, packaging, rpm
>
> While we currently build release RPMs, e.g.,
> [https://builds.apache.org/view/M-R/view/Mesos/job/Packaging/job/CentOS/job/1.7.x/],
> these artifacts are not uploaded to bintray. Due to that RPM links on the
> downloads page [http://mesos.apache.org/downloads/] are broken.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
