• Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major Major
    • github-oauth-plugin
    • Platform: All, OS: All

      Steps to reproduce:

      • add a new Job
      • make sure it's not run yet
      • configure CC-tray to look at: http://<your-server>/cc.xml?
      • try to add the new Job to CC-tray monitoring
        Expected result:
      • the new job can be added
        Actual result:
      • the new job does not show up in the list of 'Available projects'

      By visiting the cc.xml? URL, I could verify that the xml-file did not contain
      the new job.

      After the job has run correctly at least once, the job is addable.

          [JENKINS-2885] Not all jobs show-up in cc.xml report

          Sorin Sbarnea added a comment -

          That's true because the root cc.xml file exposes only the jobs that are present in the default view, which is not really what people would expect – I was surprised too.

          It seems that if you want all jobs you need to get /view/All/cc.xml but you will probably discover other issues, like the fact that this cc.xml requires authentications! (the root one doesnt!).

          Due to this, if you have github login integration, you will NOT be able to get cc.xml reports unless you have these jobs in the default view.

          Sorin Sbarnea added a comment - That's true because the root cc.xml file exposes only the jobs that are present in the default view, which is not really what people would expect – I was surprised too. It seems that if you want all jobs you need to get /view/All/cc.xml but you will probably discover other issues, like the fact that this cc.xml requires authentications! (the root one doesnt!). Due to this, if you have github login integration, you will NOT be able to get cc.xml reports unless you have these jobs in the default view.

          Jesse Glick added a comment -

          I have no idea what this issue refers to, but it does not sound like anything in Jenkins core.

          Jesse Glick added a comment - I have no idea what this issue refers to, but it does not sound like anything in Jenkins core.

          Daniel Beck added a comment -

          jglick Yes, that would be great. Unfortunately…

          https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/View/cc.xml.jelly

          IMO this shit should just be dropped. The file format definition doesn't even exist anymore outside of archive.org…

          Daniel Beck added a comment - jglick Yes, that would be great. Unfortunately… https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/View/cc.xml.jelly IMO this shit should just be dropped. The file format definition doesn't even exist anymore outside of archive.org…

          ricq added a comment -

          As somebody who knows the original reporter, I know that this issue has long been forgotten and there is no need to keep it open any longer. This has long been surpassed by new ways to monitor the builds, such as wall radiators with the build monitor plugin.

          Closing.

          ricq added a comment - As somebody who knows the original reporter, I know that this issue has long been forgotten and there is no need to keep it open any longer. This has long been surpassed by new ways to monitor the builds, such as wall radiators with the build monitor plugin. Closing.

          Jesse Glick added a comment -

          danielbeck do you volunteer to file a PR to delete cc.xml.jelly? If anyone still cares about it they can create a plugin for it.

          Jesse Glick added a comment - danielbeck do you volunteer to file a PR to delete cc.xml.jelly ? If anyone still cares about it they can create a plugin for it.

          Sorin Sbarnea added a comment -

          Please do NOT delete the cc.xml, it is extremely useful because currently is the only standardized API implemented by most CI servers. Everyone supports it and there are lots of tools consuming it. 

          Even if Jenkins is the leader, it should not break so many tools by removing it.

          Sorin Sbarnea added a comment - Please do NOT delete the cc.xml, it is extremely useful because currently is the only standardized API implemented by most CI servers. Everyone supports it and there are lots of tools consuming it.  Even if Jenkins is the leader, it should not break so many tools by removing it.

          Daniel Beck added a comment -

          ssbarnea The current plan is to release https://github.com/jenkinsci/cctray-xml-plugin and only then remove the core feature (https://github.com/jenkinsci/jenkins/pull/2691), with adequate changelog and upgrade guide entries. There's no reason this should be in core, used or not.

          Daniel Beck added a comment - ssbarnea The current plan is to release https://github.com/jenkinsci/cctray-xml-plugin and only then remove the core feature ( https://github.com/jenkinsci/jenkins/pull/2691 ), with adequate changelog and upgrade guide entries. There's no reason this should be in core, used or not.

            Unassigned Unassigned
            gkforcare gkforcare
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: