[JIRA] [sonar] (JENKINS-34942) sonar runner configurations lost in jobs configurations since moved to 'global tools config' section
Title: Message Title Alexandre Aubert created an issue Jenkins / JENKINS-34942 sonar runner configurations lost in jobs configurations since moved to 'global tools config' section Issue Type: Bug Assignee: Sonar Team Attachments: 2016-05-19_0853.png, 2016-05-19_0856.png Components: sonar Created: 2016/May/19 7:01 AM Environment: Jenkins 2.5 sonarqube plugin 2.4.1 Labels: sonar-plugin Priority: Blocker Reporter: Alexandre Aubert In 1.x jenkins version, job build step 'launch analysis with SonarQube scanner' was saved with specified 'sonarQube scanner' (screenshot 1). This 'sonarqube scanner' install was declared in jenkins global configuration. Jenkins upgrade to version 2 has moved this
[JIRA] [git-plugin] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Sverre Moe commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Meanwhile it is possible to use Groovy Post-build within Pipeline (formerly Workflow).
Using this script one could publish git tags:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
def build = manager.build
def workspace = build.getWorkspace()
def listener = manager.listener
def environment = build.getEnvironment(listener)
final def project = build.getProject()
final def gitScm = project.getScm()
final GitClient gitClient = gitScm.createClient(listener, environment, build, workspace);
final def gitTagName = "TAG_NAME"
final def comment = "COMMENT"
final def remoteURI = new URIish("origin")
gitClient.tag(gitTagName, comment)
gitClient.push().tags(true).to(remoteURI).execute()
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Sverre Moe edited a comment on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Meanwhile it is possible to use Groovy Post-build within Pipeline (formerly Workflow).Using this script one could publish git tags:{code: groovy java }def build = manager.builddef workspace = build.getWorkspace()def listener = manager.listenerdef environment = build.getEnvironment(listener)final def project = build.getProject()final def gitScm = project.getScm()final GitClient gitClient = gitScm.createClient(listener, environment, build, workspace);final def gitTagName = "TAG_NAME"final def comment = "COMMENT"final def remoteURI = new URIish("origin")gitClient.tag(gitTagName, comment)gitClient.push().tags(true).to(remoteURI).execute(){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-34943 Add support for Jenkins Pipeline Change By: Sverre Moe Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title Sverre Moe created an issue Jenkins / JENKINS-34943 Add support for Jenkins Pipeline Issue Type: Improvement Assignee: Suresh Kumar Components: nexus-artifact-uploader-plugin Created: 2016/May/19 7:30 AM Priority: Minor Reporter: Sverre Moe Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google
[JIRA] [nexus-artifact-uploader-plugin] (JENKINS-34943) Add support for Jenkins Pipeline
Title: Message Title Sverre Moe updated an issue Jenkins / JENKINS-34943 Add support for Jenkins Pipeline Change By: Sverre Moe Add support for Jenkins Pipeline with Nexus Artifact Uploaderhttps://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-33718) Release Jenkins Docker image along the normal release
Title: Message Title Baptiste Mathus commented on JENKINS-33718 Re: Release Jenkins Docker image along the normal release jenkinsci/jenkins:2.5 is missing from https://hub.docker.com/r/jenkinsci/jenkins/tags/ How was the hotfix release done Kohsuke Kawaguchi? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [delivery-pipeline-plugin] (JENKINS-34805) Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade
Title: Message Title Tommy Tynjä commented on JENKINS-34805 Re: Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade Proposed solution: https://github.com/Diabol/delivery-pipeline-plugin/pull/182 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-32164) Allow specify CLIPort manually for CLI class
Title: Message Title Kanstantsin Shautsou closed an issue as Won't Do Jenkins / JENKINS-32164 Allow specify CLIPort manually for CLI class Change By: Kanstantsin Shautsou Status: In Progress Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-34944) OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Title: Message Title
Nikhil Zinjurde created an issue
Jenkins / JENKINS-34944
OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
openstack-cloud-plugin
Created:
2016/May/19 7:56 AM
Environment:
Jenkins 1.651.1 Openstack Cloud Plugin 2.5
Labels:
openstack
Priority:
Critical
Reporter:
Nikhil Zinjurde
I am looking to launch a new slave on the run from a Jenkins job using an OpenStack template. I intend to use the OPENSTACK_PUBLIC_IP for my cloud template in the build step to get an SSH connection to it. However, if I try "echo $ {OPENSTACK_PUBLIC_IP}
" in Execute Shell build step, there is no IP value printed in the build logs.
[EnvInject] - Loading node environment variables. Building on master in workspace /var/jenkins_home/workspace/Test creator build vm Queuing cloud instance: #0 1, openstack.hh.flowcloud.systems creator-build-slave [Test creator build vm] $ /bin/sh -xe /tmp/hudson107
[JIRA] [git-client-plugin] (JENKINS-19921) Git clone fails with JGit and SSH Credentials
Title: Message Title Oded Arbel commented on JENKINS-19921 Re: Git clone fails with JGit and SSH Credentials Tizki KO : Haven't happened to me for a while now, I don't remember what I changed - if at all. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-34941) Add support for dayCondition condition from Run Condition plugin in job-dsl-plugin
Title: Message Title Daniel Spilker started work on JENKINS-34941 Change By: Daniel Spilker Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-client-plugin] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Nadine Sander commented on JENKINS-34886 Re: Jenkins Git Error Invalid ID I sent you the token by email. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gradle-jpi-plugin] (JENKINS-34945) Build fails for jenkinsCore >= 2.0
Title: Message Title
Fredrik Bruzelius created an issue
Jenkins / JENKINS-34945
Build fails for jenkinsCore >= 2.0
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
gradle-jpi-plugin
Created:
2016/May/19 8:17 AM
Environment:
Windows 10 x64, Gradle 2.9, JDK 8u92 x64
Priority:
Minor
Reporter:
Fredrik Bruzelius
Jenkins version 2.x dependes on javax.servlet:javax.servlet-api:3.1.0 but the generated dependency uses the old module name servlet-api which is not resolvable.
I have managed to work around this by adding the dependency explicitly and excluding the erroneous one, like so:
dependencies {
compile 'javax.servlet:javax.servlet-api:3.1.0'
}
configurations {
all*.exclude module: 'servlet-api'
}
[JIRA] [p4-plugin] (JENKINS-33734) P4 Plugin does not reload UI configuration using the Pipeline Workflow
Title: Message Title Russell Gallop commented on JENKINS-33734 Re: P4 Plugin does not reload UI configuration using the Pipeline Workflow I think this is a duplicate of JENKINS-29979. I don't know of a good workaround. I'm using job-dsl-plugin to store jobs in SCM and generate pipeline jobs with embedded scripts. If you accidentally save a job with this configuration then you can just re-run the seed job to get it back. This can get quite unpleasant though as you end up writing pipeline DSL code within Job DSL code. It would be much better if we could use the "Pipeline Script from SCM" option. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-34946) P4 Plugin runs out of memory reverting files
Title: Message Title Henry Falconer created an issue Jenkins / JENKINS-34946 P4 Plugin runs out of memory reverting files Issue Type: Bug Assignee: Unassigned Attachments: consoleText.txt Components: p4-plugin Created: 2016/May/19 8:37 AM Environment: Windows 7 64-bit JRE 1.8.0_91 Jenkins version 1.656, running as Windows service Initially had the default -Xmx256, raised to -Xmx1024 but didn't help P4 Plugin version 1.3.9 Web browser is Chome Labels: memory Priority: Major Reporter: Henry Falconer An out of memory exception was triggered when P4 Plugin tried to revert some files. It looks like it actually tries to load the files into memory while reverting.
[JIRA] [p4-plugin] (JENKINS-34946) P4 Plugin runs out of memory reverting files
Title: Message Title Henry Falconer updated an issue Jenkins / JENKINS-34946 P4 Plugin runs out of memory reverting files Change By: Henry Falconer An out of memory exception was triggered when P4 Plugin tried to revert some files. It looks like it actually tries to load the files into memory while reverting.Our depot has some very large files, so the Populate options are as follows:Sync onlyPopulate have listRevert any open or unshelved filesUsually the workspace is left clean without any files left checked out, but on one occasion there were a couple of files totalling about 1GB in size checked out in the master node's workspace when it tried to start a build. It got as far as trying to revert the checked out files and then threw an out of memory exception.From that point on, it retried every 2 minutes (which is our SCM poll time) and every build on the master node failed with the same issue (all our builds on a given node share the same P4 workspace). I took a heap dump when Jenkins was idle to see if there were any leaks, but its memory usage was only 30MB.I then triggered a build and took another heap after a couple of seconds to try to catch the memory spike, and that time I found a single instance of byte[], 113MB in size, was in the heap (the contents of the array was all zeroes), but not attached to the GC root. One of the files it was attempting to revert was about that size, and there was another file of about 800MB that it also needed to revert, so I suspect it successfully allocated space for the 113MB file and then threw an exception trying to allocate memory for the larger file.If my analysis is correct, this bug will occur whenever P4 Plugin has to revert a file larger than the Jenkins heap, so to repro the bug I suggest creating a very large file, checking it out and then having P4 Plugin try to revert it. If that doesn't trigger the bug, I should be able to provide more info to help you track it down.I've attached a build log from one of the failures showing the OutOfMemoryException out of memory message (which is actually a ConnectionException) . Add Comment
[JIRA] [p4-plugin] (JENKINS-34946) P4 Plugin runs out of memory reverting files
Title: Message Title Henry Falconer updated an issue Jenkins / JENKINS-34946 P4 Plugin runs out of memory reverting files Change By: Henry Falconer An out of memory exception was triggered when P4 Plugin tried to revert some files. It looks like it actually tries to load the files into memory while reverting.Our depot has some very large files, so the Populate options are as follows:Sync onlyPopulate have listRevert any open or unshelved filesUsually the workspace is left clean without any files left checked out, but on one occasion there were a couple of files totalling about 1GB in size checked out in the master node's workspace when it tried to start a build. It got as far as trying to revert the checked out files and then threw an out of memory exception.From that point on, it retried every 2 minutes (which is our SCM poll time) and every build on the master node failed with the same issue (all our builds on a given node share the same P4 workspace). I took a heap dump when Jenkins was idle to see if there were any leaks, but its memory usage was only 30MB.I then triggered a build and took another heap after a couple of seconds to try to catch the memory spike, and that time I found a single instance of byte[], 113MB in size, was in the heap (the contents of the array was all zeroes), but not attached to the GC root. One of the files it was attempting to revert was about that size, and there was another file of about 800MB that it also needed to revert, so I suspect it successfully allocated space for the 113MB file and then threw an exception trying to allocate memory for the larger file.If my analysis is correct, this bug will occur whenever P4 Plugin has to revert a file larger than the Jenkins heap, so to repro the bug I suggest creating a very large file, checking it out and then having P4 Plugin try to revert it. If that doesn't trigger the bug, I should be able to provide more info to help you track it down.I've attached a build log from one of the failures showing the out of memory message (which is actually a ConnectionException). By the way, if it makes any difference, the files it was trying to revert needed resolving, as they had been modified in another workspace since being checked out. Add Comment
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-33841) Support for pipeline builds
Title: Message Title Antonio Mansilla commented on JENKINS-33841 Re: Support for pipeline builds Hi all, I would like to support pipeline but currently I've no time to work on it. So if have time to invest on this feel free to fork the plugin repository and create a pull request. Anyways I'll inform here when it's done but as I said there isn't any release date for this at the moment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Paul Allen started work on JENKINS-24591 Change By: Paul Allen Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [gradle-jpi-plugin] (JENKINS-34945) Build fails for jenkinsCore >= 2.0
Title: Message Title Fredrik Bruzelius commented on JENKINS-34945 Re: Build fails for jenkinsCore >= 2.0 Improving on the workaround (using Gradle v2.12 and later) the dependency can also be written as a compileOnly dependency, thus avoiding having the servlet-api JAR ending up in the plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Paul Allen reopened an issue Use an option in the global config to enable/disable P4_PICKET in the environment. Jenkins / JENKINS-24591 Unable to run perforce commands within build steps Change By: Paul Allen Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [buildgraph-view-plugin] (JENKINS-34803) Update to version 1.3 of build-graph-view plugin crashes Jenkins hard
Title: Message Title Alex Domoradov commented on JENKINS-34803 Re: Update to version 1.3 of build-graph-view plugin crashes Jenkins hard I can confirm that with buildgraph view plugin v1.3 jenkins became unresponsive. It seems work fine with buildgraph view plugin v1.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [bitbucket-plugin] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Joe Maffia commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json Saw this marked as "close" but do we have a final resolution? Still seeing javax.servlet.ServletException: net.sf.json.JSONException: JSONObject["user"] not found. and I tried to build the plugin from source based on Christian Eichenberger but no luck... Thanks for any suggestion. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-28915) Thread Death and build number is already in use
Title: Message Title Timmy Brolin commented on JENKINS-28915 Re: Thread Death and build number is already in use I got the same issue. Log output: ** Unexpected executor death java.lang.IllegalStateException: cannot create a build with number 18 since that (or higher) is already in use among [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 195] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:192) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at org.jenkinsci.plugins.workflow.job.WorkflowJob.createExecutable(WorkflowJob.java:230) at hudson.model.Executor$1.call(Executor.java:362) at hudson.model.Executor$1.call(Executor.java:344) at hudson.model.Queue._withLock(Queue.java:1403) at hudson.model.Queue.withLock(Queue.java:1268) at hudson.model.Executor.run(Executor.java:344) ** Running Jenkins 1.625.2 If I create a copy of the troublesome job, then the copy will run just fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-28915) Thread Death and build number is already in use
Title: Message Title Timmy Brolin edited a comment on JENKINS-28915 Re: Thread Death and build number is already in use I got the same issue.Log output:**Unexpected executor deathjava.lang.IllegalStateException: cannot create a build with number 18 since that (or higher) is already in use among [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 195] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:192) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at org.jenkinsci.plugins.workflow.job.WorkflowJob.createExecutable(WorkflowJob.java:230) at hudson.model.Executor$1.call(Executor.java:362) at hudson.model.Executor$1.call(Executor.java:344) at hudson.model.Queue._withLock(Queue.java:1403) at hudson.model.Queue.withLock(Queue.java:1268) at hudson.model.Executor.run(Executor.java:344)** The latest build of this job visible in its build history is #12. So the number 195 is clearly an error somewhere. Running Jenkins 1.625.2If I create a copy of the troublesome job, then the copy will run just fine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [warnings-plugin] (JENKINS-27131) Possibility to get used logfile and line number of warning in logfile
Title: Message Title Nico Falk closed an issue as Fixed Jenkins / JENKINS-27131 Possibility to get used logfile and line number of warning in logfile Change By: Nico Falk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne commented on JENKINS-34783 Re: Parameters not written to slave after upgrade to latest LTS Unfortunately I don't have debug environment now, but read security advisory then fix this. https://github.com/jenkinsci/export-params-plugin/commit/5b2875f0e40e1b53469f99a056b8a216dd54ae05 Attached built hpi. Please test it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne updated an issue Jenkins / JENKINS-34783 Parameters not written to slave after upgrade to latest LTS Change By: rin_ne Attachment: export-params.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title VISHAL DALAL commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Thanks Paul! I tried this on freestyle type job and found it working. The workflow type jobs have been moved to pipeline-jobs does this trigger mechanism will work to initiate the pipeline jobs also? is there any future plan to introduce the Jenkinsfile kind of support like github? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34676) Outdated version of js-modules causes loading issues on JS module conflicts
Title: Message Title Tom FENNELLY commented on JENKINS-34676 Re: Outdated version of js-modules causes loading issues on JS module conflicts Keith Zantow has agreed to resolve the underlying issue as part of https://github.com/jenkinsci/jenkins/pull/2281 b5576a7 might be the commit, but need to check with Keith. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title Antoine Musso commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked From the discussion on https://github.com/jenkinsci/ircbot-plugin/commit/d18cc7b617155100f8afadb73b324f378c5661da (which bumps Pircbotx to 2.0.1) the deadlock might be solved by Pircbotx 2.1. Would be nice to have a commit that bump the dependency. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Title: Message Title pjdarton commented on JENKINS-15331 Re: Workaround Windows unpredictable file locking in Util.deleteContentsRecursive Code changes are in Jenkins 2.2 onwards. Parameters that control this functionality have been documented on https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [export-params-plugin] (JENKINS-34783) Parameters not written to slave after upgrade to latest LTS
Title: Message Title rin_ne commented on JENKINS-34783 Re: Parameters not written to slave after upgrade to latest LTS Note that this issue should be fixed by other plugins that contributes parameters. So this fix is temporary solution. I would not release new version including this commit. The issue that this plugin should fix is "2 parameters are not contributed to build". but no way to fix from plugin side as of now. This means other plugins are the same situation. Thus, current official solution is "define system properties" only. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title Paul Allen commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Great to hear it is working for you. Support for pipeline and multi-branch (https://jenkins.io/doc/pipeline/) are on my list, but I don't have a lot of free time at the moment. If you get there first, I would be happy to review a pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva edited a comment on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) My master Jenkins (unfortunately) is hosted on windows platform and I cannot make it work. I tried adding this line:-Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war"in %JENKINS_HOME%/jenkins.xml, so after I edited the tag it looks like this: %BASE%\jre\bin\java -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080I also tried adding JENKINS_JAVA_OPTIONS & JENKINS_ARGS as windows environment variables.No success with either approaches. Any ideas? EDIT: I was putting the wrong parameter (safeParameters instead undefinedParameters)Switched to the right one and it works as before. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)
Title: Message Title Vassilena Treneva edited a comment on JENKINS-34871 Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?) My master Jenkins (unfortunately) is hosted on windows platform and I cannot make it work. I tried adding this line:-Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war"in %JENKINS_HOME%/jenkins.xml, so after I edited the tag it looks like this: %BASE%\jre\bin\java -Dhudson.model.ParametersAction.safeParameters=true -jar "%BASE%\jenkins.war" -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080I also tried adding JENKINS_JAVA_OPTIONS & JENKINS_ARGS as windows environment variables.No success with either approaches. Any ideas? EDIT: I was putting the wrong parameter ( hudson.model.ParametersAction. safeParameters instead hudson.model.ParametersAction. undefinedParameters)Switched to the right one and it works as before. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34947) Add Bitbucket Branch Source Plugin to list of available plugins shown in Install Wizard
Title: Message Title Chris Pearce created an issue Jenkins / JENKINS-34947 Add Bitbucket Branch Source Plugin to list of available plugins shown in Install Wizard Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/May/19 10:29 AM Priority: Minor Reporter: Chris Pearce The GitHub Branch Source plugin is installed by default with Jenkins 2.x. Bitbucket is also used extensively by the community. The Bitbucket Branch Source Plugin provides similar functionality for Bitbucket. It would be very helpful for this plugin to be included in the list of plugins available for selection by the user when using the new Jenkins 2.x Install wizard. Currently the user has to go to Manage Plugins after the installation wizard completes. Having the Bitbucket related plugin selectable from the wizard would help to get Bitbucket users up and running more quickly, and broaden the audience of the Install wizard.
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki created an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Issue Type: Bug Assignee: Unassigned Components: assembla-auth, core Created: 2016/May/19 10:42 AM Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Assembla Auth Plugin 1.06 Assembla plugin 1.4 Credentials Plugin 1.27 Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Labels: authentication auth Priority: Major Reporter: Jakub Czaplicki Jobs intermittently finish and fail with the following error message: FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken java.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.
[JIRA] [_unsorted] (JENKINS-34949) Jenkins is passing Javadoc parameters to Java after parsing the poms
Title: Message Title Ben Abramson created an issue Jenkins / JENKINS-34949 Jenkins is passing Javadoc parameters to Java after parsing the poms Issue Type: Bug Assignee: Oleg Nenashev Attachments: releaseoutput.txt Components: _unsorted Created: 2016/May/19 10:43 AM Labels: jenkins java8 Priority: Major Reporter: Ben Abramson I am running Jenkins 1.644 on Red Hat Enterprise Linux 6.6 When trying to perform a Maven Release build of my projects I am encountering the following error: [release] $ /usr/java/jdk1.8/bin/java -Xdoclint:none -cp /opt/dmct/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.5.jar:/usr/lib/apache-maven/boot/plexus-classworlds-2.5.1.jar:/usr/lib/apache-maven/conf/logging jenkins.maven3.agent.Maven31Main /usr/lib/apache-maven /opt/dmct/jenkins/data/war/WEB-INF/lib/remoting-2.53.2.jar /opt/dmct/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.5.jar /opt/dmct/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Change By: Jakub Czaplicki Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Authorization integrated with Assembla .Assembla Auth Plugin 1.06Assembla plugin 1.4Credentials Plugin 1.27Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken Change By: Jakub Czaplicki Environment: Jenkins 2.5 (installed via apt-get upgrade), master only Authorization integrated with Assembla .Assembla Auth Plugin 1.06Assembla plugin 1.4Credentials Plugin 1.27Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-74-generic x86_64) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Title: Message Title
Jakub Czaplicki updated an issue
Jenkins / JENKINS-34948
UsernamePasswordAuthenticationToken cannot be cast AssemblaAuthenticationToken
Change By:
Jakub Czaplicki
Jenkins Authorization is integrated with Assembla's auth. Security Realm uses Assembla Auth Plugin. Jobs intermittently finish and fail with the following error message:{code:java}FATAL: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.UsernamePasswordAuthenticationToken cannot be cast to com.assembla.jenkinsci.plugin.AssemblaAuthenticationToken at com.assembla.jenkinsci.plugin.AssemblaSecurityRealm.loadUserByUsername(AssemblaSecurityRealm.java:333) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1050) at hudson.model.User.get(User.java:395) at hudson.model.User.get(User.java:364) at hudson.plugins.git.GitChangeSet.findOrCreateUser(GitChangeSet.java:374) at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:435) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE{code}This behaviour didn't occur in the previous Jenkins version 1.6.x
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [assembla-auth] (JENKINS-34948) UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken
Title: Message Title Jakub Czaplicki updated an issue Jenkins / JENKINS-34948 UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Change By: Jakub Czaplicki Summary: UsernamePasswordAuthenticationToken cannot be cast to AssemblaAuthenticationToken Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-34941) Add support for dayCondition condition from Run Condition plugin in job-dsl-plugin
Title: Message Title
Daniel Spilker commented on JENKINS-34941
Re: Add support for dayCondition condition from Run Condition plugin in job-dsl-plugin
https://github.com/jenkinsci/job-dsl-plugin/pull/855
Job DSL 1.47 will support this with the automatically generated DSL:
job('example') {
steps{
conditionalSteps {
condition {
dayCondition {
daySelector {
weekday()
}
useBuildTime(false)
}
}
runner('Fail')
steps {
shell('echo Hello')
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-34951) Allow recommended plugins for Install Wizard to be set via a JSON file
Title: Message Title Chris Pearce created an issue Jenkins / JENKINS-34951 Allow recommended plugins for Install Wizard to be set via a JSON file Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/May/19 11:16 AM Priority: Minor Reporter: Chris Pearce It would be be very useful if the recommended plugins shown by the Jenkins Install Wizard could be customized without having to create a new custom build. e.g. by copying a JSON file into the /var/jenkin_home directory before running Jenkins for the first time. This would allow users/organizations to customise the Install Wizard process without having to build and compile the Jenkins source code. Looking at the source code, it seems that the "jenkins/core/src/main/resources/jenkins/install/platform-plugins.json" file is used to populate the plugin choices available to the user when using the Install Wizard. A potential approach could be to check for a "platform-plugins.json" file in /var/jenkins_home and, if it exists, use the contents of that file rather than the file contained within the .war.
[JIRA] [core] (JENKINS-34950) GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Title: Message Title
Paulo Moreira created an issue
Jenkins / JENKINS-34950
GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, gitlab-merge-request-jenkins
Created:
2016/May/19 11:16 AM
Environment:
Linux Ubuntu
Priority:
Blocker
Reporter:
Paulo Moreira
Dear All,
Facing an error related with the gitlab merge request plugin (updated from 2.1 to 2.5): ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Roll backed to 2.1 and its working!
The gitlab merge request plugin is the same version, so therefor the issue should be related with something else.
using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN **.git +refs/heads/:refs/remotes/origin/* > git rev-parse refs/remotes/origin/$ {gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch}
^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit}
[JIRA] [core] (JENKINS-34950) GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Title: Message Title
Paulo Moreira updated an issue
Jenkins / JENKINS-34950
GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Change By:
Paulo Moreira
Dear All,Facing an error related with the gitlab merge request plugin (* when updated Jenkins from 2.1 to 2.5*):ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Roll backed to 2.1 and its working!The gitlab merge request plugin is the same version, so therefor the issue should be related with something else.using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN ***.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-34952) New behavior for item categorization
Title: Message Title Manuel Jesús Recena Soto created an issue Jenkins / JENKINS-34952 New behavior for item categorization Issue Type: Improvement Assignee: Manuel Jesús Recena Soto Components: core Created: 2016/May/19 11:29 AM Labels: ux Priority: Critical Reporter: Manuel Jesús Recena Soto Only draw categories in the UI if there are 3 or more categories that qualify to be drawn Only draw a category if 2 or more items are members of that category Ad
[JIRA] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL
Title: Message Title Sverre Moe commented on JENKINS-26126 Re: DSLD and/or GDSL Any time frame when DSLD will be available in Jenkins? Running version 2.5 I still se only GDSL available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-34712) "master is offline" preventing Pipeline from executing
Title: Message Title Daniel Beck commented on JENKINS-34712 Re: "master is offline" preventing Pipeline from executing Looks a lot like Not A Defect to me. If the master is offline (especially for disk space reasons), no need to run any builds anywhere. The only RFE I could think of would be to not hide the executor-less master node in the executors sidepanel if it's marked offline. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-34944) OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Title: Message Title Oliver Gondža commented on JENKINS-34944 Re: OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step OPENSTACK_PUBLIC_IP is a variable available on the Jenkins node created by this plugin to point back to the host itself. You do not see it on your slave because your build is not run on a node created by the plugin. The OpenStack Instance Creation feature you seem to be using exposes ips in JCLOUDS_IPS variable for the build. Please reopen in case you find this insufficiently documented on wiki/jenkins help. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-34944) OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Title: Message Title
Oliver Gondža edited a comment on JENKINS-34944
Re: OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
{{OPENSTACK_PUBLIC_IP}} is a variable available on the Jenkins node created by this plugin to point back to the host itself. You do not see it on your slave because your build is not run _on_ *on* a node created by the plugin. The *OpenStack _OpenStack Instance Creation* Creation_ feature you seem to be using exposes ips in {{JCLOUDS_IPS}} variable for the build.Please reopen in case you find this insufficiently documented on wiki/jenkins help.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [openstack-cloud-plugin] (JENKINS-34944) OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Title: Message Title Oliver Gondža resolved as Not A Defect Jenkins / JENKINS-34944 OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step Change By: Oliver Gondža Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [pipeline-stage-view-plugin] (JENKINS-34953) pipeline-stage-view doesn't update when pipeline is in SCM
Title: Message Title Simon Watson created an issue Jenkins / JENKINS-34953 pipeline-stage-view doesn't update when pipeline is in SCM Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/May/19 11:50 AM Environment: Jenkins Version 2.2 Pipeline Stage View: 1.4 Priority: Minor Reporter: Simon Watson If I take a script that I have created within jenkins - and export it to a groovy script and store it in my SCM, stage view no longer updates showing the pipeline flow. Can't find any mention of this as expected/unexpected behaviour so have raised a ticket. Add Comment
[JIRA] [openstack-cloud-plugin] (JENKINS-34944) OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step
Title: Message Title Nikhil Zinjurde commented on JENKINS-34944 Re: OPENSTACK_PUBLIC_IP environment variable not available for Execute Shell build step Thanks Oliver Gondža, that clarifies. Yes, it would really help to point out in the wiki/jenkins help page how the OpenStack Instance Creation works in an identical manner as to the JClouds Instance Creation feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [slave-status-plugin] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message
Title: Message Title Dorian Daumiller commented on JENKINS-19445 Re: Jobs randomly stuck with "building remotely on slave-name" message Can we agree on having this in LTS? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title Jan Dohl commented on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES I would have worded this differently, but I, too, stumbled across this problem. We trigger a parameterized job called "param-builder" and the environment variable turns this into: TRIGGERED_JOB_NAMES=param_builder essentially replacing all "-" with "_". While I can work around that it's still quite annoying to do so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-34340) Don't rename job names in TRIGGERED_JOB_NAMES
Title: Message Title Jan Dohl edited a comment on JENKINS-34340 Re: Don't rename job names in TRIGGERED_JOB_NAMES I would have worded this differently, but I, too, stumbled across this problem. We trigger a parameterized job called "param-builder" and the environment variable turns this into:* TRIGGERED_JOB_NAMES=param_builderessentially replacing all "-" with "_". While I can work around that it's still quite annoying to do so. Also, having a variable with a link to the parameterized build would be nice. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [_unsorted] (JENKINS-34949) Jenkins is passing Javadoc parameters to Java after parsing the poms
Title: Message Title Ben Abramson commented on JENKINS-34949 Re: Jenkins is passing Javadoc parameters to Java after parsing the poms I managed to fix this by deleting and recreating the job (although the config was no different). It might be worth investigating though as something strange was happening. The javadoc / doclint declarations in the pom didn't seem to be it as I got the same error when I commented them out. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-trigger-plugin] (JENKINS-34954) Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin
Title: Message Title Juan Farré created an issue Jenkins / JENKINS-34954 Upgrade from LTS 1.651.1 to 1.651.2 broke functionality of parameterized trigger plugin Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/May/19 12:11 PM Environment: SUSE Linux Enterprise Server 11 SP2 Oracle JDK 1.8.0_91 x64 Tomcat 8.0.33 Jenkins LTS version 1.651.2 Parameterized Trigger plugin 2.30 Promoted builds plugin Labels: LST 1.651.2 ParameterFactories file parameterized-trigger Priority: Major Reporter: Juan Farré After upgrading from 1.651.1 to 1.651.2, when accessing administration page, I found a warning about configuration versions. I found messages related to parameterized trigger and also promoted builds plugins, stating config version was 1.653. The option to change configuration compatibility only showed the same version 1.653. After applying it, however, the messages disappeared (though they appeared again later, perhaps because of executions of other tasks or new executions of the same ones).
[JIRA] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title John Wynne commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I agree with Dana Goyette here. Not sure how feasible/scalable it would be, but here's a mockup that I think could work well with the Pipeline Stage View Plugin http://imgur.com/riSCG2y!http://imgur.com/riSCG2y! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title John Wynne edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I agree with [~danagoyette] here. Not sure how feasible/scalable it would be, but here's a mockup that I think could work well with the Pipeline Stage View Plugin!http:// i. imgur.com/riSCG2y .png ! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [pipeline-stage-view-plugin] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title John Wynne edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage I agree with [~danagoyette] here. Not sure how feasible/scalable it would be, but here's a mockup that I think could work well with the Pipeline Stage View Plugin http://imgur.com/riSCG2y !http://imgur.com/riSCG2y! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [active-directory-plugin] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java src/main/java/hudson/plugins/active_directory/ActiveDirectoryUserDetail.java http://jenkins-ci.org/commit/active-directory-plugin/57f4d97b7b14985272427e461c7d19d90a98fbd4 Log: JENKINS-34426 Fix to handle SECURITY-243 (#34) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title James Nord commented on JENKINS-34150 Re: Pipeline Batch hangs I believe I have a 100% reproducible test-case for this issue It seems that in the case that the parent process has been killed (e.g. the slave dies) then all though the script terminates successfully and the wrapper terminates successfully (checked with process monitor) there is no attempt to create the result file. where the parent process has not been killed I never see this issue. All I needed to do to fix the issue I was observing is add @echo off as the first line of the wrapper script. Basically I believe it is trying to echo the commands to be run before running the commands and as there is no longer anything consuming the wrappers input/output when echoing the command it is doomed to fail (but strangely not with an exit code that implies something died!??! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title Paul Allen resolved as Fixed Slated for release 1.3.10 Jenkins / JENKINS-24591 Unable to run perforce commands within build steps Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [p4-plugin] (JENKINS-24591) Unable to run perforce commands within build steps
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24591 Re: Unable to run perforce commands within build steps Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/ConfigurationListener.java src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/resources/org/jenkinsci/plugins/p4/PerforceScm/global.jelly http://jenkins-ci.org/commit/p4-plugin/3cb5d2208e274843512a0838ce0f7900dc4c0ae4 Log: Hide P4_TICKET for secure systems. An option in the global configuration to hide the P4_TICKET variable (not set by default). JENKINS-24591 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title
Dmitry Vyazelenko commented on JENKINS-34150
Re: Pipeline Batch hangs
I'm also having a build hang with simple pipeline that uses bat script to run Gradle tasks:
node {
timeout(time: 10, unit: 'MINUTES') {
timestamps {
stage 'Checkout'
git ...
stage 'Tests'
bat 'gradlew test'
step([$class: 'JUnitResultArchiver', testResults: 'build/test-results/*.xml'])
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Dmitry Vyazelenko updated an issue Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: Dmitry Vyazelenko Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [tfs-plugin] (JENKINS-33435) TFS SDK fails with TF14045 when encountering an unrecognized identity
Title: Message Title James Young commented on JENKINS-33435 Re: TFS SDK fails with TF14045 when encountering an unrecognized identity Having the same issue, tested with upper & lowercase chars, keeping us from using Jenkins for any build activities with TFS. Error: TF14045: The identity is not a recognized identity. Some more info from /var/log/Jenkins/Jenkins.log: INFO: HttpClient configured for , authenticating as May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal INFO: SOAP method='Connect', status=200, content-length=3728, server-wait=57 ms, parse=1 ms, total=58 ms, throughput=64276 B/s, gzip May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal INFO: SOAP method='QueryHistory', status=200, content-length=678, server-wait=82 ms, parse=0 ms, total=82 ms, throughput=8268 B/s, gzip May 19, 2016 8:10:13 AM com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory logHTTPClientConfiguration INFO: HttpClient configured for authenticating as May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal INFO: SOAP method='Connect', status=200, content-length=3728, server-wait=24 ms, parse=0 ms, total=24 ms, throughput=155333 B/s, gzip May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternal INFO: SOAP method='QueryWorkspaces', status=500, content-length=0, server-wait=114 ms, parse=1 ms, total=115 ms, throughput=0 B/s, uncompressed May 19, 2016 8:10:13 AM com.microsoft.tfs.core.TFSConnection close WARNING: httpClientReference is null Based on the 200 return, it appears that the user CAN properly authenticate w/ TFS but the user name is changed at some point later in the process with the GUID. Please let me know if there is any part of the investigation I can help with, this is very important for us to get resolved. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [tfs-plugin] (JENKINS-33435) TFS SDK fails with TF14045 when encountering an unrecognized identity
Title: Message Title
James Young edited a comment on JENKINS-33435
Re: TFS SDK fails with TF14045 when encountering an unrecognized identity
Having the same issue, tested with upper & lowercase chars, keeping us from using Jenkins for any build activities with TFS. {code:java} Error: TF14045: Theidentity is not a recognized identity. {code} Some more info from /var/log/Jenkins/Jenkins.log: {code:java} INFO: HttpClient configured for , authenticating as May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternalINFO: SOAP method='Connect', status=200, content-length=3728, server-wait=57 ms, parse=1 ms, total=58 ms, throughput=64276 B/s, gzipMay 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternalINFO: SOAP method='QueryHistory', status=200, content-length=678, server-wait=82 ms, parse=0 ms, total=82 ms, throughput=8268 B/s, gzipMay 19, 2016 8:10:13 AM com.microsoft.tfs.core.config.httpclient.DefaultHTTPClientFactory logHTTPClientConfigurationINFO: HttpClient configured for authenticating as May 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternalINFO: SOAP method='Connect', status=200, content-length=3728, server-wait=24 ms, parse=0 ms, total=24 ms, throughput=155333 B/s, gzipMay 19, 2016 8:10:13 AM com.microsoft.tfs.core.ws.runtime.client.SOAPService executeSOAPRequestInternalINFO: SOAP method='QueryWorkspaces', status=500, content-length=0, server-wait=114 ms, parse=1 ms, total=115 ms, throughput=0 B/s, uncompressedMay 19, 2016 8:10:13 AM com.microsoft.tfs.core.TFSConnection closeWARNING: httpClientReference is null {code} Based on the 200 return, it appears that the user CAN properly authenticate w/ TFS but the user name is changed at some point later in the process with the GUID.Please let me know if there is any part of the investigation I can help with, this is very important for us to get resolved.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] [docker] (JENKINS-34955) userid of jenkins master not known on slave in docker setup
Title: Message Title Tom Deseyn created an issue Jenkins / JENKINS-34955 userid of jenkins master not known on slave in docker setup Issue Type: Bug Assignee: Nicolas De Loof Components: docker Created: 2016/May/19 1:19 PM Priority: Minor Reporter: Tom Deseyn I setup jenkins 2 and provided a -u option to the docker run command to set the user. docker run --restart=always -d -p 80:8080 -p 5:5 -u `id -u jenkinsmaster` -v `pwd`:/var/jenkins_home jenkins:2.3 Then I configured my setup with a build slave over SSH. Then I added a multibranch pipeline project. The build slave failed to check out the git project with an error message: No user exists for uid 1003. 1003 is the uid of jenkinsmaster (id -u jenkinsmaster). It is normal that there is no such user on the build slave. It is peculiar the build slave even knows about the build master user id and that this causes the git checkout to fail on the slave. Note: docker is only used to run the jenkins master in this setup.
[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title James Nord commented on JENKINS-34150 Re: Pipeline Batch hangs Fo anyone observing the issue you can try installing the build from PR24 or PR21 and see if this resolves your issue. (I would start with PR24 first as it is a much smaller change, but then I am biased!) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title James Nord edited a comment on JENKINS-34150 Re: Pipeline Batch hangs Fo For anyone observing the issue you can try installing [the build from PR24 | https://jenkins.ci.cloudbees.com/job/plugins/job/durable-task-plugin/99/org.jenkins-ci.plugins$durable-task/artifact/org.jenkins-ci.plugins/durable-task/1.10-SNAPSHOT/durable-task-1.10-SNAPSHOT.hpi] or [PR21 | https://jenkins.ci.cloudbees.com/job/plugins/job/durable-task-plugin/97/org.jenkins-ci.plugins$durable-task/artifact/org.jenkins-ci.plugins/durable-task/1.10-SNAPSHOT/durable-task-1.10-SNAPSHOT.hpi] and see if this resolves your issue. (I would start with PR24 first as it is a much smaller change, but then I am biased!) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [publish-over-ssh-plugin] (JENKINS-34884) Not able to execute sudo command on "Send files or execute commands over SSH"
Title: Message Title Manoj Kumar commented on JENKINS-34884 Re: Not able to execute sudo command on "Send files or execute commands over SSH" I am able to run this command "sudo service tomcat7 stop" from "Putty" and its working there.But it id giving error while running from jenkins. Even I can see this in "chkconfig --list" from "Putty" tomcat7 0:off 1:off 2:on 3:on 4:on 5:on 6:off Please give me solution for this Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title Leon Leon commented on JENKINS-33980 Re: Document (List) Pipeline features of email-ext-plugin Hello, this works fine for committers, do you have any idea about accessing the culprits list ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title Leon Leon edited a comment on JENKINS-33980 Re: Document (List) Pipeline features of email-ext-plugin Hello, this works fine for committers, do you have any idea about accessing the culprits list within a pipeline ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [publish-over-ssh-plugin] (JENKINS-34884) Not able to execute sudo command on "Send files or execute commands over SSH"
Title: Message Title Kumar J updated an issue Jenkins / JENKINS-34884 Not able to execute sudo command on "Send files or execute commands over SSH" Change By: Kumar J Started by user Manoj Tumati Kumar Building on master in workspace /xxx/xx/xxx/Copied 1 artifact from "" build number xxxSSH: Connecting from host []SSH: Connecting with configuration [x] ...SSH: EXEC: STDOUT/STDERR from command [sudo service tomcat7 stop] ...sudo: no tty present and no askpass program specifiedSSH: EXEC: completed after 200 msSSH: Disconnecting configuration [x] ...ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [1]]Build step 'Send files or execute commands over SSH' changed build result to UNSTABLESending e-mails to: xxStarted calculate disk usage of buildFinished Calculation of disk usage of build in 0 secondsStarted calculate disk usage of workspaceFinished Calculation of disk usage of workspace in 0 secondsFinished: UNSTABLE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [publish-over-ssh-plugin] (JENKINS-34884) Not able to execute sudo command on "Send files or execute commands over SSH"
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-34884 Not able to execute sudo command on "Send files or execute commands over SSH" Change By: Oleg Nenashev Assignee: bap Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [publish-over-ssh-plugin] (JENKINS-34884) Not able to execute sudo command on "Send files or execute commands over SSH"
Title: Message Title Oleg Nenashev commented on JENKINS-34884 Re: Not able to execute sudo command on "Send files or execute commands over SSH" It's not a Jenkins issue. Your jenkins user on the slave/master just does not have appropriate permissions. Further reading: http://stackoverflow.com/questions/21659637/how-to-fix-sudo-no-tty-present-and-no-askpass-program-specified-error . There are also other many other pages with the solution in Google. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [maven-plugin] (JENKINS-34949) Jenkins is passing Javadoc parameters to Java after parsing the poms
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-34949 Jenkins is passing Javadoc parameters to Java after parsing the poms Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Jon Whitcraft commented on JENKINS-24824 Re: Asynchronous cleanup not removing renamed workspace directories on slaves +1 to a timeframe for fixing this I'm thinking of rolling back to 0.23 becuase of this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [maven-plugin] (JENKINS-34949) Jenkins is passing Javadoc parameters to Java after parsing the poms
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-34949 Jenkins is passing Javadoc parameters to Java after parsing the poms Change By: Oleg Nenashev Component/s: maven-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34952) New behavior for item categorization
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 New behavior for item categorization Change By: Manuel Jesús Recena Soto # Only draw categories in a category if 2 or more items are members of that category# # Only draw the UI categories if there are 3 or more categories that qualify to be drawn # Only draw a category if 2 or more items are members of that category Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34952) New behavior for item categorization
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 New behavior for item categorization Change By: Manuel Jesús Recena Soto # Only draw a category if 2 or more items are members of that category# # Only draw the categories if there are 3 or more categories that qualify to be drawn Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-33499) Workflow EC2 Integration - build node not provisioned
Title: Message Title Alban Crequy commented on JENKINS-33499 Re: Workflow EC2 Integration - build node not provisioned I have the same issue. Parallel provisioning would be useful to me as well. Do you know of any workaround? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [publish-over-ssh-plugin] (JENKINS-34884) Not able to execute sudo command on "Send files or execute commands over SSH"
Title: Message Title bap commented on JENKINS-34884 Re: Not able to execute sudo command on "Send files or execute commands over SSH" The answer is in this line of output: sudo: no tty present and no askpass program specified Check the "Exec in pty" Advanced option for the transfer set https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin#PublishOverSSHPlugin-Execinpty Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [sonar-gerrit-plugin] (JENKINS-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Stephane Le Bris edited a comment on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Hello, I post this comment because I have also communication problem with Gerrit Server : in the log file, there is the following message :Getting Sonar Report from: [...]/.sonar/sonar-report.jsonReport has loaded and contains 1801 issuesConnected to Gerrit: server name: r008.jo.tadfr.thales. Change Number: 306, PatchSetNumber: 1*Unable to post review: Request failed.*Build step 'Post SonarQube issues as Gerrit comments' marked build as failure It is my first installation and tentative to use the plugin. After a long time to check me configuration and perform several tests I have not idea why the connection with Gerrit does not work.My configuration is :Jenkins : 1.625.1Plugin Gerrit : 2.18.4Plugin SonarGerrit : 1.0.6 Settings are checked and everything seems OK : REST API connection test is OK and project uses the correct server in my gerrit-trigger settings. The plugin Gerrit works perfectly and the connection (via ssh) is also OK. Could you tell me how I can investigate the problem ? Regards, Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34952) New behavior for item categorization
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 New behavior for item categorization Change By: Manuel Jesús Recena Soto The current implementation of item categorization needs to be improved in order to draw the categories in the UI. Actually the items is being drawn in _flat mode_ (all item in a listing). # Only draw a category if 2 or more items are members of that category# Only draw the categories if there are 3 or more categories that qualify to be drawn Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-34952) New behavior for item categorization
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-34952 New behavior for item categorization Change By: Manuel Jesús Recena Soto The current implementation of item categorization needs to be improved in order to draw the categories in the UI. Actually the items is being drawn in _flat mode_ (all item in a listing). The proposal here is: # Only draw a category if * 2 or more * items are members of that category# Only draw the categories if there are * 3 or more * categories that qualify to be drawn This issues has been discussed with [~gusreiber] in a offline. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-33980) Document (List) Pipeline features of email-ext-plugin
Title: Message Title Alex Earl commented on JENKINS-33980 Re: Document (List) Pipeline features of email-ext-plugin You can look at the source for AbstractBuild on github and it's getCulprits method. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [template-project-plugin] (JENKINS-34956) variables are not visible/expanded in bundled/linked jobs and templates
Title: Message Title
Alexey Bychko created an issue
Jenkins / JENKINS-34956
variables are not visible/expanded in bundled/linked jobs and templates
Issue Type:
Bug
Assignee:
huybrechts
Components:
template-project-plugin
Created:
2016/May/19 1:48 PM
Environment:
Centos 6 x64, Jenkins 1.651.2
Priority:
Major
Reporter:
Alexey Bychko
after upgrade from 1.642.2 to 1.651.2 (LTS) some variables are not visible in other jobs/templates.
to repeat on 1.651.2:
create empty job
add empty string parameter (GIT_REPO in our case)
in shell step do "echo $ {GIT_REPO}" * test it, should work ok then * move code "echo ${GIT_REPO}
" to another job
add that job to "use builders from another project" step in first jo
[JIRA] [credentials-plugin] (JENKINS-34957) jenkins Failed to connect to GIT repository
Title: Message Title Carlos Cabezali created an issue Jenkins / JENKINS-34957 jenkins Failed to connect to GIT repository Issue Type: Bug Assignee: stephenconnolly Attachments: git_jenkins_problem.JPG, jenkins_system_properties.pdf Components: credentials-plugin, girls-plugin Created: 2016/May/19 1:51 PM Environment: Jenkins version 1.651.1 Git Client Plugin: 1.19.6 Git Plugin: 2.4.4. Git server Plugin 1.6 Credentials plugin: 1.28 Labels: git Priority: Minor Reporter: Carlos Cabezali Hello, I just try to configure a job using git, after selecting git as a Source Code Management, and filling up the Repository url, when I add the credentials I got following message: (see attached file git_jenkins_problem.jpg), and to check jenki
[JIRA] [artifactory-plugin] (JENKINS-26720) Artifactory plugin causes exception in project/configure page
Title: Message Title Seymour Pattisson updated an issue Jenkins / JENKINS-26720 Artifactory plugin causes exception in project/configure page Change By: Seymour Pattisson Attachment: Jenkins2-5_configureJogIssue26720.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [artifactory-plugin] (JENKINS-26720) Artifactory plugin causes exception in project/configure page
Title: Message Title
Seymour Pattisson edited a comment on JENKINS-26720
Re: Artifactory plugin causes exception in project/configure page
I have experienced the same issue with Jenkins ver. 2.5 installed on a Centos host. I also was able to avoid/workaround the problem by disabling the Artifactory plugin.I had a slightly different stack trace so I've also included that below this information about my environment. !Jenkins2-5_configureJogIssue26720.png|width=50%! h2. Environment infoh3. Host systemos.arch amd64os.name Linuxos.version 3.10.0-327.18.2.el7.x86_64h3. Plugins||Name||Version||Enabled|||active-directory|1.45|TRUE||analysis-collector|1.47|TRUE||analysis-core|1.76|TRUE||ant|1.3|TRUE||antisamy-markup-formatter|1.3|TRUE||artifactory|2.4.7|TRUE||build-pipeline-plugin|1.5.2|TRUE||cloudbees-credentials|3.3|TRUE||cobertura|1.9.8|TRUE||codesonar|1.0.1 (f267f)|TRUE||create-fingerprint|1.2|TRUE||credentials|1.28|TRUE||DotCi|2.28.1|TRUE||ec2-deployment-dashboard|1.0.10|TRUE||external-monitor-job|1.4|TRUE||git|2.4.4|TRUE||git-client|1.19.6|TRUE||github|1.19.1|TRUE||github-api|1.75|TRUE||github-pullrequest|0.1.0-rc7|TRUE||gitlab-hook|1.4.2|TRUE||gitlab-logo|1.0.1|TRUE||gitlab-merge-request-jenkins|2.0.0|TRUE||gitlab-plugin|1.2.2|TRUE||icon-shim|2.0.3|TRUE||javadoc|1.3|TRUE||jquery|1.11.2-0|TRUE||junit|1.13|TRUE||ldap|1.12|TRUE||mailer|1.17|TRUE||matrix-auth|1.3.2|TRUE||matrix-project|1.6|TRUE||maven-plugin|2.13|TRUE||monitoring|1.59.0|TRUE||pam-auth|1.2|TRUE||parameterized-trigger|2.3|TRUE||plain-credentials|1.1|TRUE||publish-over-ssh|1.14|TRUE||rebuild|1.25|TRUE||ruby-runtime|0.12|TRUE||scm-api|1.2|TRUE||script-security|1.19|TRUE||sonar|2.4.1|TRUE||ssh-credentials|1.12|TRUE||structs|1.1|TRUE||token-macro|1.12.1|TRUE||windows-slaves|1.1|TRUE||workflow-step-api|2|TRUE|h2. Stack trace{code}javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.5.jar!/lib/form/nested.jelly:33:22: hudson/plugins/gradle/Gradle at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilte
[JIRA] [plain-credentials-plugin] (JENKINS-34877) Fix PCT against 2.x baseline and migrate to 2.9 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34877 Re: Fix PCT against 2.x baseline and migrate to 2.9 parent POM Code changed in jenkins User: Jesse Glick Path: .gitignore pom.xml src/main/resources/index.jelly src/test/java/org/jenkinsci/plugins/plaincredentials/BaseTest.java src/test/java/org/jenkinsci/plugins/plaincredentials/FileCredentialsTest.java http://jenkins-ci.org/commit/plain-credentials-plugin/3f3c7fdfb468147eeaa3fce872cfeafdf5c97263 Log: Merge pull request #4 from armfergom/JENKINS-34877 JENKINS-34877 Fix PCT against 2.x and migrate to 2.9 parent pom Compare: https://github.com/jenkinsci/plain-credentials-plugin/compare/792b70b3e5ea...3f3c7fdfb468 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [plain-credentials-plugin] (JENKINS-34877) Fix PCT against 2.x baseline and migrate to 2.9 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34877 Re: Fix PCT against 2.x baseline and migrate to 2.9 parent POM Code changed in jenkins User: Armando Fernandez Path: .gitignore pom.xml src/main/resources/index.jelly http://jenkins-ci.org/commit/plain-credentials-plugin/c0250cd017adcae8b026cd2055a6d3717115253c Log: JENKINS-34877 Migrate to 2.9 parent pom. Fix PCT against 2.x baseline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [plain-credentials-plugin] (JENKINS-34877) Fix PCT against 2.x baseline and migrate to 2.9 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34877 Re: Fix PCT against 2.x baseline and migrate to 2.9 parent POM Code changed in jenkins User: Armando Fernandez Path: src/test/java/org/jenkinsci/plugins/plaincredentials/BaseTest.java http://jenkins-ci.org/commit/plain-credentials-plugin/b613c48b4658afce32d7b070c66c98ef7e29191f Log: JENKINS-34877 Fix typos Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [plain-credentials-plugin] (JENKINS-34877) Fix PCT against 2.x baseline and migrate to 2.9 parent POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34877 Re: Fix PCT against 2.x baseline and migrate to 2.9 parent POM Code changed in jenkins User: Armando Fernandez Path: src/test/java/org/jenkinsci/plugins/plaincredentials/BaseTest.java src/test/java/org/jenkinsci/plugins/plaincredentials/FileCredentialsTest.java http://jenkins-ci.org/commit/plain-credentials-plugin/0eb953a6a6399155d24f6860617114e7512a8a44 Log: JENKINS-34877 Add basic test suite for creating, updating and removing credentials. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
