[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Those following this issue might try to enable the new long file name support in Windows 10 Anniversary Edition, where Microsoft has now removed the path limitation if you turn that support on. I ran into a very interesting problem with that setting enabled / on that new version of Windows: JENKINS-39179 Thought I would link here, in case anyone tries to go that route. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10
Title: Message Title Greg Smith commented on JENKINS-39179 Re: All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10 Another very interesting point of information: I looked at the code for getWin32FileAttributes() – and it is taking different code paths based on the length of the path. The reason we updated these slaves to Windows 10 Anniversary Edition was that this new build of Windows 10 includes support for long file paths. IE, Windows 10 is supposed to support long file paths natively now – if you enable it, as listed here: https://mspoweruser.com/ntfs-260-character-windows-10/ We have enabled this long file path ability in our Windows 10 slave image. We did this because of JENKINS-38706 So its possible that we: Tried to work around issues caused by JENKINS-38706 on Windows by using this new feature Enabling the feature causes the JNI windows task getWin32FileAttributes to hang That hang in the Windows slave then caused all current builds to hang Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10 Change By: Greg Smith Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10 Change By: Greg Smith Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, hung FileMonitoringTask.cleanup / get attributes on Windows 10 Change By: Greg Smith Summary: All builds hang, Builds cannot be stopped, hung FileMonitoringCleanup FileMonitoringTask.cleanup / get attributes on Windows 10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, Builds cannot be stopped, hung FileMonitoringCleanup
Title: Message Title Greg Smith commented on JENKINS-39179 Re: All builds hang, Builds cannot be stopped, hung FileMonitoringCleanup I have been tracking this down via the /threadDump, to figure out what was hung. And it seems that the problem lies in the attempt to deleteRecursive within the FileMonitoringController on Windows 10. Here is an example part of the thread dump that lead me to look there: "jenkins.util.Timer [#1] / waiting for hudson.remoting.Channel@64ce159:Windows10Slave-1_84a5e84b-395e-4e76-af9a-083bda1c8258" Id=21 Group=main TIMED_WAITING on hudson.remoting.UserRequest@3d7106cf at java.lang.Object.wait(Native Method) - waiting on hudson.remoting.UserRequest@3d7106cf at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:796) at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:974) at hudson.FilePath.deleteRecursive(FilePath.java:1176) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.cleanup(FileMonitoringTask.java:171) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:288) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:234) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) To summarize the steps that I took: All of my builds (about 8 total, 1 per slave, all dynamic slaves, 3 Linux, 5 Windows 10) were hung. The console logs for all were frozen, none could be stopped via UI. I investigated the /threadDump, and found that there were several Timers all waiting on a specific slave to complete a "deleteRecursive" call I logged into that slave, and killed the java.exe process running. All other slaves immediately came back, and their builds continued. If you go look at the thread dump on the machine that was hung (before I logged in and killed it) – it looks like this: "pool-1-thread-13 for channel" Id=72 Group=main RUNNABLE at hudson.util.jna.Kernel32Utils.getWin32FileAttributes(Kernel32Utils.java:77) at hudson.util.jna.Kernel32Utils.isJunctionOrSymlink(Kernel32Utils.java:98) at hudson.Util.isSymlink(Util.java:507) at hudson.FilePath.deleteRecursive(FilePath.java:1199) at hudson.FilePath.access$1000(FilePath.java:195) at
[JIRA] (JENKINS-39179) All builds hang, Builds cannot be stopped, hung FileMonitoringCleanup
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, Builds cannot be stopped, hung FileMonitoringCleanup Change By: Greg Smith Summary: All builds hang, Builds cannot be stopped, only restart solves hung FileMonitoringCleanup Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39190) Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure
Title: Message Title Neelam Tolmare created an issue Jenkins / JENKINS-39190 Failure to resolve a PagerDuty incident as a "Post-build Action" marks the Jenkins build itself as a failure Issue Type: Bug Assignee: Alexander Leibzon Components: pagerduty-plugin Created: 2016/Oct/21 11:04 PM Environment: PagerDuty Plugin 0.2.4 Labels: plugins Priority: Major Reporter: Neelam Tolmare Using PagerDuty Plugin 0.2.4 PagerDuty Incident Trigger is set up as one of the "Post-build Actions" for a Jenkins job with these settings enabled: 1) Trigger Incident on FAILURE job result 2) Resolve on BACK-TO-NORMAL Jenkins job failed in one of the runs, thus creating a PD incident successfully. On the next run, the job itself succeeded however it failed to resolve the incident due to some connection issues. Failure to resolve a PagerDuty incident as a "Post-build Action" marked the Jenkins build result itself as a failure. This needs to be fixed because any downstream jobs scheduled to trigger on FAILURE of this job can undesirably get triggered just because of failure to resolve PD incident which is just a post-build action.
[JIRA] (JENKINS-39179) All builds hang, Builds cannot be stopped, only restart solves
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, Builds cannot be stopped, only restart solves Change By: Greg Smith Environment: Jenkins 2.19.1 LTS andJenkins 2.26 Durable Task Plugin 1.12 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, Builds cannot be stopped, only restart solves
Title: Message Title Greg Smith updated an issue Jenkins / JENKINS-39179 All builds hang, Builds cannot be stopped, only restart solves Change By: Greg Smith Component/s: durable-task-plugin Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39188) Stage view shows almost done when there is a long way to go
Title: Message Title Sam Van Oort commented on JENKINS-39188 Re: Stage view shows almost done when there is a long way to go Sam Krishna Can you provide information to reproduce this, in a case where Stage View has enough information to make a reasonable estimate? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-26640 Re: svn: E175002: handshake alert: unrecognized_name with JDK >1.7 you have to add -Djsse.enableSNIExtension=false to JENKINS_JAVA_ARGS JENKINS_JAVA_OPTIONS or configure properly your server, the reason is a wrong configuration of virtual hosts on the server side. The server sends a warning, browsers are ignoring it, but Java terminates. Oracle means it's "not a defect": http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7127374 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-26640 Re: svn: E175002: handshake alert: unrecognized_name with JDK >1.7 you have to add -Djsse.enableSNIExtension=false to JENKINS_JAVA_ARGS or configure properly your server, the reason is a wrong configuration of virtual hosts on the server side. The server sends a warning, browsers are ignoring it, but Java terminates. Oracle means it's "not a defect": http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7127374 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39136) Remove CustomNameJobColumn
Title: Message Title Stephen Connolly updated JENKINS-39136 Jenkins / JENKINS-39136 Remove CustomNameJobColumn Change By: Stephen Connolly Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32246) Is it absolutely necessary to keep full .git repository in the sub-projects?
Title: Message Title Jesse Glick resolved as Duplicate Not intending to solve it that way; see duplicate. Jenkins / JENKINS-32246 Is it absolutely necessary to keep full .git repository in the sub-projects? Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title
Xian Yi Teng updated an issue
Jenkins / JENKINS-39189
JOB_NAME includes parameters
Change By:
Xian Yi Teng
According to https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables JOB_NAME should only be the project name, but it actually includes parameters, e.g. job_name/parameter1=value2,parameter2=value2 Workaround:{code}JOB_NAME=$(echo $JOB_NAME | cut -d '/' -f 1){code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37011) Provide a way to write full-fledged Steps in CPS-transformed Groovy
Title: Message Title Jesse Glick updated JENKINS-37011 Jenkins / JENKINS-37011 Provide a way to write full-fledged Steps in CPS-transformed Groovy Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26055) DurableTaskStep
Title: Message Title Jesse Glick resolved as Won't Do A more general change that might be useful here… …is JENKINS-37011. Going with that for now as it seems to be easier than the original plan. Jenkins / JENKINS-26055 DurableTaskStep Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are
[JIRA] (JENKINS-26056) Workflow build step for Ant
Title: Message Title Jesse Glick updated JENKINS-26056 Jenkins / JENKINS-26056 Workflow build step for Ant Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39189) JOB_NAME includes parameters
Title: Message Title Xian Yi Teng created an issue Jenkins / JENKINS-39189 JOB_NAME includes parameters Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Oct/21 9:39 PM Priority: Minor Reporter: Xian Yi Teng According to https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables JOB_NAME should only be the project name, but it actually includes parameters, e.g. job_name/parameter1=value2,parameter2=value2 Add Comment
[JIRA] (JENKINS-39188) Stage view shows almost done when there is a long way to go
Title: Message Title Sam Krishna created an issue Jenkins / JENKINS-39188 Stage view shows almost done when there is a long way to go Issue Type: Improvement Assignee: Sam Van Oort Attachments: almost-done.JPG Components: pipeline-stage-view-plugin Created: 2016/Oct/21 9:18 PM Priority: Minor Reporter: Sam Krishna Stage view shows as 'Almost done' eventhough there is quite a ways to go. Almost done should be ideally shown when only a couple of minutes are remaining, yeah? Add Comment
[JIRA] (JENKINS-39187) Pipeline timeout should still raise an error if a terminated shell command exits normally
Title: Message Title Jett Jones created an issue Jenkins / JENKINS-39187 Pipeline timeout should still raise an error if a terminated shell command exits normally Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Oct/21 9:17 PM Environment: Jenkins 2.25; Pipeline 2.2; Pipeline: Basic Steps 2.2; Pipeline Nodes and Processes 2.5; Pipeline: Supporting Apis 2.10 Priority: Minor Reporter: Jett Jones The timeout pipeline step will send an TERM signal to an inner process when its time window ends. If that inner process is listening for TERM and exits normally when it sees one - it seems that no other error appears in the jenkins pipeline. Later tasks within the `timeout` block still execute and no exception is caught by the pipeline. I hit this by running docker containers using dumb init: https://github.com/Yelp/dumb-init, wrapping `python -m unittest` - all combined that ends up exiting with code 0 on termination. I expect I can work around this by changing the docker entrypoint for the test to use bash instead of dumb-init. But the behavior seemed unexpected enough (timeout followed by ... no errors) to file this issue.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title Owen Mehegan commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility Folks, it's not helpful to keep posting +1 comments. This generates a fairly pointless email to everyone who is watching this issue. If you want the feature, just add a vote. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27299) Refactor Disable Build feature out of AbstractProject for Workflow Compatibility
Title: Message Title David Yerkess commented on JENKINS-27299 Re: Refactor Disable Build feature out of AbstractProject for Workflow Compatibility +1 I am loving pipelines, but keep finding various small things that seem to be missing even when they seem important. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Kanstantsin Shautsou commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node Any other questions please fill to issues to not flood this thread. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33555) Provide option to disable master build executors while starting service
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-33555 Provide option to disable master build executors while starting service Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39186) Process leaked file descriptors
Title: Message Title javydreamercsw created an issue Jenkins / JENKINS-39186 Process leaked file descriptors Issue Type: Bug Assignee: lacostej Components: unity3d-plugin Created: 2016/Oct/21 8:39 PM Environment: Ubuntu 16.04 Jenkins 2.19.1 Labels: jenkins Priority: Minor Reporter: javydreamercsw Everything seems to be set up as per the instructions including XVFB installed, configured and starting prior to the build. I'm getting this error: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information FATAL: Unity3d command line execution failed with status 134 Build step 'Invoke Unity3d Editor' marked build as failure Xvfb stopping Add Comment
[JIRA] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Ebrahim Moshaya commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node wow Kanstantsin Shautsou this plugin looks promising. However, I just installed it and i'm struggling to understand how to use it as it's missing help documentation for the various fields. Do you know if this plugin provides a way to ignore pushes from certain users? We have a jenkinCI user that updates version and we want to be able to ignore pushes from that user. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Kanstantsin Shautsou commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node I just implemented branch trigger in https://github.com/KostyaSha/github-integration-plugin it doesn't require workspace. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39185) Pipeline library name with hyphen is not available as an environment variable
Title: Message Title
Tim Eapen created an issue
Jenkins / JENKINS-39185
Pipeline library name with hyphen is not available as an environment variable
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-global-lib-plugin
Created:
2016/Oct/21 8:13 PM
Priority:
Minor
Reporter:
Tim Eapen
If I use a Library name such as 'pipeline-common', the *library.pipeline-common.version *environment variable is not available. When I try and using it in the SCM configuration (i.e. tags/$ {library.pipeline-common.version}, the literal value is used in the Git operations: > git fetch --tags --progress https:///pipeline-common.git +refs/heads/:refs/remotes/origin/ > git rev-parse tags/${library.pipeline-common.version} ^ {commit} # timeout=10 If I change the Library name to simply pipeline, the feature works as expected.
Add Comment
[JIRA] (JENKINS-18079) GitHub Push always builds if workspace is on offline slave node
Title: Message Title Ebrahim Moshaya commented on JENKINS-18079 Re: GitHub Push always builds if workspace is on offline slave node Does anyone have any workaround for this in 2016? I am using the ec2 plugin to stop the ec2 slave instance when idle to save on costs. However, builds are needlessly getting triggered by pushes to the github repo on branches that the jenkins job doesn't care about. The Jenkins job is only monitoring the master branch but because the workspace goes offline when idle, any push will trigger a build...Kanstantsin Shautsou I'd really appreciate if you could assist.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39184) Add an include filter for additional configuration files to track
Title: Message Title jchatham created an issue Jenkins / JENKINS-39184 Add an include filter for additional configuration files to track Issue Type: New Feature Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2016/Oct/21 7:18 PM Priority: Minor Reporter: jchatham Specifically, I'm trying to use the JobConfigHistory plugin with the Promoted Builds plugin, which saves additional configuration files under jobs//promotions//config.xml - though the UI presents the information in these extra config files as if it were just part of the base job configuration. I'd like to be able to track changes to those files, and it makes sense to me to request a user-configurable include filter to allow general-case handling of non-standard configuration information rather than asking for a one-off fix for a specific plugin. Add Comment
[JIRA] (JENKINS-38914) hudson.model.TextParameterValue heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memorey
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.TextParameterValue heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memorey Change By: Dilip Mahadevappa Summary: hudson.model. TextParamterheavily TextParameterValue heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory memorey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38914) hudson.model.TextParamterheavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.TextParamterheavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Summary: hudson.model. ParametersAction heavily TextParamterheavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20516) Do not warn anymore if there is no description available
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-20516 Do not warn anymore if there is no description available Change By: Ulli Hafner Summary: No Do not warn anymore if there is no description available . Please upgrade checkstyle version Seeing this The message "No description available. Please upgrade checkstyle versionuplications in different files shown only in one file" appears when hovering over an identified line.i'm using coffeelint to create a checkstyle.xml. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-20516) No description available. Please upgrade checkstyle version
Title: Message Title Ulli Hafner commented on JENKINS-20516 Re: No description available. Please upgrade checkstyle version Yes this is true: I'm using the descriptions of the checkstyle project! For each warning, I use the warning type as a key to extract the description from the checkstyle jar. So if the warning is not from checkstyle, no description is shown. (Actually the error message in the issue title was intended as a reminder, that I need to update the descriptions to the latest checkstyle version. Since there are so many other tools now reporting in the checkstyle format I should remove the warnings.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36281) Dashboard trend graphs not displayed following plugin upgrade
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36281 Re: Dashboard trend graphs not displayed following plugin upgrade Code changed in jenkins User: Ulli Hafner Path: analysis-core http://jenkins-ci.org/commit/analysis-suite-plugin/814f7410d14436ec368501266280a5299b027955 Log: [FIXED JENKINS-36281] Downgrade to joda-time 1.6. Use the same library as dashboard-view to avoid classloading problems. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39110) The Pipeline load statement returns Null
Title: Message Title Mike Kingsbury commented on JENKINS-39110 Re: The Pipeline load statement returns Null I'm stumbling over this same problem. I thin there's a documentation issue. Try putting a 'return this;' at the end of the build.groovy file... solved it for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39183) Allow ability for Change Log to show changes since last build
Title: Message Title Matthew Smith updated an issue Jenkins / JENKINS-39183 Allow ability for Change Log to show changes since last build Change By: Matthew Smith Summary: Allow ability for Change Log to manually set ChangeLog show changes since last build Currently, the Change Log that appears after a build shows all of the changes since the last successful build. We would like the option to only show the changes since the previous build, regardless of success whether or failure not it failed . It would be nice if the p4 plugin allowed the Change Log to be set manually. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-39183) Allow ability to manually set ChangeLog
Title: Message Title Matthew Smith created an issue Jenkins / JENKINS-39183 Allow ability to manually set ChangeLog Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2016/Oct/21 6:03 PM Priority: Major Reporter: Matthew Smith Currently, the Change Log that appears after a build shows all of the changes since the last successful build. We would like to only show the changes since the previous build, regardless of success or failure. It would be nice if the p4 plugin allowed the Change Log to be set manually. Add Comment
[JIRA] (JENKINS-39182) Test Connection Fails after providing valid certificate to WAS 7 admin console
Title: Message Title
Tim Muse updated an issue
Jenkins / JENKINS-39182
Test Connection Fails after providing valid certificate to WAS 7 admin console
Change By:
Tim Muse
I've successfully been able to deploy to WAS with self-assigned certificates, but that involved 3 steps:Copying the dummyclientkey.jks and dummyclienttrust.jks files to the jenkins server and specifying them in the configuration along with exporting the certificate from Chrome when opening the webconsole, adding it to a cacerts keyfile, and restarting jenkins (as jenkins loads the cacerts file upon startup).I'm now however looking to try and give my WAS installation an Internal cert, and upon doing so, the Deployer Plugin breaks. Test connection comes up with the following:{code:java}Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host calws7timdev01.harborfreight.com websphere7ndhost at port 8879.at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:634)at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:125)at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:208)at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:204)at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.connect(WebSphereDeploymentService.java:449)at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin$DescriptorImpl.doTestConnection(WebSphereDeployerPlugin.java:465)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233)at
[JIRA] (JENKINS-39182) Test Connection Fails after providing valid certificate to WAS 7 admin console
Title: Message Title Tim Muse updated an issue Jenkins / JENKINS-39182 Test Connection Fails after providing valid certificate to WAS 7 admin console Change By: Tim Muse Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39182) Test Connection Fails after providing valid certificate to WAS 7 admin console
Title: Message Title Tim Muse created an issue Jenkins / JENKINS-39182 Test Connection Fails after providing valid certificate to WAS 7 admin console Issue Type: New Feature Assignee: Greg Peters Components: websphere-deployer-plugin Created: 2016/Oct/21 5:35 PM Environment: Websphere 7.0.0.44 Network Deployment Installation Jenkins 2.17 WebSphere Deployer Plugin 1.4.0 Priority: Major Reporter: Tim Muse I've successfully been able to deploy to WAS with self-assigned certificates, but that involved 3 steps: Copying the dummyclientkey.jks and dummyclienttrust.jks files to the jenkins server and specifying them in the configuration along with exporting the certificate from Chrome when opening the webconsole, adding it to a cacerts keyfile, and restarting jenkins (as jenkins loads the cacerts file upon startup). I'm now however looking to try and give my WAS installation an Internal cert, and upon doing so, the Deployer Plugin breaks. Test connection comes up with the following: Connection failed: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host calws7timdev01.harborfreight.com at port 8879. at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:634) at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:125) at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:208) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) at
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick updated JENKINS-39168 Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39181) Invalid fully qualified image name when registry URL specified.
Title: Message Title
Greg Liebowitz created an issue
Jenkins / JENKINS-39181
Invalid fully qualified image name when registry URL specified.
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-commons-plugin
Created:
2016/Oct/21 5:06 PM
Environment:
Jenkins 2.20 OpenJDK 1.8.0_92 docker-commons 1.5 docker-workflow 1.9
Priority:
Minor
Reporter:
Greg Liebowitz
This issue was discovered in the docker-workflow-plugin, which has a dependency on docker-commons-plugin. Given the following pipeline code:
docker.withRegistry('http://localhost:5000/') {
def dockerImage = docker.image('localhost:5000/test-image')
dockerImage.inside {
echo "container running on ${port}"
}
}
The rendered "docker pull" command incorrectly formats the qualified image name as: localhost:5000/localhost:5000/test-image I have submitted a PR that adds a condition to check whether or not the image name already contains the registry prefix to avoid appending again. https://github.com/jenkinsci/docker-commons-plugin/pull/56
[JIRA] (JENKINS-39180) Milestone option to coalesce queue items while awaiting executor
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-39180
Milestone option to coalesce queue items while awaiting executor
Issue Type:
New Feature
Assignee:
Antonio Muñiz
Components:
pipeline-milestone-step-plugin
Created:
2016/Oct/21 4:59 PM
Priority:
Major
Reporter:
Jesse Glick
Currently Pipeline builds will almost always start running immediately upon entering the queue (unless you disable concurrent builds altogether), since the Groovy code itself does not require a heavyweight executor. Unfortunately this makes it impossible to reproduce a sometimes desirable behavior of freestyle projects, which is queue coalescing: cf. QueueAction, FoldableAction, and ScheduleResult.Existing. The main use case is running only as many concurrent builds as available executors permit, coalescing SCM commits where necessary, while tracking Cause. I would suggest this be implemented as an option to the milestone step. For example, if your script is written like
milestone number: 1, queue: true
node {
milestone 2
checkout scm
sh 'make'
}
and build #1 is running in node while #2 is running but waiting for an executor, if the same job is added to the queue again, rather than immediately starting build #3, Existing should be returned from schedule2 and any FoldableAction in #2 retroactively updated. Once an executor frees up and #2 makes it to the second milestone, new builds can be scheduled again. Not sure if this is implementable using current core APIs. QueueDecisionHandler can only return Refused; we would like an option to return Existing instead (or simply take over the ScheduleResult).
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Brenden Conte updated an issue Jenkins / JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration Change By: Brenden Conte Component/s: branch-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33555) Provide option to disable master build executors while starting service
Title: Message Title Jesse Glick commented on JENKINS-33555 Re: Provide option to disable master build executors while starting service Daniel Beck I guess this is one of those things we considered for 2.0 but dropped, right? IMO the initial state should be zero executors, and you should either be prohibited from configuring nonzero executors until you disable security generally, or sternly warned about it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33555) Provide option to disable master build executors while starting service
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-33555 Provide option to disable master build executors while starting service Change By: Jesse Glick Labels: jenkins security Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition
Title: Message Title Jesse Glick commented on JENKINS-28178 Re: Option to disable sandbox in CpsScmFlowDefinition Do not install that plugin unless as an admin you can verify that either all authenticated users are fully trusted, or there is no way anyone can either create jobs or edit Pipeline script. I really do not recommend it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, Builds cannot be stopped, only restart solves
Title: Message Title Greg Smith created an issue Jenkins / JENKINS-39179 All builds hang, Builds cannot be stopped, only restart solves Issue Type: Bug Assignee: Unassigned Attachments: JenkinsHungThreadStack.txt Components: core Created: 2016/Oct/21 4:36 PM Environment: Jenkins 2.19.1 LTS and Jenkins 2.26 Priority: Critical Reporter: Greg Smith I hate to create a general "core" bug, as I wish I could redirect this to the correct component. Unfortunately, I can not identify which component is hanging and why, so I do not know how to direct this problem. This problem started about 2 weeks ago, as we have been adding new Pipeline builds to our build server. So it could be related to one of the pipeline plugins. The behavior is the following: 1 to 2 times a day, all builds on all build slaves will hang. The console log of the build just stops moving forward, and stays stuck at the last line executed / last line returned. Once this occurs, attempting to stop a build fails. Clicking stop results in no change in the build status or console log output New builds will not start. They sit in the queue, but the slaves will not be started. The UI continues to function, so it is possible to view config, get threaddumps, etc.
[JIRA] (JENKINS-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa commented on JENKINS-38914 Re: hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Daniel Beckham Thanks for checking. We did some more investigation and here are our findings. We have a got internal Test Framework which is kicked in with every builds and it is generating large amount of Environment variables. One of the Environment variable is having a large value as seen in heap-screenshot-1.png ; We have got some 3k jobs like this with each build.xml ~ 500k. Noting that there is a major code changes between 1.596.3 and 1.609.1, we did some testing by setting jenkins.model.lazy.BuildReference.MODE to none and weak. With Core 1.651.3 lazy_BuildReference.MODE.JPG With core 2.19.1 ( jenkins.model.lazy.BuildReference.MODE unset) lazy_BuildReference.MODE-2.JPG As we see in the graph, there is significant amount of GC with jenkins.model.lazy.BuildReference.MODE set to weak in core 1.651.3 Looks like core 2.19.1 with default jenkins.model.lazy.BuildReference.MODE (i.e. soft) does perform well with huge build history. Any insights in very much appreciated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38914) hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory
Title: Message Title Dilip Mahadevappa updated an issue Jenkins / JENKINS-38914 hudson.model.ParametersAction heavily bloats memory use and size of build.xml by loading all builds TextParameterValue in memory Change By: Dilip Mahadevappa Attachment: lazy_BuildReference.MODE.JPG Attachment: lazy_BuildReference.MODE-2.JPG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Jesse Glick Component/s: pipeline-graph-analysis-plugin Component/s: pipeline-stage-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38392) Input step implies that values are set to environment variables when they are not
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38392 Input step implies that values are set to environment variables when they are not Change By: Jesse Glick Component/s: core Labels: documentation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38392) Input step implies that values are set to environment variables when they are not
Title: Message Title Jesse Glick commented on JENKINS-38392 Re: Input step implies that values are set to environment variables when they are not Yeah the help comes from Jenkins core, which assumed that the only use of this API was for initial build parameters. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38857) Three options (True, False, Cancel) for input step
Title: Message Title Jesse Glick commented on JENKINS-38857 Re: Three options (True, False, Cancel) for input step You can already go to the separate input page and accomplish this; the RFE would be to provide special behavior in the console log, and perhaps also Blue Ocean. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39168 Re: Input step 2.x + Abort behaves badly with Stage View Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputAction.java http://jenkins-ci.org/commit/pipeline-input-step-plugin/be5984a600d1a25d252ca5bfcf757e5af7f5e0bb Log: [FIXED JENKINS-39168] NPE from last update. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38671) Email-ext plugin sending duplicate email notifications
Title: Message Title Matěj Korvas updated an issue Jenkins / JENKINS-38671 Email-ext plugin sending duplicate email notifications Change By: Matěj Korvas Comment: We have observed this behaviour too, running Jenkins 1.651.1, email-ext version 2.40.5.We have an email-ext post-build step as a substep of a Conditional Action (this didn't trigger in the case where we saw duplicate emails, they came from the post-build step described next), and as a separate post-build step. The "Trigger for matrix projects" option is set to "Trigger for each configuration" and the duplicate email is indeed sent for a failed matrix child build, as expected, just that it comes twice for the same configuration, build number, with the same timestamp. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick started work on JENKINS-39168 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Jesse Glick Assignee: Sam Van Oort Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38671) Email-ext plugin sending duplicate email notifications
Title: Message Title Matěj Korvas commented on JENKINS-38671 Re: Email-ext plugin sending duplicate email notifications We have observed this behaviour too, running Jenkins 1.651.1, email-ext version 2.40.5. We have an email-ext post-build step as a substep of a Conditional Action (this didn't trigger in the case where we saw duplicate emails, they came from the post-build step described next), and as a separate post-build step. The "Trigger for matrix projects" option is set to "Trigger for each configuration" and the duplicate email is indeed sent for a failed matrix child build, as expected, just that it comes twice for the same configuration, build number, with the same timestamp. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Jesse Glick Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick updated JENKINS-39168 Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Jesse Glick commented on JENKINS-39168 Re: Input step 2.x + Abort behaves badly with Stage View I see the problem. loadExecutions used to guarantee that executions was set after it returned; now it does not. Will propose a hotfix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37528) JiraTestResultReporter-plugin needs TestNG support
Title: Message Title Emmanuel Flores commented on JENKINS-37528 Re: JiraTestResultReporter-plugin needs TestNG support Catalin Luta is the work around you tested something I could attempt or will I need to wait for an update to your plugin to go through first? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38777) Signing for "Unity-iPhone" requires a development team
Title: Message Title Hulusi Önder commented on JENKINS-38777 Re: Signing for "Unity-iPhone" requires a development team Hi Steven, You saved my day. Thank you. Your solution working properly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39175) "Build after other projects are built" option doesn't work for Bitbucket Team/Project
Title: Message Title Lukasz Zachulski edited a comment on JENKINS-39175 Re: "Build after other projects are built" option doesn't work for Bitbucket Team/Project Not a issue. I simply had problems with "/" characters in job name which are translated to %2F and relative paths path . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39175) "Build after other projects are built" option doesn't work for Bitbucket Team/Project
Title: Message Title Lukasz Zachulski closed an issue as Cannot Reproduce Not a issue. I simply had problems with "/" characters and relative paths. Jenkins / JENKINS-39175 "Build after other projects are built" option doesn't work for Bitbucket Team/Project Change By: Lukasz Zachulski Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39168) Input step 2.x + Abort behaves badly with Stage View
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-39168 Input step 2.x + Abort behaves badly with Stage View Change By: Sam Van Oort Summary: Input step 2.x + Abort behaves badly with Stage View Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) Input step + Abort behaves badly with Stage View
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-39168 Input step + Abort behaves badly with Stage View Change By: Sam Van Oort Summary: The stage view can't be loaded anymore Input step + Abort behaves badly with Stage View Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) The stage view can't be loaded anymore
Title: Message Title Sam Van Oort commented on JENKINS-39168 Re: The stage view can't be loaded anymore Leif Bladt Looking into this now – it looks like a bad interaction b/w the input step and the flow analysis methods (tagging places where similar logic is used in order to review). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39168) The stage view can't be loaded anymore
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-39168 The stage view can't be loaded anymore Change By: Sam Van Oort Component/s: pipeline-graph-analysis-plugin Component/s: pipeline-stage-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33796) Make Repository Connector Plugin Pipeline Compatible
Title: Message Title Yuriy Kruchko commented on JENKINS-33796 Re: Make Repository Connector Plugin Pipeline Compatible Hi ! I need pipeline support too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Luka Orelj commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates Yeah I am also interested in this feature. Any news? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39150) Improve remoting channel diagnostics in Support Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39150 Re: Improve remoting channel diagnostics in Support Core Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/com/cloudbees/jenkins/support/impl/RemotingDiagnostics.java http://jenkins-ci.org/commit/support-core-plugin/1f43ffb1e0cdf7de4ab1090aedf2b623f151e006 Log: JENKINS-39150 report remoting diagnostics when it's available Since this plugin cannot assume the version of core, access the method in question via reflection (and also report the failure to find that method, so that we have evidence either way.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38433) Make declarative pipelines agent section pluggable
Title: Message Title Peter Leibiger commented on JENKINS-38433 Re: Make declarative pipelines agent section pluggable Andrew Bayer Yes, I would say so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37588) Multibranch pipleine does not allow quiet time or throttle
Title: Message Title Jesse Glick commented on JENKINS-37588 Re: Multibranch pipleine does not allow quiet time or throttle not all the options are listed there I am not sure I understand what options you are expecting to see and what you actually saw. Sounds like an independent bug at any rate. Documentation is sparse to say the least. The code is in workflow-job-plugin but there is not much to it: basically, any JobProperty compatible with Pipeline can be specified, and should appear as an option under properties. In turn the trigger property should offer any Trigger compatible with Pipeline. upstream refers to ReverseBuildTrigger in Jenkins core (for 1.x users the syntax is different). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/workflow-cps-plugin/c663f2b22661a8c78ffdf466daca9e119ee804b7 Log: [FIXED JENKINS-39154] Revert to 2.16 parent POM as 2.17 changed npm configuration incompatibly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38433) Make declarative pipelines agent section pluggable
Title: Message Title
Jesse Glick commented on JENKINS-38433
Re: Make declarative pipelines agent section pluggable
when we allow extensions to have any arbitrary key, how do we know that docker here means "Docker Pipeline" and not "Some other Docker implementation"?
Well in general extensions need to be written coöperatively so they do not clash. That applies to @Symbol too. Anyway agent label:'foo', docker:'bar' is compatible with a modularized system so long as you design the extension point appropriately:
public abstract class AgentKind implements ExtensionPoint {
public abstract boolean handles(@Nonnull Map arguments);
public abstract @Nonnull URL groovyImplementation();
}
where the DockerAgentKind would simply have a higher ordinal than the LabelAgentKind, which in turn would have a higher ordinal than the AnyAgentKind.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-39178) RTC Plugin: Request Build Fails toolkit not found
Title: Message Title Stefan Harris created an issue Jenkins / JENKINS-39178 RTC Plugin: Request Build Fails toolkit not found Issue Type: Bug Assignee: Deluan Quintão Components: rtc-plugin, teamconcert-plugin Created: 2016/Oct/21 2:22 PM Environment: Red Hat Linux 3.8.13-16.2.1.el6uek.x86_64 Jenkins v 1.609.2 Team Concert Plugin 1.1.9.8 RTC-BuildSystem-Toolkit-Linux-5.0.2/jazz/buildsystem/buildtoolkit Windows Slave: Labels: jenkins rtcBuildToolKit Priority: Blocker Reporter: Stefan Harris Hello, I am having a hard time trying to solve a strange issue and I appreciate any and all help I can get. I have a project which includes checkout from RTC, build a vb.net project on a Windows Slave and then run some tests before deploying to an application server. When I initiate a build manually from within the Jenkins interface I am able to build perfectly. When I deliver code to RTC, the Jenkins job polls and successfully finds changes and builds perfectly. But, when I initiate a build request from an IDE (Eclipse or Visual Studio 2013) the build fails and provides the following message. Building remotely on WindowsNET45 in workspace C:\jenkins\workspace\ RTC : checkout... ERROR: Built toolkit directory not found at: /C:\jazz\buildsystem\buildtoolkit [MSTEST-PLUGIN] Processing test results in file(s) **/UnitTest_Results.trx MSTest: .trx Finished: FAILURE I can see the leading slash before the toolkit directory and I'm not sure if this is what's causing the issue. I am happy to provide more details on request. Hopefully I can get some help to solve this issue.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick updated JENKINS-39154 Working on a 2.21 release. Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39177) Publish HP test results saves reports only for the first SSE run action
Title: Message Title Alexander Neutov updated an issue Jenkins / JENKINS-39177 Publish HP test results saves reports only for the first SSE run action Change By: Alexander Neutov Actual: If Jenkins job contains several actions of type "Execute HP tests using ALM Lab management" and post-build action "Publish HP test results", then results only for first such actions will be saved. Expected: All results are archived and accessible from build. Relevant for dev 5.0 version, both Jenkins 1.643.4 on Linux and Windows 2.x .That's a regression from last release version (see attached). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick updated JENKINS-39154 Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: Jesse Glick Labels: npm regression ui Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39178) RTC Plugin: Request Build Fails toolkit not found
Title: Message Title Stefan Harris updated an issue Jenkins / JENKINS-39178 RTC Plugin: Request Build Fails toolkit not found Change By: Stefan Harris Environment: Red Hat Linux 3.8.13-16.2.1.el6uek.x86_64 Jenkins v 1.609.2Team Concert Plugin 1.1.9.8RTC-BuildSystem-Toolkit-Linux-5.0.2/jazz/buildsystem/buildtoolkitWindows Slave:Windows Server 2012 R2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39177) Publish HP test results saves reports only for the first SSE run action
Title: Message Title Alexander Neutov created an issue Jenkins / JENKINS-39177 Publish HP test results saves reports only for the first SSE run action Issue Type: Bug Assignee: Ofir Shaked Attachments: ConsoleFor_plugin4.5.png, ConsoleFor_plugin5.png, ResultsFor_plugin4.5.png, ResultsFor_plugin5.png Components: hp-application-automation-tools-plugin Created: 2016/Oct/21 2:21 PM Priority: Major Reporter: Alexander Neutov If Jenkins job contains several actions of type "Execute HP tests using ALM Lab management" and post-build action "Publish HP test results", then results only for first such actions will be saved. Relevant for dev 5.0 version, both Jenkins 1.643.4 on Linux and Windows 2.x . That's a regression from last release version (see attached). Add Comment
[JIRA] (JENKINS-39004) org.kohsuke.stapler.NoStaplerConstructorException in Pipeline Sytax: Reference
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39004 org.kohsuke.stapler.NoStaplerConstructorException in Pipeline Sytax: Reference Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39150) Improve remoting channel diagnostics in Support Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39150 Re: Improve remoting channel diagnostics in Support Core Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/Channel.java src/main/java/hudson/remoting/Command.java src/test/java/hudson/remoting/ChannelTest.java http://jenkins-ci.org/commit/remoting/f911574fdac609ce16bb93fb1503b541a918 Log: Merge pull request #122 from jenkinsci/JENKINS-39150 JENKINS-39150 expose diagnostics across all the channels Compare: https://github.com/jenkinsci/remoting/compare/0c7df253043c...f911574f Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39150) Improve remoting channel diagnostics in Support Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39150 Re: Improve remoting channel diagnostics in Support Core Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml src/main/java/com/cloudbees/jenkins/support/impl/RemotingDiagnostics.java http://jenkins-ci.org/commit/support-core-plugin/d5b009c20f80839b49641d0419f6475e1cce513f Log: JENKINS-39150 report remoting diagnostics when it's available Since this plugin cannot assume the version of core, access the method in question via reflection (and also report the failure to find that method, so that we have evidence either way.) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process
Title: Message Title Cliff Meyers updated JENKINS-38594 Jenkins / JENKINS-38594 User can click "Create Pipeline" and open the creation flow process Change By: Cliff Meyers Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38023) Favourite card label does not contain full path
Title: Message Title Cliff Meyers updated JENKINS-38023 Jenkins / JENKINS-38023 Favourite card label does not contain full path Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38594) User can click "Create Pipeline" and open the creation flow process
Title: Message Title Cliff Meyers commented on JENKINS-38594 Re: User can click "Create Pipeline" and open the creation flow process PR: https://github.com/jenkinsci/blueocean-plugin/pull/567 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39176) Project-based security configuration doesn't work for folders and subfolders
Title: Message Title Roman Stepanchuk created an issue Jenkins / JENKINS-39176 Project-based security configuration doesn't work for folders and subfolders Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-10-18 at 21.53.24.png Components: cloudbees-folder-plugin Created: 2016/Oct/21 2:14 PM Environment: Jenkins in docker ver. 2.19.1 Folders Plugin 5.13 Role-based Authorization Strategy 2.3.2 Priority: Major Reporter: Roman Stepanchuk project-based security configuration doesn't work for folders and subfolders. and it works with Folders Plugin ver. 5.1 Add Comment
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title
Toby Broyles edited a comment on JENKINS-39154
Re: Can not edit Pipeline script - text not visible on Configure Page
Same issue here. Upgraded Pipeline Groovy from 2.19 to 2.20 and could no longer edit pipeline scripts in the UI. Produced the same error as above. Downgrading back to 2.19 worked though.Jenkins 2. 71 7.1 {code}Oct 21, 2016 7:21:36 AM org.kohsuke.stapler.framework.adjunct.AdjunctsInPage findNeededWARNING: No such adjunct found: org.jenkinsci.plugins.workflow.cps.workflow-editororg.kohsuke.stapler.framework.adjunct.NoSuchAdjunctException: Neither org.jenkinsci.plugins.workflow.cps.workflow-editor.css, .js, .html, nor .jelly were found at org.kohsuke.stapler.framework.adjunct.Adjunct.(Adjunct.java:125) at org.kohsuke.stapler.framework.adjunct.AdjunctManager.get(AdjunctManager.java:147) at org.kohsuke.stapler.framework.adjunct.AdjunctsInPage.findNeeded(AdjunctsInPage.java:161) at org.kohsuke.stapler.framework.adjunct.AdjunctsInPage.generate(AdjunctsInPage.java:113) at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:83) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick started work on JENKINS-39154 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Jesse Glick resolved as Won't Do The way the build history page is implemented is not compatible with Pipeline. This page should not be used anyway—the design is fundamentally unsound in terms of performance (you can easily bring a large installation to its knees by browsing this page). There are various longer-term plans for analytic capabilities. Jenkins / JENKINS-38877 Build History by Node doesn't work with Pipeline Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received
[JIRA] (JENKINS-39175) "Build after other projects are built" option doesn't work for Bitbucket Team/Project
Title: Message Title Lukasz Zachulski created an issue Jenkins / JENKINS-39175 "Build after other projects are built" option doesn't work for Bitbucket Team/Project Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Oct/21 2:07 PM Priority: Major Reporter: Lukasz Zachulski I've run some tests with Jenkins 2.7.4 and Bitbucket Branch Source Plug-in 1.8 and apparently this feature works perfectly well for ordinary Multibranch, but is not supported by ie. Bitbucket Team/Project. Example: properties([pipelineTriggers([upstream( threshold: hudson.model.Result.SUCCESS, upstreamProjects: "another-job")])]) Add Comment
[JIRA] (JENKINS-38433) Make declarative pipelines agent section pluggable
Title: Message Title rsandell commented on JENKINS-38433 Re: Make declarative pipelines agent section pluggable With my latest change the docker label would be optional, so it could be slightly closer to what we have now. agent docker 'foo' or with named parameters agent docker image: 'foo', args: '-v /foo:/bar -p 90:80' Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
