Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48408

GitHub status updating and exposing URL should be an option

      This is somewhat similar to -JENKINS-33151-, but all I'm looking for is to have the option to not push any metadata back to github (such as pr/branch/commit status updating), or, if that isn't possible, to hide the Jenkins URL.

       

      Rationale: we are using a private Jenkins to build our open-source Github repositories (many of them per org).  Currently, all built commits and PRs get marked with our internal Jenkins URL.  This is bad.  

       

      Of course we could use a public Cloudbees-hosted Jenkins, and in fact we do, but for a variety of reasons we need both (e.g.: to populate our internal artifact repos).  

       

      I'd be very happy to submit a PR that adds a checkbox or some other means of controlling this behavior (any pointers would be appreciated).  Thoughts?

          [JENKINS-48408] GitHub status updating and exposing URL should be an option

          Alexander Komarov created issue -
          Alexander Komarov made changes -
          Description Original: This is somewhat similar to JENKINS-33151, but all I'm looking for is to have the option to *not push any metadata back to github* (such as pr/branch/commit status updating).

           

          *Rationale*: we are using a private jenkins to build our open-source github repositories (many of them).  We also use a public cloudbees-hosted jenkins, but for a variety of reasons we need both (e.g.: to populate to our internal artifact repos).  Currently, all built commits and PRs get marked with our internal jenkins URL.  This is bad.  

          I'd be very happy to submit a PR that adds a checkbox (any pointers would be appreciated).
          New: This is somewhat similar to -JENKINS-33151-, but all I'm looking for is to have the option to *not push any metadata back to github* (such as pr/branch/commit status updating), or, failing that, to hide the Jenkins URL.

           

          *Rationale*: we are using a private jenkins to build our open-source github repositories (many of them).  We also use a public cloudbees-hosted jenkins, but for a variety of reasons we need both (e.g.: to populate to our internal artifact repos).  Currently, all built commits and PRs get marked with our internal jenkins URL.  This is bad.  

          I'd be very happy to submit a PR that adds a checkbox (any pointers would be appreciated).
          Alexander Komarov made changes -
          Summary Original: GitHub status updating should be an option New: GitHub status updating and exposing URL should be an option
          Alexander Komarov made changes -
          Description Original: This is somewhat similar to -JENKINS-33151-, but all I'm looking for is to have the option to *not push any metadata back to github* (such as pr/branch/commit status updating), or, failing that, to hide the Jenkins URL.

           

          *Rationale*: we are using a private jenkins to build our open-source github repositories (many of them).  We also use a public cloudbees-hosted jenkins, but for a variety of reasons we need both (e.g.: to populate to our internal artifact repos).  Currently, all built commits and PRs get marked with our internal jenkins URL.  This is bad.  

          I'd be very happy to submit a PR that adds a checkbox (any pointers would be appreciated).
          New: This is somewhat similar to --JENKINS-33151--, but all I'm looking for is to have the option to *not push any metadata back to github* (such as pr/branch/commit status updating), or, if that isn't possible, to hide the Jenkins URL.

           

          *Rationale*: we are using a private Jenkins to build our open-source Github repositories (many of them per org).  Currently, all built commits and PRs get marked with our internal Jenkins URL.  This is bad.  

           

          Of course we could use a public Cloudbees-hosted Jenkins, and in fact we do, but for a variety of reasons we need both (e.g.: to populate our internal artifact repos).  

           

          I'd be very happy to submit a PR that adds a checkbox or some other means of controlling this behavior (any pointers would be appreciated).  Thoughts?
          Alexander Komarov made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Alexander Komarov made changes -
          Attachment New: Screenshot_2017-12-06_12-06-09.png [ 40599 ]

            Unassigned Unassigned
            akom Alexander Komarov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: