[Jenkins-infra] Automatically linking tickets between JENKINS and internal tracker

R. Tyler Croy tyler at monkeypox.org
Thu Nov 30 05:39:39 UTC 2017

(replies inline)

On Thu, 30 Nov 2017, Richard Bywater wrote:

> Ok cool. I guess as long as a summary of any private ticket activity gets
> pushed back to the main ticket that should give people an idea about why a
> private link has turned up on the ticket.

As a broader FYI to the list, there is no policy that the Jenkins project has
presently which requires or even encourages this kind of thing. In fact with a
number of plugins maintained by non-hobbyists there are links and references to
all kinds of internal data.  Sometimes we even have people posting references
to internal hosts and then some time later their infosec teams email me asking
to delete it (I don't :)).

The reason I don't care about James running a bot is because I know there are
others already doing this and we have no "thou shalt practice open development"
policies in the project, let alone bot/automated-account guidelines.

I'm loathe to apply special standards to CloudBees (who are currently my
employer) when we don't have any policy formalzed, or even any means to enforce
such guidance.

- R. Tyler Croy

     Code: <https://github.com/rtyler>
  Chatter: <https://twitter.com/agentdero>
     xmpp: rtyler at jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171129/930adfbc/attachment.asc>

More information about the Jenkins-infra mailing list