[JIRA] (JENKINS-58639) pipeline job runs every two minutes

0 views
Skip to first unread message

luckyhk.lee@samsung.com (JIRA)

unread,
Jul 24, 2019, 8:17:02 AM7/24/19
to jenkinsc...@googlegroups.com
Hokwang Lee updated an issue
 
Jenkins / Task JENKINS-58639
pipeline job runs every two minutes
Change By: Hokwang Lee
Summary: pipeline job runs every two minutes
Attachment: image-2019-07-24-21-13-16-710.png
Attachment: img1.png
Hi,

 

I use pipeline job. (not multibranch)

The config of this job is,

 
# Build Triggers > Poll SCM checked, Schedule */2 * * * *
# Pipeline > Definition : Pipeline script from SCM, SCM : Perforce Software, Polling build filters : Polling per Change Enabled checked

 

I think jenkins job runs well
usally , but sometimes this problem occurs.

!
img1.png!

You can see job created every two minutes.

 

In this case, #114 shows one CL 2921937

and also #115 shows same CL 2921937

actually  up to #141 all runs shows same CL.

 

I do not know why this happened, I found that it could be a clue.

Two CLs are submitted very closely.

!
image-2019-07-24- 20 21 - 58 13 - 40 16 - 514 710 .png!

 

Please check this situation.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

luckyhk.lee@samsung.com (JIRA)

unread,
Jul 24, 2019, 8:22:02 AM7/24/19
to jenkinsc...@googlegroups.com
Hokwang Lee updated an issue
Change By: Hokwang Lee
Attachment: image-2019-07-24-21-20-41-904.png
Attachment: image-2019-07-24-21-19-48-805.png
Attachment: image-2019-07-24-21-18-42-220.png
Hi,

 

I use pipeline job. (not multibranch)

The config of this job is,

 
# Build Triggers > Poll SCM checked, Schedule */2 * * * *
# Pipeline > Definition : Pipeline script from SCM, SCM : Perforce Software, Polling build filters : Polling per Change Enabled checked

 

I think jenkins job runs well usally, but sometimes this problem occurs.


!img1.png!

You can see job created every two minutes.

 

In this case, #114 shows one CL 2921937

and also #115 shows same CL 2921937

actually  up to #141 all runs shows same CL.

 

I do not know why this happened, I found that it could be a clue.

Two CLs are submitted very closely.

!image-2019-07-24-21-13-16-710.png!

 

Please check this situation.


 

Edited:

Several Polling Log :

!image-2019-07-24-21-19-48-805.png!

!image-2019-07-24-21-20-41-904.png!

!image-2019-07-24-21-18-42-220.png!

luckyhk.lee@samsung.com (JIRA)

unread,
Jul 24, 2019, 8:24:02 AM7/24/19
to jenkinsc...@googlegroups.com
Hokwang Lee commented on Task JENKINS-58639
 
Re: pipeline job runs every two minutes

Karl Wirth I will update description and I will send Jenkinsfile to email.

luckyhk.lee@samsung.com (JIRA)

unread,
Jul 24, 2019, 8:46:02 AM7/24/19
to jenkinsc...@googlegroups.com
Hokwang Lee updated an issue
Change By: Hokwang Lee
Attachment: image-2019-07-24-21-44-35-561.png
Attachment: image-2019-07-24-21-43-11-522.png
Attachment: image-2019-07-24-21-42-18-483.png
Hi,

 

I use pipeline job. (not multibranch)

The config of this job is,

 
# Build Triggers > Poll SCM checked, Schedule */2 * * * *
# Pipeline > Definition : Pipeline script from SCM, SCM : Perforce Software, Polling build filters : Polling per Change Enabled checked

 

I think jenkins job runs well usally, but sometimes this problem occurs.

!img1.png!

You can see job created every two minutes.

 

In this case, #114 shows one CL 2921937

!image-2019-07-24-21-42-18-483.png!

and also #115 shows same CL 2921937

!image-2019-07-24-21-43-11-522.png!

actually  up to # 141 140 all runs shows same CL.

 
!image-2019-07-24-21-44-35-561.png!

I do not know why this happened, I found that it could be a clue.

Two CLs are submitted very closely.

!image-2019-07-24-21-13-16-710.png!

 

Please check this situation.

 

Edited:

Several Polling Log :

!image-2019-07-24-21-19-48-805.png!

!image-2019-07-24-21-20-41-904.png!

!image-2019-07-24-21-18-42-220.png!

luckyhk.lee@samsung.com (JIRA)

unread,
Jul 26, 2019, 1:51:02 AM7/26/19
to jenkinsc...@googlegroups.com

kwirth@perforce.com (JIRA)

unread,
Aug 13, 2019, 4:47:02 AM8/13/19
to jenkinsc...@googlegroups.com

Hi Hokwang Lee - I'm now back from vacation and have some more questions so will email you directly.

kwirth@perforce.com (JIRA)

unread,
Sep 2, 2019, 11:34:02 AM9/2/19
to jenkinsc...@googlegroups.com

Believe I have reproduced this. Reproduction steps:

(1) Create a workspace in ws

(2) Create files in "/ws/JENKINS-58639"

(3) Created "/ws/JENKINS-58639/Jenkinsfile":

pipeline {
  options {
        skipDefaultCheckout()
  }  agent { label 'docker-slave' }  stages {
    stage("Sync") {
      steps {
         script{
             checkout perforce(credential: 'JenkinsMaster', filter: [incremental(true)], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minb
ytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'none', format: 'jenkins-${NODE_NAME}-${JOB_NAME}-src', pinHost: 
false, templateName: "JENKINS-58639-template"))
      }
     }
    }
    stage ("wait_prior_starting_smoke_testing") {
         steps {
          echo 'Waiting 20 seconds'
          sleep 30
          }
        }
    stage("Test") {
      steps {
          sh 'ls'
      }
    }
  }
}

(4) Create a job with

(5) Set quiet period to 5 (not so important).

(6) Build job once.

(7) Submit a file to '/ws/JENKINS-58639'.

(8) Add a trigger to perforce to slow down syncs. For example create script "sleep.sh":

echo Sleeping for 600s in trigger...
sleep 600

make the file executable, then create a trigger entry:

	trigger.sleep.1 command pre-user-sync ./sleep.sh

(9) Run Poll now. Job will wait 5 seconds then start building.

(10) Submit another changelist to '/ws/JENKINS-58639'.

(11) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(12) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(13) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(14) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

kwirth@perforce.com (JIRA)

unread,
Sep 2, 2019, 11:37:01 AM9/2/19
to jenkinsc...@googlegroups.com
Karl Wirth edited a comment on Task JENKINS-58639
Believe I have reproduced this. Reproduction steps:

(1) Create a workspace in ws

(2) Create files in "/ws/JENKINS-58639"

(3) Created "/ws/JENKINS-58639/Jenkinsfile":
{code:java}

pipeline {
  options {
        skipDefaultCheckout()
  }  agent { label 'docker-slave' }  stages {
    stage("Sync") {
      steps {
         script{
             checkout perforce(credential: 'JenkinsMaster', filter: [incremental(true)], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minb
ytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'none', format: 'jenkins-${NODE_NAME}-${JOB_NAME}-src', pinHost:
false, templateName: "JENKINS-58639-template"))
      }
     }
    }
    stage ("wait_prior_starting_smoke_testing") {
         steps {
          echo 'Waiting 20 seconds'
          sleep 30
          }
        }
    stage("Test") {
      steps {
          sh 'ls'
      }
    }
  }
}
{code}

(4) Create a job with

!image-2019-09-02-16- 25 35 - 39 17 - 289 464 .png!

!image-2019-09-02-16-
25 35 - 59 31 - 683 486 .png!

!image-2019-09-02-16-
26 35 - 19 47 - 383 986 .png!

!image-2019-09-02-16-
26 36 - 46 07 - 699 417 .png!


(5) Set quiet period to 5 (not so important).

(6) Build job once.

(7) Submit a file to '/ws/JENKINS-58639'.

(8) Add a trigger to perforce to slow down syncs. For example create script "sleep.sh":
{code:java}

echo Sleeping for 600s in trigger...
sleep 600
{code}

make the file executable, then create a trigger entry:
{code:java}
trigger.sleep.1 command pre-user-sync ./sleep.sh
{code}

(9) Run Poll now. Job will wait 5 seconds then start building.

(10) Submit another changelist to '/ws/JENKINS-58639'.

(11) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(12) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(13) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

(14) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.

kwirth@perforce.com (JIRA)

unread,
Sep 2, 2019, 11:37:02 AM9/2/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
 
Change By: Karl Wirth
Labels: P4_SUPPORT P4_VERIFY

kwirth@perforce.com (JIRA)

unread,
Sep 18, 2019, 7:16:01 AM9/18/19
to jenkinsc...@googlegroups.com
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

pallen@perforce.com (JIRA)

unread,
Oct 3, 2019, 9:44:06 AM10/3/19
to jenkinsc...@googlegroups.com
Paul Allen started work on Task JENKINS-58639
 
Change By: Paul Allen
Status: Open In Progress

pallen@perforce.com (JIRA)

unread,
Oct 3, 2019, 9:44:07 AM10/3/19
to jenkinsc...@googlegroups.com
Paul Allen assigned an issue to Charusheela Bopardikar
 
Change By: Paul Allen
Assignee: Charusheela Bopardikar

pallen@perforce.com (JIRA)

unread,
Oct 3, 2019, 9:45:02 AM10/3/19
to jenkinsc...@googlegroups.com
Paul Allen updated an issue
Change By: Paul Allen
Labels: P4_VERIFY P4_A

pallen@perforce.com (JIRA)

unread,
Oct 10, 2019, 9:17:03 AM10/10/19
to jenkinsc...@googlegroups.com
Paul Allen closed an issue as Fixed
 

Released in 1.10.5

Change By: Paul Allen
Status: In Progress Closed
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages