[JIRA] (JENKINS-39508) Revision checked out by "checkout scm" can change if new commits happen during build
Title: Message Title Marcus Cobden commented on JENKINS-39508 Re: Revision checked out by "checkout scm" can change if new commits happen during build Oh! Sorry, that's easy to miss! Thanks for the clarification. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39508) Revision checked out by "checkout scm" can change if new commits happen during build
Title: Message Title Marcus Cobden commented on JENKINS-39508 Re: Revision checked out by "checkout scm" can change if new commits happen during build FWIW this is not a new regression, we noticed this ages ago, and have been using stash/unstash for ~6 months. I hadn't realised this wasn't intended behaviour. config.xml consoleText.txt Nothing complicated, just a normal project, not a multibranch project, see attached. Jenkins version 2.30, I updated all plugins yesterday, I can give you specific versions, but here are the pipeline ones: ``` Pipeline: API - 2.6 Pipeline: Basic Steps - 2.3 Pipeline: Build Step - 2.3 Pipeline: Declarative Agent API - 0.5 Pipeline: Groovy - 2.22 Pipeline: Input Step - 2.3 Pipeline: Job - 2.8 Pipeline: Milestone Step - 1.1 Pipeline: Model API - 0.5 Pipeline: Model Definition - 0.5 Pipeline: Multibranch - 2.9 Pipeline: REST API Plugin - 2.2 Pipeline: SCM Step - 2.2 Pipeline: Shared Groovy Libraries - 2.4 Pipeline: Stage Step - 2.2 Pipeline: Stage View Plugin - 2.2 Pipeline: Step API - 2.5 Pipeline: Supporting APIs - 2.10 ``` Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39508) Revision checked out by "checkout scm" can change if new commits happen during build
Title: Message Title Marcus Cobden updated an issue Jenkins / JENKINS-39508 Revision checked out by "checkout scm" can change if new commits happen during build Change By: Marcus Cobden Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39508) Revision checked out by "checkout scm" can change if new commits happen during build
Title: Message Title Marcus Cobden updated an issue Jenkins / JENKINS-39508 Revision checked out by "checkout scm" can change if new commits happen during build Change By: Marcus Cobden Attachment: consoleText.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-26100) SCM steps should return revision state
Title: Message Title Marcus Cobden commented on JENKINS-26100 Re: SCM steps should return revision state I'm seeing the issue where `checkout scm` results in different commits between the start/end of a build; I've made a separate bug with a reproduction example: https://issues.jenkins-ci.org/browse/JENKINS-39508 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39508) Revision checked out by "checkout scm" can change if new commits happen during build
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-39508 Revision checked out by "checkout scm" can change if new commits happen during build Issue Type: Bug Assignee: Unassigned Components: workflow-scm-step-plugin Created: 2016/Nov/04 2:09 PM Priority: Minor Reporter: Marcus Cobden If new commits go into a repo after a build has started we find later stages running against a different commit to the earlier stages. We've been using checkout scm + stash/unstash to work around this I've made a test repo to demonstrate the issue: https://github.com/leth/jenkins-pipeline-scm-test Add Comment
[JIRA] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Marcus Cobden commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin This commit highlights the areas I need some advice on: https://github.com/leth/cobertura-plugin/commit/52a2ce9b2ec9dde01ff9054e1184c2e833e00a60 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] [workflow-plugin] (JENKINS-33126) unstash fails to overwrite read-only files
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-33126 unstash fails to overwrite read-only files Issue Type: Bug Assignee: Jesse Glick Attachments: stacktrace.txt Components: workflow-plugin Created: 24/Feb/16 12:04 PM Priority: Minor Reporter: Marcus Cobden We're using stash & unstash to pass a checked out git repository between steps in our workflow. On first run the unstash works successfully, however on a second run the unstash fails because some of the files in the `.git` directory are read-only. I've attached the stack trace, it's a bit misleading, we've fixed it by running a `sh 'chmod -R u+w .git'` before the unstash step. Add Comment
[JIRA] [multi-branch-project-plugin] (JENKINS-33125) "add property" button broken in property strategy
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-33125 "add property" button broken in property strategy Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 24/Feb/16 11:59 AM Priority: Minor Reporter: Marcus Cobden You can change the property strategy from the UI, but you can't add properties. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Marcus Cobden commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin I'm working a changeset for this, but I could do with some advice from someone more familiar with how Jenkins plugins work, as I'm mostly guessing and copying from the junit and xunit plugins. 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] [workflow-plugin] (JENKINS-32829) Older builds allowed to wait for a throttled stage which a newer build is in
Title: Message Title Marcus Cobden commented on JENKINS-32829 Re: Older builds allowed to wait for a throttled stage which a newer build is in The linear option sounds exactly like what I was hoping for, thanks! 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] [workflow-plugin] (JENKINS-32829) Pre-empted builds not stopped in stage with concurrency:1
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-32829 Pre-empted builds not stopped in stage with concurrency:1 Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 08/Feb/16 10:00 AM Priority: Minor Reporter: Marcus Cobden The docs suggest that marking a stage with "concurrency: 1" will allow only the latest build to run, and that if older builds reach such a section, it will stop executing: "The stage command lets you mark certain sections of a build as being constrained by limited concurrency. Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if they are preëmpted." I instead observed an older build simply waiting until a newer build had finished, and then continuing to run the concurrency: 1 section. This is a problem for us this is our deploy stage, and we wish to only deploy the latest code. Add Comment
[JIRA] [workflow-plugin] (JENKINS-31737) Configure build triggers for generated workflow-multibranch branch jobs
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-31737 Configure build triggers for generated workflow-multibranch branch jobs Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 25/Nov/15 10:21 AM Priority: Minor Reporter: Marcus Cobden I can't find a way to configure the branch job's SCM poll schedule or build frequency. I can ask the `checkout` step to be included in polling, but not configure any polling. Add Comment
[JIRA] [workflow-plugin] (JENKINS-31100) Workflow Job has no git submodule options
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-31100 Workflow Job has no git submodule options Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 22/Oct/15 9:19 AM Priority: Minor Reporter: Marcus Cobden I'd like to request recursive submodule checkout on my git repo, but there doesn't seem to be an option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-31086) 'stash' step applies default ant exclude patterns, no way to disable this
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-31086 'stash' step applies default ant exclude patterns, no way to disable this Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 21/Oct/15 4:10 PM Priority: Minor Reporter: Marcus Cobden I've been trying to stash the output of a git checkout, but it keeps losing my .gitignore files. I've confirmed that the files are there immediately after a checkout, but missing after an unstash. It'd be great if there was a way to avoid this default exclude list being applied. The list of default excludes is here: http://stackoverflow.com/a/6351685 Add Comment
[JIRA] [durable-task-plugin] (JENKINS-30240) Durable tasks fail with no message if tracking files accidentally deleted
Title: Message Title Marcus Cobden created an issue Jenkins / JENKINS-30240 Durable tasks fail with no message if tracking files accidentally deleted Issue Type: Bug Assignee: Jesse Glick Components: durable-task-plugin Created: 01/Sep/15 9:23 AM Priority: Minor Reporter: Marcus Cobden My build ran a "git clean" which deleted the "." directory which this plugin was using to track the task. The build log seemed to just stop, and the task exited `-1`, I only figured out what was going on due to a hunch. Perhaps these tracking files shouldn't live inside the workspace. Add Comment
[JIRA] [workflow-plugin] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title
Marcus Cobden created an issue
Jenkins / JENKINS-30244
Stash command with includes: '**' fails due to "unclosed entries"
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
01/Sep/15 12:37 PM
Priority:
Minor
Reporter:
Marcus Cobden
I highly suspect it's attempting to archive the DurableTask's controlDir.
{{ java.io.IOException: remote file operation failed: /home/jenkins/workspace/TTVM/DSL at hudson.remoting.Channel@4946711c:ttvm-build-02-1e8c2034: java.io.IOException: This archives contains unclosed entries. at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:969) at hudson.FilePath.archive(FilePath.java:450) at org.jenkinsci.plugins.workflow.flow.StashManager.stash(StashManager.java:87) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:85) at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: This archives
[JIRA] [xunit] (JENKINS-12900) Better feedback needed when a report can't be processed
Marcus Cobden commented on JENKINS-12900 Better feedback needed when a report cant be processed I found that the actual error message ended up in the logs for the build node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
