[JIRA] (JENKINS-57476) Build timeout should include only successful builds, not unstable builds
Title: Message Title trejkaz created an issue Jenkins / JENKINS-57476 Build timeout should include only successful builds, not unstable builds Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: build-timeout-plugin Created: 2019-05-15 05:57 Priority: Minor Reporter: trejkaz Build Timeout plugin currently takes unstable builds into account when computing the average duration of the last N runs. Because of this, if a test suite fails due to an early abort N times in a row, the average time of the build drops. When you eventually fix the issue, the build actually runs all the tests, so it inevitably gets timed out. This is seemingly only recoverable by deleting the build history. I'd like the build timeout plugin to consider only successful results, so that we can be reasonably sure that all tests actually ran when computing the expected time. Add Comment
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Abhyudaya Sharma started work on JENKINS-57437 Change By: Abhyudaya Sharma 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.745.1557898680249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Abhyudaya Sharma commented on JENKINS-57437 Re: Update jenkins.io page for the Role Strategy GSoC 2019 project See https://github.com/jenkins-infra/jenkins.io/pull/2266 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.747.1557898680269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55553) Active flag in jenkins build engine gets de-activated
Title: Message Title Lakshmi Narasimhan Vaikuntam closed an issue as Cannot Reproduce No response. Closing. Reopen if you have more information. Jenkins / JENKINS-3 Active flag in jenkins build engine gets de-activated Change By: Lakshmi Narasimhan Vaikuntam Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196715.1547276236000.733.1557890220256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57475) Cannot "Disable" a multi-branch job
Title: Message Title Rick created an issue Jenkins / JENKINS-57475 Cannot "Disable" a multi-branch job Issue Type: Improvement Assignee: Unassigned Components: branch-api-plugin Created: 2019-05-15 02:22 Priority: Minor Reporter: Rick 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199335.1557886956000.731.1557886980095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57469) Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error)
Title: Message Title Jie Shen commented on JENKINS-57469 Re: Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error) Valentin Delaye Could you please provide any sample of your configuration so that I could test on your case? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199329.155785830.730.1557885720393%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37436) unable to find valid certification path to requested target;
Title: Message Title Hem Tail commented on JENKINS-37436 Re: unable to find valid certification path to requested target; Is there any solution this problem? I am getting the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173539.1471339906000.728.1557885720346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57469) Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error)
Title: Message Title Azure DevOps started work on JENKINS-57469 Change By: Azure DevOps 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199329.155785830.721.1557883980425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57469) Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error)
Title: Message Title Azure DevOps assigned an issue to Jie Shen Jenkins / JENKINS-57469 Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error) Change By: Azure DevOps Assignee: Azure DevOps Jie Shen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199329.155785830.724.1557883980477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57473) Replace second x with an up arrow
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-57473 Replace second x with an up arrow Change By: Josh Soref Assignee: Josh Soref 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199333.1557874263000.717.1557879120071%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57468) scm/SubversionSCM/enterCredential link is obsolete
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-57468 scm/SubversionSCM/enterCredential link is obsolete Change By: Josh Soref Assignee: Josh Soref 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199328.1557857142000.716.1557878520056%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57467) missing space in "Subversion repository.This"
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-57467 missing space in "Subversion repository.This" Change By: Josh Soref Assignee: Josh Soref 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199327.1557852424000.715.1557878280063%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57474) Ignore committer doesn't work for non-email subversion users
Title: Message Title Bryce Schober created an issue Jenkins / JENKINS-57474 Ignore committer doesn't work for non-email subversion users Issue Type: Bug Assignee: Bernard Baltrusaitis Components: ignore-committer-strategy-plugin Created: 2019-05-14 22:59 Environment: Latest Jenkins LTS and plugins as of 2019-05-14 Priority: Major Reporter: Bryce Schober My subversion usernames aren't full email addresses, and this branch build strategy seems to have no effect in my subversion multi-branch pipeline. Add Comment
[JIRA] (JENKINS-57473) Replace second x with an up arrow
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57473 Replace second x with an up arrow Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-14-18-51-03-199.png Components: blueocean-plugin Created: 2019-05-14 22:51 Priority: Minor Reporter: Josh Soref When a build fails, the top of the pipeline view looks like this: Conceptually, when using blue ocean, the right x takes one up a stage, e.g. from a build number to the branch/PR. So, instead of using an x, we can use an up arrow. Add Comment
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Mez Pahlan commented on JENKINS-55013 Re: support for App Center Just checking in. I have something that works! Yaaay! It needs error handling and more tests added.. Boo!! I'm working on it! You can follow along here: https://github.com/mezpahlan/appcenter-plugin/tree/feature/initial-structure 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196049.1543936697000.711.1557870540443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Ulli Hafner commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views I see. It would also make sense to see the actual arguments of the step. I have no idea how to set or change it... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.699.1557869940116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57369) Docker build-args incorrectly rejected and successful build marked failed
Title: Message Title
Jack Peterson commented on JENKINS-57369
Re: Docker build-args incorrectly rejected and successful build marked failed
I'm going to +1 this issue as a totally annoying problem here as I'm working on using Jenkins Dockerfiles that depend on an upstream private image as well as a private-key needing to be passed in in order to perform git clones of private repositories as part of a dependency management step in the primary Dockerfile. I too don't like how the credentials get displayed willy-nilly as soon as they become multiline parameters.
pipeline {
agent none
...
environment {
GITHUB_SSH_PRIVATE_KEY=credentials('github_ssh_key')
DOCKER_REGISTRY_CREDENTIALS=credentials('dockerhub')
}
...
stages {
stage("run unit tests") {
agent {
dockerfile {
filename "Dockerfile"
additionalBuildArgs "--build-arg SSH_PRIVATE_KEY=\"${env.GITHUB_SSH_PRIVATE_KEY}\""
registryCredentialsId 'dockerhub'
}
}
steps {
sh '//commands run here'
}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199150.1557317521000.692.1557867780831%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36835) Change secret text field to textarea to support multiline text
Title: Message Title Jack Peterson commented on JENKINS-36835 Re: Change secret text field to textarea to support multiline text Making the text-input a textarea does allow saving the secret text as multiline; however, the credentials are echoed out plain as day in the build logs ... effectively breaking the security model. See https://issues.jenkins-ci.org/browse/JENKINS-57369 as an example where that scenario would occur. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172880.1469046862000.697.1557867900220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57472) Parameterized Trigger: incorrectly sets node label to master if node disconnects
Title: Message Title Elliot Nelson created an issue Jenkins / JENKINS-57472 Parameterized Trigger: incorrectly sets node label to master if node disconnects Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-05-14 21:02 Environment: Jenkins 2.138.2, Plugin 2.35.2, Java 1.8.x, Linux Labels: jenkins plugin slave Priority: Minor Reporter: Elliot Nelson If Project A triggers Project B on same node, but while Project A is running the build agent it is running on disconnects abnormally (machine disconnect, network issue, etc.), what happens is that Project B is triggered on master instead of the target node. The expected behavior is that Project B is triggered with the original node label, and ends up in the queue waiting for the target machine to reconnect, since it is no longer connected.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Jason Faust commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views I'll work on generating an actual example of the bug, with input files, as soon as I get a chance. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.689.1557867600208%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title
Jason Faust edited a comment on JENKINS-57378
Re: warnings-ng commands show up as General Build Step in pipeline views
It should be reading (I imagine) {{Record compiler warnings and static analysis results}} (for each line, all seven of those are {{recordIssues}} commands)
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.687.1557867360238%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Jason Faust commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views It should be reading (I imagine) Record compiler warnings and static analysis results 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.685.1557867360195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Ulli Hafner commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views I must admit that I'm not really a pipeline user... I still have no clue where your output from above comes from and what are you expecting. Should there be something more specific than "General Build Step"? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.683.1557867241344%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57471) User preference to set the metrics type (Average, Median or 90%) for the trend graphing
Title: Message Title Selven Pillai updated an issue Jenkins / JENKINS-57471 User preference to set the metrics type (Average, Median or 90%) for the trend graphing Change By: Selven Pillai At present, the Performance plugin shows the trend graphs for the URI derived from the average response time. As the average numbers are tends to influence influenced by outliers, So looking at the trend graph to see and performance deviation between two or more test runs is misleading. If there is a options for the user to select the metrics type (Average, Median or 90%) then it will be beneficial. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199331.1557866266000.681.1557867123958%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57471) User preference to set the metrics type (Average, Median or 90%) for the trend graphing
Title: Message Title Selven Pillai created an issue Jenkins / JENKINS-57471 User preference to set the metrics type (Average, Median or 90%) for the trend graphing Issue Type: New Feature Assignee: Andrey Pokhilko Components: performance-plugin Created: 2019-05-14 20:37 Priority: Critical Reporter: Selven Pillai At present, the Performance plugin shows the trend graphs for the URI derived from the average response time. As the average numbers are tends to influence by outliers, So looking at the trend graph to see and performance deviation between two or more test runs is misleading. If there is a options for the user to select the metrics type (Average, Median or 90%) then it will be beneficial. Add Comment
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Jason Faust reopened an issue I'll try to track this down better for debugging, but did see it happen again. Jenkins / JENKINS-57378 warnings-ng commands show up as General Build Step in pipeline views Change By: Jason Faust Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.669.1557862860160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title
Jason Faust edited a comment on JENKINS-57378
Re: warnings-ng commands show up as General Build Step in pipeline views
Just had it pop up again. Using Warnings-NG 5.0.0, analysis-model-api 5.0.2, Jenkins 2.164.3, and all the other plugins patched up to the version as of writing this note.Note, had just did an inplace restart of Jenkins to patch analysis-model-apiBut the output of the stage where I had all the static analysis bits in it looks like:{code :text }Stage : Start - (2 min 2 sec in block) Static Analysis Console Output SuccessStatic Analysis - (2 min 2 sec in block) SuccessGeneral Build Step - (24 sec in self) Console Output SuccessGeneral Build Step - (20 sec in self) Console Output SuccessGeneral Build Step - (18 sec in self) Console Output SuccessGeneral Build Step - (12 sec in self) Console Output SuccessGeneral Build Step - (15 sec in self) Console Output SuccessGeneral Build Step - (12 sec in self) Console Output SuccessGeneral Build Step - (16 sec in self) Console Output Success{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, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.667.1557862800341%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Jason Faust commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views Just had it pop up again. Using Warnings-NG 5.0.0, analysis-model-api 5.0.2, Jenkins 2.164.3, and all the other plugins patched up to the version as of writing this note. Note, had just did an inplace restart of Jenkins to patch analysis-model-api But the output of the stage where I had all the static analysis bits in it looks like: Unable to find source-code formatter for language: text. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, _javascript_, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml Stage : Start - (2 min 2 sec in block) Static Analysis Console Output Success Static Analysis - (2 min 2 sec in block) Success General Build Step - (24 sec in self) Console Output Success General Build Step - (20 sec in self) Console Output Success General Build Step - (18 sec in self) Console Output Success General Build Step - (12 sec in self) Console Output Success General Build Step - (15 sec in self) Console Output Success General Build Step - (12 sec in self) Console Output Success General Build Step - (16 sec in self) Console Output Success 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
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title Artem Stasiuk resolved as Done Thx, close as issue is gone, feel free to reopen if any problems/questions. No code change in plugin assume it was Jenkins/version related. Jenkins / JENKINS-48696 When an offline node comes online, pending jobs don't get assigned to it Change By: Artem Stasiuk Status: Open Resolved Assignee: Artem Stasiuk Resolution: Done 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. To view this discussion on the web visit
[JIRA] (JENKINS-57467) missing space in "Subversion repository.This"
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-57467 missing space in "Subversion repository.This" Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199327.1557852424000.657.1557860940181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57468) scm/SubversionSCM/enterCredential link is obsolete
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-57468 scm/SubversionSCM/enterCredential link is obsolete Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199328.1557857142000.659.1557860940221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57470) Plugin Manager page does not render correctly
Title: Message Title JC Putter created an issue Jenkins / JENKINS-57470 Plugin Manager page does not render correctly Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-05-14 at 20.51.14.png Components: plugin-usage-plugin Created: 2019-05-14 19:07 Priority: Minor Reporter: JC Putter Upgrading to Jenkins ver. 2.164.3 we discovered that the plugin manager page does not render correctly. Tried Chrome,FF Add Comment
[JIRA] (JENKINS-57469) Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error)
Title: Message Title
Valentin Delaye created an issue
Jenkins / JENKINS-57469
Not able to use custom image with associated plan (Marketplace image requires Plan information in the request' error)
Issue Type:
Improvement
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-05-14 18:25
Environment:
Jenkins 2.164.3 Azure VM Agents 0.9.0
Priority:
Minor
Reporter:
Valentin Delaye
Hello, It's not possible to use a custom image with attached plan (created from the Market place) For example using RancherOS 1.5.1
Create an custom image using Packer (inject SSH keys, configure engine etc..)
Use this custom image to start new machines using SSH
We cannot do it because the API is expecting we pass the plan information in the request
Creating a virtual machine from Marketplace image requires Plan information in the request
In case of packer it stores the plan information directly on the tags of the image
"tags": {
"PlanInfo": "os",
"PlanProduct": "rancheros",
"PlanPromotionCode": "",
"PlanPublisher": "rancher",
[JIRA] (JENKINS-48715) Retain last N builds
Title: Message Title Nisarg Shah commented on JENKINS-48715 Re: Retain last N builds Martin d'Anjou What do you mean by retain last N builds. Does it mean getting last N builds which were discarded or something else. Or you want that both age and number of builds both factor plays a role in discarding build and no overwritten happens.(Similar to my GSoC Proposal) Can you please clarify? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187418.1514330382000.650.1557858000424%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-57430 Getting issue when using github Change By: Liam Newman Assignee: Kirill Merkushev Liam Newman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.645.1557858000334%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman assigned an issue to Kirill Merkushev Jenkins / JENKINS-57430 Getting issue when using github Change By: Liam Newman Assignee: Liam Newman Kirill Merkushev 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.642.1557857940271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42438) Wrong JUnit test duration shown in classes list
Title: Message Title Devin Nusbaum resolved as Fixed Looks like a fix for this was released in version 1.27 of the plugin. Jenkins / JENKINS-42438 Wrong JUnit test duration shown in classes list Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: junit 1.27 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179345.1488459545000.639.1557857820560%40Atlassian.JIRA. For more options,
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman edited a comment on JENKINS-57430 Re: Getting issue when using github [~alphaomega]This is happening when you scan the organization from the Jenkins UI or are you seeing this when webhook fires and starts a scan? It looks like the underlying issue is that the (external to Jenkins project) GitHub API package doesn't support that webhook event type. We'll need to file an issue with that project: https://github.com/kohsuke/github-api . Filed: https://github.com/kohsuke/github-api/issues/519 As a workaround, you should be able to edit the webhooks for that repo (or the org as whole) and set you Jenkins webhook to not include the "check run" or "check suite" events. In the links below, edit any Jenkins webhooks to "Let me select individual events".https://github.com/organizations/YOUR_ORG/settings/hookshttps://github.com/YOUR_ORG/YOUR_REPO/settings/hooksPlease tell me if that 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.633.1557857700211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman edited a comment on JENKINS-57430 Re: Getting issue when using github [~alphaomega]This is happening when you scan the organization from the Jenkins UI or are you seeing this when webhook fires and starts a scan? It looks like the underlying issue is that the (external to Jenkins project) GitHub API package doesn't support that webhook event type. We'll need to file an issue with that project: https://github.com/kohsuke/github-apiAs a workaround, you should be able to edit the webhooks for that repo (or the org as whole) and set you Jenkins webhook to not include the "check run" or "check suite" events. In the links below, edit any Jenkins webhooks to "Let me select individual events". https://github.com/organizations/YOUR_ORG/settings/hookshttps://github.com/YOUR_ORG/YOUR_REPO/settings/hooks Please tell me if that 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.631.1557857640178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman commented on JENKINS-57430 Re: Getting issue when using github Valerian Martin This is happening when you scan the organization from the Jenkins UI or are you seeing this when webhook fires and starts a scan? It looks like the underlying issue is that the (external to Jenkins project) GitHub API package doesn't support that webhook event type. We'll need to file an issue with that project: https://github.com/kohsuke/github-api As a workaround, you should be able to edit the webhooks for that repo (or the org as whole) and set you Jenkins webhook to not include the "check run" or "check suite" events. https://github.com/organizations/YOUR_ORG/settings/hooks https://github.com/YOUR_ORG/YOUR_REPO/settings/hooks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.629.1557857400102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57468) scm/SubversionSCM/enterCredential link is obsolete
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57468 scm/SubversionSCM/enterCredential link is obsolete Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2019-05-14 18:05 Priority: Minor Reporter: Josh Soref Daniel Beck says that this path /scm/SubversionSCM/enterCredential is obsolete as of the credentials-plugin. https://github.com/jenkinsci/subversion-plugin/blob/2a14db8c50beeab8ae96f57e8e23176dad58944a/src/main/resources/hudson/scm/SubversionSCM/DescriptorImpl/url-help.properties#L33 Add Comment
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-57430 Getting issue when using github Change By: Liam Newman Assignee: Kirill Merkushev Liam Newman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.625.1557855480162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin commented on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch Did you have a chance to look at my suggested 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.621.1557854760136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title John Zila commented on JENKINS-48696 Re: When an offline node comes online, pending jobs don't get assigned to it No, it seems to be fine now, 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187380.1513974343000.619.1557853920168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe updated an issue Jenkins / JENKINS-55597 Jenkins JNLP agent disconnects when it fails to delete an old build workspace Change By: James Howe Component/s: remoting Component/s: ssh-agent-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.609.1557852840261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe updated an issue Jenkins / JENKINS-55597 Jenkins JNLP agent disconnects when it fails to delete an old build workspace Change By: James Howe Component/s: ssh-agent-plugin Component/s: ws-cleanup-plugin Component/s: _unsorted 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.601.1557852780362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57467) missing space in "Subversion repository.This"
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57467 missing space in "Subversion repository.This" Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: image-2019-05-14-12-47-44-872.png, image-2019-05-14-12-47-58-838.png Components: subversion-plugin Created: 2019-05-14 16:47 Priority: Minor Reporter: Josh Soref jenkins/scm/SubversionSCM/enterCredential Enter the authentication information needed to connect to the Subversion repository.This information will be stored in Jenkins. Add Comment
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title Liam Newman commented on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace Okay, I was wrong about security only, it turns out to be just adding a label, which I've done for JENKINS-57111. We'll see how that goes. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.591.1557852300353%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman edited a comment on JENKINS-57111 Re: Base class setChannel does not handle exceptions from onOnline call LTS Justification:This fixes long-standing agent disconnect issues for a number of plugins, probably more than just the ones linked. This change is very low risk. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.589.155785290%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe commented on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace To justify a security patch, any user who can submit a job the uses Docker can probably use this to make a DoS attack. That's how I'm getting it - the docker container runs as root and can write to the workspace, resulting in files the jenkins user cannot delete. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.579.1557851940436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe edited a comment on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace To justify a security patch, any user who can submit a job the that uses Docker can probably use this to make a DoS attack.That's how I'm getting it - the docker container runs as root and can write to the workspace, resulting in files the jenkins user cannot delete. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.581.1557851940472%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman commented on JENKINS-57111 Re: Base class setChannel does not handle exceptions from onOnline call LTS Justification: This fixes long-standing agent disconnect issues for a number of plugins, probably more than just the ones linked. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.571.1557851760138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Labels: lts-candidate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.569.1557851640122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title Liam Newman edited a comment on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace [~jameshowe]It is my understanding the LTS backporting is reserved for security issues and we missed the window for 2.164.3. The next LTS will be out in June, but the base looks like it will be 2.176 - missed by one. I will see what I can do to get this pulled into that release. In the meanwhile, do you have test instance you can try on 2.177 and verify this is fixed? That would be very helpful. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.561.1557851460345%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman commented on JENKINS-57111 Re: Base class setChannel does not handle exceptions from onOnline call The next LTS will be out in June, but the base looks like it will be 2.176 - missed by one. I will see what I can do to get this pulled into that release. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.559.1557851400113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title Liam Newman commented on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace James Howe It is my understanding the LTS backporting is reserved for security issues and we missed the window for 2.164.3. The next LTS will be out in June, but the base looks like it will be 2.176 - missed by one. I will see what I can do to get this pulled into that release. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.557.1557850680418%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57466) non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-57466 non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue Change By: Josh Soref Assignee: Josh Soref 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199326.1557850171000.549.1557850500088%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57466) non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57466 non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-14-12-07-58-232.png Components: core Created: 2019-05-14 16:09 Priority: Minor Reporter: Josh Soref IntelliJ IDEA 2019.1.2 (Ultimate Edition) Build #IU-191.7141.44, built on May 7, 2019 JRE: 1.8.0_202-release-1483-b49 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.14.4 Steps: Open hudson.model.UpdateSite (.java) in IntelliJ Analyze > Inspect Code... File ...UpdateSite.java OK Actual results non-atomic operations on volatile field inspection Reports any non-atomic operations on volatile fields. Non-atomic operations on volatile fields are operations where the field is read and the value is used to update the field. It is possible for the value of the field to change between the read and the write, possibly invalidating the operation. The non-atomic operation can be avoided by surrounding it with a synchronized block or by making use of one of the classes from the java.util.concurrent.atomic
[JIRA] (JENKINS-57466) non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57466 non-atomic operations on volatile field inspection - hudson.model.UpdateSite.isDue Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-14-12-07-58-232.png Components: core Created: 2019-05-14 16:09 Priority: Minor Reporter: Josh Soref IntelliJ IDEA 2019.1.2 (Ultimate Edition) Build #IU-191.7141.44, built on May 7, 2019 JRE: 1.8.0_202-release-1483-b49 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.14.4 Steps: Open hudson.model.UpdateSite (.java) in IntelliJ Analyze > Inspect Code... File ...UpdateSite.java OK Actual results non-atomic operations on volatile field inspection Reports any non-atomic operations on volatile fields. Non-atomic operations on volatile fields are operations where the field is read and the value is used to update the field. It is possible for the value of the field to change between the read and the write, possibly invalidating the operation. The non-atomic operation can be avoided by surrounding it with a synchronized block or by making use of one of the classes from the java.util.concurrent.atomic
[JIRA] (JENKINS-43194) Lightweight checkout for PR merge jobs
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-43194 Lightweight checkout for PR merge jobs Change By: Liam Newman Status: Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180315.149080708.526.1557850021599%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57465) Add support for fields in RocketChat attachments
Title: Message Title Brian Jackson created an issue Jenkins / JENKINS-57465 Add support for fields in RocketChat attachments Issue Type: New Feature Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2019-05-14 15:51 Priority: Major Reporter: Brian Jackson Add support for the fields property of attachments as documented here: https://rocket.chat/docs/developer-guides/rest-api/chat/postmessage/#attachment-field-objects Possible implementation: Create a new class named Field here: https://github.com/jenkinsci/rocketchatnotifier-plugin/tree/develop/src/main/java/jenkins/plugins/rocketchatnotifier/model The java property (field + getter/setters) of type List with a proper @JsonProperty annotation would need to be added to: https://github.com/jenkinsci/rocketchatnotifier-plugin/blob/develop/src/main/java/jenkins/plugins/rocketchatnotifier/model/MessageAttachment.java The rest of the code will likely remain untouched since it's a property of MessageAttachment which is already used implicitly in classes like RocketChatClientImpl and RocketChatClientCallBuilder Add Comment
[JIRA] (JENKINS-57464) Edge case in AdminFilePathFilterTest
Title: Message Title
Wadeck Follonier updated an issue
Jenkins / JENKINS-57464
Edge case in AdminFilePathFilterTest
Change By:
Wadeck Follonier
When running under Windows (to trigger [this code|https://github.com/jenkinsci/jenkins/blob/264980c707c6cafc01369378b1e90d247561df78/core/src/main/java/jenkins/security/s2m/FilePathRuleConfig.java#L49]), and when you are unlucky enough to have a rootPath starting with {{E}}, the [regex|https://github.com/jenkinsci/jenkins/blob/264980c707c6cafc01369378b1e90d247561df78/core/src/main/java/jenkins/security/s2m/FilePathRuleConfig.java#L45] will contains two {{\\E}}, where only one is expected to close the {{\\Q}} for the quoting. This is visible in every tests from {{jenkins.security.s2m.AdminFilePathFilterTest}}. This occured in https://github.com/jenkinsci/jenkins/pull/3972. Stacktrace:{code:java}Invalid filter rule line: deny all \QC:\Jenkins\workspace\ENKINS-56575_rest_client_restart\test\target\j h499499801099785285\E\\secrets($|\\.*)java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 67\QC:\Jenkins\workspace\ENKINS-56575_rest_client_restart\test\target\j h499499801099785285\E\\secrets($|\\.*) ^ at java.util.regex.Pattern.error(Pattern.java:1957) at java.util.regex.Pattern.escape(Pattern.java:2473) at java.util.regex.Pattern.atom(Pattern.java:2200) at java.util.regex.Pattern.sequence(Pattern.java:2132) at java.util.regex.Pattern.expr(Pattern.java:1998) at java.util.regex.Pattern.compile(Pattern.java:1698) at java.util.regex.Pattern.(Pattern.java:1351) at java.util.regex.Pattern.compile(Pattern.java:1028) at jenkins.security.s2m.FilePathRuleConfig.parse(FilePathRuleConfig.java:57) at jenkins.security.s2m.FilePathRuleConfig.parse(FilePathRuleConfig.java:22) at jenkins.security.s2m.ConfigDirectory.load(ConfigDirectory.java:50) at jenkins.security.s2m.ConfigFile.get(ConfigFile.java:111) at jenkins.security.s2m.FilePathRuleConfig.checkFileAccess(FilePathRuleConfig.java:81) at jenkins.security.s2m.AdminWhitelistRule.checkFileAccess(AdminWhitelistRule.java:158) at jenkins.security.s2m.AdminFilePathFilterTest.matchBuildDir(AdminFilePathFilterTest.java:63) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:554) at
[JIRA] (JENKINS-57464) Edge case in AdminFilePathFilterTest
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-57464 Edge case in AdminFilePathFilterTest Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-14 15:33 Environment: Windows Priority: Minor Reporter: Wadeck Follonier When running under Windows (to trigger this code), and when you are unlucky enough to have a rootPath starting with E, the regex will contains two E, where only one is expected to close the Q for the quoting. This is visible in every tests from jenkins.security.s2m.AdminFilePathFilterTest. Stacktrace: Invalid filter rule line: deny all \QC:\Jenkins\workspace\ENKINS-56575_rest_client_restart\test\target\j h499499801099785285\E\\secrets($|\\.*) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 67 \QC:\Jenkins\workspace\ENKINS-56575_rest_client_restart\test\target\j h499499801099785285\E\\secrets($|\\.*) ^ at java.util.regex.Pattern.error(Pattern.java:1957) at java.util.regex.Pattern.escape(Pattern.java:2473) at java.util.regex.Pattern.atom(Pattern.java:2200) at java.util.regex.Pattern.sequence(Pattern.java:2132) at java.util.regex.Pattern.expr(Pattern.java:1998) at java.util.regex.Pattern.compile(Pattern.java:1698) at java.util.regex.Pattern.(Pattern.java:1351) at java.util.regex.Pattern.compile(Pattern.java:1028) at jenkins.security.s2m.FilePathRuleConfig.parse(FilePathRuleConfig.java:57) at jenkins.security.s2m.FilePathRuleConfig.parse(FilePathRuleConfig.java:22) at
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc updated JENKINS-57324 Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Cyrille Le Clerc Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.519.1557847920743%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc updated JENKINS-57324 Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Cyrille Le Clerc Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.517.1557847920708%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57458) Trigger job by creation of new p4 labels
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57458 Trigger job by creation of new p4 labels Change By: Karl Wirth Labels: P4_SUPPORT 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199318.1557843577000.514.1557847800145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57462) Upload the bio with an avatar in jenkins.io
Title: Message Title Prastik Gyawali updated JENKINS-57462 Jenkins / JENKINS-57462 Upload the bio with an avatar in jenkins.io Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199322.1557847038000.511.1557847680151%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57462) Upload the bio with an avatar in jenkins.io
Title: Message Title Prastik Gyawali updated JENKINS-57462 Jenkins / JENKINS-57462 Upload the bio with an avatar in jenkins.io Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199322.1557847038000.512.1557847680179%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57458) Trigger job by creation of new p4 labels
Title: Message Title
Karl Wirth commented on JENKINS-57458
Re: Trigger job by creation of new p4 labels
Hi Matthew Dews. You could possibly do this with a paramaterized job and Perforce command triggers. (1) Create a Jenkins job that takes label as a parameter and builds at that label. (2) Create a post command trigger on 'tag' and 'label' that fires starts the job passing the label as the paramater. Note: The difficult part of this solution is deciding what paths to build. If your the label contains the exact paths to build you could use that to build up the workspace. More on Perforce command triggers can be found here: https://www.perforce.com/manuals/p4sag/Content/P4SAG/scripting.triggers.order.html And below is a really simple script I have used in the past to fire a Jenkins job:
$ cat /scripts/fire_jenkins_job.py
import jenkins
import sys
url = "" class="code-quote" style="color: #009100">'JenkinsServer:8080'
job = 'Freestyle_Paramaterized'
j = jenkins.Jenkins(url)
j.build_job(job, parameters={'LABEL':'label1'})
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199318.1557843577000.508.1557847620247%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated JENKINS-57460 Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Resolution: Fixed Status: Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.506.1557847620180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57458) Trigger job by creation of new p4 labels
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57458 Trigger job by creation of new p4 labels Change By: Karl Wirth Assignee: Karl Wirth 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199318.1557843577000.510.1557847620270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated JENKINS-57460 Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.505.1557847560089%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57463) Start discussion in the respective pipeline-authoring channel and mailing list
Title: Message Title Prastik Gyawali assigned an issue to Prastik Gyawali Jenkins / JENKINS-57463 Start discussion in the respective pipeline-authoring channel and mailing list Change By: Prastik Gyawali Assignee: Devin Nusbaum Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199323.1557847154000.504.1557847200277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57463) Start discussion in the respective pipeline-authoring channel and mailing list
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57463 Start discussion in the respective pipeline-authoring channel and mailing list Issue Type: Task Assignee: Devin Nusbaum Components: promoted-builds-plugin Created: 2019-05-14 15:19 Priority: Minor Reporter: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199323.1557847154000.502.1557847200249%40Atlassian.JIRA. For more options,
[JIRA] (JENKINS-57453) Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server
Title: Message Title Jeff Thompson commented on JENKINS-57453 Re: Invalid encoded sequence when connecting Windows Agent with Bitvise SSH Server This looks like a duplicate of JENKINS-44408, including the use of Bitvise. There are no solutions on that one, either. This one seems to be using Bitvise successfully, though, JENKINS-54394. The [Troubleshooting|https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md] page for ssh-slaves-plugin mentions this error and might be useful. This [StackOverflow post|https://stackoverflow.com/questions/44768139/unable-to-connect-to-slave-from-master-invalid-encoded-sequence-encountered], mentions the error, but it's not clear how it was 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199311.1557833375000.497.1557847140385%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title Mike Alberghini closed an issue as Fixed Jenkins / JENKINS-57264 accessing file credential in pipeline causes nullPointerException Change By: Mike Alberghini Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199029.1556649159000.500.1557847140423%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57264) accessing file credential in pipeline causes nullPointerException
Title: Message Title Mike Alberghini commented on JENKINS-57264 Re: accessing file credential in pipeline causes nullPointerException Updating Structs to 1.19 seems to have fixed the problem. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199029.1556649159000.493.1557847080317%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57462) Upload the bio with an avatar in jenkins.io
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57462 Upload the bio with an avatar in jenkins.io Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-14 15:17 Priority: Minor Reporter: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199322.1557847038000.492.1557847080287%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57460) Create a new design document from the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document from the original proposal. Change By: Prastik Gyawali Summary: Create a new design document of from the original proposal. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.484.1557846900079%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57426) Make pipeline-model-extensions dependency optional
Title: Message Title Emilio Escobar updated JENKINS-57426 Jenkins / JENKINS-57426 Make pipeline-model-extensions dependency optional Change By: Emilio Escobar Status: In Review Resolved Resolution: Fixed Released As: 1.27 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199238.1557742883000.483.1557846540223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57461) Pipeline checkout stage fails with "java.io.IOException: Unable to serialize"
Title: Message Title Markus Schulte created an issue Jenkins / JENKINS-57461 Pipeline checkout stage fails with "java.io.IOException: Unable to serialize" Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2019-05-14 15:07 Environment: Jenkins ver. 2.164.3 with OpenJDK "11.0.3+1-Debian-1bpo91" git-client-plugin v2.7.7 and v3.0.0-beta9 Jenkins slave running OpenJDK11 Priority: Minor Reporter: Markus Schulte Hi, I have an automated Jenkins setup. While provisioning, I add as part of init.groovy.d an SSH key as a new SSH key as credentials to the Jenkins master (new BasicSSHUserPrivateKey(..., new BasicSSHUserPrivateKey.FileOnMasterPrivateKeySource(sshKeyPath))). Furthermore, I add a job using this credentials, and I setup Jenkins slaves automatically. When running my job the first time (which will run on a slave), I get the following exception java.io.NotSerializableException: com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey$FileOnMasterPrivateKeySource at java.base/java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1185) at java.base/java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1553) at java.base/java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1510) at java.base/java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1433) at java.base/java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1179) at java.base/java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1379) at
[JIRA] (JENKINS-57460) Create a new design document of the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document of the original proposal. Change By: Prastik Gyawali - Duplicate the original proposal into a new document open for redesign redesigning .- Add all the necessary changes as per the discussion mentors' feedback. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.472.1557845220326%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document of the original proposal.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57460 Create a new design document of the original proposal. Change By: Prastik Gyawali - Duplicate the original proposal into a new document and open it for redesigning.- Add all the necessary changes as per mentors' feedback. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199320.1557845087000.473.1557845220355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57460) Create a new design document of the original proposal.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57460 Create a new design document of the original proposal. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-14 14:44 Priority: Minor Reporter: Prastik Gyawali Duplicate the original proposal into a new document open for redesign. Add all the necessary changes as per the discussion Add Comment
[JIRA] (JENKINS-57457) GSoC '19: promoted builds plugin for pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promoted builds plugin for pipeline. Community bonding tasks Change By: Prastik Gyawali Summary: GSoC '19: promotion promoted builds plugin for Jenkins' pipeline. Community Bonding bonding tasks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199317.1557843061000.447.155780167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57457) GSoC '19: promotion plugin for Jenkins' pipeline. Community Bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promotion plugin for Jenkins' pipeline. Community Bonding tasks Change By: Prastik Gyawali Summary: GSoC '19: promoted builds promotion plugin for Jenkins' pipeline. Community bonding Bonding tasks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199317.1557843061000.446.155780138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57457) GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promotion plugin for Jenkins' pipeline. Community bonding tasks Change By: Prastik Gyawali Summary: GSoC '19: promoted builds promotion plugin for Jenkins' pipeline. Community bonding tasks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199317.1557843061000.448.155780177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57459) For type missingOverride, base class is reported instead of derived class
Title: Message Title Jeremy Martinez updated an issue Jenkins / JENKINS-57459 For type missingOverride, base class is reported instead of derived class Change By: Jeremy Martinez Reporting the base class is misleading because the error occurs in the derived classJenkins reports:|unchanged|[/home/users/host/gitlab/ gen6linux project / mobis/ source/frameworks/broadcast/IMUtils/data/DataClassBase.h|http://10.114.170.101:8060/job/HDData%20Gen6/9/cppcheckResult/source.18]|[99|http://10.114.170.101:8060/job/HDData%20Gen6/9/cppcheckResult/source.18#89]|style|missingOverride|false|The function 'ChangeInfo' overrides a function in a base class but is not marked with a 'override' specifier.|cppcheck-htmlreport reports:|[/home/users/host/gitlab/ gen6linux project / mobis/ source/apps/av/QtCommon/src/system/data/AVStatusIconInfo.h|file:///home/jeremy/Desktop/report/4.html]||[26|file:///home/jeremy/Desktop/report/4.html#line-26]|missingOverride| |style|The function 'ChangeInfo' overrides a function in a base class but is not marked with a 'override' specifier.| The xml file created by cppcheck shows ' ChangeInfo ' overrides a function in a base class but is not marked with a' override ' specifier." verbose="The function' ChangeInfo ' overrides a function in a base class but is not marked with a' override ' specifier."> gen6linux project / mobis/ source/apps/av/QtCommon/src/system/data/AVStatusIconInfo.h" line="26" info="Function in derived class"/> gen6linux project / mobis/ source/frameworks/broadcast/IMUtils/data/DataClassBase.h" line="99" info="Virtual function in base class"/> The behavior of the cppcheck plugin is incorrect, and the behavior of cppcheck-htmlreport is correct. Add Comment
[JIRA] (JENKINS-52806) Pipeline: Parallel syncs don't set environment variables properly.
Title: Message Title Matthew Dews commented on JENKINS-52806 Re: Pipeline: Parallel syncs don't set environment variables properly. Thanks Karl Wirth. We'd really like to swith to the declarative pipeline from freestyle jobs and use more of the p4 plugin but this is the main feature holding us back. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192727.153298856.424.1557843900251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57459) For type missingOverride, base class is reported instead of derived class
Title: Message Title Jeremy Martinez created an issue Jenkins / JENKINS-57459 For type missingOverride, base class is reported instead of derived class Issue Type: Bug Assignee: Marco Steffan Components: cppcheck-plugin Created: 2019-05-14 14:23 Environment: Jenkins 2.164.3 Cppcheck Plug-in 1.24 Ubuntu 16.04 Priority: Minor Reporter: Jeremy Martinez Reporting the base class is misleading because the error occurs in the derived class Jenkins reports: unchanged /home/users/host/gitlab/gen6linux/mobis/source/frameworks/broadcast/IMUtils/data/DataClassBase.h 99 style missingOverride false The function 'ChangeInfo' overrides a function in a base class but is not marked with a 'override' specifier. cppcheck-htmlreport reports:
[JIRA] (JENKINS-57457) GSoC '19: promoted builds plugin for pipeline. Community bonding tasks
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57457 GSoC '19: promoted builds plugin for pipeline. Community bonding tasks Change By: Prastik Gyawali Summary: List of tasks to be completed during the community bonding period GSoC '19 : promoted builds plugin for pipeline. Community bonding tasks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199317.1557843061000.421.1557843840646%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title
sudhakar sidhu commented on JENKINS-51138
Re: Links inside LoadRunner Analysis Reports not working [Performance Report]
Hello, We are having same issue running System.setProperty("hudson.model.DirectoryBrowserSupport.CSP", "") in script console resolved issue temporarily every time Jenkins is re-started its not working. Can you provide arguments that we can add to Jenkins.xml to resolve issue permanently please. Regards, Sudhakar
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190431.1525438738000.413.1557843660655%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title sudhakar sidhu reopened an issue Jenkins / JENKINS-51138 Links inside LoadRunner Analysis Reports not working [Performance Report] Change By: sudhakar sidhu Resolution: Incomplete 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190431.1525438738000.417.1557843660880%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57458) Trigger job by creation of new p4 labels
Title: Message Title Matthew Dews created an issue Jenkins / JENKINS-57458 Trigger job by creation of new p4 labels Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2019-05-14 14:19 Priority: Minor Reporter: Matthew Dews I'd like to accomplish the following: Create a new label in Helix Jenkins job picks up that a new label was created and does a build at that label/changelist Other submissions do not trigger the job to run As far as I can tell there's no way to accomplish this with the current features of P4 Jenkins. Is that correct or is there something I'm missing? Add Comment
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title sudhakar sidhu assigned an issue to Daniel Gront Jenkins / JENKINS-51138 Links inside LoadRunner Analysis Reports not working [Performance Report] Change By: sudhakar sidhu Assignee: sudhakar sidhu Daniel Gront 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190431.1525438738000.408.1557843420499%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51138) Links inside LoadRunner Analysis Reports not working [Performance Report]
Title: Message Title sudhakar sidhu assigned an issue to sudhakar sidhu Jenkins / JENKINS-51138 Links inside LoadRunner Analysis Reports not working [Performance Report] Change By: sudhakar sidhu Assignee: Rolando-Mihai Vlad sudhakar sidhu 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190431.1525438738000.404.1557843420315%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title
kyle ian edited a comment on JENKINS-55214
Re: NullPointerException when starting a pipeline in a multibranch project
[~p4karl]Steps I took while investigating: 1. Updated `description` to have comma after value - all sibiling pipelines still failed with NPE 2. Removed `ParameterDefinitionProperty` from pipeline props entirely - offending pipeline ran successfully without prop with no NPE, sibiling pipelines failed with NPE still 3. Added parameterDefinitionProperty back, removing redundant `name` 4. Rescanned multibranch pipeline after (3) 5. All sibiling multibranch pipelines run successfully without NPEExample: {code:java}properties([ pipelineTriggers([p4Trigger()]), [$class: 'ParametersDefinitionProperty',parameterDefinitions:[ [$class: 'hudson.model.BooleanParameterDefinition', name: 'I_AM_A_BOOL_PARAMETER_NAME', name: 'I_AM_AN_UNNECESSARY_REDUNDANT_BOOL_PARAMETER_NAME', description: 'I am a description that is missing a comma after my string ends, which will be detected by linting on a given branch's branchs pipeline, but other pipelines belonging to the same parent multibranch pipeline will fail with JENKINS-55214 NPE until this is corrected.' defaultValue: false]] ]]){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, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.400.1557843360383%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title kyle ian commented on JENKINS-55214 Re: NullPointerException when starting a pipeline in a multibranch project Karl Wirth Steps I took while investigating: 1. Updated `description` to have comma after value - all sibiling pipelines still failed with NPE 2. Removed `ParameterDefinitionProperty` from pipeline props entirely - offending pipeline ran successfully without prop with no NPE, sibiling pipelines failed with NPE still 3. Added parameterDefinitionProperty back, removing redundant `name` 4. Rescanned multibranch pipeline after (3) 5. All sibiling multibranch pipelines run successfully without NPE Example: properties([ pipelineTriggers([p4Trigger()]), [$class: 'ParametersDefinitionProperty', parameterDefinitions: [ [$class: 'hudson.model.BooleanParameterDefinition', name: 'I_AM_A_BOOL_PARAMETER_NAME', name: 'I_AM_AN_UNNECESSARY_REDUNDANT_BOOL_PARAMETER_NAME', description: 'I am a description that is missing a comma after my string ends, which will be detected by linting on a given branch's pipeline, but other pipelines belonging to the same parent multibranch pipeline will fail with JENKINS-55214 NPE until this is corrected.' defaultValue: false] ] ] ]) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.396.1557843360303%40Atlassian.JIRA.
[JIRA] (JENKINS-57457) List of tasks to be completed during the community bonding period GSoC '19
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57457 List of tasks to be completed during the community bonding period GSoC '19 Issue Type: Epic Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-05-14 14:11 Priority: Minor Reporter: Prastik Gyawali Subsequently, add tasks and bugs to be fixed during the community bonding period. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57456) User language prefer setting
Title: Message Title Rick created an issue Jenkins / JENKINS-57456 User language prefer setting Issue Type: New Feature Assignee: Rick Components: locale-plugin Created: 2019-05-14 14:08 Priority: Minor Reporter: Rick Allow different users have their own language setting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
