Hi,
It seems that the daemon listens to all repos and all branches belonging
to the jenkinsci organisation. When I reverted a couple of commits on the
stable branch it got linked to the jira[1] so it might seem to get
reverted in master which it was not. (in case you are wondering why the
original commits are not linked it was because they referenced incorrect
jira issue). Similar things can happen when someone works on an issue in a
feature branch in repo hosted under jenkinsci.[2]
This unnecessary clutters issue comments with commit that never will be in
master. In case it is possible to resolve an issue committing to a
non-master branch it is definitely a bug (not sure this ever happened,
though).
I prefer to link only commit that are in master branch of a repository.
What do you think?
Btw.: I did not manage to find the sources on github. Could someone
provide a link? Thanks.
[1]
https://issues.jenkins-ci.org/browse/JENKINS-18776?focusedCommentId=183536#comment-183536
[2]
https://issues.jenkins-ci.org/browse/JENKINS-19154?focusedCommentId=183476#comment-183476
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
