[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Ali Narenji commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines We have the same problem on Jenkins 2.138.2. Is there any time estimation for resolving the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen commented on JENKINS-54225 Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace I can confirm that adding deleteDirs solved the issue of the partial delete. As workaround on Windows we use `rm -rf` from MinGW, it looks that we have some files in the workspace which are still in use in some builds, rm can remove them without problems, with get the error below, is there a forced delete options (... is a full path) ERROR: Cannot delete workspace :Unable to delete '...ACE_ETCL_Parserd.dll’. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. Error when executing always post condition: hudson.AbortException: Cannot delete workspace: Unable to delete '...\ACE_ETCL_Parserd.dll’. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at hudson.plugins.ws_cleanup.WsCleanup.perform(WsCleanup.java:244) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55965) Build data could not be found for git SCM
Title: Message Title Jovica Zaric commented on JENKINS-55965 Re: Build data could not be found for git SCM Confirming andy o findings. Don't have the option to downgrade to 3.9 (without digging further). But after downgrade to git 3.7.4 build status started working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56017) Getting error "unrecognized option --httpsPort", while configuring jenkins(2.150.2) but it was working as expected in the older versions
Title: Message Title Shahid Sameer created an issue Jenkins / JENKINS-56017 Getting error "unrecognized option --httpsPort", while configuring jenkins(2.150.2) but it was working as expected in the older versions Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-02-07 07:25 Priority: Critical Reporter: Shahid Sameer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56016) Input Submitter parameter ignored
Title: Message Title
Adrian Wyssmann updated an issue
Jenkins / JENKINS-56016
Input Submitter parameter ignored
Change By:
Adrian Wyssmann
I use the following snippet in my DSL pipeline {code:java}operators = "ldapUserGroup"ChoiceParameterDefinition choice = new ChoiceParameterDefinition('continue', ['YES'] as String[], 'Description')returnValue = input message: 'DEPLOY ?', parameters: [choice], submitter: operators, submitterParameter: 'approver'{code}I am not part of the {{ldapUserGroup}} thus I would expect the pipeline not to continue. However the pipeline continues anyway. {code:java}07:39:05 Approved by Surname Lastname[Pipeline] }{code} The same happens if i use a particular userID or list of userIDs rather than an ldapGroup{code:java}operators = "userID0001,userID0002"ChoiceParameterDefinition choice = new ChoiceParameterDefinition('continue', ['YES'] as String[], 'Description')returnValue = input message: 'DEPLOY ?', parameters: [choice], submitter: operators, submitterParameter: 'approver'{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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,
[JIRA] (JENKINS-56016) Input Submitter parameter ignored
Title: Message Title
Adrian Wyssmann created an issue
Jenkins / JENKINS-56016
Input Submitter parameter ignored
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-input-step-plugin
Created:
2019-02-07 06:56
Environment:
Jenkins 2.151.0 Pipeline Input Step: 2.9
Priority:
Major
Reporter:
Adrian Wyssmann
I use the following snippet in my DSL pipeline
operators = "ldapUserGroup"
ChoiceParameterDefinition choice = new ChoiceParameterDefinition('continue', ['YES'] as String[], 'Description')
returnValue = input message: 'DEPLOY ?',
parameters: [choice],
submitter: operators,
submitterParameter: 'approver'
I am not part of the ldapUserGroup thus I would expect the pipeline not to continue. However the pipeline continues anyway.
07:39:05 Approved by Surname Lastname
[Pipeline] }
The same happens if i use a particular userID or list of userIDs rather than an ldapGroup
operators = "userID0001,userID0002"
ChoiceParamete
[JIRA] (JENKINS-55953) JCasC compability with RocketChat Notifier Plugin
Title: Message Title Martin Reinhardt commented on JENKINS-55953 Re: JCasC compability with RocketChat Notifier Plugin have to look after it, but currently don't have much time for this and never uses JCasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56015) Requires capabilities : [CAPABILITY_AUTO_EXPAND]
Title: Message Title Suleman Khan created an issue Jenkins / JENKINS-56015 Requires capabilities : [CAPABILITY_AUTO_EXPAND] Issue Type: Bug Assignee: LambdaTest Automation Attachments: Requires capabilities.JPG Components: lambdatest-automation-plugin Created: 2019-02-07 06:23 Labels: jenkins lambda deployment Priority: Major Reporter: Suleman Khan I'm trying to deploy lambda function using AWS Lambda plugin. But, when it tries to create cloudformation, it gives "Requires capabilities : [CAPABILITY_AUTO_EXPAND]" error Add Comment
[JIRA] (JENKINS-54900) Concurrency issues in Role Strategy REST API
Title: Message Title runze xia updated JENKINS-54900 https://github.com/jenkinsci/role-strategy-plugin/pull/48 Jenkins / JENKINS-54900 Concurrency issues in Role Strategy REST API Change By: runze xia Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56014) C:\Program Files\Git\bin\git.exe read-tree -mu HEAD" returned status code 128: stdout: stderr: fatal: Not a valid object name HEAD
Title: Message Title Bismaya Kumar Biswal created an issue Jenkins / JENKINS-56014 C:\Program Files\Git\bin\git.exe read-tree -mu HEAD" returned status code 128: stdout: stderr: fatal: Not a valid object name HEAD Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, jenkinslint-plugin Created: 2019-02-07 05:46 Environment: production Priority: Blocker Reporter: Bismaya Kumar Biswal [EnvInject] - Loading node environment variables. Building remotely on test_node3 (test windows emma cc) in workspace D:\Hudson_Slaves\slave_test_node3\workspace\cfets_db Cloning the remote Git repository Using no checkout clone with sparse checkout. Cloning repository g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git > C:\Program Files\Git\bin\git.exe init D:\Hudson_Slaves\slave_test_node3\workspace\cfets_db\postgres # timeout=10 Fetching upstream changes from g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git > C:\Program Files\Git\bin\git.exe --version # timeout=10 using GIT_SSH to set credentials > C:\Program Files\Git\bin\git.exe fetch --tags --progress g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git +refs/heads/:refs/remotes/origin/ > C:\Program Files\Git\bin\git.exe config remote.origin.url g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git # timeout=10 > C:\Program Files\Git\bin\git.exe config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > C:\Program Files\Git\bin\git.exe config remote.origin.url g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git # timeout=10 Fetching upstream changes from g...@git.sami.int.thomsonreuters.com:TRDA-Development/database.git using GIT_SSH to set credentials > C:\Program Files\Git\bin\git.exe fetch --tags --progress g...@git
[JIRA] (JENKINS-56013) Jenkins LTS shows prerelease plugins
Title: Message Title Michael Kriese updated an issue Jenkins / JENKINS-56013 Jenkins LTS shows prerelease plugins Change By: Michael Kriese Component/s: git-client-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56013) Jenkins LTS shows prerelease plugins
Title: Message Title Michael Kriese created an issue Jenkins / JENKINS-56013 Jenkins LTS shows prerelease plugins Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-02-07 05:42 Environment: Jenkins ver. 2.150.2 http://updates.jenkins-ci.org/update-center.json Priority: Critical Reporter: Michael Kriese The update center is showing the following plugins with a prerelease version Git 4.0.0-rc Git client 3.0.0-rc I think there should no prerelease be visible. At least for the Jenkins LTS release. Add Comment
[JIRA] (JENKINS-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita updated JENKINS-48488 Just released 3.16 with the change. Also updated the plugin Wiki. Thanks! Jenkins / JENKINS-48488 Request to make Testcase version available in Jenkins Build environment Change By: Bruno P. Kinoshita Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55736) Support proxy logins
Title: Message Title Fernando Boaglio commented on JENKINS-55736 Re: Support proxy logins Have you tried to use proxyuser[proxieduser] in username field ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title loongle tse commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Now I can only roll back the whole package to work properly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title loongle tse commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError I've hit the same issue, the latest version of Jenkins + all plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56012) stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters
Title: Message Title Pavel Roskin created an issue Jenkins / JENKINS-56012 stash-pullrequest-builder-plugin variables not seen in multi-configuration jobs unless listed in safeParameters Issue Type: Bug Assignee: Jakub Bochenski Components: stash-pullrequest-builder-plugin Created: 2019-02-07 03:05 Environment: Jenkins 2.150.2. stash-pullrequest-builder-plugin built locally from current git (6115a02e9c081b6ee02325d93608e89bf78be93a) Labels: stash multi-configuration variable Priority: Minor Reporter: Pavel Roskin stash-pullrequest-builder-plugin defines 10 variables, such as `sourceCommitHash`. Those variables are not available in multi-configuration jobs apart from the top-level process. Those variable can be made available to the jobs by listing them in hudson.model.ParametersAction.safeParameters on the java command line. That's a workaround for SECURITY-170 that is no longer needed for free-style jobs. Even with that workaround, Jenkins spams logs with messages like this: WARNING: Skipped parameter `sourceCommitHash` as it is undefined on `TestRepository_pull_request_builder`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters=true` to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even though it represents a security breach or `-Dhudson.model.ParametersAction.keepUndefinedParameters=false` to no long
[JIRA] (JENKINS-56011) UI fails to set ECS Task Creation Timeout
Title: Message Title Michael Ward updated an issue Jenkins / JENKINS-56011 UI fails to set ECS Task Creation Timeout Change By: Michael Ward Attempting to set the ECS task timeout through the Jenkins web interface fails. This appears to be due to the typo correction for slaveTimoutInSeconds not being performed in [https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/plugins/amazonecs/ECSCloud/config.jelly] As a result, it's still trying to set slaveTimoutInSeconds instead of slaveTimeoutInSeconds. Similarly, it doesn't display the current value due to the same issue. This is using version 1.19 of the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56011) UI fails to set ECS Task Creation Timeout
Title: Message Title Michael Ward created an issue Jenkins / JENKINS-56011 UI fails to set ECS Task Creation Timeout Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2019-02-07 00:38 Priority: Minor Reporter: Michael Ward Attempting to set the ECS task timeout through the Jenkins web interface fails. This appears to be due to the typo correction for slaveTimoutInSeconds not being performed in https://github.com/jenkinsci/amazon-ecs-plugin/blob/master/src/main/resources/com/cloudbees/jenkins/plugins/amazonecs/ECSCloud/config.jelly As a result, it's still trying to set slaveTimoutInSeconds instead of slaveTimeoutInSeconds. Similarly, it doesn't display the current value due to the same issue. Add Comment
[JIRA] (JENKINS-41173) Rundeck logging with Jenkins tailing
Title: Message Title Greg Schueler commented on JENKINS-41173 Re: Rundeck logging with Jenkins tailing https://github.com/jenkinsci/rundeck-plugin/pull/34 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-41173) Rundeck logging with Jenkins tailing
Title: Message Title Greg Schueler resolved as Fixed Jenkins / JENKINS-41173 Rundeck logging with Jenkins tailing Change By: Greg Schueler Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56010) Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin
Title: Message Title R W created an issue Jenkins / JENKINS-56010 Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-02-07 00:13 Priority: Major Reporter: R W After upgrade from 3.9.2 to 4.0.0-rc, git tag message plugin is not creating GIT_TAG_NAME env anymore. From build logs, I can also see, that 4.0 does not: > git tag -l ... -n1 anymore. Sounds related. Rolling back to 3.9.2 fixes the issue. Add Comment This messa
[JIRA] (JENKINS-34510) Very long Jenkins startup time with a vast number of Rundeck jobs
Title: Message Title Greg Schueler resolved as Fixed Jenkins / JENKINS-34510 Very long Jenkins startup time with a vast number of Rundeck jobs Change By: Greg Schueler Status: Open Resolved Assignee: Vincent Behar Greg Schueler Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50643) Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files
Title: Message Title Olivier Lamy commented on JENKINS-50643 Re: Jira Plugin v2.4.2 leaks selectors resulting in Too Many Open Files do you still have issues with last versions of the plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56001 NG Warnings plugin pre-pending '/workspace' before agent's workspace Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: warnings-ng 2.2.0 and analysis-model 2.1.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55442) Need filter by message text
Title: Message Title Ulli Hafner updated JENKINS-55442 Jenkins / JENKINS-55442 Need filter by message text Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-17196) Add an action that allows to reset the reference build
Title: Message Title Ulli Hafner updated JENKINS-17196 Jenkins / JENKINS-17196 Add an action that allows to reset the reference build Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55730) Show absolute/relative path for source files
Title: Message Title Ulli Hafner updated JENKINS-55730 Jenkins / JENKINS-55730 Show absolute/relative path for source files Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51439) Make package/namespace detection configurable
Title: Message Title Ulli Hafner updated JENKINS-51439 Jenkins / JENKINS-51439 Make package/namespace detection configurable Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55679) XML source files not displayed in warnings-ng
Title: Message Title Ulli Hafner updated JENKINS-55679 Jenkins / JENKINS-55679 XML source files not displayed in warnings-ng Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51438) Add support for filtering by path
Title: Message Title Ulli Hafner updated JENKINS-51438 Jenkins / JENKINS-51438 Add support for filtering by path Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-51267) Detection of path names does not work
Title: Message Title Ulli Hafner updated JENKINS-51267 Jenkins / JENKINS-51267 Detection of path names does not work Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-22526) Health threshold rebaseline command
Title: Message Title Ulli Hafner updated JENKINS-22526 Jenkins / JENKINS-22526 Health threshold rebaseline command Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55805) Warnings Next Generation Plugin is slow at parsing the log output
Title: Message Title Ulli Hafner updated JENKINS-55805 Jenkins / JENKINS-55805 Warnings Next Generation Plugin is slow at parsing the log output Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55846) No issues found when parsing Error-Prone output from console log during gradle build
Title: Message Title Ulli Hafner updated JENKINS-55846 Jenkins / JENKINS-55846 No issues found when parsing Error-Prone output from console log during gradle build Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Ulli Hafner updated JENKINS-55873 Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55839) Introduce a view ordered by folders besides files, tools, categories, etc.
Title: Message Title Ulli Hafner updated JENKINS-55839 Jenkins / JENKINS-55839 Introduce a view ordered by folders besides files, tools, categories, etc. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55775) Warning reports does not show absolute file path.
Title: Message Title Ulli Hafner updated JENKINS-55775 Jenkins / JENKINS-55775 Warning reports does not show absolute file path. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55715) TagList parser should present files as file names, not classes.
Title: Message Title Ulli Hafner updated JENKINS-55715 Jenkins / JENKINS-55715 TagList parser should present files as file names, not classes. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.2.0 (and analysis model 2.1.1) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56007) warnings-ng does not create file-with-issues folder when running on a slave
Title: Message Title Ulli Hafner commented on JENKINS-56007 Re: warnings-ng does not create file-with-issues folder when running on a slave In the upcoming 2.2.0 release I moved the creating of the folder to a previous part of the code. Maybe that helps. If not, I also improved the logging statements. Please try the new version and report back if this is working now... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55694) Log audit events for user property changes
Title: Message Title David Olorundare assigned an issue to Unassigned Jenkins / JENKINS-55694 Log audit events for user property changes Change By: David Olorundare Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title Steve Johnson commented on JENKINS-56006 Re: Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml". Found an easy work-around for this problem. The following pre-build step avoids the problem: ln -sf pom_fetcherproxy.xml pom.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55694) Log audit events for user property changes
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55694 Log audit events for user property changes Change By: David Olorundare - Log the audit events generated by various Jenkins user credential property changes, such as: - password updates (updatePassword), and - key API Key updates (createKey, deleteKey) , and - credential updates (createCredentials, deleteCredentials) - Implement appropriate unit-tests for each category of changes property change . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56009) Log audit events for user credentials
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-56009 Log audit events for user credentials Issue Type: Task Assignee: Unassigned Components: audit-log-plugin Created: 2019-02-06 23:18 Labels: audit-logging Priority: Minor Reporter: David Olorundare Log the audit events generated by various Jenkins user credential changes, such as: - creation of credentials (createCredentials) - update of credentials (updateCredentials) - deletion of credentials (deleteCredentials) Implement appropriate unit-tests for each category of changes. Add Comment
[JIRA] (JENKINS-55694) Log audit events for user property changes
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-55694 Log audit events for user property changes Change By: David Olorundare Summary: Log audit events for user credentials property changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55694) Log audit events for user credentials
Title: Message Title David Olorundare stopped work on JENKINS-55694 Change By: David Olorundare Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener
Title: Message Title David Olorundare assigned an issue to David Olorundare Jenkins / JENKINS-56008 Update HudsonPrivateSecurityRealm.Details use of SecurityListener Change By: David Olorundare Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener
Title: Message Title David Olorundare started work on JENKINS-56008 Change By: David Olorundare Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56008) Update HudsonPrivateSecurityRealm.Details use of SecurityListener
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-56008 Update HudsonPrivateSecurityRealm.Details use of SecurityListener Issue Type: Task Assignee: Unassigned Components: audit-log-plugin Created: 2019-02-06 23:13 Labels: audit-logging Priority: Minor Reporter: David Olorundare Related to JENKINS-55694 Update the newInstance() method within the Details class of HudsonPrivateSecurityRealm; to make use of the user-property-change listener method of the SecurityListener class. The Details class specifically handles the update of user-password changes made from the Jenkins UI in a user's configuration page. To perform this update will require modifying the HudsonPrivateSecurityRealm.Details class within the jenkins-core hudson/security package. Unit tests for the updated HudsonPrivateSecurityRealm.Details class method should be implemented, to verify its correctness, and should be added to the preexisting Jenkins unit tests for the HudsonPrivateSecurityRealm.Details class. The SecurityListener class method related to listening for user-property-change events was added in --JENKINS-56005
[JIRA] (JENKINS-56007) warnings-ng does not create file-with-issues folder when running on a slave
Title: Message Title Mark Dulfer created an issue Jenkins / JENKINS-56007 warnings-ng does not create file-with-issues folder when running on a slave Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-06 23:01 Environment: Jenkins: 2.150.1 warnings-ng: 2.1.2 Jenkins Master: Windows Server 2012R2, jre 1.8.0_181 Jenkins Slave: Windows Server 2012R2, jre 1.8.0_181 Slave and Master both run as a Windows service under the same domain account with local admin rights Priority: Minor Reporter: Mark Dulfer Running the warnings-ng plugin in a pipeline job on a slave, the output is parsed correctly and generates report otuput as expected, but errors are generated because the files-with-issues folder is not created on the master. Other than suspect files not being copied to this folder, the rest of the plugin processes appear to run just fine. The pipeline step is recordIssues tools: [msBuild()] Log output from Jenkins is: [Pipeline] recordIssues Skipping issues blame since Git is the only supported SCM up to now. [MSBuild] Sleeping for 5 seconds due to JENKINS-32191... [MSBuild] Parsing console log (workspace: 'D:\caProjects\workspace\MyProject\eptest') [MSBuild] [ERROR] Can't copy some affected workspace files to Jenkins build folder: [MSBuild] [ERROR] - 'D:/caProjects/workspace/MyProject/eptest/MyProject.WebService/Startup.cs', IO exception has been thrown: java.io.IOException: Can't create directory for workspace files that contain issues: files-with-issues ...I have removed an additional 19 errors identical to above except for filename [MSBuild] [ERROR] ... skipped logging of 23 additional errors ... [MSBuild] Post processing issues on 'MyProject' with encoding 'windows-1252' [MSBuild] Resolving absolute file names for all issues [
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM pom file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM pom (those are the same in this case).Is this a known NO NO in Jenkins? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM pom file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.To be clear, here's how I'm specifying the pom file name:!https://files.gitter.im/jenkinsci/jenkins/pDOr/th
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM pom file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM pom (those are the same in this case).Is this a known NO NO in Jenkins? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM pom file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.To be clear, here's how I'm specifying the pom file name:!https://files.gitter.im/jenkinsci/jenkins/pDOr/th
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM pom file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM pom (those are the same in this case).Is this a known NO NO in Jenkins? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM pom file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.To be clear, here's how I'm specifying the pom file name:!https://files.gitter.im/jenkinsci/jenkins/pDOr/th
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM (those are the same in this case).Is this a known NO NO in Jenkins : ? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.To be clear, here's how I'm specifying the pom file name:!https://files.gitter.im/jenkinsci/jenkins/pDOr/thumb/image.png!
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM (those are the same in this case).Is this a known NO NO in Jenkins:? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.BTW, to be clear, here's how I'm specifying the pom file name (hope this image sticks) :!https://files.gitter.im/jenkinsci/jen
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM (those are the same in this case).Is this a known NO NO in Jenkins:? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine. BTW, to To be clear, here's how I'm specifying the pom file name:!https://files.gitter.im/jenkinsci/jenkins/pDOr/thumb/image.
[JIRA] (JENKINS-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title
Steve Johnson updated an issue
Jenkins / JENKINS-56006
Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Change By:
Steve Johnson
Jenkins version: [Jenkins ver. 2.150.2|https://jenkins.io/] via current Docker LTS releaseI have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know.When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: {code:java}[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom[JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jarERROR: Failed to parse POMsjava.nio.file.NoSuchFileException: /var/jenkins_home/workspace/deploy_fetcherproxy/pom.xmlat sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107){code} In this case, the pom file I specified is /var/jenkins_home/workspace/pom_fetcherproxy.xml. If I add a symlink "pom.xml -> pom_fetcherproxy.xml" to the root of my source tree and specify my pom name to be either "pom_fetcherproxy.xml" or "pom.xml" (or leave that field blank), then the build works fine. It seems evident that Jenkins is at some point forgetting my custom POM file name and is instead looking for the standard "pom.xml" file either at the root of the source tree or in the same location as my specified POM (those are the same in this case). Is this a known NO NO in Jenkins:? If it is, then it's at least a bug in that the field that accepts the "Root POM" should not allow specification of the POM file name, but only the directory containing a "pom.xml" file, and should be clearer about what can go there. The help text attached to that field might be saying that the name has to be "pom.xml", but it isn't very clear. Also, I expect that this behavior is unexpected or undesirable given that Jenkins makes it most of the way through as though specifying a non-standard pom file name is just fine.BTW, to be clear, here's how I'm specifying the pom file name (hope this image sticks):!https://files.gitter.im/jenkinsci/j
[JIRA] (JENKINS-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Wisen Tanasa commented on JENKINS-55859 Re: jira-trigger-plugin not triggering build after creating issue Sounds good. The last time I check, when an issue is created, issue_updated event will be fired from Jira as well Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Dan O'Brien yes your message is basically the same as that originally reported here; the same fix would cover both. See my comments of 2018-11-01. There is no workaround beyond ignoring the warnings. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56006) Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml".
Title: Message Title Steve Johnson created an issue Jenkins / JENKINS-56006 Jenkins breaks when you specify a Maven root pom file with a name other than "pom.xml". Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-02-06 22:43 Environment: Docker, standard Jenkins container image Priority: Major Reporter: Steve Johnson Jenkins version: Jenkins ver. 2.150.2 via current Docker LTS release I have multiple aggregate pom files at the root of my source tree to allow different subsets of the whole tree to be built. They have names like "pom_foo.xml" and "pom_bar.xml". For development, we often create a symlink named "pom.xml" pointing to one of these to avoid having to specify the pom file name when running Maven. This is a standard Maven practice as far as I know. When I attempt to have Jenkins build my project by specifying one of these specific pom file names in the Build->Root Pom configuration field in Jenkins, the build almost succeeds. Jenkins causes Maven to successfully build my source tree. But then, at the end of the build, I get this: [JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/poms/pom.xml to org.springframework.boot/poms/2.1.1.RELEASE/poms-2.1.1.RELEASE.pom [JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/pom.xml to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.pom [JENKINS] Archiving /var/jenkins_home/workspace/deploy_fetcherproxy/common/common-jutil/target/common-jutil-1.0-SNAPSHOT.jar to com.inlet/common-jutil/1.0-SNAPSHOT/common-jutil-1.0-SNAPSHOT.jar ERROR: Failed to pa
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref This is the preferred style:!https://user-images.githubusercontent.com/2119212/51774426-47af6f00-20c0-11e9-8f58-ce82bd17dee4.png!As opposed to:!https://user-images.githubusercontent.com/2119212/51774439-539b3100-20c0-11e9-9c96-6569a173d80c.png!or !https://user-images.githubusercontent.com/2119212/51774473-6f9ed280-20c0-11e9-922c-42ea7ddedd34.png! -- – I'm going to point to this issue for a bunch of plugins. Note: my initial efforts relied on using optionalBlock instead of entry+checkbox. Unfortunately this interacts poorly w/ the form submission magic, and so rather than continue down that path, I'm switching to moving fields from the entry to the checkbox. The rendering won't generally change from the examples above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56005) Add user property change listener method to SecurityListener
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-56005 Add user property change listener method to SecurityListener Change By: David Olorundare Related to JENKINS-55694Project tasks that involve logging of audit events such as Jenkins User property changes (e.g. password updates) and APIKey changes (e.g. createKey, updateKey, deleteKey) require the existence of a listener method that notifies subscribers on occurrence of these events. * This new listener method is implemented as a SecurityListener class method. * Corresponding unit tests which exercise this method must be added to the existing unit tests for the HudsonPrivateSecurityRealm class. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56005) Add user property change listener method to SecurityListener
Title: Message Title David Olorundare updated an issue Jenkins / JENKINS-56005 Add user property change listener method to SecurityListener Change By: David Olorundare Labels: audit-logging Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56005) Add user property change listener method to SecurityListener
Title: Message Title David Olorundare started work on JENKINS-56005 Change By: David Olorundare Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55787) Switch labels from entry to checkbox
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch labels from entry to checkbox Change By: Josh Soref Summary: Switch labels from entry to optional block checkbox Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56005) Add user property change listener method to SecurityListener
Title: Message Title David Olorundare created an issue Jenkins / JENKINS-56005 Add user property change listener method to SecurityListener Issue Type: Task Assignee: Unassigned Components: audit-log-plugin Created: 2019-02-06 22:25 Priority: Minor Reporter: David Olorundare Related to JENKINS-55694 Project tasks that involve logging of audit events such as Jenkins User property changes (e.g. password updates) and APIKey changes (e.g. createKey, updateKey, deleteKey) require the existence of a listener method that notifies subscribers on occurrence of these events. This new listener method is implemented as a SecurityListener class method. Corresponding unit tests which exercise this method must be added to the existing unit tests for the HudsonPrivateSecurityRealm class. Add Comment
[JIRA] (JENKINS-56000) Pipeline fails if more than 250 parameters specified
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-56000 Pipeline fails if more than 250 parameters specified Groovy limitation in list literals. In Scripted you could work around that by using a loop or similar constructions. Change By: Jesse Glick Component/s: pipeline-model-definition-plugin Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56005) Add user property change listener method to SecurityListener
Title: Message Title David Olorundare assigned an issue to David Olorundare Jenkins / JENKINS-56005 Add user property change listener method to SecurityListener Change By: David Olorundare Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace I think I found the problem. Since your master is running Linux and the console log is scanned on the master, the path C:\something is not interpreted as absolute Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55106) Build stuck on final "exit 0"
Title: Message Title Shawn Baker commented on JENKINS-55106 Re: Build stuck on final "exit 0" I can also confirmed this on Windows Server 2012 R2, JDK 8 on Jenkins 2.150.2. After the Build portion of the configuration has completed, there is a 10 minute delay before the Post-build Actions begin. I reverted back to 2.138.4. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56004) Overall/Administrator required to view s3 artifacts?
Title: Message Title Peter Salvatore created an issue Jenkins / JENKINS-56004 Overall/Administrator required to view s3 artifacts? Issue Type: Bug Assignee: Unassigned Attachments: artifacts.log Components: artifact-manager-s3-plugin Created: 2019-02-06 21:34 Environment: CloudBees Core 2.150.2.3 w/ CAP enabled artifact-manager-s3 plugin v1.1 Priority: Major Reporter: Peter Salvatore Users without Overall/Administrator are not able to view artifacts in the UI or download them. In the Jenkins log, I'm seeing the following traceback (full details in attachment): "February 6th 2019, 17:01:48.696","Feb 06, 2019 5:01:48 PM hudson.model.Run getArtifactsUpTo" "February 6th 2019, 17:01:48.696","WARNING: null" "February 6th 2019, 17:01:48.697"," at io.jenkins.plugins.artifact_manager_jclouds.JCloudsVirtualFile.run(JCloudsVirtualFile.java:328)" "February 6th 2019, 17:01:48.697","java.io.IOException: hudson.security.AccessDeniedException2: mat007 is missing the Overall/Administer permission" "February 6th 2019, 17:01:48.698"," at hudson.model.Run.getArtifactsUpTo(Run.java:1104)" "February 6th 2019, 17:01:48.698"," at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getArtifactsZipFile(AbstractRunImpl.java:278)" "February 6th 2019, 17:01:48.698"," at hudson.model.Run.getHasArtifacts(Run.java:1121)" "February 6th 2019, 17:01:48.699"," at io.jenkins.blueocean.commons.stapler.export.E
[JIRA] (JENKINS-55965) Build data could not be found for git SCM
Title: Message Title andy o edited a comment on JENKINS-55965 Re: Build data could not be found for git SCM This issue is due to the git 4.0 rc library being updated. Downgrading to git 3.9 has resolved the issue ([~scddev]) . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55998) recordIssues cannot see /workspace within docker.image.inside
Title: Message Title Ulli Hafner commented on JENKINS-55998 Re: recordIssues cannot see /workspace within docker.image.inside The absolute path is automatically resolved. Are you building with make and have some make directory logging statements? make[2]: Entering directory '/dir1/dir2/dir3' I wonder why the original workspace is shown at /var/lib/docker/builder/repo/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ, but the warnings has the prefix /workspace Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Ulli Hafner commented on JENKINS-56001 Re: NG Warnings plugin pre-pending '/workspace' before agent's workspace Seems that the path is broken: /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp, it is composed of /workspace/TinyXml/ and C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp. How does this warning look in the original log? Are you building with make and have some make directory logging statements? make[2]: Entering directory '/dir1/dir2/dir3' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29198) Console logs get truncated without reason
Title: Message Title Ryan Fenton-Garcia commented on JENKINS-29198 Re: Console logs get truncated without reason As of today am also seeing this on version 2.154 I don't see any success or failure messages. I also noticed that loading output for nodes in the blue ocean view seems to give a red console error. (I'm guessing these are somehow loaded from the log which doesn't have the info since it's truncated.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56003) Jenkins - MultipleBranch Pipeline creates too long workspace folder path
Title: Message Title Suemiao Rossignol created an issue Jenkins / JENKINS-56003 Jenkins - MultipleBranch Pipeline creates too long workspace folder path Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2019-02-06 20:43 Environment: Jenkins version - 2.150.2 Priority: Critical Reporter: Suemiao Rossignol Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop re
[JIRA] (JENKINS-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita updated JENKINS-48488 PR merged. Release pending, but will do it in some 7/8 hours. Jenkins / JENKINS-48488 Request to make Testcase version available in Jenkins Build environment Change By: Bruno P. Kinoshita Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-48488) Request to make Testcase version available in Jenkins Build environment
Title: Message Title Bruno P. Kinoshita commented on JENKINS-48488 Re: Request to make Testcase version available in Jenkins Build environment Hadn't seen that one Achim Zimmer! Sorry. Merged, will release it tonight. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56002) Upgrading Git Plugin to :latest causes Issues with SQS Plugin
Title: Message Title Justin Seiser created an issue Jenkins / JENKINS-56002 Upgrading Git Plugin to :latest causes Issues with SQS Plugin Issue Type: Bug Assignee: Mark Waite Attachments: Error.txt, Jenkins.png, noidea.png Components: git-plugin Created: 2019-02-06 20:30 Environment: Jenkins Version 2.150.2 jenkins/jenkins:lts All plugins set to latest Priority: Minor Reporter: Justin Seiser Upgraded Docker container, and it with the plugins. Started getting the attached error, and the UI for the SQS plugin broke. Reverting the git plugin, brought the UI for the SQS plugin back, and everything started flowing again. Error.txt Add Comment
[JIRA] (JENKINS-29198) Console logs get truncated without reason
Title: Message Title Ben Eng edited a comment on JENKINS-29198 Re: Console logs get truncated without reason I am seeing this exact problem today on version *2.121.3*The console output displays to the end, showing Finished: SUCCESS. The consoleText output is truncated (at 4604 lines in the case I'm looking at this moment). The consoleFull output is truncated at exactly the same line as consoleText. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29198) Console logs get truncated without reason
Title: Message Title Ben Eng edited a comment on JENKINS-29198 Re: Console logs get truncated without reason I am seeing this exact problem today on version *2.121.3* The console output displays to the end, showing Finished: SUCCESS. The consoleText output is truncated (at 4604 lines in the case I'm looking at this moment). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29198) Console logs get truncated without reason
Title: Message Title Ben Eng commented on JENKINS-29198 Re: Console logs get truncated without reason I am seeing this exact problem today on version 2.121.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50429) Shell command are really slower than before
Title: Message Title
Claes Buckwalter edited a comment on JENKINS-50429
Re: Shell command are really slower than before
[~mrjgreen], you wrote:{quote}Commenting out all the env variable setting only reduced the individual container time to 1s... This seems to tally with the stack overflow post reporting the piped input stream bug.{quote}I think you are saying that: - Removing the [environment variable code introduced in 1.2.1|https://github.com/jenkinsci/kubernetes-plugin/compare/kubernetes-1.2...jenkinsci:kubernetes-1.2.1] brings the time it takes to run a trivial {{sh}} step down to 1s. I see that change was [merged in December|https://github.com/jenkinsci/kubernetes-plugin/pull/393]. Is it in the latest plugin release? - We cannot get below 1s because of [the 1s wait in java.io.PipedInputStream|https://github.com/karianna/jdk8_tl/blob/master/jdk/src/share/classes/java/io/PipedInputStream.java#L274].Was it really ever faster than 1s to execute a {{sh}} step with the k8s plugin? I assume that for each sh step, the plugin has to do the equivalent of a "kubectl exec" to run the shell command in the container. What is the normal overhead of doing that?If we think it can be faster, then it looks like we have to [fix it in the fabric8io library|https://github.com/fabric8io/kubernetes-client/issues/1008]. This is also discussed in the [pull request mentioned above|https://github.com/jenkinsci/kubernetes-plugin/pull/393]. Does JenkinsX use the same fabric8io library for its k8s communication and does JenkinsX have the same performance bottleneck? Maybe [~jstrachan] (formerly at fabric8io, now at CloudBees) can point us in the right direction for a fix?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.c
[JIRA] (JENKINS-7004) cause not working in parameterized projects
Title: Message Title jerry wiltse commented on JENKINS-7004 Re: cause not working in parameterized projects We've done some testing and reviewed the commits, and the Cause field does not seem to be fully supported on parameterized builds. As victor maslov has said, the `cause` field does not work at all when using http auth via header or URL. The job MUST have a `token` assigned, and as Adam Monsen has said, it MUST come before the `cause` parameter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-7004) cause not working in parameterized projects
Title: Message Title jerry wiltse edited a comment on JENKINS-7004 Re: cause not working in parameterized projects We've done some testing and reviewed the commits, and the Cause field does not seem to be fully supported on parameterized builds. As [~nakilon] has said, the `cause` field does not work at all when using http auth via header or URL. The job MUST have a `token` assigned, and as [~amonsen] has said, it MUST come before the `cause` parameter. I suggest reopening this ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50429) Shell command are really slower than before
Title: Message Title Claes Buckwalter commented on JENKINS-50429 Re: Shell command are really slower than before Joseph Green, you wrote: Commenting out all the env variable setting only reduced the individual container time to 1s... This seems to tally with the stack overflow post reporting the piped input stream bug. I think you are saying that: Removing the environment variable code introduced in 1.2.1 brings the time it takes to run a trivial sh step down to 1s. We cannot get below 1s because of the 1s wait in java.io.PipedInputStream. Was it really ever faster than 1s to execute a sh step with the k8s plugin? I assume that for each sh step, the plugin has to do the equivalent of a "kubectl exec" to run the shell command in the container. What is the normal overhead of doing that? If we think it can be faster, then it looks like we have to fix it in the fabric8io library. Does JenkinsX use the same fabric8io library for its k8s communication and does JenkinsX have the same performance bottleneck? Maybe James Strachan (formerly at fabric8io, now at CloudBees) can point us in the right direction for a fix? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title
Shannon Kerr updated an issue
Jenkins / JENKINS-56001
NG Warnings plugin pre-pending '/workspace' before agent's workspace
Change By:
Shannon Kerr
(related to JENKINS-55998) We're moving from the legacy Warnings plugin to the NG plugin. For our Windows build executed on a Windows agent/slave, we're not getting to see the msbuild warnings in context on the build page. Our master is Linux and our pipeline agent node is also a Linux (Debian Stretch) node, but we execute some parallel builds on Windows agents.Here is some output from the NG Warnings info page:{code:java}Error MessagesCan't resolve absolute paths for some files:- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/ptypes/src/pstring.cxx- /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/transport/source/AddrInfo.cpp ... skipped logging of 469 additional errors ...Can't create fingerprints for some files:- '/workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp{code} {code:java} Information MessagesParsing console log (workspace: '/var/lib/docker/exacqu/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ')Post processing issues on 'DockerAgent0' with encoding 'UTF-8'Resolving absolute file names for all issues-> 0 resolved, 489 unresolved, 0 already resolvedCopying affected files to Jenkins' build folder /var/jenkins_home/jobs/Server Branch/branches/build_updates/builds/167-> 0 copied, 0 not in workspace, 489 not-found, 0 with I/O errorResolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 9210 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 489 affected filesNo filter has been set, publishing all 9210 issuesCreating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issuesSkipping blaming as requested in the job configurationNo valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE)All reported issues will be considered outstandingNo quality gates have been set - skippingHealth report is disabled - skipping{code} Here is what our build block looks like:{code:java}node (build_mach) {bat '''@echo off'''recordIssues(tools: [msBuild(id: "msbuild-$os$arch", name: "MSBuild Compiler $target")])}{code} It does appear to capture all/only [?] the
[JIRA] (JENKINS-55998) recordIssues cannot see /workspace within docker.image.inside
Title: Message Title
Shannon Kerr updated an issue
Jenkins / JENKINS-55998
recordIssues cannot see /workspace within docker.image.inside
Change By:
Shannon Kerr
(related to JENKINS-56001) I'm running multiple parallel builds. Some of these builds are run within docker containers. The code would look something like this: {code:java}docker.image("$docker_server/$docker_image-dev-$arch:$build_tag").inside("--privileged -v $docker_image-$arch-ccache:/root/.ccache") { sh '''#!/bin/bash -epushd /workspace ''' recordIssues(tools: [gcc4(id: "gcc4-$os$arch", name: "GNU C Compiler $target")])}{code}It does appear to capture all/only [?] the issues for that build within the docker container, but on the build page we are unable to see any of the issues in source context. The build happens at /workspace within the docker container instead of $WORKSPACE, so the parallel build containers may share the one $WORKSPACE. I don't think this is our issue though.It appears the console output being parsed has the actual absolute path to the source files and this location is not visible to recordIssues. Since I can't tell recordIssues to ignore /workspace and instead look for the source in $WORKSPACE, it seems I'm stuck.Example output from info screen:{code:java}Error MessagesCan't resolve absolute paths for some files:- /workspace/live555/groupsock/../../live555/transport/include/TransportMediaSession.h- /workspace/TinyXml/pixelproDevice.cpp- /workspace/live555/BasicUsageEnvironment/../shared/ipplugin.h- /workspace/TinyXml/../../live555/transport/include/StreamsockTransport.h- /opt/gtest/1.8.0/x64/include/gtest/gtest.h- /workspace/TinyXml/Services/soapC_003.cpp- /workspace/TinyXml/./source/TransportMultiFramedRTPSource.cpp- /workspace/TinyXml/tests.cpp- /workspace/TinyXml/AudioOut.h ... skipped logging of 453 additional errors ...Can't create fingerprints for some files:- '/workspace/TinyXml/../AES/aeskey.c', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/../AES/aeskey.c- '/workspace/TinyXml/../AES/aeskey.c', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/../AES/aeskey.c...{code} {code:java}Information MessagesParsing console log (workspace: '/var/lib/docker/builder/repo/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ')Post processing issues on 'DockerAgent0' with encoding 'UTF-8'Resolving absolute file names for all issues-> 0 resolved, 473 unresolved, 0 already resolvedCopying affected files to Jenkins' build folder /var/jenkins_home/jobs/Server Branch/branches/build_updates/builds/169-> 0 copied, 0 not in workspace, 473 not-found, 0 with I/O errorResolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 3061 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 473 affected filesNo filter has been set, publishing all 3061 issuesCreating fingerprints for all
[JIRA] (JENKINS-56001) NG Warnings plugin pre-pending '/workspace' before agent's workspace
Title: Message Title Shannon Kerr created an issue Jenkins / JENKINS-56001 NG Warnings plugin pre-pending '/workspace' before agent's workspace Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-06 19:37 Environment: Jenkins 2.138.1 and NG Warnings plugin 2.1.2 Priority: Major Reporter: Shannon Kerr (related to JENKINS-55998) We're moving from the legacy Warnings plugin to the NG plugin. For our Windows build executed on a Windows agent/slave, we're not getting to see the msbuild warnings in context on the build page. Our master is Linux and our pipeline agent node is also a Linux (Debian Stretch) node, but we execute some parallel builds on Windows agents. Here is some output from the NG Warnings info page: Error Messages Can't resolve absolute paths for some files: - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/liveMedia/AMRAudioFileSource.cpp - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/ptypes/src/pstring.cxx - /workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/live555/transport/source/AddrInfo.cpp ... skipped logging of 469 additional errors ... Can't create fingerprints for some files: - '/workspace/TinyXml/C:/DVR/workspace/_Branch_build_updates-SDSYGOEWO53Z6ASKV6W4GSRWQU4DXCNNDGKGTWMQJ4O7LTMGYQVQ/edvrserver/ipcam/src/DeviceStorageStatus.cpp', IO exception has been thrown: java.nio.file.NoSuchFileException: /workspace/TinyXml/C:/DVR/workspace/_
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Dan O'Brien commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults This is the only related issue I can find with workflow-cps 2.63 we're hitting: I'm happy to open a new issue if needed, but if it's related just wanted to see if there's any additional work arounds that have been found. Downgrading to 2.58 causes a range of other dependency issues. Error storing the arguments for step: checkoutError storing the arguments for step: checkoutorg.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.git.AbstractGitSCMSource$SpecificRevisionBuildChooser at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of(DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:311) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeListAndRecordMutation(ArgumentsActionImpl.java:242) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:313) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:311) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.(ArgumentsActionImpl.java:74) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:243) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor297.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:76) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$Cont
[JIRA] (JENKINS-56000) Pipeline fails if more than 250 parameters specified
Title: Message Title
Craig Rodrigues created an issue
Jenkins / JENKINS-56000
Pipeline fails if more than 250 parameters specified
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-02-06 19:24
Priority:
Minor
Reporter:
Craig Rodrigues
I created a pipeline with 419 booleanParams like this:
parameters {
booleanParam(name: 'TestOne', defaultValue: false, description: '')
booleanParam(name: 'TestTwo', defaultValue: false, description: '')
booleanParam(name: 'TestThree', defaultValue: false, description: '')
booleanParam(name: 'TestFour', defaultValue: false, description: '')
booleanParam(name: 'TestFive', defaultValue: false, description: '')
...
When I tried to build/run the pipeline, I got:
WorkflowScript: -1: List expressions can only contain up to 250 elements @ line -1, column -1.
1 error
[JIRA] (JENKINS-55999) email-ext - Content Token Reference not being set in email
Title: Message Title David Metzer created an issue Jenkins / JENKINS-55999 email-ext - Content Token Reference not being set in email Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2019-02-06 19:21 Environment: Jenkins version 2.150.2 email-ext version 2.56 Windows Server 2012 R2 Standard java.version 1.8.0_144 Labels: plugin Priority: Critical Reporter: David Metzer When a job fails an editable email notification is configured to send details as per the default system configurations. This is not happening. These email are being delivered with the tokens not being replaced and it appears they are coming through as a string or text. Sample email format being recieved: Subject: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS! Content: $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS: Check console output at $BUILD_URL to view the results. Feb 06, 2019 7:01:50 PM hudson.plugins.emailext.plugins.ContentBuilder transformText SEVERE: null java.lang.RuntimeException: Error creating extended parser class: No constructor found for class org.jenkinsci.plugins.tokenmacro.Parser$$parboiled and the given 5 arguments at org.parboiled.Parboiled.createParser(Parboiled.java:58) at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:80) at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:74) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:199) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:237) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(Conte
[JIRA] (JENKINS-55998) recordIssues cannot see /workspace within docker.image.inside
Title: Message Title Shannon Kerr commented on JENKINS-55998 Re: recordIssues cannot see /workspace within docker.image.inside It's kind of odd. Here is a snippet from the console output: include/TransportMediaSession.h:114:32: warning: 'transport::TransportMediaSubsession::m_parent' will be initialized after [-Wreorder] TransportMediaSession& m_parent; ^~~~ As you can see, there is no absolute path. I checked a different build, pre NG Warnings plugin upgrade, and I can click on the file and see the warning in context, so it must be something with the new next gen plugin. I'm glad to provide whatever info I can to help. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55998) recordIssues cannot see /workspace within docker.image.inside
Title: Message Title
Shannon Kerr created an issue
Jenkins / JENKINS-55998
recordIssues cannot see /workspace within docker.image.inside
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-02-06 19:05
Environment:
Jenkins 2.138.1 and NG Warnings plugin version 2.1.2
Priority:
Major
Reporter:
Shannon Kerr
I'm running multiple parallel builds. Some of these builds are run within docker containers. The code would look something like this:
docker.image("$docker_server/$docker_image-dev-$arch:$build_tag").inside("--privileged -v $docker_image-$arch-ccache:/root/.ccache") {
sh '''#!/bin/bash -e
pushd /workspace
'''
recordIssues(tools: [gcc4(id: "gcc4-$os$arch", name: "GNU C Compiler $target")])
}
It does appear to capture all/only [?] the issues for that build within the docker container, but on the build page we are unable to see any of the issues in source context. The build happens at /workspace within the docker container instead of $WORKSPACE, so the parallel build containers may share the one $WORKSPACE. I don't think this is our issue though. It appears the console output being parsed has the actual absolute path to the source files and this location is not visible to recordIssues. Since I can't tell recordIssues to ignore /workspace and instead look for the source in $WORKSPACE, it seems I'm stuck. Example output from info screen:
[JIRA] (JENKINS-55965) Build data could not be found for git SCM
Title: Message Title andy o commented on JENKINS-55965 Re: Build data could not be found for git SCM This issue is due to the git 4.0 rc library being updated. Downgrading to git 3.9 has resolved the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55707) Upgrade fb-contrib messages to latest version
Title: Message Title Ulli Hafner commented on JENKINS-55707 Re: Upgrade fb-contrib messages to latest version I just need to update the messages to the latest version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55707) Upgrade fb-contrib messages to latest version
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55707 Upgrade fb-contrib messages to latest version Change By: Ulli Hafner Summary: SpotBug: Unknown bug pattern Upgrade fb-contrib messages to latest version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55733) Wrong parsing of CppCheck results
Title: Message Title Ulli Hafner commented on JENKINS-55733 Re: Wrong parsing of CppCheck results Well I don't think we need the other plugin to decide what to do. The question is whether each location is a different warning or not. And from the context (without seeing the source code) it looks like different warnings of the same type. These will be shown in violations lib and in the warnings plugin as separate warnings. So the current implementation seems to be correct. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jesse Glick commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields does anyone know what other plugins / behaviours might be affected I would start with this, though I would not expect that to be an exhaustive list of affected functionality. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50429) Shell command are really slower than before
Title: Message Title Fabrice Pipart edited a comment on JENKINS-50429 Re: Shell command are really slower than before We are facing the same issue described here and we don't know exactly what to do. The issue has been discovered almost a year ago and there is still no workaround proposed. Could we, at least, raise the severity of the issue? Such a performance drop looks like a showstopper to me. I guess that the logger did comment the environment variable setting like mentioned earlier. I am afraid I will have to do the same. We need to use a version > 1.2 because of the security concerns. But can't use it because of the performance concerns. I did not have the time to dive into the technical details but could we at least propose an option to deactivate this part of the code that slows down the execution? Would it be acceptable as a PR? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
