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

Random behavior on direct commit

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins 2.303.2
      Chrome Browser
      plugin 0.4.0
      jenkins is running as kubernetes pod
      Bitbucket version control

      I have a jenkins multibranch pipeline where i have kept skip build strategy if commit message contains '[ci skip]'..

      my colleague was trying several commits with commit message as '[ci skip] test', '[ci skip] 12' etc. Most of the times it trigger a build and only a few times it does not.

      Then i created another branch and repeated above. It perfectly works for me and build won't trigger.

       

      My concern is does it have anything to do with browser cache/branch naming convention etc?

      The behavior is random.

       

      The branch name my colleague was trying is feature/test-william .

      The one i tried is feature/test_pra.

      Surprisingly when i make a commit in his branch with '[ci skip]', it does not trigger a build.

      This makes me think of any browser cache or anything like that.

       

      Anyway, please let me know if someone finds a solution for it.

            witokondoria Javier Delgado
            pburnwal Pramod Burnwal
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: