[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Paul Allen commented on JENKINS-49678 Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file We can't fix the behaviour in the p4-plugin as Jenkins tells us to sync by calling SCM.checkout, the skipDefaultCheckout() is a workaround. 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Simon Watts commented on JENKINS-49678 Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Has this issue actually been fixed, or was it delegated to JENKINS-49714 which was closed as a "won't fix"? 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth commented on JENKINS-49678 Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Raised job against jenkins pipeline behavior - JENKINS-49714 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title
Paul Allen closed an issue as Fixed
Added MultiBranch and Pipeline lightweight checkout documentation for: options { skipDefaultCheckout() }
Jenkins / JENKINS-49678
Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Change By:
Paul Allen
Status:
In Progress Closed
Resolution:
Fixed
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
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49678 Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Code changed in jenkins User: Paul Allen Path: MULTI.md WORKFLOW.md docs/images/declarative.png docs/images/lightweight.png http://jenkins-ci.org/commit/p4-plugin/9d17790788a394b73726335cad2b391b7930903d Log: Document lightweight checkout for Pipeline and MultiBranch. JENKINS-49048 JENKINS-49678 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth started work on JENKINS-49678 Change By: Karl Wirth Status: Open In Progress 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth assigned an issue to Paul Allen Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Karl Wirth Assignee: Karl Wirth Paul Allen 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Karl Wirth Assignee: Karl Wirth 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title
Karl Wirth commented on JENKINS-49678
Re: Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Not controlled by P4Jenkins. The pipeline option 'skipDefaultCheckout' will disable this implict Sync:
pipeline {
agent any
options { skipDefaultCheckout() }
stages{
stage('Test') {
steps {
echo 'Testing..'
}
}
stage('Deploy') {
steps {
echo 'Deploying'
}
}
}
}
We are planning to document this in on help pages. Note: Lightweight checkout is not our option so we cant update the help bubble text.
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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Change By: Karl Wirth Labels: P4_VERIFY 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.
[JIRA] (JENKINS-49678) Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-49678 Pipleine lightweight Jenkinsfile checkout still runs p4 sync after 'p4 print' of Jenkins file Issue Type: Bug Assignee: Unassigned Attachments: ExampleJobOutput.txt Components: p4-plugin Created: 2018-02-21 16:57 Environment: P4-Plugin 1.8.4 Priority: Major Reporter: Karl Wirth The aim of lightweight checkout is to only get the Jenkinsfile instead of the whole directory/branch contents. At the moment P4Jenkins does a p4 print that is not displayed in the job log (due to known issue in Jenkins and lightweight checkout) then does a sync of the whole workspace that is visible. For example: P4 Task: syncing files at change: 92 (p4):cmd:... p4 sync /var/lib/jenkins/workspace/LightweightPipeline/...@92 p4 sync /var/lib/jenkins/workspace/LightweightPipeline/...@92 ... totalFileSize 615 ... totalFileCount 2 //depot/lightweight/Jenkinsfile#1 - added as /var/lib/jenkins/workspace/LightweightPipeline/Jenkinsfile //depot/lightweight/f1#1 - added as /var/lib/jenkins/workspace/LightweightPipeline/f1 Lightweight checkout should imply that full sync is disabled and left to the control of the Jenkinsfile
