[JIRA] (JENKINS-62041) PrioritySorter doesn't work as expected. High Prio jobs last in queue
Title: Message Title Tomasz Koźlak commented on JENKINS-62041 Re: PrioritySorter doesn't work as expected. High Prio jobs last in queue I solved the problem by downgrading Pipepilne plugin from 2.6 to 2.5. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205932.1587715678000.19227.1588141260108%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title
tharilya updated an issue
Jenkins / JENKINS-61743
Customizable workspace and working directory of docker.images.inside()
Change By:
tharilya
Hello,I want to have a possibility to change the "workdir" & "volume" destination directory within the image which will be started by the "docker.image.inside"-command.The current problem is that the path to the mount-destination within the container and the working directory are hard-coded: Hard-coded volumes: * [https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L193] * [https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L194]Hard-coded Work-Dir (parameter 4 is always "ws" == "workspace"): * [https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L198]So the "default" image.inside command (on windows) results in something like:{code:java}docker run -t -d -w ${WORKSPACE} -v ${WORKSPACE}:${WORKSPACE} -v ${WORKSPACE}@tmp:${WORKSPACE}@tmp{code}It's not "clean" because the destination in the started container is hardcoded as the same directory of the workspace. This can cause issues with rights, existing drives, and other stuff.Feature-Request in short: I want to have the possibility to change the working directory and the volume mounting directory which points into the started container. * The default behavior can be kept as it isI have two proposals (from the user side of view) attached in (proposal.txt) It would be nice to make the "image.inside" command will result in something like this: {code:java} docker run -t -d -w ${IMG_WORK_DIR} -v ${HOST_WORKSPACE}:${IMG_WORKSPACE} -v ${HOST_WORKSPACE}@tmp:${IMG_WORKSPACE}@tmp{code} Background how I ran into this: My System is a Jenkins-Master on a Linux-Server. I have two Slaves one Linux & one Windows. * all this are real physical machines, no VM's or other stuff * The Windows-Slave has a Windows-Server 2016 OSIn my case the "workspace" of Jenkins is on the "E"-Drive. If you run the attached "example.txt" you can reproduce the error on every jenkins * of course on my machine, dont need the "ws(...)" partThe Error is an error on the docker run command because docker is unable to create a new Drive, as mounting point in the created container. * I tried very much to create a "E"-Drive as volume in the Image, but I wasn't able to make it ** I tried symlinks, registry changes and stuff ... * after all this I looked into the Code of the Plugin and thought this should be changeable ...All in all I think the origin of the problem are the hard-coded directories within the containers.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary updated an issue Jenkins / JENKINS-61992 Adding Veracode Scan to Veracode Jenkins Open source project Change By: Shihaaz Buhary It is better to scan our Veracode Jenkins open source plugin in platform before we are releasing into Jenkins Marketplace.The best option is adding Veracode scan into GitHub Jenkins build pipeline, but not sure it is feasible or not.The other options is to adding script to do it by download binary from Jenkins Artifcatory, or scan it manually before releasing it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205883.1587480871000.19228.1588141440159%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Sprint: Declarative backlog Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205572.1585581551000.19235.1588143120233%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Sprint: Declarative backlog Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205572.1585581551000.19234.1588143120203%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-62088 Plugin manager loading incorrect fonts Issue Type: Task Assignee: Unassigned Components: core Created: 2020-04-29 07:15 Labels: ux ux-sig Priority: Minor Reporter: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary commented on JENKINS-61992 Re: Adding Veracode Scan to Veracode Jenkins Open source project I have added a GitHub workflow to our Jenkins open-source code-base and included the Veracode Scan by adding a stage. This worked successfully for pushes and pull requests. Please find these changes in the below PR. PR: https://github.com/jenkinsci/veracode-scan-plugin/pull/12 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205883.1587480871000.19229.1588141500051%40Atlassian.JIRA.
[JIRA] (JENKINS-61992) Adding Veracode Scan to Veracode Jenkins Open source project
Title: Message Title Shihaaz Buhary resolved as Done Jenkins / JENKINS-61992 Adding Veracode Scan to Veracode Jenkins Open source project Change By: Shihaaz Buhary Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205883.1587480871000.19230.1588141560103%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-62088 Plugin manager loading incorrect fonts Change By: Tim Jacomb Raised in ux-sig gitter https://gitter.im/jenkinsci/ux-sig?at=5ea09e52dc6ae2132b438ed1The filter / search of plugin manager is using the Roboto font and the button is using system default rather than our full list of fallbacks,on my system the button looks fine but on the reporters the button and link button fonts looked different Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205996.1588144537000.19238.1588144680205%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-62088 Plugin manager loading incorrect fonts Change By: Tim Jacomb Assignee: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205996.1588144537000.19239.1588144680248%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb started work on JENKINS-62088 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205996.1588144537000.19240.1588144680263%40Atlassian.JIRA.
[JIRA] (JENKINS-62088) Plugin manager loading incorrect fonts
Title: Message Title Tim Jacomb updated JENKINS-62088 Jenkins / JENKINS-62088 Plugin manager loading incorrect fonts Change By: Tim Jacomb Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205996.1588144537000.19241.1588144680278%40Atlassian.JIRA.
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Ryan Slobojan updated JENKINS-62043 This has now been merged and released: https://github.com/jenkinsci/ec2-plugin/releases/tag/ec2-1.50.1 Jenkins / JENKINS-62043 EC2 plugin stops builds on ALL nodes Change By: Ryan Slobojan Status: In Review Resolved Resolution: Fixed Released As: 1.50.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-62062) EC2 Plugin Null Pointer Exception IsAcceptingTask
Title: Message Title Ryan Slobojan updated JENKINS-62062 This has now been merged and released: https://github.com/jenkinsci/ec2-plugin/releases/tag/ec2-1.50.1 Jenkins / JENKINS-62062 EC2 Plugin Null Pointer Exception IsAcceptingTask Change By: Ryan Slobojan Status: In Review Resolved Resolution: Fixed Released As: 1.50.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Alex Miller commented on JENKINS-61480 Re: Dark Theme Félix Queiruga Balado it looks like the neo2 maintainer removed dark mode the day after you posted that, saying it looked bad and was unmaintainable: https://github.com/TobiX/jenkins-neo2-theme/commit/fc74c10f27d66e25c65f436a3ac7ad68dc652caa I look forward to the day when jenkins can match the rest of my dashboards in dark mode, will be glad to test prerelease work when it's available. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205164.1584202104000.19406.1588172460199%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck updated JENKINS-62065 Jenkins / JENKINS-62065 The bread crumb navigation on the top of the job is not responding after clicking Apply Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205964.1588002509000.19357.1588166880966%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck started work on JENKINS-62065 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205964.1588002509000.19353.1588166880706%40Atlassian.JIRA.
[JIRA] (JENKINS-62094) Extract unrelated elements in BS3 grid css file
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62094 Extract unrelated elements in BS3 grid css file Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-04-29 14:22 Labels: UX user-experience Priority: Minor Reporter: Ulli Hafner As already mentioned in JENKINS-61326, Jenkins bundles a customized Boostrap 3 grid that should be replaced in the long term. In order to make this transition easier, the current patched Bootstrap 3 grid should be cleaned up so that the file actually only contains the grid elements. Additional elements like breakpoints and CSS styling of Jenkins components should be moved to corresponding CSS files. Add Comment
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Govind Sureka commented on JENKINS-61520 Re: At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Hello Anda- Thanks, we updated(Deleted and created a new node of Windows services type) the Node but still the issue persists. Please advise. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205217.1584601273000.19410.1588172880118%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names I was planning to put together a PR last night and then I had to stop. One question is: would it be worth it to read the full Gradle model to figure out the resolved and configured module names, or should we just start with a way to detect the common base directory name between the report file and the nearest build.gradle file? The base directory would work for the most common scenario, but it's possible to redefine the module name or the $buildDir in which case it might not even be moduleA/build/. I'll take a first pass at the simple case, and see if it proves useful. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19419.1588174560193%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Mez Pahlan commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 I am a very new to Docker so please excuse me if I am doing something wrong but I was following the CWP demo and running the commands from the Makefile. I've ran the commands from buildInDocker: .copySource .buildInDocker .buildImage. Same error output at the very start but the pipeline did execute successfully after that. Am I doing something wrong? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199254.1557791602000.19360.1588167960228%40Atlassian.JIRA.
[JIRA] (JENKINS-62094) Extract unrelated elements in BS3 grid css file
Title: Message Title Ulli Hafner commented on JENKINS-62094 Re: Extract unrelated elements in BS3 grid css file See https://github.com/uhafner/jenkins/pull/1 and https://github.com/jenkinsci/jenkins/pull/4693. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206004.1588170143000.19367.1588170300051%40Atlassian.JIRA.
[JIRA] (JENKINS-33974) Add option to verify "secret" token
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-33974 Add option to verify "secret" token Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/github-plugin/releases/tag/v1.21.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.169465.1459504593000.19422.1588174620422%40Atlassian.JIRA.
[JIRA] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title
Randall Becker commented on JENKINS-20947
Re: Failed to monitor for Free Swap Space
I also just started experiencing this situation under 2.222.3 under Java 1.8_242 under z/OS USS. This was after increasing the Node SSH timeout to something large. The Node log is showing: ERROR: Failed to monitor for Response Time java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)}} {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}} ERROR: Failed to monitor for Free Disk Space java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}} {{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}} ERROR: Failed to monitor for Free Temp Space java.util.concurrent.TimeoutException {{ at hudson.remoting.Request$1.get(Request.java:316)}} {{ at hudson.remoting.Request$1.get(Request.java:240)}} {{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}} {{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}} at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306) ... in a loop until the SSH timeout hits, which then cancels the job by closing the connection. Are we possibly missing a dependency on the server? The server only has a straight up JDK with no additional tools (other than git and perl).
Add Comment
[JIRA] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title
Randall Becker edited a comment on JENKINS-20947
Re: Failed to monitor for Free Swap Space
I also just started experiencing this situation under 2.222.3 under Java 1.8_242 under z/OS USS. This was after increasing the Node SSH timeout to something large. The Node log is showing:{{ERROR: Failed to monitor for Response Time}}{{java.util.concurrent.TimeoutException}}{{ at hudson.remoting.Request$1.get(Request.java:316)}}{{ at hudson.remoting.Request$1.get(Request.java:240)}}{{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}{{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}{{ at hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)}}{{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}}{{ERROR: Failed to monitor for Free Disk Space}}{{java.util.concurrent.TimeoutException}}{{ at hudson.remoting.Request$1.get(Request.java:316)}}{{ at hudson.remoting.Request$1.get(Request.java:240)}}{{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}{{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}{{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}}{{ at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306)}}{{ERROR: Failed to monitor for Free Temp Space}}{{java.util.concurrent.TimeoutException}}{{ at hudson.remoting.Request$1.get(Request.java:316)}}{{ at hudson.remoting.Request$1.get(Request.java:240)}}{{ at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)}}{{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitorDetailed(AbstractAsyncNodeMonitorDescriptor.java:114)}}{{ at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:78)}}{{at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:306) }}{{ ...}}in a loop until the SSH timeout hits, which then cancels the job by closing the connection. Are we possibly missing a dependency on the server? The server only has a straight up JDK with no additional tools (other than git and perl).
Add Comment
[JIRA] (JENKINS-61057) execute a GroovyScript
Title: Message Title MicroNova MicroNova updated JENKINS-61057 Jenkins / JENKINS-61057 execute a GroovyScript Change By: MicroNova MicroNova Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204537.158143413.19369.1588170900239%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated JENKINS-57351 Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199127.1557217283000.19469.1588175162484%40Atlassian.JIRA.
[JIRA] (JENKINS-57351) Support for making Jenkins a "GitHub App"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57351 Support for making Jenkins a "GitHub App" Change By: Jesse Glick Released As: https://github.com/jenkinsci/github-branch-source-plugin/releases/tag/github-branch-source- 2.7. 0 1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.199127.1557217283000.19445.1588175162146%40Atlassian.JIRA.
[JIRA] (JENKINS-48762) Unsigned Webhooks are always accepted
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-48762 Unsigned Webhooks are always accepted Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.187529.1514927303000.19441.1588174860413%40Atlassian.JIRA.
[JIRA] (JENKINS-48012) Webhook signature checking is skipped if incoming webhook has no signature
Title: Message Title Jesse Glick updated JENKINS-48012 Jenkins / JENKINS-48012 Webhook signature checking is skipped if incoming webhook has no signature Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/github-plugin/releases/tag/v1.29.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.186551.1510689021000.19434.1588174800588%40Atlassian.JIRA.
[JIRA] (JENKINS-62093) Using GitHub Webhooks with Jenkins where CSRF-Protection is enabled
Title: Message Title Thorsten Klein closed an issue as Cannot Reproduce Jenkins / JENKINS-62093 Using GitHub Webhooks with Jenkins where CSRF-Protection is enabled Change By: Thorsten Klein Status: Open Closed Assignee: Kirill Merkushev Thorsten Klein Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206002.1588164972000.19503.1588176780249%40Atlassian.JIRA.
[JIRA] (JENKINS-60859) Support type values that do not contain a dot in CheckStyle parser
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60859 Support type values that do not contain a dot in CheckStyle parser Change By: Ulli Hafner Labels: help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.204233.1579861105000.19375.1588171260750%40Atlassian.JIRA.
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55911 java lint warning about annotation processor is not recognized Change By: Ulli Hafner Labels: help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.197314.1549031392000.19381.1588171260824%40Atlassian.JIRA.
[JIRA] (JENKINS-56815) Make "note" lines available in warning details
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56815 Make "note" lines available in warning details Change By: Ulli Hafner Labels: help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198468.1553949491000.19372.1588171260711%40Atlassian.JIRA.
[JIRA] (JENKINS-56915) Clang-Tidy reporting does not work for errors without line dependency
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56915 Clang-Tidy reporting does not work for errors without line dependency Change By: Ulli Hafner Labels: help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198588.155446954.19383.1588171260863%40Atlassian.JIRA.
[JIRA] (JENKINS-56613) MSBuild parser reports errors when message contains tool instead of file
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56613 MSBuild parser reports errors when message contains tool instead of file Change By: Ulli Hafner Labels: help-wanted newbie-friendly testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.198237.1552983409000.19379.1588171260794%40Atlassian.JIRA.
[JIRA] (JENKINS-48012) Webhook signature checking is skipped if incoming webhook has no signature
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48012 Webhook signature checking is skipped if incoming webhook has no signature Change By: Jesse Glick Labels: security Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.186551.1510689021000.19427.1588174740404%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Jesse Glick commented on JENKINS-60480 Re: github is deprecating basic authentication using password You can certainly use a PAT, but note that JENKINS-57351 was released which allows github-branch-source to use App authentication. Not currently available for non-multibranch use cases, though it has been proposed to push this code down into the github-api library. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203567.1576268869000.19493.1588175280338%40Atlassian.JIRA.
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Alex Earl commented on JENKINS-62079 Re: No way to email just a PR's owner Jenkins is full of such extension points. It makes it very extendable. I do not know about the owner of the primary patch being lost, but there is no recipient provider that I know about that does what you want. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205984.1588084934000.19508.1588177980175%40Atlassian.JIRA.
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Brian J Murrell commented on JENKINS-62079 Re: No way to email just a PR's owner I do not know about the owner of the primary patch being lost Not lost, but not identifiable as the single individual for which the patches in the PR belong, among the many authors of the perhaps many patches that got added from a merged branch (i.e. again, when say, merging master to a PR). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205984.1588084934000.19602.1588181220134%40Atlassian.JIRA.
[JIRA] (JENKINS-62096) Migrate History graph to ECharts
Title: Message Title David S created an issue Jenkins / JENKINS-62096 Migrate History graph to ECharts Issue Type: Improvement Assignee: David S Components: junit-plugin Created: 2020-04-29 18:35 Labels: user-experience plugin chart Priority: Minor Reporter: David S Currently the history graphs for test results are generated on the server side. This requires a non-headless jdk to be installed in order to work correctly (when using openjdk). This is an issue since installing the non-headless jdk contains a lot of unnecessary dependencies and X-11 components which are definitely not required on a server. My proposal is to migrate the graphs to the [ECharts API|https://plugins.jenkins.io/echarts-api/] as already used by the warnings-ng plugin. This would allow for a simpler server side code, allow access to the history data via an api and get rid of the X-11 dependencies that a non-headless jdk comes with. I'm planning to do the implementation but I'm happy to hear your thoughts on this topic and if a PR for this would make sense.
[JIRA] (JENKINS-62043) EC2 plugin stops builds on ALL nodes
Title: Message Title Ryan Slobojan commented on JENKINS-62043 Re: EC2 plugin stops builds on ALL nodes Side note: this bug would also impact anyone who upgraded to 1.50 following the suggested process (kill all executors, upgrade plugin, restart) upon reboot of Jenkins if executors were not all wiped out before shutdown - because this is a serialization bug, any deserialization was failing with 1.50 (we just ran into this on a Jenkins server I managed, and the upgrade to 1.50.1 fixed it on restart and all existing executors started working immediately) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205934.1587719449000.19633.1588187040325%40Atlassian.JIRA.
[JIRA] (JENKINS-62101) Remove UI assertions from JobActionITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62101 Remove UI assertions from JobActionITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:38 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62102) Remove UI assertions from MiscIssueRecorederITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62102 Remove UI assertions from MiscIssueRecorederITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:39 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names Makes sense - I've pushed the simple case(s) with just looking for parent directory names of build.gradle, to my fork (haven't opened a PR yet), and also working on a way to parse the rootProject name from settings.gradle. The rootProject case might be worth resolving, because most Jenkins projects will checkout their SCM into the workspace directory which matches the Jenkins job name (usually). So this might treat anything in the root project as if moduleName=jenkins-job-name. You can check out current progress here: https://github.com/jhansche/analysis-model/commits/pr-62087 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19687.1588190580159%40Atlassian.JIRA.
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Alex Earl commented on JENKINS-62079 Re: No way to email just a PR's owner I don't know of any way to identify that from the email-ext plugin perspective. Which plugin are you using for SCM? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205984.1588084934000.19610.1588181760115%40Atlassian.JIRA.
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-62097 Permit multiple webhook secrets to be registered Issue Type: Improvement Assignee: Jesse Glick Components: github-plugin Created: 2020-04-29 18:48 Priority: Minor Reporter: Jesse Glick It is good that you can verify signatures of webhooks from GitHub (JENKINS-33974) but an unfortunate restriction that you are limited to listing only one webhook secret. This would make it more difficult to configure multiple webhooks, or mixtures of manual webhooks and Apps, on a single Jenkins service. It would be useful to be able to set a list of webhook secrets, where an incoming hook would just need to match one of them. Add Comment
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Ulli Hafner commented on JENKINS-62087 Re: Detect Gradle module names I think it makes sense to start with the simple case. I think for the other approaches we also tried to be as simple as possible. We can refine that later on if someone encounters problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19630.1588186860151%40Atlassian.JIRA.
[JIRA] (JENKINS-62098) Remove UI assertions from GitBlamerITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62098 Remove UI assertions from GitBlamerITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:32 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Brian J Murrell commented on JENKINS-62079 Re: No way to email just a PR's owner I am using the github-branch-source plugin with pipelines. Ultimately the problem is that (AFAICT) the most useful recipientProvider to use with a single PR is: developers Sends email to all the people who caused a change in the change set. But as I mentioned before that list gets polluted with every author of every patch that was merged from a parent branch when doing a merge to get one's PR up-to-date with it's parent branch. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205984.1588084934000.19617.1588182900112%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixing#createProject() does not call Jenkins#checkGoodName
Title: Message Title Calvin Park commented on JENKINS-61956 Re: ItemGroupMixing#createProject() does not call Jenkins#checkGoodName Daniel Beck Please change the title of this ticket to ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205840.1587161495000.19660.1588188840051%40Atlassian.JIRA.
[JIRA] (JENKINS-62099) Remove UI assertions from DryITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62099 Remove UI assertions from DryITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:34 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62100) CLONE - Remove UI assertions from GitBlamerITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62100 CLONE - Remove UI assertions from GitBlamerITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:34 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62103) Remove UI assertions from AffecteddFilesResolverITest
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62103 Remove UI assertions from AffecteddFilesResolverITest Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 19:41 Labels: testing-course Priority: Minor Reporter: Ulli Hafner Several integration tests of the warnings plugin verify the plugin behavior by inspecting the UI using HTML Unit. This approach has some drawbacks: the integration tests are much slower and they are error prone (and sometimes are flaky as well). So it makes sense to replace the assertion part of these test with model based assertions. In the end, the corresponding page objects can be deleted as well. For a couple of scenarios, real UI tests can be created that use a real Jenkins instance with unmodified class loading behavior. Since UI tests are now part of the plugin, they still can ensure the quality of pull requests. Add Comment
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick started work on JENKINS-62097 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206007.1588186126000.19628.1588186320085%40Atlassian.JIRA.
[JIRA] (JENKINS-62103) Remove UI assertions from AffectedFilesResolverITest
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62103 Remove UI assertions from AffectedFilesResolverITest Change By: Ulli Hafner Summary: Remove UI assertions from AffecteddFilesResolverITest AffectedFilesResolverITest Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206014.1588189316000.19667.1588189380133%40Atlassian.JIRA.
[JIRA] (JENKINS-62099) Remove UI assertions from DryITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62099 Remove UI assertions from DryITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206010.1588188853000.19669.1588189380436%40Atlassian.JIRA.
[JIRA] (JENKINS-62101) Remove UI assertions from JobActionITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62101 Remove UI assertions from JobActionITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206012.1588189133000.19672.1588189440208%40Atlassian.JIRA.
[JIRA] (JENKINS-62100) Remove UI assertions from ChartsITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62100 Remove UI assertions from ChartsITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206011.1588188875000.19670.1588189440119%40Atlassian.JIRA.
[JIRA] (JENKINS-62098) Remove UI assertions from GitBlamerITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62098 Remove UI assertions from GitBlamerITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206009.1588188775000.19671.1588189440177%40Atlassian.JIRA.
[JIRA] (JENKINS-62103) Remove UI assertions from AffectedFilesResolverITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62103 Remove UI assertions from AffectedFilesResolverITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206014.1588189316000.19668.1588189380201%40Atlassian.JIRA.
[JIRA] (JENKINS-60149) Add UI test for Global Configuration
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60149 Add UI test for Global Configuration Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.203013.1573595193000.19679.1588189620057%40Atlassian.JIRA.
[JIRA] (JENKINS-47188) CmakeTool fails with no message when binaries are not available
Title: Message Title Martin Weber resolved as Incomplete Resolving this after waiting more that two years for feed-back. Jenkins / JENKINS-47188 CmakeTool fails with no message when binaries are not available Change By: Martin Weber Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-62095) Webhook not working with return Processed
Title: Message Title Boris Manchette created an issue Jenkins / JENKINS-62095 Webhook not working with return Processed Issue Type: Bug Assignee: Unassigned Components: gitea-plugin Created: 2020-04-29 18:12 Environment: Jenkins version : 2.222.3 Gitea version : 1.8.1 All components run on docker container Labels: webhook gitea plugin Priority: Minor Reporter: Boris Manchette I have configured a Weeb Hook on Gitea server. The test of this hook seems to works fine (HTTP 200 return code and Response body = Processe) but no build is visible on Jenkins side. Add Comment
[JIRA] (JENKINS-62097) Permit multiple webhook secrets to be registered
Title: Message Title Jesse Glick updated JENKINS-62097 Jenkins / JENKINS-62097 Permit multiple webhook secrets to be registered Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206007.1588186126000.19642.1588187100087%40Atlassian.JIRA.
[JIRA] (JENKINS-62100) Remove UI assertions from ChartsITest
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62100 Remove UI assertions from ChartsITest Change By: Ulli Hafner Summary: CLONE - Remove UI assertions from GitBlamerITest ChartsITest Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206011.1588188875000.19663.1588189020061%40Atlassian.JIRA.
[JIRA] (JENKINS-62104) An APK-file is uploaded instead of file with debug symbols
Title: Message Title Alexander Suslov created an issue Jenkins / JENKINS-62104 An APK-file is uploaded instead of file with debug symbols Issue Type: Bug Assignee: Mez Pahlan Components: appcenter-plugin Created: 2020-04-29 19:44 Priority: Major Reporter: Alexander Suslov I noticed that we have apk-files on the 'mappings' tab in the AppCenter web-console. The 'pathToApp' and 'pathToDebugSymbols' params in my jenkins-file are correct. I browse the source code of the plugin and found that the 'pathToDebugSymbols' param is used for determine a symbol type only and nothing else. It leads to the situation when an APK-file is uploaded instead of file with debug symbols. Add Comment
[JIRA] (JENKINS-62102) Remove UI assertions from MiscIssueRecorderITest
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62102 Remove UI assertions from MiscIssueRecorderITest Change By: Ulli Hafner Summary: Remove UI assertions from MiscIssueRecorederITest MiscIssueRecorderITest Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206013.1588189191000.19676.1588189500394%40Atlassian.JIRA.
[JIRA] (JENKINS-62102) Remove UI assertions from MiscIssueRecorederITest
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62102 Remove UI assertions from MiscIssueRecorederITest Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206013.1588189191000.19673.1588189500220%40Atlassian.JIRA.
[JIRA] (JENKINS-61397) Source location not clickable in Matrix jobs
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-61397 Source location not clickable in Matrix jobs Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205051.1583761943000.19678.1588189560141%40Atlassian.JIRA.
[JIRA] (JENKINS-62109) Add integration tests with actual sources
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62109 Add integration tests with actual sources Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2020-04-29 21:59 Priority: Minor Reporter: Ulli Hafner It would be a good enhancement to add an integration test that verifies that the new warnings detection is working with an actual refactored source file. (Fingerprinting works) Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Calvin Park commented on JENKINS-61956 Re: ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Ah sorry, I didn't realize the name itself was clickable. Thank you! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205840.1587161495000.19731.1588199220140%40Atlassian.JIRA.
[JIRA] (JENKINS-62111) Add integration test that verifies the GitMiner table model
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62111 Add integration test that verifies the GitMiner table model Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206022.1588198186000.19733.1588199940246%40Atlassian.JIRA.
[JIRA] (JENKINS-62079) No way to email just a PR's owner
Title: Message Title Alex Earl commented on JENKINS-62079 Re: No way to email just a PR's owner Correct, it looks through all of the changesets and grabs all the authors. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205984.1588084934000.19735.1588199940280%40Atlassian.JIRA.
[JIRA] (JENKINS-62112) Add integration test with metrics aggregation plugin
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62112 Add integration test with metrics aggregation plugin Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206023.1588199889000.19736.1588199940300%40Atlassian.JIRA.
[JIRA] (JENKINS-62105) github-plugin doesnt properly handle API (rate limit) exhaustion
Title: Message Title Chad Feller created an issue Jenkins / JENKINS-62105 github-plugin doesnt properly handle API (rate limit) exhaustion Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2020-04-29 20:10 Environment: Jenkins 2.222.3 Ubuntu 16.04 Github Plugin 1.29.5 Priority: Minor Reporter: Chad Feller In a situation where Github API calls are exhausted (rate limited), Github plugin will claim to have set a git commit status when it was unable to. In such a scenario, using "Set GitHub commit status (universal)" as Post build action, a status line such as this will be printed out to the console of the affected build: [Set GitHub commit status (universal)] SUCCESS on repos [] (sha:bfc5a2c) with context: On a build where the API calls are not exhausted, it should look more like this. [Set GitHub commit status (universal)] SUCCESS on repos [GHRepository@1234abc [, , , , , ]]. (sha:bfc5a2c) with context: The issue appears to be that this line: https://github.com/jenkinsci/github-plugin/blob/51dc96b336818b6df56bb85ec91fa384fe55ab86/src/main/java/org/jenkinsci/plugins/github/status/GitHubCommitStatusSetter.java#L136 doesn't care if it gets an empty list back. Somewhere we should raise an error rather than silently failing due to API rate limiting.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck commented on JENKINS-61956 Re: ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Calvin Park Done! Note that you can just change it yourself Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205840.1587161495000.19695.1588192140591%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61956 ItemGroupMixin#createProject() does not call Jenkins#checkGoodName Change By: Daniel Beck Summary: ItemGroupMixing ItemGroupMixin #createProject() does not call Jenkins#checkGoodName Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205840.1587161495000.19693.1588192140278%40Atlassian.JIRA.
[JIRA] (JENKINS-55403) Integration with JIRA in declarative Jenkins pipeline for maven builds
Title: Message Title Milan Konzal closed an issue as Done Jenkins / JENKINS-55403 Integration with JIRA in declarative Jenkins pipeline for maven builds Change By: Milan Konzal Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.196512.1546600617000.19708.1588195020267%40Atlassian.JIRA.
[JIRA] (JENKINS-62107) Provide a pipeline step to get the value of given properties assigned to specific artifact
Title: Message Title Milan Konzal created an issue Jenkins / JENKINS-62107 Provide a pipeline step to get the value of given properties assigned to specific artifact Issue Type: New Feature Assignee: Eyal Ben Moshe Components: artifactory-plugin Created: 2020-04-29 21:42 Environment: Artifactory Plugin 3.6.1 Artifactory Pro 6.5.9 Priority: Minor Reporter: Milan Konzal Similar to rtSetProps and rtDeleteProps I would like to have rtGetProps. When I promote my artifacts in the pipeline I need to known the build. I select the artifact depending on unique value of his custom property (was set with rtSetProps). Then I use the build.name and build.number properties to get the respective build, which should be promoted. Currently I'm able to do it with curl. Add Comment
[JIRA] (JENKINS-62111) Add integration test that verifies the GitMiner table model
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62111 Add integration test that verifies the GitMiner table model Change By: Ulli Hafner Labels: test testing -course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206022.1588198186000.19729.1588198260057%40Atlassian.JIRA.
[JIRA] (JENKINS-62113) Add integration test for parasoft-findings
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62113 Add integration test for parasoft-findings Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 22:45 Labels: testing-course Priority: Minor Reporter: Ulli Hafner The parasoft-findings-plugin extends the warnings plugin. An integration test should make sure that API changes will not break that plugin. Add Comment
[JIRA] (JENKINS-62113) Add integration test for parasoft-findings
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62113 Add integration test for parasoft-findings Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206024.158820031.19739.1588200480170%40Atlassian.JIRA.
[JIRA] (JENKINS-62115) Review: support swarm's update url
Title: Message Title Joel Brown created an issue Jenkins / JENKINS-62115 Review: support swarm's update url Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-04-29 23:35 Priority: Minor Reporter: Joel Brown Latest Swarm suggests use of the update parameter in the review/build to show running and some (hopefully) meaningful message(s). The "update" (instead of pass and fail) also as formatted in JSON in the body of the POST request. Test status: valid test status values are running, pass, and fail. Messages: you can pass a maximum 10 messages, if you provide more than 10 messages only the first 10 are saved. See https://www.perforce.com/manuals/swarm/Content/Swarm/admin.integrate_test_suite.html?Highlight=update Add Comment
[JIRA] (JENKINS-62105) github-plugin doesn't properly handle API rate limit exhaustion
Title: Message Title Chad Feller updated an issue Jenkins / JENKINS-62105 github-plugin doesn't properly handle API rate limit exhaustion Change By: Chad Feller Summary: github-plugin doesn't properly handle API ( rate limit ) exhaustion Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206016.1588191034000.19706.1588194540209%40Atlassian.JIRA.
[JIRA] (JENKINS-62105) github-plugin doesn't properly handle API (rate limit) exhaustion
Title: Message Title Chad Feller updated an issue Jenkins / JENKINS-62105 github-plugin doesn't properly handle API (rate limit) exhaustion Change By: Chad Feller Summary: github-plugin doesnt doesn't properly handle API (rate limit) exhaustion Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206016.1588191034000.19704.1588194480222%40Atlassian.JIRA.
[JIRA] (JENKINS-55218) Lockable resources plugin does not always work
Title: Message Title Chi Leung commented on JENKINS-55218 Re: Lockable resources plugin does not always work We are seeing this issue in 2.7. It happens randomly. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.196294.1545038398000.19720.1588197000132%40Atlassian.JIRA.
[JIRA] (JENKINS-62109) Add integration tests with actual sources
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62109 Add integration tests with actual sources Change By: Ulli Hafner Labels: testing-course Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206020.158819757.19723.1588197660066%40Atlassian.JIRA.
[JIRA] (JENKINS-62108) Add integration test with Ansi-Color plugin
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62108 Add integration test with Ansi-Color plugin Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206019.1588197433000.19727.1588198080268%40Atlassian.JIRA.
[JIRA] (JENKINS-62109) Add integration tests with actual sources
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62109 Add integration tests with actual sources Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206020.158819757.19726.1588198080252%40Atlassian.JIRA.
[JIRA] (JENKINS-62110) Add integration tests for task scanner
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62110 Add integration tests for task scanner Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 22:07 Labels: testing-course Priority: Minor Reporter: Ulli Hafner There are some ok tests for the task scanner but no not tests (file exception, wrong encoding). It would make sense to add such tests as well. Add Comment
[JIRA] (JENKINS-62110) Add integration tests for task scanner
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62110 Add integration tests for task scanner Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206021.158819802.19725.1588198080239%40Atlassian.JIRA.
[JIRA] (JENKINS-62112) Add integration test with metrics aggregation plugin
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62112 Add integration test with metrics aggregation plugin Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 22:38 Labels: testing-course Priority: Minor Reporter: Ulli Hafner The metrics-aggregation-plugin will aggregate static analysis results. This is something we should not destroy. It automatically creates a Jenkins action if there are results. Add Comment
[JIRA] (JENKINS-62106) NullPointerException in IssueCommentTrigger
Title: Message Title Nigel Armstrong created an issue Jenkins / JENKINS-62106 NullPointerException in IssueCommentTrigger Issue Type: Bug Assignee: Aaron Whiteside Components: pipeline-github-plugin Created: 2020-04-29 20:23 Environment: Pipeline-github-plugin 2.5 Jenkins 2.222.3 Priority: Minor Reporter: Nigel Armstrong During startup I get a large number of NullPointerExceptions java.lang.NullPointerExceptionat org.jenkinsci.plugins.pipeline.github.trigger.IssueCommentTrigger.getKey(IssueCommentTrigger.java:69)at org.jenkinsci.plugins.pipeline.github.trigger.IssueCommentTrigger.start(IssueCommentTrigger.java:50)at org.jenkinsci.plugins.pipeline.github.trigger.IssueCommentTrigger.start(IssueCommentTrigger.java:34)at org.jenkinsci.plugins.workflow.job.properties.PipelineTriggersJobProperty.startTriggers(PipelineTriggersJobProperty.java:113)at org.jenkinsci.plugins.workflow.job.WorkflowJob.onLoad(WorkflowJob.java:150)at com.cloudbees.hudson.plugins.folder.AbstractFolder.loadChildren(AbstractFolder.java:454)at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:559)at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.onLoad(ComputedFolder.java:220)at jenkins.branch.MultiBranchProject.onLoad(MultiBranchProject.java:176)at org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.onLoad(WorkflowMultiBranchProject.java:85)at com.cloudbees.hudson.plugins.folder.AbstractFolder.loadChildren(AbstractFolder.java:454)at com.cloudbees.hudson.plugins.folder.AbstractFolder.onLoad(AbstractFolder.java:559)at
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche commented on JENKINS-62087 Re: Detect Gradle module names Pull request has been opened: https://github.com/jenkinsci/analysis-model/pull/362 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19714.1588196820468%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche updated JENKINS-62087 Jenkins / JENKINS-62087 Detect Gradle module names Change By: Joe Hansche Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19717.1588196820527%40Atlassian.JIRA.
[JIRA] (JENKINS-62087) Detect Gradle module names
Title: Message Title Joe Hansche started work on JENKINS-62087 Change By: Joe Hansche Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.205995.1588116528000.19715.1588196820489%40Atlassian.JIRA.
[JIRA] (JENKINS-62108) Add integration test with Ansi-Color plugin
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62108 Add integration test with Ansi-Color plugin Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 21:57 Labels: testing-course Priority: Minor Reporter: Ulli Hafner The plugin enhances the console log output and might break some parsers. Add Comment
[JIRA] (JENKINS-62114) Add integration test for autograder plugin
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62114 Add integration test for autograder plugin Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-29 22:47 Labels: testing-course Priority: Minor Reporter: Ulli Hafner The autograding plugin depends on the warnings plugin. An integration test should make sure that API changes will not break that plugin. Add Comment
[JIRA] (JENKINS-62114) Add integration test for autograder plugin
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62114 Add integration test for autograder plugin Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google 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.206025.158820043.19740.1588200540053%40Atlassian.JIRA.
