[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title John Mellor resolved as Cannot Reproduce This issue has not been seen for the last 29 minor Jenkins releases. Assumed fixed. Jenkins / JENKINS-29688 Promotion sometimes fails to copy artifacts to workspace Change By: John Mellor Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title Daniel Beck commented on JENKINS-29688 Re: Promotion sometimes fails to copy artifacts to workspace Please provide minimal but complete steps to reproduce this issue from scratch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title John Mellor commented on JENKINS-29688 Re: Promotion sometimes fails to copy artifacts to workspace The conditions where CopyArtifact skips the artifact copying are unknown. All builds that were occasionally exhibiting this incorrect behaviour had the following general steps during promotion: 1) Script to build product on multiple platforms and then merge the deliverables into one subdirectory (artifacts). 2) copy artifacts to master so that they are on a known host. 3) wait for manual promotion, sometimes delayed by weeks until test results are accepted. 4) promote specific build: 4a) copy artifacts from another project (always our own project: $PROMOTED_JOB_NAME or exact test of the name) to get it to the current host. 4b) script to promote to an internal Debian repo mechanism I have abandoned this CopyArtifact mechanism in steps (2 and 4a) because of the inconsistency, and can no longer reproduce the issue as a consequence. The following is the promotion job build.xml from a simpler project that only builds one platform: ?xml version='1.0' encoding='UTF-8'? hudson.plugins.promoted__builds.Promotion plugin=promoted-builds@2.21 actions hudson.model.ParametersAction parameters/ /hudson.model.ParametersAction hudson.plugins.promoted__builds.PromotionTargetAction jobNamedart/jobName number13/number /hudson.plugins.promoted__builds.PromotionTargetAction hudson.model.CauseAction causes hudson.model.Cause_-UserCause authenticationNamejmellor/authenticationName /hudson.model.Cause_-UserCause /causes /hudson.model.CauseAction hudson.plugins.copyartifact.CopyArtifact_-EnvAction plugin=copyartifact@1.35.2/ hudson.tasks.Fingerprinter_-FingerprintAction record entry stringdart_1.3.0-1_amd64.changes/string string128238385dd8db61072b21c0f6bbfc54/string /entry entry stringdart_1.3.0-1.dsc/string stringd863b418a7676b7a0cbff649ace198e1/string /entry entry stringdart_1.3.0-1_amd64.deb/string stringbf06f5b64673b029f352110747c515c9/string /entry /record /hudson.tasks.Fingerprinter_-FingerprintAction /actions queueId6179/queueId timestamp1439392433073/timestamp startTime1439392433073/startTime resultFAILURE/result duration291/duration charsetUTF-8/charset keepLogfalse/keepLog builtOnbuildslave1/builtOn workspace/var/lib/jenkins/workspace/dart/workspace hudsonVersion1.623/hudsonVersion scm class=hudson.scm.NullChangeLogParser/ culprits class=com.google.common.collect.EmptyImmutableSortedSet/ /hudson.plugins.promoted__builds.Promotion Add Comment This message was sent by
[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title
John Mellor updated an issue
Jenkins / JENKINS-29688
Promotion sometimes fails to copy artifacts to workspace
Change By:
John Mellor
Sometimestheartifactcopystepisskippedforunknownreasons,resultinginabadpromotion.Icanlocatenousefullogstoidentifytheissue,otherthanthepromotionlogitselfshowingamissedcriticalstep.Allpromotionsaremanual,andrunashellscriptastheactualpromotion.Logheadfromanincorrectpromotionexamplelog:{quote}StartedbyuserilijabBuildingremotelyonbuildslave4inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#93[esensor-core]$/bin/bash-xe/tmp/hudson5568737232874898866.sh...{quote}Logheadfromacorrectpromotionofthesamejob,runearlierinthedaywithnoproductorbuildchanges:{quote}StartedbyuserwfangBuildingremotelyonbuildslave1inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#92{color:red}Copied2artifactsfromesensor-corebuildnumber92{color}buildhudson.plugins.copyartifact.CopyArtifact@144ec690SUCCESS{quote}...Ascanbeseen,thepromotionsometimescopiesthecorrectartifactsfrommaster,andsometimesincorrectlydecidesnotto.Sincethepromotion runs andtherelatedbuildprocesseswillrun onanarbitraryhostinthecluster,oldworkspacecontentsaregenerallypresentanditisnotclearwhyitdecidestowronglyskipthecopystep.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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,
[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title
John Mellor created an issue
Jenkins / JENKINS-29688
Promotion sometimes fails to copy artifacts to workspace
Issue Type:
Bug
Assignee:
Unassigned
Components:
promoted-builds-plugin
Created:
28/Jul/15 5:31 PM
Environment:
Jenkins 1.620 on Ubuntu 12 with multiple slaves, promoted-builds plugin version 2.21 (latest)
Priority:
Critical
Reporter:
John Mellor
Sometimes the artifact copy step is skipped for unknown reasons, resulting in a bad promotion. I can locate no useful logs to identify the issue, other than the promotion log itself showing a missed critical step. All promotions are manual, and run a shell script as the actual promotion.
Log head from an incorrect promotion example log: {{Started by user ilijab Building remotely on buildslave4 in workspace /var/lib/jenkins/workspace/esensor-core Promoting esensor-core #93 [esensor-core] $ /bin/bash -xe /tmp/hudson5568737232874898866.sh . . .}}
Log head from a correct promotion of the same job, run earlier in the day with no product or build changes: {{Started by user wfang Building remotely on buildslave1 in workspace /var/lib/jenkins/workspace/esensor-core Promoting esensor-core #92 Copied 2 artifacts from esensor-core build number 92 build
[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title
John Mellor updated an issue
Jenkins / JENKINS-29688
Promotion sometimes fails to copy artifacts to workspace
Change By:
John Mellor
Sometimestheartifactcopystepisskippedforunknownreasons,resultinginabadpromotion.Icanlocatenousefullogstoidentifytheissue,otherthanthepromotionlogitselfshowingamissedcriticalstep.Allpromotionsaremanual,andrunashellscriptastheactualpromotion.Logheadfromanincorrectpromotionexamplelog:{ { quote} StartedbyuserilijabBuildingremotelyonbuildslave4inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#93[esensor-core]$/bin/bash-xe/tmp/hudson5568737232874898866.sh... {quote } } Logheadfromacorrectpromotionofthesamejob,runearlierinthedaywithnoproductorbuildchanges:{ { quote} StartedbyuserwfangBuildingremotelyonbuildslave1inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#92{color:red}Copied2artifactsfromesensor-corebuildnumber92{color}buildhudson.plugins.copyartifact.CopyArtifact@144ec690SUCCESS {quote } } ...Ascanbeseen,thepromotionsometimescopiesthecorrectartifactsfrommaster:,andsometimesincorrectlydecidesnotto.Sincethepromotionrunsonanarbitraryhostinthecluster,oldworkspacecontentsaregenerallypresentanditisnotclearwhyitdecidestowronglyskipthecopystep.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [promoted-builds-plugin] (JENKINS-29688) Promotion sometimes fails to copy artifacts to workspace
Title: Message Title
John Mellor updated an issue
Jenkins / JENKINS-29688
Promotion sometimes fails to copy artifacts to workspace
Change By:
John Mellor
Sometimestheartifactcopystepisskippedforunknownreasons,resultinginabadpromotion.Icanlocatenousefullogstoidentifytheissue,otherthanthepromotionlogitselfshowingamissedcriticalstep.Allpromotionsaremanual,andrunashellscriptastheactualpromotion.Logheadfromanincorrectpromotionexamplelog:{quote}StartedbyuserilijabBuildingremotelyonbuildslave4inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#93[esensor-core]$/bin/bash-xe/tmp/hudson5568737232874898866.sh...{quote}Logheadfromacorrectpromotionofthesamejob,runearlierinthedaywithnoproductorbuildchanges:{quote}StartedbyuserwfangBuildingremotelyonbuildslave1inworkspace/var/lib/jenkins/workspace/esensor-corePromotingesensor-core#92{color:red}Copied2artifactsfromesensor-corebuildnumber92{color}buildhudson.plugins.copyartifact.CopyArtifact@144ec690SUCCESS{quote}...Ascanbeseen,thepromotionsometimescopiesthecorrectartifactsfrommaster : ,andsometimesincorrectlydecidesnotto.Sincethepromotionrunsonanarbitraryhostinthecluster,oldworkspacecontentsaregenerallypresentanditisnotclearwhyitdecidestowronglyskipthecopystep.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
