[JIRA] (JENKINS-60672) Timestamper plugin causes chrome frozen when there are too many console logs
Title: Message Title Kaiyuan Zhao commented on JENKINS-60672 Re: Timestamper plugin causes chrome frozen when there are too many console logs Hi Basil Crow, I tried Chrome 80.0.3987.122, it seems ok now. When I create this issue, I was using Chrome 79.0.3945.88(64 bit) described in 'Environment' Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203915.1578386867000.2181.1583130900220%40Atlassian.JIRA.
[JIRA] (JENKINS-60672) Timestamper plugin causes chrome frozen when there are too many console logs
Title: Message Title Kaiyuan Zhao created an issue Jenkins / JENKINS-60672 Timestamper plugin causes chrome frozen when there are too many console logs Issue Type: Bug Assignee: Steven G Brown Components: timestamper-plugin Created: 2020-01-07 08:47 Environment: Jenkins ver. 2.204.1 Timestamper 1.10 Java OpenJDK 1.8.0_232-b09 Chrome 79.0.3945.88(64 bit) install Jenkins via kubernetes helm Labels: jenkins plugin timestamp Priority: Critical Reporter: Kaiyuan Zhao For a Free-Style job: Enable 'Add timestamps to the Console Output' Execute Shell: ``` for i in $(seq 1 1 1) do echo "Welcome $i times" done ``` After build, open /consoleFull, scroll from top to bottom, Chrome will be frozen. When I disable timestamper, everything is ok. When I open /consoleText instead of /consoleFull, it is ok too. I tried install jenkins directly in ubuntu or centos, Chrome will be frozen too. I also tried FireFox and Edge, they won't be frozen and scroll smoothly.
[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Mark Waite Using "${GERRIT_REFSPEC}" fix the first problem.
10:38:45 Cloning the remote Git repository
10:38:45 Using shallow clone
10:38:45 shallow clone depth 2
10:38:45 Avoid fetching tags
10:38:45 Honoring refspec on initial clone
10:38:45 Cloning repository hide
10:38:45 > git init hide # timeout=10
10:38:45 Fetching upstream changes from hide
10:38:45 > git --version # timeout=10
10:38:45 using GIT_SSH to set credentials
10:38:45 > git fetch --no-tags --progress hide refs/changes/50/4750/1 --depth=2 # timeout=10
10:39:34 > git config remote.origin.url hide # timeout=10
10:39:34 > git config --add remote.origin.fetch refs/changes/50/4750/1 # timeout=10
10:39:34 > git config remote.origin.url hide # timeout=10
10:39:34 Fetching upstream changes from hide
10:39:34 using GIT_SSH to set credentials
10:39:34 > git fetch --no-tags --progress hide refs/changes/50/4750/1 --depth=2 # timeout=10
10:40:34 > git rev-parse 44fd5ca794ef1d4ccbfb437d94ef804626dea726^{commit} # timeout=10
10:40:34 Checking out Revision 44fd5ca794ef1d4ccbfb437d94ef804626dea726 (refs/changes/50/4750/1)
10:40:34 > git config core.sparsecheckout # timeout=10
10:40:34 > git checkout -f 44fd5ca794ef1d4ccbfb437d94ef804626dea726 # timeout=10
10:40:38 Commit message: "hide"
10:40:38 > git rev-parse FETCH_HEAD^{commit} # timeout=10
10:40:38 > git rev-list --no-walk eb696053ba8f4c94c388db0334b886879e6aaa42 # timeout=10
But it's also triggering fetch twice and the second fetch is not cost free. In our case, both fetch cost about one minute.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Mark Waite First of all, my job is using Gerrit Trigger. When my Jenkinsfile is like
def scm = [
$class : 'GitSCM',
branches : [[name: '*/master']],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class: 'WipeWorkspace'],
[$class: 'CloneOption', depth: 2, honorRefspec: true, noTags: true, reference: '', shallow: true, timeout: 10],
[$class: 'BuildChooserSetting', buildChooser: [$class: 'GerritTriggerBuildChooser']]
],
submoduleCfg : [],
userRemoteConfigs: [
[
credentialsId: 'hide',
refspec : '$GERRIT_REFSPEC',
url : 'hide'
]
]
]
pipeline {
agent {
node {
label 'gerrit'
}
}
options {
skipDefaultCheckout true
}
stages {
stage('CheckOut') {
steps {
checkout(scm)
}
}
}
}
The console log
Wiping out workspace first.
Cloning the remote Git repository
Using shallow clone
shallow clone depth 2
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository hide
> git init hide # timeout=10
Fetching upstream changes from hide
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --no-tags --progress hide $GERRIT_REFSPEC --depth=2 # timeout=10
> git config remote.origin.url hide # timeout=10
> git config --add remote.origin.fetch $GERRIT_REFSPEC # timeout=10
> git config remote.origin.url hide # timeout=10
Fetching upstream changes from hide
using GIT_SSH to set credentials
> git fetch --no-tags --progress hide refs/changes/64/4264/7 --depth=2 # timeout=10
> git rev-parse 4b5226960edd4551bbafc058db4afc0e69bd103f^{commit} # timeout=10
Checking out Revision 4b5226960edd4551bbafc058db4afc0e69bd103f (refs/changes/64/4264/7)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b5226960edd4551bbafc058db4afc0e69bd103f
Commit message: "hide"
> git rev-parse FETCH_HEAD^{commit} # timeout=10
> git rev-list --no-walk a1323feb6fa57ce13c87a5fd6886b14aa3f75dab # timeout=10
Fetch twice and the first fetch cannot recognize $GERRIT_REFSPEC Then I changed my Jenkinsfile like
def scm = [
$class : 'GitSCM',
branches : [[name: '*/master']],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class: 'CloneOption', depth: 2, honorRefspec: true, noTags: true, reference: '', shallow: true, timeout: 10],
[$class:
[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Facing same issue when using gerrit trigger. My solution is using pipeline job like below
stage('CheckOut') {
steps {
sh "git init"
checkout(scm)
}
}
post {
cleanup {
deleteDir()
}
}
Init git repo first will skip clone step. Do not use WipeWorkspace in scm step, clean workspace in post closure
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
