[jira] [Comment Edited] (BIGTOP-3611) Upgrade Jenkins to latest upstream

["Olaf Flebbe (Jira)" <ji...@apache.org>]

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

Olaf Flebbe edited comment on BIGTOP-3611 at 1/19/22, 7:03 PM:
---------------------------------------------------------------

Looking at the config pages of cwiki.a.o you should have write access as bigtop-committer (given you are using your apache ID to log in) . 
However I remember I had issues in the past with write access as well and I see a lot of accounts (including mine) being configured ad hoc as well. 
I checked I do not have admin access to confluence. 



was (Author: oflebbe):
Looking at the config pages of cwiki.a.o you should have write access as bigtop-committer (given you are using your apache ID to log in) . 
However I remember I had issues in the past with write access as well and I see a lot of accounts being configured ad hoc as well. 
I checked I do not have admin access to confluence. 


> Upgrade Jenkins to latest upstream
> ----------------------------------
>
>                 Key: BIGTOP-3611
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3611
>             Project: Bigtop
>          Issue Type: Improvement
>            Reporter: Luca Toscano
>            Priority: Major
>
> Hi everybody,
> I noticed that our Jenkins' UI suggests to upgrade, should we do it?
> From https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide#BigtopCISetupGuide-SetupaJenkinsmaster it seems relatively easy:
> docker inspect #jenkins-container > backup_container.log
> docker image inspect jenkins/jenkins > backup_image.log
> docker stop #jenkins-container
> docker pull jenkins/jenkins:2.324
> docker run etc..
> Should we do it?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)