[JIRA] (JENKINS-40110) Tasks sometimes get broken clients on connection
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Closing old issues. Jenkins / JENKINS-40110 Tasks sometimes get broken clients on connection Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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-47602) Perforce changelist maxfiles stuck at 50.
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-47602 Perforce changelist maxfiles stuck at 50. Change By: Paul Allen Status: Resolved Closed 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt edited a comment on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction ; there is in JENKINS-49141There has been a lot of pain and error in the way utf8 has been introduced/supported.The change in behaviour dependant upon client/plugin version has caused much confusion... however right now things are definitely broken/wrong as the latest plugin behaves differently from the latest client, and possible the server being in unicode mode further changes things. Please also JENKINS-49141 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-46919) "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec"
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46919 "checkout perforce" does not fail on "Syntax error" when "Missing client name and/or owner in spec" Change By: Paul Allen Labels: P4_B 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-49527) Use Global rule Parsing is not working
Title: Message Title pramendra kumar created an issue Jenkins / JENKINS-49527 Use Global rule Parsing is not working Issue Type: Bug Assignee: Victor Martinez Attachments: image-2018-02-13-18-12-16-702.png, image-2018-02-13-18-13-55-273.png Components: jenkinslint-plugin Created: 2018-02-13 12:51 Priority: Critical Reporter: pramendra kumar jenkins version : 2.93 Log parser plugin 2.0 Under jenkins server->Manage Jenkins->Configure System, i have done as below: While Job creation, i have selected global parsing, as below: After deploying the job, use global rule parsing option is not working but use project rule is working. Parsed console output is showing as below: ERROR: Failed to parse console log java.nio.file.NoSuchFileException: /var/lib/jenkins/parser Add Comment
[JIRA] (JENKINS-43556) Stage View shows incorrect build result
Title: Message Title Russell Gallop commented on JENKINS-43556 Re: Stage View shows incorrect build result I also see this with jenkins 2.73.3, pipeline stage view 2.9 and pipeline rest api plugin 2.9. Build history view on the left shows success, stage view shows the whole row in red with no cell highlighted in stripey red. The normal api for the build: //api/python?pretty=true says "result": "SUCCESS" The wfapi: /wfapi/run shows as having "status": "FAILED" . All stages within that report "SUCCESS". The pipeline steps view shows SUCCESS for every step so it seems like a problem with the overall status from the wfapi. 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-49529) retry at stage level in declarative pipeline fails
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-49529
retry at stage level in declarative pipeline fails
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-13 13:59
Environment:
Pipeline declarative: 1.2.2
Labels:
declarative multibranch pipeline retry stage
Priority:
Minor
Reporter:
davidkarlsen
Docs https://jenkins.io/doc/book/pipeline/syntax/ declare retry is allowed at stage level, but I get:
WorkflowScript: 52: Unknown stage section "options". Starting with version 0.5, steps in a stage must be in a steps block. @ line 52, column 5.
stage('test') {
^
when doing:
stage('test') {
options {
// TODO: Fix - some tests are flaky - sometimes pass, sometimes not
retry(3)
}
steps {
runCompose( 'test' )
}
}
[JIRA] (JENKINS-46902) Double Byte Order Mark - UTF8
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46902 Double Byte Order Mark - UTF8 Change By: Paul Allen Labels: P4_A 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-46574) P4 Plugin uses backslash '\' in multibranch pipeline instead of slash / when scanning for Jenkinsfile
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46574 P4 Plugin uses backslash '\' in multibranch pipeline instead of slash / when scanning for Jenkinsfile Change By: Paul Allen Labels: P4_A 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-49528) Peformance graphs for individual tests are not created when a single test has failed
Title: Message Title Tobias Lingemann created an issue Jenkins / JENKINS-49528 Peformance graphs for individual tests are not created when a single test has failed Issue Type: Bug Assignee: Eugene Schava Components: perfpublisher-plugin Created: 2018-02-13 13:48 Environment: Jenkins 2.89.3 Performance Publisher plugin 8.05 JRE 1.8.0_144-b01 Windows 7 Priority: Minor Reporter: Tobias Lingemann I have tried a lot of things, but whenever a single test fails, the performance publisher plugin does not create graphs for individual tests. Only the overview (sum) of all tests is created. If no test has failed, the graphs are created as expected. Since I cannot think of any reason why someone would want this, I must assume that this is a bug. Add Comment
[JIRA] (JENKINS-45465) Performance work on Sync/Populate options
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-45465 Performance work on Sync/Populate options Change By: Paul Allen Labels: P4_BACKLOG 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-47630) p4-plugin should support multi-branch declarative pipelines with default checkout
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-47630 p4-plugin should support multi-branch declarative pipelines with default checkout Change By: Paul Allen Labels: P4_BACKLOG 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-46574) P4 Plugin uses backslash '\' in multibranch pipeline instead of slash / when scanning for Jenkinsfile
Title: Message Title Paul Allen closed an issue as Fixed Fixed in 1.7.5 (change @22758) Jenkins / JENKINS-46574 P4 Plugin uses backslash '\' in multibranch pipeline instead of slash / when scanning for Jenkinsfile Change By: Paul Allen Status: Open Closed Assignee: Paul Allen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-49319) Old Prototype library causes problems with modern UI frameworks
Title: Message Title Ulli Hafner commented on JENKINS-49319 Re: Old Prototype library causes problems with modern UI frameworks Here is an example of the upcoming release of analysis-core: Priority Doughnut Graph. If I change the graph type to a bar-chart then the error in the stack trace (comment before) appears. 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-49525) Rare exception sync'ing global pipeline library with new project
Title: Message Title Simon Watts created an issue Jenkins / JENKINS-49525 Rare exception sync'ing global pipeline library with new project Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-02-13 11:45 Environment: Jenkins 2.89.2 P4 Plugin 1.8.4 Pipeline 2.5 Priority: Minor Reporter: Simon Watts I've seen this a couple of times now – when first building a new project in Jenkins, an exception is thrown when loading the global pipeline library used by all our projects. This does not happen every time. There seems to be some confusion with the exception mentioning a job folder for a different project (see below). The exception has not been seen to reoccur when another build is triggered immediately after this failure (this may be due to the low frequency of this occurance). We have not seen this type of failure in projects which are not new – so seems related to the initial checkout? Note that no other projects where building at the time, and none where scheduled to build. The 'ANOTHERPROJECT' in the logs below was not recently rebuilt, and is not lexcially close to the project being built. Complete log for the initial failed build (with named redacted): Started by user anonymous Obtained DEPOT/PROJECT/Jenkinsfile from p4-HASH-PROJECT Running in Durability level: MAX_SURVIVABILITY Loading library LIBRARY@1.0 (p4):cmd:... p4 client -o extlib-LIBRARY p4 client -o extlib-LIBRARY (p4):stop:4 (p4):cmd:... p4 info p4 info (p4):stop:5 (p4):cmd:... p4 client -o extlib-LIBRARY p4 client -o extlib-LIBRARY (p4):stop:6 (p4):cmd:... p4 client -i p4 client -i Client
[JIRA] (JENKINS-49041) clobber is always true
Title: Message Title Mykola Ulianytskyi commented on JENKINS-49041 Re: clobber is always true Thank you 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-48434) Perforce based Pipelines with polling can Delete Jenkins Home directory
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-48434 Perforce based Pipelines with polling can Delete Jenkins Home directory Change By: Paul Allen Labels: perforce-plugin P4_A 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt commented on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction. 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-31664) Help text for available Environment variable descriptions missing
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-31664 Help text for available Environment variable descriptions missing Change By: Paul Allen Labels: P4_A 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-44512) Client Spec with Folders
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-44512 Client Spec with Folders Change By: Paul Allen Labels: P4_BACKLOG 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-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Erik Jonsson assigned an issue to Erik Jonsson Jenkins / JENKINS-49508 warnings-plugin aborts if unable to git-blame. Change By: Erik Jonsson Assignee: Ulli Hafner Erik Jonsson 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-49526) SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded
Title: Message Title Jim Klimov created an issue Jenkins / JENKINS-49526 SCM Polling frequency in Branch Source generated Multibranch projects seems hardcoded Issue Type: Improvement Assignee: Aaron Whiteside Components: pipeline, pipeline-github-plugin Created: 2018-02-13 12:34 Priority: Major Reporter: Jim Klimov Use-case: a Jenkins deployment on internal LAN, corporate IT won't allow incoming connections - so no webhooks. Polling must be used to find and build new code from public or corporate SCM systems. Prerequisite: have a Github (or Stash) organization with some component repositories, each has Jenkinsfile pipelines in master and other branches - and those pipeline scripts define a speedy polling frequency (H/2 .. H/5) On Jenkins: create a New Item / Github Organization (AFAIK backed by Branch source nowadays - at least I have no Github Organization plugin installed anymore) point the setup at desired organization have it scan the org, find repos, set up MultiBranch pipelines for the repos, scan repos, find branches, find Jenkinsfiles, set up jobs for each matching branch. Review that the final jobs have the frequent polling in their read-only configuration, and that it is indeed honored (add a commit, see it built in a couple of minutes) Add a branch or PR against the monitored repo... and wait a day for it to be found! When it is finally found, see the subsequent additions to the branch (or origin of the PR) get discovered and built as frequently as set up via Jenkinsfile.
[JIRA] (JENKINS-48845) Recent Changes / changelog not shown correctly by P4 Plugin
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-48845 Recent Changes / changelog not shown correctly by P4 Plugin Change By: Paul Allen Status: Resolved Closed 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-45611) Console log output and timestamper/ansi color
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-45611 Console log output and timestamper/ansi color Change By: Paul Allen Status: Resolved Closed Assignee: 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-41217) Use consistent syntax in View and build filters
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-41217 Use consistent syntax in View and build filters Change By: Paul Allen Status: Resolved Closed Assignee: 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-49041) clobber is always true
Title: Message Title Paul Allen reopened an issue Jenkins / JENKINS-49041 clobber is always true Change By: Paul Allen Resolution: Won't Do Status: Closed Reopened Assignee: 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-45612) Running tests litters source directory
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-45612 Running tests litters source directory Change By: Paul Allen Status: Resolved Closed Assignee: 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-49041) clobber is always true
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.8.5 Jenkins / JENKINS-49041 clobber is always true Change By: Paul Allen Status: Reopened 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 to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44706) Tracking of P4 Credentials is slowing down REST API queries
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-44706 Tracking of P4 Credentials is slowing down REST API queries Change By: Paul Allen Labels: P4_C 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-40355) P4 hangs on reconcile call
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-40355 P4 hangs on reconcile call Change By: Paul Allen Labels: P4_B 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-49527) Use Global rule Parsing is not working
Title: Message Title pramendra kumar updated an issue Jenkins / JENKINS-49527 Use Global rule Parsing is not working Change By: pramendra kumar Component/s: log-parser-plugin Component/s: jenkinslint-plugin 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-46984) p4-plugin: rebuild doesn't work properly with "build review"
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46984 p4-plugin: rebuild doesn't work properly with "build review" Change By: Paul Allen Labels: P4_BACKLOG 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-34946) P4 Plugin runs out of memory reverting files
Title: Message Title Paul Allen stopped work on JENKINS-34946 Change By: Paul Allen Status: In Progress Open 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-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Erik Jonsson commented on JENKINS-49508 Re: warnings-plugin aborts if unable to git-blame. Yes, that must have been the problem. I got it working now. Sorry about this missunderstandig. 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-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Erik Jonsson resolved as Fixed Acuall issue was with a different plugin. Jenkins / JENKINS-49508 warnings-plugin aborts if unable to git-blame. Change By: Erik Jonsson Status: Open Resolved 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 to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49041) clobber is always true
Title: Message Title
Mykola Ulianytskyi updated an issue
Jenkins / JENKINS-49041
clobber is always true
Change By:
Mykola Ulianytskyi
HelloP4 plugin always creates workspaces with 'clobber: true' even if 'clobber: false' was specified.Example:{code:java}node { checkout perforce( credential: 'e0cd5f60-0ddd-4289-b0f3-x', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), workspace: manualSpec(charset: 'none', name: 'xxx', pinHost: false, spec: clientSpec(allwrite: false, backup: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: "//depot/stream/Jenkinsfile //xxx/Jenkinsfile")))}{code} {code:java}> p4 workspace -o xxxClient: xxxOwner: build_gamek02 xxx Root: /home/ warface xxx /workspace/xxxOptions: noallwrite clobber nocompress unlocked nomodtime normdirSubmitOptions: submitunchangedLineEnd: localView://depot/stream/Jenkinsfile //xxx/Jenkinsfile{code}Please fix.Thank you
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49528) Peformance graphs for individual tests are not created when a single test has failed
Title: Message Title Tobias Lingemann updated an issue Jenkins / JENKINS-49528 Peformance graphs for individual tests are not created when a single test has failed Change By: Tobias Lingemann I have tried a lot of things, but whenever a single test fails, the performance publisher plugin does not create graphs for individual tests. Only the overview (sum) of all tests is created. If no test has failed, the graphs are created as expected.Since I cannot think of any reason why someone would want this, I must assume that this is a bug. My Jenkins job runs the tests with MSTest. Each test measures the execution time for various scenarios and each test creates a new xml file that is parsed by the performance publisher plugin. If a test reports an error (e.g. the execution time exceeds a certain limit), the job is marked as unstable. This is done automatically by the MSTest plugin.The plugin works fine with multiple xml files, as long as all tests have passed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-33981) P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-33981 P4 Plugin - Using auto cleanup & sync with REPLACE missing/modified files fails Change By: Paul Allen Labels: p4-plugin P4_B 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-30878) Observing no improvement from the addition of the modtime -m reconcile
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-30878 Observing no improvement from the addition of the modtime -m reconcile Change By: Paul Allen Labels: P4_B 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-49141) P4 plugin removed BOM from utf8 files
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49141 P4 plugin removed BOM from utf8 files Change By: Paul Allen Labels: P4_B 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Robert Pitt edited a comment on JENKINS-46902 Re: Double Byte Order Mark - UTF8 Similar problem but in the opposite direction ; there is a lot of pain and error in the way utf8 has been introduced/supported . The change in behaviour dependant upon client/plugin version has caused much confusion... however right now things are definitely broken/wrong as the latest plugin behaves differently from the latest client, and possible the server being in unicode mode further changes things. Please also JENKINS-49141 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-34946) P4 Plugin runs out of memory reverting files
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-34946 P4 Plugin runs out of memory reverting files Change By: Paul Allen Labels: memory P4_B 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master I think it would be useful to add to the documentation that the name of the container for the jnpl agent must be named jnlp. This issue was quite hard to debug 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-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Luca Naldini commented on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Just me or the tests fail when building with maven? Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.805 sec <<< FAILURE! - in com.orctom.jenkins.plugin.globalpostscript.ScriptTest testExecuteGroovy2(com.orctom.jenkins.plugin.globalpostscript.ScriptTest) Time elapsed: 1.734 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy2(ScriptTest.java:106) testExecuteGroovy(com.orctom.jenkins.plugin.globalpostscript.ScriptTest) Time elapsed: 0.013 sec <<< FAILURE! org.junit.ComparisonFailure: expected:<[dropdeploy to: server1]> but was:<[]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at com.orctom.jenkins.plugin.globalpostscript.ScriptTest.testExecuteGroovy(ScriptTest.java:94) Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 16.311 sec - in InjectedTest Results : Failed tests: ScriptTest.testExecuteGroovy2:106 expected:<[dropdeploy to: server1]> but was:<[]> ScriptTest.testExecuteGroovy:94 expected:<[dropdeploy to: server1]> but was:<[]> Tests run: 9, Failures: 2, Errors: 0, Skipped: 0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48922) Groovy PostBuild plugin is not compatible with JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48922 Re: Groovy PostBuild plugin is not compatible with JEP-200 Code changed in jenkins User: ikedam Path: Jenkinsfile pom.xml http://jenkins-ci.org/commit/groovy-postbuild-plugin/61f2d13e491ea42a5572590b1903a0acfbfef11c Log: Merge pull request #29 from oleg-nenashev/jep-200/pct-compat JENKINS-48922 - Update plugin to make it runnable in PCT Compare: https://github.com/jenkinsci/groovy-postbuild-plugin/compare/c2638a586703...61f2d13e491e 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-48922) Groovy PostBuild plugin is not compatible with JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48922 Re: Groovy PostBuild plugin is not compatible with JEP-200 Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/groovy-postbuild-plugin/6fd0cd8a95015e394fc61bae14ab4bcc2cf2bc08 Log: JENKINS-48922 - Update plugin POM to reproduce the issue in PCT 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-49522) [withCredentials] MissingPropertyException from shared library class
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49522 [withCredentials] MissingPropertyException from shared library class Change By: Oleg Nenashev Component/s: pipeline 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-49210) Do not use ArrayList#sublist()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49210 Re: Do not use ArrayList#sublist() Code changed in jenkins User: ikedam Path: pom.xml src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceWatchQueueDecisionHandler.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceWatchRunListener.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinition.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/510132ee60ed0e7ee5dc1083035dccc76ab0bcbc Log: JENKINS-49017JENKINS-49210 Allow to run tests against latest cores This change allows us to run "mvn test -Djenkins.version=2.102 -Djava.level=8" to test compatibility with JEP-200 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza commented on JENKINS-49263 Re: Determine minimal useful test case for running ATH for Jenkins Core ScriptTest and SlaveTest have not shown flakiness in my runs, BUT they have shown some lack of robustness against changes in the UI in the history, so is better to remove them from the list for the first implementation 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-49468) Pipeline view only able to select the top-most of the in-progress parallel nodes
Title: Message Title Christian Ciach commented on JENKINS-49468 Re: Pipeline view only able to select the top-most of the in-progress parallel nodes Can confirm. It should be noted that this issue is only with pipelines that are currently in progress. If the pipeline has finished, I can select and view the data of all parallel nodes just fine. 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-49468) Pipeline view only able to select the top-most of the in-progress parallel nodes
Title: Message Title Christian Ciach edited a comment on JENKINS-49468 Re: Pipeline view only able to select the top-most of the in-progress parallel nodes This issue seems to pop up again from time to time. Related issues are - - JENKINS-43747- - and - - JENKINS-42312- - .Edit: Seems to be fixed alread already : - JENKINS-49272 - 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza commented on JENKINS-49263 Re: Determine minimal useful test case for running ATH for Jenkins Core So my proposal is to run the SmokeTest Category "fixed" by #PR-410 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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Oleg Nenashev commented on JENKINS-49523 Re: archiveArtifacts excludes does not work with spaces It seems we just need to improve the documentation to clarify that the field should be comma-separated. 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-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Stefan Drissen created an issue Jenkins / JENKINS-49523 archiveArtifacts excludes does not work with spaces Issue Type: Bug Assignee: Unassigned Attachments: image-2018-02-13-09-56-20-897.png, image-2018-02-13-09-57-11-238.png Components: core Created: 2018-02-13 08:58 Environment: Windows 2012R2 x64 Java 1.8.0_161 x64 Jenkins 2.105 Priority: Minor Reporter: Stefan Drissen The Post-build action Archive the Artifacts has an 'excludes' property to exclude files. The help text points to http://ant.apache.org/manual/Types/fileset.html: Which states that excludes can be comma- or space-separated list. When using space nothing is excluded. When using comma the exclude works fine. Add Comment
[JIRA] (JENKINS-44647) Support pipeline jobs (i.e. call the script on pipeline job completion)
Title: Message Title Hao CHEN commented on JENKINS-44647 Re: Support pipeline jobs (i.e. call the script on pipeline job completion) Merged and released, please 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-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title Oleg Nenashev commented on JENKINS-48204 Re: NPE in BlueOcean REST API / JIRA interaction Michael Neale there is still a bug in JIRA plugin IMO. It should not fail with NPE on such calls. I would create a follow-up ticket 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-49524) JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-49524 JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky Issue Type: Bug Assignee: Raul Arabaolaza Components: acceptance-test-harness Created: 2018-02-13 09:33 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza When analyzing the robustness of the SmokeTest category for JENKINS-49263 I have found that JenkinsDatabaseSecurityRealmTest#login_and_logout is failing sometimes with the following error: expected: but was: I have debugged the problem and the issue seems to be that login is not finished (or at least not shown in the UI) Things that I have tried so far: Dynamic wait of 10 seconds for log in link -> Seems to reduce flakiness but did not solve it Refresh the page in case log link is not found to avoid cache problems -> No effect The login form is correctly submitted because the test is automatically redirected to home after logging Not sure if this may be a performance issue, but 10 seconds for a login seems more than adequate for me. The test has to be fixed and reincorporated into SmokeTest category
[JIRA] (JENKINS-49017) configSubmit exception with Textarea choices ended with empty line
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49017 Re: configSubmit exception with Textarea choices ended with empty line Code changed in jenkins User: ikedam Path: pom.xml src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceWatchQueueDecisionHandler.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ChoiceWatchRunListener.java src/main/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/ExtensibleChoiceParameterDefinition.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/510132ee60ed0e7ee5dc1083035dccc76ab0bcbc Log: JENKINS-49017JENKINS-49210 Allow to run tests against latest cores This change allows us to run "mvn test -Djenkins.version=2.102 -Djava.level=8" to test compatibility with JEP-200 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-49017) configSubmit exception with Textarea choices ended with empty line
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49017 Re: configSubmit exception with Textarea choices ended with empty line Code changed in jenkins User: ikedam Path: src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/GlobalTextareaChoiceListProviderJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/TextareaChoiceListProviderJenkinsTest.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/7c6a39bcf4069edeb71b9723052f0506135273cb Log: JENKINS-49017JENKINS-49210 Add tests to reproduce issues with JEP-200 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-49210) Do not use ArrayList#sublist()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49210 Re: Do not use ArrayList#sublist() Code changed in jenkins User: ikedam Path: src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/GlobalTextareaChoiceListProviderJenkinsTest.java src/test/java/jp/ikedam/jenkins/plugins/extensible_choice_parameter/TextareaChoiceListProviderJenkinsTest.java http://jenkins-ci.org/commit/extensible-choice-parameter-plugin/7c6a39bcf4069edeb71b9723052f0506135273cb Log: JENKINS-49017JENKINS-49210 Add tests to reproduce issues with JEP-200 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master This was related to this issue. If the name of the custom agent is not `jnlp`, then another agent with the default jnlp image is created. This explains messages like `channel already closed` etc.. 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-32776) Jenkins shouldn't store API tokens in a recoverable format
Title: Message Title Wadeck Follonier started work on JENKINS-32776 Change By: Wadeck Follonier 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-32442) Disable Jenkins API tokens by default
Title: Message Title Wadeck Follonier started work on JENKINS-32442 Change By: Wadeck Follonier 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza commented on JENKINS-49263 Re: Determine minimal useful test case for running ATH for Jenkins Core Confirmed that I have not been able to remove the flakiness of `JenkinsDatabaseSecurityRealmTest#login_and_logout` in a reasonable amount of time, so my proposal is to remove it from the `SmokeTest` category, create a ticket to try to fix it properly and add it again when 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 to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49523) archiveArtifacts excludes does not work with spaces
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49523 archiveArtifacts excludes does not work with spaces Change By: Oleg Nenashev Labels: documentation 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-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace
Title: Message Title Cyrille Le Clerc commented on JENKINS-49413 Re: IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace Mirko Streckenbach please create de dedicated JIRA issue if you get an IllegalArgumentException when the Maven project is in a sub folder of your "checkout". javydreamercsw I am afraid that we cannot do much if some generated artifacts are stored outside of the "workspace". There is a security question here. javydreamercsw Can you help us understand why you needed to go outside of the "checkout" and outside of a "target" folder. 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Ok I seem to have missed it then. Could it be in jenkins itself? At the moment the name field for the container doesn't have a help text. I think it would be really useful to add it there 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-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title Oleg Nenashev updated JENKINS-49433 It has been released in 2.31.1 Jenkins / JENKINS-49433 Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration Change By: Oleg Nenashev Status: In Review Resolved 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 to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-48634) Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Title: Message Title Oleg Nenashev updated JENKINS-48634 It has been released in 2.31.1 Jenkins / JENKINS-48634 Promoted Builds plugin cannot reexecute promotion- java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Change By: Oleg Nenashev Status: In Review Resolved 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 to
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Carlos Sanchez commented on JENKINS-49511 Re: Connection fails between agent and master It's in the docs already 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-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Kseniia Nenasheva assigned an issue to Kseniia Nenasheva Jenkins / JENKINS-49520 Log rotator: empty values decorated with 'Not a positive integer' Change By: Kseniia Nenasheva Assignee: Kseniia Nenasheva 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-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Cyrille Le Clerc commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Bing Shiao yes and yes. I am thinking of "always" enabling the database behind the "PipelineGraphPublisher" as it happens to be stable (I have some test instances with 1K artifacts, 70K dependencies and 10K generated artifacts). I'll improve the config screen 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-49468) Pipeline view only able to select the top-most of the in-progress parallel nodes
Title: Message Title Christian Ciach commented on JENKINS-49468 Re: Pipeline view only able to select the top-most of the in-progress parallel nodes This issue seems to pop up again from time to time. Related issues are JENKINS-43747 and JENKINS-42312. 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-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Ulli Hafner commented on JENKINS-49508 Re: warnings-plugin aborts if unable to git-blame. The text Build step 'Console output (build log) parsing' changed build result to ABORTED seems to be from a different plugin, are you using the console parser plugin? Is there a rule defined to abort the build on a warning message? 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title
Raul Arabaolaza edited a comment on JENKINS-49263
Re: Determine minimal useful test case for running ATH for Jenkins Core
Confirmed that I have not been able to remove the flakiness of ` {{ JenkinsDatabaseSecurityRealmTest#login_and_logout ` }} in a reasonable amount of time, so my proposal is to remove it from the `SmokeTest` category, create a ticket to try to fix it properly and add it again when 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 to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Feel free to submit a PR to improve docs https://github.com/jenkinsci/kubernetes-plugin/#constraints Jenkins / JENKINS-49511 Connection fails between agent and master Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-49413 IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace Change By: Cyrille Le Clerc Summary: IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace 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-49468) Pipeline view only able to select the top-most of the in-progress parallel nodes
Title: Message Title Christian Ciach edited a comment on JENKINS-49468 Re: Pipeline view only able to select the top-most of the in-progress parallel nodes Can confirm. It should be noted that this issue is only with pipelines that are currently in progress. If the pipeline has finished, I can select and view the data of all parallel nodes just fine. [~retronym], you accidentally linked to this issue, instead of a related issue. 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-49468) Pipeline view only able to select the top-most of the in-progress parallel nodes
Title: Message Title Christian Ciach edited a comment on JENKINS-49468 Re: Pipeline view only able to select the top-most of the in-progress parallel nodes This issue seems to pop up again from time to time. Related issues are - JENKINS-43747 - and - JENKINS-42312 - . Edit: Seems to be fixed alread: JENKINS-49272 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-49263) Determine minimal useful test case for running ATH for Jenkins Core
Title: Message Title Raul Arabaolaza updated JENKINS-49263 Jenkins / JENKINS-49263 Determine minimal useful test case for running ATH for Jenkins Core Change By: Raul Arabaolaza Status: In Progress Review 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-49476) Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS)
Title: Message Title Iosif Bancioiu commented on JENKINS-49476 Re: Jenkins Error Code 7 on KDE Neon (Ubuntu 16.04LTS) Oleg Nenashev I only managed to get is started using /usr/bin/java -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 But using jenkins service, it won't start. I don't see any -ex flags for the service. I also posted the question on stackoverflow, you can take a look also there for details https://stackoverflow.com/questions/48703458/jenkins-not-starting-on-kde-neon 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-40536) Show question answered on build approvals
Title: Message Title Steven Visagie updated an issue Jenkins / JENKINS-40536 Show question answered on build approvals Change By: Steven Visagie Attachment: jenkins view.PNG 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-49531) Docker ps command output is empty when adding a command to the image.run() section
Title: Message Title
Maksim Gerasimenko created an issue
Jenkins / JENKINS-49531
Docker ps command output is empty when adding a command to the image.run() section
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2018-02-13 15:03
Environment:
Windows 10 x64; Docker client/server version: 17.12.0-ce; Docker plugin: 1.1.2; Docker pipeline: 1.15; Jenkins version: 2.0.50727
Priority:
Major
Reporter:
Maksim Gerasimenko
Scenario 1: I try to run the Selenoid image via Jenkinsfile with the following command:
stage('Start services') {
docker.image('aerokube/selenoid').
run('--name selenoid ' +
'-p : ' +
'-v C:/workspace/selenoid:/etc/selenoid ' +
'-v C:/workspace/output:/opt/selenoid/video ' +
'-v //var/run/docker.sock:/var/run/docker.sock ' +
'-e "OVERRIDE_VIDEO_OUTPUT_DIR=/C/workspace/output/"',
'-video-output-dir /output')
}
After the completion of this code and run the
docker ps
I don't see any information related to the selenoid. When I try to run this command from my PC
[JIRA] (JENKINS-49442) Builds hanging on htmlpublisher
Title: Message Title Derek Kinney commented on JENKINS-49442 Re: Builds hanging on htmlpublisher Still happening in 2.106 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-46902) Double Byte Order Mark - UTF8
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Not able to reproduce double BOM on Windows. Windows Unicode Perforce server 17.2 Windows Jenkins 2.89.3 P4-plugin 1.8.5 P4CHARSET UTF8 Korean text file added as type utf8 with BOM Jenkins / JENKINS-46902 Double Byte Order Mark - UTF8 Change By: Paul Allen Status: Open Closed Assignee: Paul Allen Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-40536) Show question answered on build approvals
Title: Message Title Steven Visagie updated an issue Jenkins / JENKINS-40536 Show question answered on build approvals Change By: Steven Visagie Attachment: pipeline view.PNG 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-49278) cat command in docker agents not detected correctly
Title: Message Title Benjamin Heilbrunn commented on JENKINS-49278 Re: cat command in docker agents not detected correctly Nicolas De Loof, thanks for the quick 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-49385) containers exit early in docker-workflow 1.15
Title: Message Title Nicolas De Loof resolved as Fixed Jenkins / JENKINS-49385 containers exit early in docker-workflow 1.15 Change By: Nicolas De Loof Status: Open Resolved 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 to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40536) Show question answered on build approvals
Title: Message Title
Steven Visagie commented on JENKINS-40536
Re: Show question answered on build approvals
Not sure if this is resolved by the stage description. We're using a scripted pipeline with the stages similar to the following:
node {
stage ("test") {
input(message: "Proceed?")
}
}
We get this in Blue Ocean But this is in the Jenkins run view:Is there any way to get the stage description into the Jenkins view e.g. "Stage 'test' was approved by ..."
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-49528) Peformance graphs for individual tests are not created when a single test has failed
Title: Message Title Eugene Schava commented on JENKINS-49528 Re: Peformance graphs for individual tests are not created when a single test has failed Sorry, I need more details Is your issue related to multiple XML files only? I usually use only one XML report file and cannot confirm that some chart differs if there is no or only one failed test 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-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Tim Pierce created an issue Jenkins / JENKINS-49532 autogenerated keystore should not be kept in temp directory Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2018-02-13 16:31 Environment: SAML-plugin 1.0.5 Priority: Minor Reporter: Tim Pierce The SAML plugin automatically generates a keystore in /tmp (when it has not been manually configured otherwise). However, /tmp files are subject to garbage collection; if the keystore is subsequently deleted by a cleanup process (e.g. tmpwatch, systemd-tmpfiles-clean, etc), it will break SAML authentication and require a restart of the Jenkins process. Being able to specify a path or directory for where to create the autogenerated keystore would solve this problem. The existing mechanism for specifying a keystore requires configuring the plugin manually with a key password and keystore password. We deploy and manage a fleet of Jenkins instances via Ansible and are limited to configuration options that can be scripted. The automatically generated keystore would be a satisfactory solution if it were not subject to garbage collection.
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof resolved as Fixed
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Nicolas De Loof
Status:
Reopened Resolved
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 to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49528) Peformance graphs for individual tests are not created when a single test has failed
Title: Message Title Tobias Lingemann commented on JENKINS-49528 Re: Peformance graphs for individual tests are not created when a single test has failed I don't believe it is related to the number of XML files. I took a look at the source code and while I'm not sure, I believe the problem is in TestDetails.java. The graph for execution time, compile time and performance is only created when the result of the abstract build is success. if (!abstractBuild.isBuilding() && abstractBuild.getResult().isBetterOrEqualTo(Result.SUCCESS)) Curiously the graph for custom metrics is created if the build is unstable or better. I have updated my tests to use a custom metric in the meantime. I will check tomorrow if it worked. 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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Please don't re-open this issue, regression has been caught already and addressed in JENKINS-49278
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-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title Vivek Pandey assigned an issue to Sam Van Oort Jenkins / JENKINS-43995 Individual Pipeline steps and stages/blocks should have Result statuses Change By: Vivek Pandey Assignee: Sam Van Oort 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-49530) Declarative pipeline: 'agent any' doesn't honour node restriction
Title: Message Title Marian Stranecky created an issue Jenkins / JENKINS-49530 Declarative pipeline: 'agent any' doesn't honour node restriction Issue Type: Bug Assignee: Unassigned Attachments: jenkins_plugins_2018_02_13.txt Components: pipeline Created: 2018-02-13 14:49 Environment: CentOS 7.4 Jenkins 2.106 (http://pkg.jenkins.io/redhat) for installed plugins - see the attachment master (no executor) + node A + node B, where node B has been set with "only build jobs with label expressions matching this node" and labels Priority: Major Reporter: Marian Stranecky I have a multibranch pipeline with a stage having 'agent any' statement. The pipeline job ended up being blocked with node-B is reserved for jobs with matching label _expression_ despite the fact that: it should not be run on this node at all (as the node should be restricted by using a label) node-a had idle executors Expected behaviour: The job should be queued to any node, except those which have "only build jobs with label expressions matching this node", considering the job doesn't match the label criteria
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nik Reiman commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Ditto here, 1.15 has caused a bunch of our container-related builds to fail. Looking at the diff of https://github.com/jenkinsci/docker-workflow-plugin/pull/116/files, it seems that the "detection" is looking for `cat` commands, which we are not using within `docker.image.inside`. Sadly the `–entrypoint ""` workaround also does not work in our case and we have reverted to 1.14 for now. Is there another JIRA issue already to track this regression, or should this one be re-opened?
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-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49532 Re: autogenerated keystore should not be kept in temp directory as a workaround you can change the temporal folder with `java.io.tmpdir` java property, but probably this file should be created into the JENKINS_HOME folder 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-49533) Problems using project-inheritance-plugin
Title: Message Title Heiko Nardmann created an issue Jenkins / JENKINS-49533 Problems using project-inheritance-plugin Issue Type: Bug Assignee: Unassigned Components: p4-plugin, project-inheritance-plugin Created: 2018-02-13 16:51 Environment: Jenkins v2.61, p4 v1.6.2, project-inheritance-plugin v2.0.0 Priority: Major Reporter: Heiko Nardmann I just gave it a try: I've setup a base class job using project-inheritance-plugin. Inside I've specified a Perforce repo based on a stream. The initial saving has been successfull. Problem is when trying to change the base class now: I cannot 'Save' the settings if the P4 plugin reports a problem, e.g. 1) 'Not currently connected to a Perforce server' 2) 'Stream name shouldn't null or empty.' and so on ... Always a nasty dialog with that warning/error message blocks saving the settings. Based on the description of the inheritance plugin this is intentional. Not being connected to a Perforce server should not raise an error here? Not sure how to solve resp. who resp. which plugin?
[JIRA] (JENKINS-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Ivan Fernandez Calvo updated JENKINS-49532 Jenkins / JENKINS-49532 autogenerated keystore should not be kept in temp directory Change By: Ivan Fernandez Calvo Status: In Progress Review 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.
