You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benno Evers (JIRA)" <ji...@apache.org> on 2019/04/11 09:13:00 UTC
[jira] [Comment Edited] (MESOS-9697) Release RPMs are not uploaded
to bintray
[ https://issues.apache.org/jira/browse/MESOS-9697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814545#comment-16814545 ]
Benno Evers edited comment on MESOS-9697 at 4/11/19 9:12 AM:
-------------------------------------------------------------
After some investigation, here's my current understanding of the situation:
* The ASF Jenkins is successfully running the `Mesos/Packaging/CentOS` job ( https://builds.apache.org/view/M-R/view/Mesos/job/Packaging/job/CentOS/ ) to a branch that contains the file `support/jenkins/Jenkinsfile-packaging-centos`, i.e. currently branches 1.7.x, 1.8.x and master. This jenkinsfile creates rpm packages for centos 6 and 7 as artifacts (using the script `support/packaging/centos/build-rpm-docker.sh`), but does not do anything with them, i.e. there is no connection to bintray. I don't know if there is any public download for the generated artifacts.
* The is another job `Mesos/Packaging/CentosRPMs` (https://builds.apache.org/job/Mesos/job/Packaging/job/CentosRPMs) defined in the ASF Jenkins that is not run automatically. For its setup, its using the file `support/packaging/Jenkinsfile` from branch `bintray` on `http://github.com/karya0/mesos.git`. It is taking parameters `MESOS_RELEASE` and `MESOS_TAG` and will build centos 6/7 rpm packages for that release (I still don't understand where exactly it's taking the source code from) and afterwards upload them to bintray using credentials "karya_bintray_credentials". It was last run by [~karya] on Feb 8, 2018 to produce Mesos 1.5.0 packages.
So it looks like this might not actually be broken, but rather just release managers not being aware that they are supposed to manually run this Jenkins job. I'd like to test that theory by triggering a 1.7.0 build of the latter job, but I don't seem to have permissions to do that on the ASF Jenkins.
was (Author: bennoe):
After some investigation, here's my current understanding of the situation:
* The ASF Jenkins is successfully running the `Mesos/Packaging/CentOS` job ( https://builds.apache.org/view/M-R/view/Mesos/job/Packaging/job/CentOS/ ) to a branch that contains the file `support/jenkins/Jenkinsfile-packaging-centos`, i.e. currently branches 1.7.x, 1.8.x and master. This jenkinsfile creates rpm packages for centos 6 and 7 as artifacts (using the script `support/packaging/centos/build-rpm-docker.sh`), but does not do anything with them, i.e. there is no connection to bintray. I don't know if there is any public download for the generated artifacts.
* The is another job `Mesos/Packaging/CentosRPMs` (https://builds.apache.org/job/Mesos/job/Packaging/job/CentosRPMs) defined in the ASF Jenkins that is not run manually. For its setup, its using the file `support/packaging/Jenkinsfile` from branch `bintray` on `http://github.com/karya0/mesos.git`. It is taking parameters `MESOS_RELEASE` and `MESOS_TAG` and will build centos 6/7 rpm packages for that release (I still don't understand where exactly it's taking the source code from) and afterwards upload them to bintray using credentials "karya_bintray_credentials". It was last run by [~karya] on Feb 8, 2018 to produce Mesos 1.5.0 packages.
So it looks like this might not actually be broken, but rather just release managers not being aware that they are supposed to manually run this Jenkins job. I'd like to test that theory by triggering a 1.7.0 build of the latter job, but I don't seem to have permissions to do that on the ASF Jenkins.
> 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)