[JIRA] (JENKINS-55721) Amazon Ec2Plugin Enhancement Request
Title: Message Title prashanth kasoju created an issue Jenkins / JENKINS-55721 Amazon Ec2Plugin Enhancement Request Issue Type: New Feature Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-22 08:22 Environment: Jenkins CloudBees 2.73.32 Labels: jenkins Priority: Minor Reporter: prashanth kasoju My Jenkins master is on Prem Machine and once all the executors are occupied on the Master, a new Slave should spin up in the AWS account, . We have succeeded doing it when the Master Jenkins and the Slave Agents both are in AWS. But now i am trying to execute it when the Master is On Prem. We have Contacted the Enterprise CloudBees Support Team regarding the same and they have suggested to use user credentials approach to connect Jenkins to EC2 and they have confirmed these is the only available approach to use the Ec2 plugin to connect Jenkins with AWS. But in Our organization we have multi factor authentication and role based authorizations to connect to AWS environment. The way we connect to AWS console is as below: we first provide our AD credentials (user/pwd) followed by the symantec VIP token, once connected we get a list of roles which we need to select in order authorize. SO could you please consider the below Requirement and enhance the functionality to include Role Based authorization.
[JIRA] (JENKINS-55704) Run jenkinsci/usage-in-plugins on JAXB usages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55704 Run jenkinsci/usage-in-plugins on JAXB usages Change By: Baptiste Mathus Labels: java11 triaged 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-55541) PCT on git plugin with JDK11 fails because of old powermock versions and xstream library dependencies
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55541 PCT on git plugin with JDK11 fails because of old powermock versions and xstream library dependencies Change By: Baptiste Mathus Labels: java11 java11-devtools-compatibility scrub triaged 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 started work on JENKINS-51267 Change By: Ulli Hafner 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-22526) Health threshold rebaseline command
Title: Message Title Ulli Hafner started work on JENKINS-22526 Change By: Ulli Hafner 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-51438) Add support for filtering by path
Title: Message Title Ulli Hafner started work on JENKINS-51438 Change By: Ulli Hafner 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-51267) Detection of path names does not work
Title: Message Title Ulli Hafner stopped work on JENKINS-51267 Change By: Ulli Hafner 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-17196) Add an action that allows to reset the reference build
Title: Message Title Ulli Hafner started work on JENKINS-17196 Change By: Ulli Hafner 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-51438) Add support for filtering by path
Title: Message Title Ulli Hafner stopped work on JENKINS-51438 Change By: Ulli Hafner 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus commented on JENKINS-53284 Re: Changing default layout for workspace and builds should not be a warning for first time startup C R we're almost there, see the updated PR. Hopefully, it should be mergeable today or so. Thanks again for your much appreciated work and your patience, sorry for the latency! 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-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM
Title: Message Title Noam Angel commented on JENKINS-55276 Re: HP ALM Plugin - when job is branched only branch appear in HP ALM uploadResultToALM(almDomain: 'SDN', almProject: 'alm_project_testing', almServerName: 'alm-server', almTestFolder: 'tempest', almTestSetFolder: env.BRANCH_NAME + '' + (env.JOB_NAME - env.BRANCH_NAME - '/'), almTimeout: '', clientType: '', credentialsId: 'e28dfgdg1fb-fb6d-4e48-a480-4532gfdh', jenkinsServerUrl: JENKINS_URL, testingFramework: 'JUnit', testingResultFile: '**/junitResult.xml', testingTool: 'tempest') 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-51454) Declarative pipeline retry operation doesn't retry when there is a timeout inside of it
Title: Message Title Nepomuk Seiler commented on JENKINS-51454 Re: Declarative pipeline retry operation doesn't retry when there is a timeout inside of it It looks like the org.jenkinsci.plugins.workflow.steps.FlowInterruptedException exception could be the cause. If the timeout directive would throw another exception, would this solve 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-55701) readProperties does not interpolate some vars
Title: Message Title
jlpinardon commented on JENKINS-55701
Re: readProperties does not interpolate some vars
It looks like interpolation is made only once, i.e. is not recursed until vars are all resolved. Let's consider : A global jenkins variable aGloblaVar initialized (on the global config) as 'rootDir' var1=${aGlobalVar}/folderPath var2=${var1}/anotherPath var1 is correctly initialized, but var2 value is '${globalVar}/folderPath' and not 'rootDir/folderPath'.
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-55701) readProperties does not interpolate some vars
Title: Message Title
jlpinardon updated an issue
Jenkins / JENKINS-55701
readProperties does not interpolate some vars
Change By:
jlpinardon
Comment:
Let's assume I have something initialized withmyVar=${instanceGlobalVar}in the property file, myVar is used as '${instanceGlobalVar}' not interpolated in the Jenkinsfile.But if I set :myVar="${instanceGlobalVar}"in an environment \{...} block, myVar has its awaited value, i.e. the one contained in "${instanceGlobalVar}.Worst is probably that this is not systematic in the property file.
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-52309) Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-52309 Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support Change By: Isa Vilacides *Acceptance criteria Run ATH over release candidate with all the 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-52309) Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-52309 Release Candidate Testing: Run ATH of Jenkins WAR with Java 11 support Change By: Isa Vilacides Labels: java11 java11-compatibility triaged 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-52052) Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11
Title: Message Title Isa Vilacides commented on JENKINS-52052 Re: Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11 Devin Nusbaum what is the status of this? We are trying to get Java11 across the line and we are not sure if this is a blocker for such an error 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-53799) ProcessTree API should support long PIDs in Java 9+
Title: Message Title Oleg Nenashev commented on JENKINS-53799 Re: ProcessTree API should support long PIDs in Java 9+ So far we didn't hit any issues with process management in tests. Although Jenkins APIs are not ideal, it does not lead to crashes in test environments and in autotests. So it is not a blocker for Java 11 GA IMO, especially after the JENKINS-46523 pacthes which will explicitly propagate 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-53799) ProcessTree API should support long PIDs in Java 9+
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-53799 ProcessTree API should support long PIDs in Java 9+ Change By: Oleg Nenashev Labels: java11 needs-details technical-debt triaged 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray created an issue Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Issue Type: Bug Assignee: Subhransubala Routray Components: ssh-credentials-plugin Created: 2019-01-22 10:25 Priority: Critical Reporter: Subhransubala Routray 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-47470) Join plugin
Title: Message Title lode leroy updated an issue Jenkins / JENKINS-47470 Join plugin Change By: lode leroy Attachment: join_exception.txt 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-47470) Join plugin
Title: Message Title lode leroy commented on JENKINS-47470 Re: Join plugin I have a similar problem since upgrading. (see attachment) 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray assigned an issue to Paul Weber Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Assignee: Subhransubala Routray Paul Weber 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-55723) Evergreen should disable the update site checking
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55723 Evergreen should disable the update site checking Issue Type: Improvement Assignee: Baptiste Mathus Components: evergreen Created: 2019-01-22 10:28 Priority: Minor Reporter: Baptiste Mathus In Sentry, we see a lot of exception around update site connection. I think Jenkins is trying to download the latest update-center.json. Acceptance criteria: The Update Manager should be disabled in Evergreen, not only hidden so that background update processes are disabled too and cannot cause noise in the logs Add Comment
[JIRA] (JENKINS-55724) join plugin no longer working since upgrade
Title: Message Title lode leroy updated an issue Jenkins / JENKINS-55724 join plugin no longer working since upgrade Change By: lode leroy Attachment: join_exception.txt 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-55724) join plugin no longer working since upgrade
Title: Message Title lode leroy created an issue Jenkins / JENKINS-55724 join plugin no longer working since upgrade Issue Type: Bug Assignee: mdonohue Attachments: join_exception.txt Components: join-plugin Created: 2019-01-22 10:30 Priority: Minor Reporter: lode leroy since upgrading to 2.161 the join plugin throws an exception for existing jobs, and cannot be used for new jobs Add Comment
[JIRA] (JENKINS-55723) Evergreen should disable the update site checking
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55723 Evergreen should disable the update site checking Change By: Baptiste Mathus In Sentry, we see a lot of exception around update site connection . (EVERGREEN-EC) I think Jenkins is trying to download the latest update-center.json. h3. Acceptance criteria:* The Update Manager should be disabled in Evergreen, not only hidden so that background update processes are disabled too and cannot cause noise in the logs 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-54452) Allow a user to install their own set of plugins
Title: Message Title Oleg Nenashev commented on JENKINS-54452 Re: Allow a user to install their own set of plugins Feedback from Jenkins X: Preview environment can be used to verify the configuration Jenkinsfile Runner Test framework could be used to add some spot-checks 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-55725) p4 sync pipeline sync not syncing files after p4 plugin update from 1.8.12 to 1.9.6
Title: Message Title
Sasidhar A created an issue
Jenkins / JENKINS-55725
p4 sync pipeline sync not syncing files after p4 plugin update from 1.8.12 to 1.9.6
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
P4 Version 1.8.12.png, P4 Version 1.9.6.png, Workspace version 1.8.12.PNG, Workspace version 1.9.6.PNG
Components:
p4-plugin
Created:
2019-01-22 11:16
Labels:
p4-plugin P4_SUPPORT v1.9.6
Priority:
Major
Reporter:
Sasidhar A
P4 sync is not syncing files when used in pipeline script after updating p4 plugin from 1.8.12 to 1.9.6 Below is the pipeline script - stages { stage('Perforce Sync') { steps { p4sync charset: 'none', credential: 'Perforce', format: 'JenkinsSAPAutomationWorkspace', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), source: depotSource('//depot/AIM_platfom/sap_trasaction_validator/... ') } {color:#FF}} The script is working fine after downgrading the version to 1.8.12. Attaching the p4 log for your reference. Please let me know if you need more information. Thanks, Sasidhar
[JIRA] (JENKINS-55725) p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6
Title: Message Title Sasidhar A updated an issue Jenkins / JENKINS-55725 p4 sync pipeline script not syncing files after p4 plugin update from 1.8.12 to 1.9.6 Change By: Sasidhar A Summary: p4 sync pipeline sync script not syncing files after p4 plugin update from 1.8.12 to 1.9.6 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-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Jon-Paul Sullivan created an issue Jenkins / JENKINS-55726 GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository Issue Type: Bug Assignee: Unassigned Components: github-api-plugin, github-branch-source-plugin Created: 2019-01-22 11:34 Environment: CloudBees Jenkins Enterprise 2.107.34.0.1-fixed GitHub API Plugin 1.90 GitHub Branch Source Plugin 2.3.5 Priority: Critical Reporter: Jon-Paul Sullivan Multiple jobs configured against the same source repo will incorrectly set all checks successful if the last completed check is successful. In my opinion, if there is no mechanism to define mandatory and optional checks, then the worst status check should provide the overall result. This could be a check prior to submitting status that validates the prior status is not unsuccessful, and it is the same git sha1, and it is a different job name. The secondary issue here is that only a single link is added to the PR, and so there is no indication on the GitHub PR how many jobs ran.
[JIRA] (JENKINS-55727) Getting 403 forbidden for scripted clients with new API token
Title: Message Title Konstantin Remizov created an issue Jenkins / JENKINS-55727 Getting 403 forbidden for scripted clients with new API token Issue Type: Bug Assignee: Unassigned Components: authentication-tokens-plugin Created: 2019-01-22 11:36 Priority: Minor Reporter: Konstantin Remizov Trying to make requests with the new tokens https://jenkins.io/blog/2018/07/02/new-api-token-system/ But allways get 403 forbidden wget http://auto:NEWSECRETTOKEN@myhost:8180/job/MyJobName/build?token=remotetoken User auto has Overall read permissions and Job read/build/workspace permissions. Role based permissions are used. Also tried to make request with admin user but with the same 403 forbidden as a result. What could be the problem? Add Comment
[JIRA] (JENKINS-45060) NullPointerException in Maven33Main
Title: Message Title Jessica-Aileen Alten commented on JENKINS-45060 Re: NullPointerException in Maven33Main Same situation here; Jenkins 2.150.2, Maven Plugin 2.2 Maven 3.6.0: Trying to use a special configuration for a single module which is part of a multi-module project - it does not build. The build of a multi-module itself works, the single module build does not. Running maven in a command line building the module works. 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup Change By: Baptiste Mathus Released As: (towards) Jenkins 2.162 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus updated JENKINS-53284 Jenkins / JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup Change By: Baptiste Mathus Status: In Review 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-53284) Changing default layout for workspace and builds should not be a warning for first time startup
Title: Message Title Baptiste Mathus updated JENKINS-53284 Jenkins / JENKINS-53284 Changing default layout for workspace and builds should not be a warning for first time startup Change By: Baptiste Mathus Status: Resolved Fixed but Unreleased 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-51026) REST API doesn't provide information on failed test-cases
Title: Message Title Juho Saarinen assigned an issue to Juho Saarinen Jenkins / JENKINS-51026 REST API doesn't provide information on failed test-cases Change By: Juho Saarinen Assignee: jpiironen Juho Saarinen 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-51026) REST API doesn't provide information on failed test-cases
Title: Message Title Juho Saarinen started work on JENKINS-51026 Change By: Juho Saarinen 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title rsandell commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Do you see any warnings in the system log relating to JEP-200 ? 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title rsandell edited a comment on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Do you see any warnings in the system log relating to [JEP-200|https://github.com/jenkinsci/jep/tree/master/jep/200] ? When you say that the config.xml gets reset to the "empty" example have you verified that the once before had more in them and then got reset to the "empty" state or perhaps have they always been like that since creation? 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-55728) Fix Access violations and update to latest parent pom
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55728 Fix Access violations and update to latest parent pom Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-22 12:39 Labels: incrementals Priority: Minor Reporter: Baptiste Mathus I tried to quickly update parent and incrementalify the plugin, but it fails because I believe the parent pom update revealed a forbidden usage of the @Restricted org/jenkinsci/plugins/github_branch_source/MergeWithGitSCMExtension class [INFO] --- access-modifier-checker:1.15:enforce (default-enforce) @ github-branch-source --- [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.BranchDiscoveryTrait [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.BranchDiscoveryTrait$DescriptorImpl [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.BranchSCMHead$MigrationImpl [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.Endpoint$DesciptorImpl [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.ForkPullRequestDiscoveryTrait$DescriptorImpl [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.GitHubConsoleNote [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator [WARNING] null Failed to find class file for org.jenkinsci.plugins.github_branch_source.GitHubSCMNavigator$DescriptorImpl [WARNING] null Failed to find class file for org.
[JIRA] (JENKINS-55728) Fix Access violations and update to latest parent pom
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55728 Fix Access violations and update to latest parent pom Change By: Baptiste Mathus Labels: incrementals java11 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-55728) Fix Access violations and update to latest parent pom
Title: Message Title Baptiste Mathus commented on JENKINS-55728 Re: Fix Access violations and update to latest parent pom https://github.com/jenkinsci/github-branch-source-plugin/pull/199 demonstrates 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-55727) Getting 403 forbidden for scripted clients with new API token
Title: Message Title Konstantin Remizov updated JENKINS-55727 Jenkins / JENKINS-55727 Getting 403 forbidden for scripted clients with new API token Change By: Konstantin Remizov Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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-55727) Getting 403 forbidden for scripted clients with new API token
Title: Message Title Konstantin Remizov updated JENKINS-55727 Jenkins / JENKINS-55727 Getting 403 forbidden for scripted clients with new API token Change By: Konstantin Remizov Status: Fixed but Unreleased Closed 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-54829) Nunit Plugin: MAX_PATH is too long for a few windows systems
Title: Message Title Martin Kadner commented on JENKINS-54829 Re: Nunit Plugin: MAX_PATH is too long for a few windows systems Is there an official update of the plugin planned for the next days? Please keep in mind my last comment form 2018-12-02 22:06. 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-54829) Nunit Plugin: MAX_PATH is too long for a few windows systems
Title: Message Title Martin Kadner commented on JENKINS-54829 Re: Nunit Plugin: MAX_PATH is too long for a few windows systems Is there an official update of the plugin planned for the next days? Please keep in mind my last comment form 2018-12-02 22:06. 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-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-51057 EventDispatcher and ConcurrentLinkedQueue ate my JVM Change By: Baptiste Mathus Assignee: Tom FENNELLY 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-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou created an issue Jenkins / JENKINS-55729 process spawned by a job is not being killed Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-22 13:11 Environment: Jenkins version - 2.150.1. Priority: Major Reporter: Ivan Ivanou This isssue is related to gracefull job termination. If we push the abort button for the build within the implemented 2-minutes graceful period one more time, the build is gonna be terminated immidiately leaving the shell process(es)/script(s) alive. Users which are not aware of the graceful shutdown will obviuosly push the abort button couple of times expecting build to be aborted immideately. Those actions will accumulate "not killed" background shell processes that is not good. Add Comment
[JIRA] (JENKINS-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou updated an issue Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Ivan Ivanou This isssue is related to [ gracefull job termination |https://issues . jenkins-ci.org/browse/JENKINS-17116]. If we push the abort button for the build within the implemented 2-minutes graceful period one more time, the build is gonna be terminated immidiately immediately leaving the shell process(es)/script(s) alive. Users which are not aware of the graceful shutdown will obviuosly push the abort button couple of times expecting build to be aborted immideately immedeately . Those actions will accumulate "not killed" background shell processes that is not good. 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-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou assigned an issue to Robin Jarry Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Ivan Ivanou Assignee: Robin Jarry 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-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou updated an issue Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Ivan Ivanou This isssue is related to gracefull job termination. If we push the abort button for the build within the implemented 2-minutes graceful period one more time, the build is gonna be terminated immediately leaving the shell process(es)/script(s) alive. Users which are not aware of the graceful shutdown will obviuosly push the abort button couple of times expecting build to be aborted immedeately. Those actions will accumulate "not killed" background shell processes that is not good. 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-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou assigned an issue to Stephan Reiter Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Ivan Ivanou Assignee: Robin Jarry Stephan Reiter 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-55729) process spawned by a job is not being killed
Title: Message Title Ivan Ivanou updated an issue Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Ivan Ivanou This isssue is related to [ gracefull job termination |https://issues . jenkins-ci.org/browse/JENKINS-17116]. If we push the abort button for the build within the implemented graceful period one more time, the build is gonna be terminated immediately leaving the shell process(es)/script(s) alive. Users which are not aware of the graceful shutdown will obviuosly push the abort button couple of times expecting build to be aborted immedeately. Those actions will accumulate "not killed" background shell processes that is not good. 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-55729) process spawned by a job is not being killed
Title: Message Title Stephan Reiter assigned an issue to Unassigned Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Stephan Reiter Assignee: Stephan Reiter 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-55729) process spawned by a job is not being killed
Title: Message Title Stephan Reiter assigned an issue to Oleg Nenashev Jenkins / JENKINS-55729 process spawned by a job is not being killed Change By: Stephan Reiter Assignee: Oleg Nenashev 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-50824) "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm
Title: Message Title Baptiste Mathus commented on JENKINS-50824 Re: "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm Oliver Gondža I stumbled into here by chance, I seem to understand this issue is actually resolved and hence could be marked as such isn't it? Cheers 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-50824) "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm
Title: Message Title Oliver Gondža resolved as Fixed I presume the contention is now reduced to manageable levels. I am resolving this as there is noone else complaining since the improvement was released. Jenkins / JENKINS-50824 "Excessive" exception logging on writing org.jenkinsci.plugins.resourcedisposer.AsyncResourceDisposer.xm Change By: Oliver Gondža 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-30756) Pass in Environment Variables on ProcessBuilder Create
Title: Message Title Jakub Pawlinski closed an issue as Won't Fix merge declined by its creator Brian Thai "A better solution with more flexibility via code was to add a Makefile to my project. I am closing this PR as it is extraneous." Jenkins / JENKINS-30756 Pass in Environment Variables on ProcessBuilder Create Change By: Jakub Pawlinski Status: Open Closed Resolution: Won't 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-55730) Show absolute/relative path for source files
Title: Message Title Stefan Schletterer created an issue Jenkins / JENKINS-55730 Show absolute/relative path for source files Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-22 14:15 Priority: Minor Reporter: Stefan Schletterer 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 Stefan Schletterer updated an issue Jenkins / JENKINS-55730 Show absolute/relative path for source files Change By: Stefan Schletterer In the legacy version of the warnings plugin there was an option to show absolute file path for the source files. This came with the additional option of sorting the issues by folder. The warnings-ng-plugin doesn't seem to offer the same option (use absolute paths and group by folder). Also, there is now way to show the absolute or module-relative paths of a source file, only the file name. 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-52052) Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-52052 Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11 Change By: Devin Nusbaum Assignee: Devin Nusbaum 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-52052) Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11
Title: Message Title Devin Nusbaum commented on JENKINS-52052 Re: Investigate bouncycastle-related errors when running JenkinsRule tests on Java 11 Isa Vilacides I do not know, this was from the Java 11 hackathon last summer. At any rate I am not working on it anymore. Likely it was some issue that has been already fixed in the parent pom or by a change to instance-identity such as https://github.com/jenkinsci/instance-identity-module/pull/11. Since all the tests were passing anyway, it probably makes to just close this now and reopen it if a PCT run shows that it is a problem in practice. 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-33952) "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed
Title: Message Title Zaur Mekhdiev commented on JENKINS-33952 Re: "Test Statistics Grid" shows all in "0" and "0%" including total as 0 tests when build never passed Good day, guys! Same issue Jenkins ver - 2.150.1 Plugin ver - 2.10 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-55731) Pass test parameters when UFT test is run from ALM
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-55731 Pass test parameters when UFT test is run from ALM Issue Type: Story Assignee: Anda Sorina Laakso Components: core Created: 2019-01-22 14:37 Priority: Major Reporter: Anda Sorina Laakso When running tests from ALM using the Execute Micro Focus functional tests from Micro Focus ALM, a user should be able to provide test parameter details for each test plan they want to run. Use the following syntax: TestSet\Test1 "Country":"US", "Count":3 Where each comma separated keypair is a set of parameter names and values. This supports only 1 value for each test parameter. This feature does not support iterations with multiple values for each parameter (one per iteration). Add Comment
[JIRA] (JENKINS-55732) [ICE] Filtering tests in ALM
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-55732 [ICE] Filtering tests in ALM Issue Type: Story Assignee: Anda Sorina Laakso Components: core Created: 2019-01-22 14:38 Priority: Major Reporter: Anda Sorina Laakso Customer requires the following filtering for tests: By name or part of a name Test result status Customer wants a way to filter tests by name and/or by status. The result would be one of the following: Tests filtered by name or part of a name and selected statuses Tests filtered by selected statuses only Tests filtered by name or part of a name only Add Comment
[JIRA] (JENKINS-55732) [ICE] Filtering tests in ALM
Title: Message Title Anda Sorina Laakso commented on JENKINS-55732 Re: [ICE] Filtering tests in ALM https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/219 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-55731) Pass test parameters when UFT test is run from ALM
Title: Message Title Anda Sorina Laakso commented on JENKINS-55731 Re: Pass test parameters when UFT test is run from ALM https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/219 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-42200) No valid crumb was included in the request in kubernetes
Title: Message Title Baptiste Mathus reopened an issue Jenkins / JENKINS-42200 No valid crumb was included in the request in kubernetes Change By: Baptiste Mathus Resolution: Fixed Status: Closed Reopened 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-42200) No valid crumb was included in the request in kubernetes
Title: Message Title Baptiste Mathus closed an issue as Not A Defect Jenkins / JENKINS-42200 No valid crumb was included in the request in kubernetes Change By: Baptiste Mathus Status: Reopened Closed Resolution: Not A Defect 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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Alex Gray updated an issue Jenkins / JENKINS-42632 CCM Plugin Not Creating Trend Graph Change By: Alex Gray Attachment: ccm.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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Alex Gray updated an issue Jenkins / JENKINS-42632 CCM Plugin Not Creating Trend Graph Change By: Alex Gray Attachment: ccm.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-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Alex Gray commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Bruno P. Kinoshita You're not supposed to be working during a conference! You're supposed to be out socializing! Nonetheless, I've attached a ccm.xml file to 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-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title André Schulz commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions Why Jenkins 2.161 (latest) contains maven-plugin-2.14 containing lib-jenkins-maven-embedder-3.11? (jenkins.war\WEB-INF\detached-plugins\maven-plugin.hpi\WEB-INF\lib) I replaced lib-jenkins-maven-embedder-3.11 by lib-jenkins-maven-embedder-3.13 (renamed maven-plugin.hpi to maven-plugin_mod.hpi) but getting same error. We have 500+ Maven jobs in our Jenkins and don't want to change a lot... 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-55720) ec2-plugin 1.42 doesn't work well with ec2 spot instances
Title: Message Title Stan Crofts commented on JENKINS-55720 Re: ec2-plugin 1.42 doesn't work well with ec2 spot instances I am unable to launch spot instances on 1.42. I get the following output in the log: INFO: Connecting to null on port 22, with timeout 1. Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud INFO: Connected via SSH. Jan 22, 2019 2:58:48 PM hudson.plugins.ec2.EC2Cloud WARNING: Authentication failed. Trying again... 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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
Title: Message Title pavan kumar commented on JENKINS-9120 Re: RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow Hi ALex, I am encountering a pretty similar issue as many of our jenkins builds stopped triggering at scheduled times and we have no idea about what could be the root cause of it. We restarted our Jenkins master many times but no luck and i dont see anything unusual errors too in the logs. Please help us to overcome this 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-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title Ethan Young updated an issue Jenkins / JENKINS-28687 spring version (2.5.x) is ancient and not compatable with many new libraries Change By: Ethan Young Priority: Minor Major 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-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title Ethan Young commented on JENKINS-28687 Re: spring version (2.5.x) is ancient and not compatable with many new libraries Upgrading the Spring framework will also resolve security issues. Specifically, CVE-2017-8046 is an _expression_ language injection vulnerability in the Spring Data REST library v2.6.8 and earlier. 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-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title Ethan Young updated an issue Jenkins / JENKINS-28687 spring version (2.5.x) is ancient and not compatable with many new libraries Change By: Ethan Young Labels: security 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-52316) The data for Test Statistics Grid shows 0 and Test Statistics Chart can not displayed when there are tests executed
Title: Message Title Zaur Mekhdiev commented on JENKINS-52316 Re: The data for Test Statistics Grid shows 0 and Test Statistics Chart can not displayed when there are tests executed Same 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-28687) spring version (2.5.x) is ancient and not compatable with many new libraries
Title: Message Title Daniel Beck commented on JENKINS-28687 Re: spring version (2.5.x) is ancient and not compatable with many new libraries Ethan Young If you actually find a way to exploit it in Jenkins, please file an issue as described here: https://jenkins.io/security/#reporting-vulnerabilities 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Nancy Belser commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Karl, We had to shut down our jenkins instance because we cannot get the pipeline project to stop constantly polling perforce and attempting to build with no 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-55547) Change base image for Evergreen (move away from Alpine)
Title: Message Title Baptiste Mathus commented on JENKINS-55547 Re: Change base image for Evergreen (move away from Alpine) Another reason that I would really like this handled rather sooner than later: recently, I was trying to make sure artifact-manager-s3 and overall the EC2 Evergreen flavor would work correctly on JDK 11. So my initial idea was to simply spawn an Evergreen instance the usual way, then hack into it, wget a JDK11, tweak PATH and restart the instance to force it to use JDK11. I was expected it to take a handful of minutes. But then I remembered given the instance was based on Alpine this was going to be actually very hard. So I stopped trying because that was out of scope for the time/effort I had planned. I think Alpine is a nice effort, but the μlibC starting from scratch is starting to show its shortcomings. The effort is not shared, and as soon as, as right now, it got an issue to support something (the JDK in our case), things simply stalled. Now, there are many possibly flavors to choose from. Debian, Ubuntu, Centos... TL;DR: I'm going to go for Centos for the following reason: Centos is downstream to RHEL and Fedora, who are handled by a group of people that have the Java Platform working correctly at the core of their concerns. (I could probably go for Fedora, for a similar reason as explained above, I don't feel that strongly for Centos or Fedora, BTW). Ubuntu Ubuntu has recently made a choice to provide a package for Java 11, but actually have Java 10 in it: https://askubuntu.com/questions/1037646/why-is-openjdk-10-packaged-as-openjdk-11 The rationale being: people would automatically this way automatically bump to Java 11 (because the package was actually name ...-lts) once it got published... I feel like these people, though basing this choice to help others, may not understand deeply enough the requirements and differences between two different major versions of the JDK. I think unfortunately this kind of action illustrates why we should move away from Debian based distributions. And this comes from someone who's been a Debian fanboy for years, and still very much likes it for a development machine, etc. Just that the overall platform does not look like (anymore?) the best possible default choice for running Java based software in production. Debian Recently, another issue arised where showing Debian would backport fixes in a potentially different way than openjdk (which can make it pretty different from other platforms): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911925 This one surfaced in https://twitter.com/jroper/status/1062869489073573888?lang=en : Don't use Debian's or Ubuntu's OpenJDK builds - they insist on backporting individual commits, rather than taking the latest patch versions, but have neither the expertise, nor the necessary empathy with the Java ecosystem, to do so. This one is also known/surfaced as SUREFIRE-1588, which has been discussed extensively in many locations and took a lot of effort to get rid of in the Jenkins ecosystem and elsewhere: https://github.com/jenkinsci/pom/pull/34 https://github.com/jenkinsci/plugin-pom/pull/131 https://github.com/jenkinsci/plugin-compat-tester/pull/93 https://github.com/jenkinsci/plugin-pom/pull/135 https://issues.apache.org/jira/browse/SUREFIRE-1588?focusedCommentId=16704836&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16704836
[JIRA] (JENKINS-55547) Change base image for Evergreen (move away from Alpine)
Title: Message Title Baptiste Mathus started work on JENKINS-55547 Change By: Baptiste Mathus 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-55733) Wrong parsing of CppCheck results
Title: Message Title sunblack created an issue Jenkins / JENKINS-55733 Wrong parsing of CppCheck results Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-22 16:19 Priority: Minor Reporter: sunblack The Warnings Next Generation Plugin count each error location as error, instead of just counting error. Example (Shortened result of CppCheck 1.86 on PCL) "redundantAssignment" severity="style" msg="Variable 'it' is reassigned a value before the old one has been used." verbose="Variable 'it' is reassigned a value before the old one has been used." cwe="563"> "apps\cloud_composer\src\point_selectors\rectangular_frustum_selector.cpp" file="apps\cloud_composer\src\point_selectors\rectangular_frustum_selector.cpp" line="53"/> "apps\cloud_composer\src\point_selectors\rectangular_frustum_selector.cpp" file="apps\cloud_composer\src\point_selectors\rectangular_frustum_selector.cpp" line="51"/> it "knownConditionTrueFalse" severity="style" msg="Condition 'rc' is always true" verbose="Condition 'rc' is always true" cwe="571"> "surface\src\3rdparty\opennurbs\opennurbs_brep_tools.cpp" file="surface\src\3rdparty\opennurbs\opennurbs_brep_tools.cpp" line="346" info="Condition 'rc' is always true"/> "surface\src\3rdparty\opennurbs\opennurbs_brep_tools.cpp" file="surface\src\3rdparty\opennurbs\opennurbs_brep_tools.cpp" line="335" info="Assignment 'rc=true', assigned value is 1"/> This is currently counted as 4 errors instead of 2. CppCheck just gives multiple locations so dev can easily see the reason for this warning.
[JIRA] (JENKINS-55734) HTML is escaped
Title: Message Title Torsten Boelting created an issue Jenkins / JENKINS-55734 HTML is escaped Issue Type: Bug Assignee: Larry Shatzer, Jr. Components: maven-deployment-linker-plugin Created: 2019-01-22 16:23 Environment: Jenkins ver. 2.138.3 Priority: Minor Reporter: Torsten Boelting Links are no longer shown as HTML but as HTML-code e.g. instead of By the way: There's a wrong Link to Github on this page https://plugins.jenkins.io/maven-deployment-linker that leads to the Favorite Plugin. Correct Link is https://github.com/jenkinsci/maven-deployment-linker-plugin Add Comment
[JIRA] (JENKINS-55734) HTML is escaped
Title: Message Title Torsten Boelting updated an issue Jenkins / JENKINS-55734 HTML is escaped Change By: Torsten Boelting Links are no longer shown as HTML but as HTML-code e.g. & ampersand lt ; li> instead of By the way:There's a wrong Link to Github on this page [https://plugins.jenkins.io/maven-deployment-linker]that leads to the Favorite Plugin. Correct Link is [ https://github.com/jenkinsci/maven-deployment-linker-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-55735) Graph with type instead of severity as content
Title: Message Title sunblack created an issue Jenkins / JENKINS-55735 Graph with type instead of severity as content Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-22 16:28 Priority: Minor Reporter: sunblack Currently the graph contains only severity (low, normal, high) as content. It would be nice to can adjust the graph to display other content, like type, because severity alone has sometimes really less information. At result it should look similar to this: Cppcheck Plugin example image Add Comment
[JIRA] (JENKINS-55630) Support declarative pipelines
Title: Message Title Benjamin Muschko commented on JENKINS-55630 Re: Support declarative pipelines FYI: I switched my project to Go modules. Go modules makes the setup much easier. You can just use a declarative pipeline definition. 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-52066) Poll per change with multibranch pipeline jobs
Title: Message Title
Daniel Hagström commented on JENKINS-52066
Re: Poll per change with multibranch pipeline jobs
I'm not seeing this working as intended in 1.9.6, but rather just as broken as before. I have several multibranch pipelines that poll e.g. once per minute, and are still lagging behind on their builds. The scanning log says something like this: {{ ... p4 changes -m1 //project/master/...@now - p4 changes -m1 //project/master/...@now Change 41254 on 2019/01/22 by bjorn@bjorn_project_workstation 'RES-11336 Update localization w' ... p4 files -e //project/master/Jenkinsfile - p4 files -e //project/master/Jenkinsfile //project/master/Jenkinsfile#3 - edit change 39828 (text) ‘Jenkinsfile’ found No changes detected: master (still at 41254) }} Whereas the last build is only at @41189. When manually triggering a build, the build correctly contains the next changelist, in this example @41224. It does not trigger any further builds automatically, but if I keep pressing "Build now" I keep getting builds until I'm caught up again. In my eyes this inconsistency is exactly as it was before this bug was considered 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-31050) Slave goes offline during the build
Title: Message Title Prudhvi Godithi commented on JENKINS-31050 Re: Slave goes offline during the build Hey I am having the same issue with Kubernetes plugin, where slaves try to connect to master with jnlp at particular port, we have even increased the ELB connection Timeout still facing the same issue where slaves go offline in between the builds and works fine when again rebuild the job, this is causing us huge impact for pipeline builds, our issue is very close to what Raghu Pallikonda has mentioned above, any solution for this, please let me know. Thank you Error: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF while receiving the data from the channel. FIFO buffer has been already closed. 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Paul Allen commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Nancy, It seems that on Karl's system a bad syncID was causing the polling logic to think there were new changes. Please can you recreate the Jenkins Job (e.g. create a new job and delete or disable the one continuously polling). If you have a support ticket open with Karl, please can you email a copy of your build.xml file for the last failing build and your config.xml. We will review the data tomorrow and see if you were experiencing the same issue Karl had when upgrading from 1.9.3 -> 1.9.6 Kind regards, Paul 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Paul Allen started work on JENKINS-55075 Change By: Paul Allen 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Nancy Belser commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Hi Paul, this is happening for 2 pipeline projects which we cannot disable. Do you suggest we recreate the entire pipeline project? 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-31050) Slave goes offline during the build
Title: Message Title Prudhvi Godithi edited a comment on JENKINS-31050 Re: Slave goes offline during the build Hey I am having the same issue with Kubernetes plugin, where slaves try to connect to master with jnlp at particular port, we have even increased the ELB connection Timeout still facing the same issue where slaves go offline in between the builds and works fine when again rebuild the job, this is causing us huge impact for pipeline builds, our issue is very close to what [~rpallikonda] has mentioned above, any solution for this, please let me know.Thank you Slave Verion: remoting-3.20.jar Error:hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF while receiving the data from the channel. FIFO buffer has been already closed. Should I upgrade the remoting 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-53022) Cannot disable a job from Blue Ocean UI
Title: Message Title Gavin Mogan commented on JENKINS-53022 Re: Cannot disable a job from Blue Ocean UI I forgot this was still assigned to me. I did look into it. Its mostly an issue of UI and workflow, but also, you can only disable certain job types. Like for example, pipelines can't be disabled, the api to even attempt it is private. https://github.com/jenkinsci/blueocean-plugin/compare/master...halkeye:disable-poc 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Paul Allen commented on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Are you referring to Pipeline Jobs or MultiBranch? If a Pipeline Job then it is the build history that is potentially causing the issue; deleting the job and then using the same name, credentials and settings worked for Karl. If you don't want to loose the build history then create a new job, but this will use a new Perforce workspace and will resync all the files (which could be expensive on a large project). Please work with Karl via support and he can guide you through the steps and advise if it is best to delete or duplicate the job based on your situation. In the meantime please send us the build.xml data. 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-55075) Pipeline: If job fails it will run again on next poll.
Title: Message Title Paul Allen edited a comment on JENKINS-55075 Re: Pipeline: If job fails it will run again on next poll. Are you referring to Pipeline Jobs or MultiBranch? If a Pipeline Job then it is the build history that is potentially causing the issue; deleting the job and then using the same name, credentials and settings worked for Karl. If you don't want to loose the build history then create a new job, but this will use a new Perforce workspace and will resync all the files (which could be expensive on a large project).Please work with Karl via support and he can guide you through the steps and advise if it is best to delete or duplicate the job based on your situation. In the meantime please send us the build.xml and config.xml data. 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-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Title: Message Title Samuel Lopez commented on JENKINS-36881 Re: Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER Hello We are seeing the same issue. Could you please share the workaround steps? Thank you kindly. Sam 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-54829) Nunit Plugin: MAX_PATH is too long for a few windows systems
Title: Message Title Alex Earl updated JENKINS-54829 Jenkins / JENKINS-54829 Nunit Plugin: MAX_PATH is too long for a few windows systems Change By: Alex Earl Status: Fixed but Unreleased Closed Released As: 0.24 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.
