You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2012/07/05 23:30:35 UTC
[jira] [Created] (BIGTOP-670) provide a link to our Jenkins server
from the Bigtop's project page
Roman Shaposhnik created BIGTOP-670:
---------------------------------------
Summary: provide a link to our Jenkins server from the Bigtop's project page
Key: BIGTOP-670
URL: https://issues.apache.org/jira/browse/BIGTOP-670
Project: Bigtop
Issue Type: Improvement
Components: General
Affects Versions: 0.4.0
Reporter: Roman Shaposhnik
Assignee: Sean Mackrory
Fix For: 0.5.0
A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
# https://builds.apache.org/view/A-F/view/Bigtop/
# http://bigtop01.cloudera.org:8080
I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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] (BIGTOP-670) provide a link to our Jenkins server
from the Bigtop's project page
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik updated BIGTOP-670:
--------------------------------------
Component/s: Documentation
> provide a link to our Jenkins server from the Bigtop's project page
> -------------------------------------------------------------------
>
> Key: BIGTOP-670
> URL: https://issues.apache.org/jira/browse/BIGTOP-670
> Project: Bigtop
> Issue Type: Improvement
> Components: Documentation, General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-670.patch.1, BIGTOP-670-VMs.patch
>
>
> A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
> # https://builds.apache.org/view/A-F/view/Bigtop/
> # http://bigtop01.cloudera.org:8080
> I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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] (BIGTOP-670) provide a link to our Jenkins
server from the Bigtop's project page
Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465365#comment-13465365 ]
Bruno Mahé commented on BIGTOP-670:
-----------------------------------
It would be nice to talk also about http://bigtop01.cloudera.org:8080/job/Bigtop-VM-matrix/ maybe?
> provide a link to our Jenkins server from the Bigtop's project page
> -------------------------------------------------------------------
>
> Key: BIGTOP-670
> URL: https://issues.apache.org/jira/browse/BIGTOP-670
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-670.patch.1
>
>
> A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
> # https://builds.apache.org/view/A-F/view/Bigtop/
> # http://bigtop01.cloudera.org:8080
> I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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] [Updated] (BIGTOP-670) provide a link to our Jenkins server
from the Bigtop's project page
Posted by "Bruno Mahé (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruno Mahé updated BIGTOP-670:
------------------------------
Attachment: BIGTOP-670-VMs.patch
Here is a patch to add some info regarding our job building virtual machines.
This patch is to be applied on top of Sean's
> provide a link to our Jenkins server from the Bigtop's project page
> -------------------------------------------------------------------
>
> Key: BIGTOP-670
> URL: https://issues.apache.org/jira/browse/BIGTOP-670
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-670.patch.1, BIGTOP-670-VMs.patch
>
>
> A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
> # https://builds.apache.org/view/A-F/view/Bigtop/
> # http://bigtop01.cloudera.org:8080
> I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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] [Updated] (BIGTOP-670) provide a link to our Jenkins server
from the Bigtop's project page
Posted by "Sean Mackrory (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Mackrory updated BIGTOP-670:
---------------------------------
Attachment: BIGTOP-670.patch.1
This is what I wrote. I don't know if we're looking for more or less detail, but this definitely contains all the technical details and enough of a rough explanation that somebody could find their way around.
Thoughts?
> provide a link to our Jenkins server from the Bigtop's project page
> -------------------------------------------------------------------
>
> Key: BIGTOP-670
> URL: https://issues.apache.org/jira/browse/BIGTOP-670
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-670.patch.1
>
>
> A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
> # https://builds.apache.org/view/A-F/view/Bigtop/
> # http://bigtop01.cloudera.org:8080
> I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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] (BIGTOP-670) provide a link to our Jenkins
server from the Bigtop's project page
Posted by "Konstantin Boudnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465396#comment-13465396 ]
Konstantin Boudnik commented on BIGTOP-670:
-------------------------------------------
I am wondering about the status of the bigtop01.cloudera.org servers. I think traditionally, companies were giving resources to the Apache Infra so they can be managed and controller by ASF. Such approach reduce the level of controversy of who can do what with the computers, and predict the time frame the servers will be around, etc.
So, what's really the status of this resource?
> provide a link to our Jenkins server from the Bigtop's project page
> -------------------------------------------------------------------
>
> Key: BIGTOP-670
> URL: https://issues.apache.org/jira/browse/BIGTOP-670
> Project: Bigtop
> Issue Type: Improvement
> Components: Documentation, General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Sean Mackrory
> Fix For: 0.5.0
>
> Attachments: BIGTOP-670.patch.1, BIGTOP-670-VMs.patch
>
>
> A lot of folks are wondering about the location of our secondary Jenkins server. Perhaps we should document both of them:
> # https://builds.apache.org/view/A-F/view/Bigtop/
> # http://bigtop01.cloudera.org:8080
> I would imagine a section on our project web page (http://incubator.apache.org/bigtop/) talking about how our continuous integration works.
--
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