by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mark Waite
    @MarkEWaite
    @Yunir there is not a milestone or progress bar or deadline for wiki page conversion to https://jenkins.io/doc, though I think that is a good idea. There is an ongoing discussion in the jenkinsci/docs gitter channel about the transition process. Gavin Mogan has suggested page redirects when a wiki page has been moved to jenkins.io.
    Oleg Nenashev
    @oleg-nenashev
    @Yunir We have the plugin Docs migration tracking in https://jenkins-wiki-exporter.jenkins.io/progress . There is no tracking for no-plugin documentation as far as I know. I could create an EPIC for it, but we would need somebody to build a list of all pages to be migrated
    YSalimzyanov
    @Yunir
    There are 3 spaces in Confluence, in "jenkins" space there are 130 pages (1st level page under the "Home" page) - so we can count as progress these 130 pages with "Home" parent, and all nested pages down the tree can be counted as parent's page progress. That is the only way to find and note all the pages if I correctly understand the logic of Confluence.
    It will be easier to draw the progress if u install trial version of any plugin that shows site-map for the separate space (after googling, I found two that might help, I suppose: better-content-archiving-for-confluence and sitemap-for-confluence) and create EPIC or the same page as https://jenkins-wiki-exporter.jenkins.io/progress but by this site-map for wiki-pages.
    YSalimzyanov
    @Yunir
    what do u think?
    Mark Waite
    @MarkEWaite

    I don't think we're willing to install a any trial plugins on that wiki instance. However, I like the idea of showing progress somewhere. We could create a ticket in Jira that tracks the progress on pages or we could extract the count of pages and compare the count of wiki pages to the count of redirects (see Gavin's proposal in the jenkinsci/docs channel)

    The wiki is intentionally read only because of the spam problems that we are not willing to spend admin time to fight.

    Oleg Nenashev
    @oleg-nenashev
    One simple way would be to just dump a list of all non-Plugin pages and automatically create Jira tickets for it
    Then we can scrub them and close ones which are already migrated
    Or close ones which should be just killed
    Mark Waite
    @MarkEWaite
    @oleg-nenashev that sounds reasonable to me. There is a REST API call that will list all the wiki pages in a space. https://community.atlassian.com/t5/Answers-Developer-Questions/Way-to-find-all-pages/qaq-p/551847
    Oleg Nenashev
    @oleg-nenashev
    @Yunir BTW, I would suggest moving this discussion to Docs SIG where we have all contributors involved into the docs migration story
    YSalimzyanov
    @Yunir
    @oleg-nenashev, I can duplicate everything we discussed here (to gitter channel jenkinsci/docs), but suppose would be better if someone just write small sum-up to avoid misinform (about milestones/issues, where people can track the progress)
    YSalimzyanov
    @Yunir
    also I want to know what is the difference between gitter docs channel and google groups channel? What is more relevant to follow and read? Do they have different goals?
    Alex Earl
    @slide
    I nuked the sorcerer link from that page
    Oleg Nenashev
    @oleg-nenashev
    @Yunir Google groups are for async communications, and they are recommended for the most of cases. Gitter and other chats are for realtime ones. Whether we follow that rule or not, ¯_(ツ)_/¯
    My recommendation is to join both mailing list and Gitter if you are interested in the area
    YSalimzyanov
    @Yunir
    @slide, thanks
    @oleg-nenashev, joined both)
    shubham20011995
    @shubham20011995
    Hi All, i am currently using multiple pipeline shared library in my jenkins pipeline. is there any plugin or script which can help me to identify which function is called from which pipeline shared library? For example fun() A-->library 1 , fun() b--> lib2 and so on. Thanks in advance
    Gavin Mogan
    @halkeye
    shubham20011995: this channel is for "Chat for people who just starting contributing to Jenkins or want to do so. https://jenkins.io/participate/", not for general help, #jenkinsci/jenkins is the right place for help, or the users mailing list
    vantangst
    @vantangst
    Hi all, I have an issue here https://issues.jenkins-ci.org/browse/JENKINS-61064. I would like to update the Usage Instructions with more detail. someone can help me?
    Gavin Mogan
    @halkeye
    vantangst: on which page? do you mean https://plugins.jenkins.io/appcenter/
    vantangst
    @vantangst
    I saw many people confuse about display app name and app name in AppCenter and then they ask in some websites. I think we should show them more detail.
    Gavin Mogan
    @halkeye
    awesome. First of all I'd make sure you mention that link in the ticket
    just, as you say, to prevent confusing
    next, your just wanting to change the documention right? not functionality?
    do you have a github account? have you submitted pull requests before?
    vantangst
    @vantangst
    yes. just for document
    yes. I have
    Gavin Mogan
    @halkeye
    awesome. Then you should be able to fork the repo, change the readme.md file, and submit a pull request
    vantangst
    @vantangst
    I can't push my commitment
    Gavin Mogan
    @halkeye
    yea you'll have to push to your fork
    vantangst
    @vantangst
    yeah. but I can't push: https://prnt.sc/r14roc
    Gavin Mogan
    @halkeye
    your pushing to jenkinsci, not your fork
    if you run git commit -v it should list your remotes
    I'm pretty sure origin is going to be jenkinsci/appcenter-plugin
    if you goto https://github.com/jenkinsci/appcenter-plugin, then click "fork" on the top right hand side of the page, it'll make a fork for you to work on
    vantangst
    @vantangst
    I see now, thank u.
    I have done
    Gavin Mogan
    @halkeye
    okay, next add your remote to your local git. git remote add vantangst git@github.com:vantangst/appcenter-plugin
    then make sure your on a branch. git branch should show you all your branches, with the * next to the current one
    (i see your screenshots your using a gui, so you can do my steps in alternative ways)
    if your on master, make a new branch git checkout -b whatever-you-want-for-new-branch
    then git push -u vantangst whatever-you-want-for-new-branch
    vantangst
    @vantangst
    ok. I have created my pull request
    Gavin Mogan
    @halkeye
    great, the maintainer will be able to review it, and give you feedback and submit
    though personally I think the credentials() should still be there
    vantangst
    @vantangst
    ok. I will put it back