[JIRA] (JENKINS-57652) Git Parameters returning default and no error logged
Title: Message Title
Phil Rumble created an issue
Jenkins / JENKINS-57652
Git Parameters returning default and no error logged
Issue Type:
Bug
Assignee:
Boguslaw Klimas
Attachments:
image-2019-05-24-11-44-43-250.png
Components:
git-parameter-plugin
Created:
2019-05-24 03:51
Environment:
Jenkins ver. 2.164.3 all plugins up to date centos7
Priority:
Blocker
Reporter:
Phil Rumble
I get intermitten results from the gitParameter option. Sometime I get no list, and the default is chosen a partial list of branches a full list of branches (rarely) This is what is in my pipeline script gitParameter branchFilter: 'origin/(.*)', defaultValue: 'master', name: 'BRANCH_NAME', type: 'PT_BRANCH' stage('Checkout') { steps { dir ('code') { git(branch: "${params.BRANCH_NAME}", url: 'XX') } } } Is there a way to fix this or can we allow users to enter a branch name manually? My scenario is I need the jobs definition to be stored in git, hence I am using pipeline jobs stored as JenkinsFiles. multibranch pipeline job does not suit as these jobs are to be triggered by users, and/or cron.
[JIRA] (JENKINS-42084) Errors when "wait for completion" is ticked
Title: Message Title
Phil Rumble created an issue
Jenkins / JENKINS-42084
Errors when "wait for completion" is ticked
Issue Type:
Bug
Assignee:
Christian McHugh
Components:
saltstack-plugin
Created:
2017/Feb/16 6:49 AM
Priority:
Blocker
Reporter:
Phil Rumble
I . get this error Started by user anonymous Building in workspace /var/lib/jenkins/jobs/salt-test/workspace ERROR: { "_links": {"jobs": []} , "return": [{}] } ERROR: {"Error": "java.io.IOException: Server returned HTTP response code: 401 for URL: http://172.16.42.10:8000/jobs/\n\tat sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)\n\tat sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)\n\tat com.waytta.Utils.getJSON(Utils.java:69)\n\tat com.waytta.Builds.runBlockingBuild(Builds.java:97)\n\tat com.waytta.SaltAPIBuilder.performRequest(SaltAPIBuilder.java:253)\n\tat com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:201)\n\tat com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:161)\n\tat hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)\n\tat hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)\n\tat hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)\n\tat hudson.model.Build$BuildExecution.build(Build.java:206)\n\tat hudson.model.Build$BuildExecution.doRun(Build.java:163)\n\tat hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)\n\tat hudson.model.Run.execute(Run.java:1728)\n\tat hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)\n\tat hudson.model.ResourceController.execute(ResourceController.java:98)\n\tat hudson.model.Executor.run(Executor.java:405)\n"} Response on test.ping for '*': [{}] Build step 'Send a message to Salt API' changed build result to FAILURE Finished: FAILURE
[JIRA] (JENKINS-42083) Allow Auth Type 'auto'
Title: Message Title Phil Rumble created an issue Jenkins / JENKINS-42083 Allow Auth Type 'auto' Issue Type: Improvement Assignee: Christian McHugh Components: saltstack-plugin Created: 2017/Feb/16 12:46 AM Priority: Minor Reporter: Phil Rumble Can you please add the 'auto' option to the Auth Type. Thank you Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] [core] (JENKINS-25609) Build Queue is not being processed! Jobs Queueing up....
Phil Rumble created JENKINS-25609 Build Queue is not being processed! Jobs Queueing up Issue Type: Bug Assignee: Unassigned Attachments: catalina.2014-11-14.log Components: core Created: 14/Nov/14 1:22 AM Description: The build queue builds up and there are plenty of executors available on several nodes as well as the master node. The system memory usage is quite low 2Gb (system has 16Gb) The log file is full of entries like Nov 14, 2014 9:09:21 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.model.Queue$MaintainTask@c2f8092d failed java.lang.IllegalThreadStateException: Thread is already started at java.lang.Thread.start(Thread.java:953) at hudson.model.Executor.start(Executor.java:497) at hudson.model.Queue$JobOffer.set(Queue.java:261) at hudson.model.queue.MappingWorksheet$ExecutorChunk.execute(MappingWorksheet.java:164) at hudson.model.queue.MappingWorksheet$ExecutorChunk.access$000(MappingWorksheet.java:112) at hudson.model.queue.MappingWorksheet$Mapping.execute(MappingWorksheet.java:313) at hudson.model.Queue.maintain(Queue.java:1064) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2033) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:482) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:315) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:193) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:308) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1176) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:795) Environment: jenkinss 1.580.1 Red Hat Enterprise Linux Server release 6.5 (Santiago) Linux Jenkins 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul 27 15:55:46 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux running jenkins in tomcat 6 (tomcat6-6.0.24-78.el6_5) running with java 1.7 java -version java version 1.7.0 Java(TM) SE Runtime Environment (build pxa6470sr7fp1-20140708_01(SR7 FP1)) IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20140627_204598 (JIT enabled, AOT enabled) J9VM - R26_Java726_SR7_20140627_0924_B204598 JIT - r11.b06_20140409_61252.04 GC - R26_Java726_SR7_20140627_0924_B204598_CMPRSS J9CL - 20140627_204598) JCL - 20140707_01 based on Oracle 7u65-b16 Project: Jenkins Priority: Blocker Reporter: Phil Rumble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [lotus-connections] (JENKINS-17811) Request Lotus Connections plugin to post to a community
Phil Rumble started work on JENKINS-17811 Request Lotus Connections plugin to post to a community Change By: Phil Rumble (10/Jan/14 2:29 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [lotus-connections] (JENKINS-17811) Request Lotus Connections plugin to post to a community
Phil Rumble commented on JENKINS-17811 Request Lotus Connections plugin to post to a community Added functionality to post to a lotus connections community forum. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [lotus-connections] (JENKINS-17811) Request Lotus Connections plugin to post to a community
Phil Rumble closed JENKINS-17811 as Fixed Request Lotus Connections plugin to post to a community completed and delivered. Change By: Phil Rumble (10/Jan/14 2:32 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [lotus-connections] (JENKINS-17811) Request Lotus Connections plugin to post to a community
Phil Rumble resolved JENKINS-17811 as Fixed Request Lotus Connections plugin to post to a community Version 1.24 now has this feature. Change By: Phil Rumble (10/Jan/14 2:32 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-17489) RTC Plugin - Password are still visible in console output if scm load fails
Phil Rumble created JENKINS-17489 RTC Plugin - Password are still visible in console output if scm load fails Issue Type: Bug Assignee: Deluan Quintão Components: rtc Created: 05/Apr/13 7:25 AM Description: Password are still visible in console output if scm load fails Project: Jenkins Priority: Major Reporter: Phil Rumble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-15874) Add the url to the build in the status message
Phil Rumble commented on JENKINS-15874 Add the url to the build in the status message Attempting a release 1.23 to handle this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-15874) Add the url to the build in the status message
Phil Rumble started work on JENKINS-15874 Add the url to the build in the status message Change By: Phil Rumble (19/Feb/13 1:22 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-15874) Add the url to the build in the status message
Phil Rumble resolved JENKINS-15874 as Fixed Add the url to the build in the status message Version 1.23 now has this feature. Change By: Phil Rumble (20/Feb/13 6:45 AM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-15874) Add the url to the build in the status message
Phil Rumble created JENKINS-15874 Add the url to the build in the status message Issue Type: Improvement Affects Versions: current Assignee: Phil Rumble Components: lotus-connections Created: 20/Nov/12 2:42 AM Description: Please add the url to the build results in the status message. Environment: all Project: Jenkins Priority: Minor Reporter: Phil Rumble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
