[JIRA] [google-container-registry-auth-plugin] (JENKINS-32700) 403 Forbidden
Title: Message Title James Green commented on JENKINS-32700 Re: 403 Forbidden This was with one of those two build plugins, choosing the credentials in the drop-down that were provided via your plugin. We were not using the docker command directly. 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-24003) Unable to wipe out workspace
Title: Message Title dan tran commented on JENKINS-24003 Re: Unable to wipe out workspace When the error occurs ( ie click on delete workspace). this is all I have at Jenkins system log Feb 22, 2016 6:11:29 PM INFO org.jenkinsci.plugins.p4.PerforceScm processWorkspaceBeforeDeletion processWorkspaceBeforeDeletion The global settings have both checkboxes unchecked 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] [multi-branch-project-plugin] (JENKINS-32255) Multi-branch multi-configuration projects
Title: Message Title Rick Liu commented on JENKINS-32255 Re: Multi-branch multi-configuration projects +1 This is a must-have feature for an enterprise. 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] [analysis-core-plugin] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title talios commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Have recently started seeing this on our Jenkins instance as well ( Centos 5 based ) running under Java 7 still. The `clearPassword` idea above doesn't seem to solve the issue either. Does anyone have any further to report on this issue? Any 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] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Arnaud Héritier commented on JENKINS-32861 Re: Checking Dockerfile in project doesn't work with Slave Fixed in 1.6.5 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] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Arnaud Héritier resolved as Fixed Jenkins / JENKINS-32861 Checking Dockerfile in project doesn't work with Slave Change By: Arnaud Héritier Status: Reopened 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] [core] (JENKINS-28289) JNLP slave should exclude non proxy hosts when connecting via HTTP proxy
Title: Message Title Arnaud Héritier commented on JENKINS-28289 Re: JNLP slave should exclude non proxy hosts when connecting via HTTP proxy remoting 2.54 including the required fix was released 3 days ago but not yet merged into master PR to upgrade remoting in master: https://github.com/jenkinsci/jenkins/pull/2054 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-28086) JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts)
Title: Message Title Arnaud Héritier commented on JENKINS-28086 Re: JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts) remoting 2.54 including the required fix was released 3 days ago This one duplicates JENKINS-28289 ? 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Can you give the list of all your plugins? I am wondering if one of the plugins includes something like Log4J. 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title Samuel Lopez commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Thanks for the reply We have quite a few plugins, is there a particular set I should be looking at? Yes it happens when I restart Jenkins 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-33093) Support new feature of upcoming Gradle Plugin 1.25
Title: Message Title Jochen Hinrichsen created an issue Jenkins / JENKINS-33093 Support new feature of upcoming Gradle Plugin 1.25 Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 22/Feb/16 11:48 PM Priority: Trivial Reporter: Jochen Hinrichsen Gradle Plugin up to version 1.24 passes job parameters as system properties (-D). The new Gradle Plugin 1.25 (yet to be released) will offer an option to pass job parameters as Gradle Properties (-P). The new feature is version agnostic and will only kick in for versions >= 1.25. For compatibility reasons, the default is to use the old behaviour (system properties). The PR for the Gradle Plugin feature itself is https://github.com/jenkinsci/gradle-plugin/pull/27 Add Comment
[JIRA] [ec2-plugin] (JENKINS-31323) When testing connection, "problem creating RSA private key" exception is raised
Title: Message Title Brian Smith edited a comment on JENKINS-31323 Re: When testing connection, "problem creating RSA private key" exception is raised After struggling with the same error for days , finally realized it was because the Key Pair being used was password protected, which the plugin doesnt support. Since the generate keypair gives a _javascript_ error in current version of chrome, try creating a new Key Pair from the AWS management console, opening up the .pem in a text editor, and pasting it into the private key text field of the ec2-plugin config. 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] [ec2-plugin] (JENKINS-31323) When testing connection, "problem creating RSA private key" exception is raised
Title: Message Title Brian Smith commented on JENKINS-31323 Re: When testing connection, "problem creating RSA private key" exception is raised After struggling with the same error for days, finally realized it was because the Key Pair being used was password protected, which the plugin doesnt support. Since the generate keypair gives a _javascript_ error in current version of chrome, try creating a new Key Pair from the AWS management console, opening up the .pem in a text editor, and pasting it into the private key text field of the ec2-plugin config. 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-32517) Queue#getApproximateItemsQuickly can cache invalid results
Title: Message Title Arnaud Héritier commented on JENKINS-32517 Re: Queue#getApproximateItemsQuickly can cache invalid results Due to the UI inconsistencies it can create could we backport it in the next 1.642 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] [tfs-plugin] (JENKINS-33092) TFS Plugin throws error: TF400367: The request could not be performed due to a host type mismatch.
Title: Message Title Rick Femmer created an issue Jenkins / JENKINS-33092 TFS Plugin throws error: TF400367: The request could not be performed due to a host type mismatch. Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 22/Feb/16 10:36 PM Environment: Jenkins ver. 1.647 Priority: Minor Reporter: Rick Femmer Jenkins ver. 1.647: using TFS plugin to create build Using TFS Online VS 2015: Tried with and alternate credentials and using a token. When creating a build I get this error: \ Building in workspace C:\Program Files (x86)\Jenkins\jobs\ECCO(DEV)\workspace FATAL: com.microsoft.tfs.core.exceptions.TECoreException: Server was unable to process request. ---> TF400367: The request could not be performed due to a host type mismatch. Please check any connection information and verify the information is correct. The request was executed against a Application. java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: Server was unable to process request. ---> TF400367: The request could not be performed due to a host type mismatch. Please check any connection information and verify the information is correct. The request was executed against a Application. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:193) at
[JIRA] [support-core-plugin] (JENKINS-33091) Allow to create an issue and submit a bundle into the OSS tracker
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-33091 Allow to create an issue and submit a bundle into the OSS tracker Change By: Arnaud Héritier We want to simplify the ability to create in the OSS tracker. For that the user gives a subject/description of the problem, its Jira credentials (or maybe we could use SSO ?) and the options to generate a bundle.I have in mind something like proposed by Jira and similar products. See the doc here : https://confluence.atlassian.com/jira/getting-help-185729600.html It requires to have JENKINS-21670 which must be enabled by default to not risk to disclose publicly users informations 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] [support-core-plugin] (JENKINS-33091) Allow to create an issue and submit a bundle into the OSS tracker
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-33091 Allow to create an issue and submit a bundle into the OSS tracker Issue Type: New Feature Assignee: Steven Christou Components: support-core-plugin Created: 22/Feb/16 10:22 PM Priority: Minor Reporter: Arnaud Héritier We want to simplify the ability to create in the OSS tracker. For that the user gives a subject/description of the problem, its Jira credentials (or maybe we could use SSO ?) and the options to generate a bundle. I have in mind something like proposed by Jira and similar products. See the doc here : https://confluence.atlassian.com/jira/getting-help-185729600.html Add Comment
[JIRA] [support-core-plugin] (JENKINS-33090) Ease the management bundles by the administrator
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-33090 Ease the management bundles by the administrator Issue Type: New Feature Assignee: Steven Christou Components: support-core-plugin Created: 22/Feb/16 10:13 PM Priority: Minor Reporter: Arnaud Héritier The Support core plugins automatically creates a bundle when the instance starts and after every hour. These bundles are directly stored under JENKINS_HOME/support but the user have to access to the Jenkins server FS to manage them. We would like to add the following features : List bundles stored on the instance (name + creation date + size) Allow to download each bundle Allow to delete each bundle or all bundles Allow to browse the content of each bundle
[JIRA] [support-core-plugin] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Arnaud Héritier commented on JENKINS-21670 Re: Option to anonymize customer labels IPs and network settings have also to be shadowed. 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] [next-build-number-plugin] (JENKINS-33046) Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs
Title: Message Title Alexander Komarov commented on JENKINS-33046 Re: Next Build Number plugin doesn't work for Workflow or Multi-branch Workflow jobs Any obvious errors in the logs? (either on startup, during job creation, or while displaying the page) I currently don't have Workflow installed in any of my instances and may not have the opportunity for a bit. 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-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title Bartosz Janda assigned an issue to Unassigned Jenkins / JENKINS-18032 "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Change By: Bartosz Janda Assignee: Bartosz Janda 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-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title Bartosz Janda assigned an issue to Bartosz Janda Jenkins / JENKINS-18032 "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Change By: Bartosz Janda Assignee: Bartosz Janda 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] [cobertura-plugin] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title kyle rockman commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin +100 on this, we just switched to jenkins pipeline (formerly workflow) and this plugin is not supported. I would hate to have to roll my own solution just to get my coverage reports publisher need back. 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] [matrix-auth-plugin] (JENKINS-31860) java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31860 java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL Change By: Jesse Glick Component/s: matrix-auth-plugin Component/s: core Component/s: branch-api-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] [matrix-auth-plugin] (JENKINS-31860) java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL
Title: Message Title Jesse Glick resolved as Fixed 1.3 Jenkins / JENKINS-31860 java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL Change By: Jesse Glick 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] [svn-tag-plugin] (JENKINS-33089) Tagging when Multiple Repos used, user can Select the only Repos to be Tagged & Define seperate Tag Base URL's
Title: Message Title Raghavendra Tallam created an issue Jenkins / JENKINS-33089 Tagging when Multiple Repos used, user can Select the only Repos to be Tagged & Define seperate Tag Base URL's Issue Type: Improvement Assignee: k2nakamura Attachments: Capture.PNG Components: svn-tag-plugin Created: 22/Feb/16 8:49 PM Labels: svn-tag multiple-repo tag tags Priority: Minor Reporter: Raghavendra Tallam Current Scenario: When SVN Code is checked out with Multiple Modules, and Tagging Option can be Defined with only one Generic URL TAG. All the Modules are to be Tagged as Mandatory and User dont have any Option to Uncheck or Not Tag the Unwanted Repo. Cant Skip tagging for a single Repo. Improvement Suggestion: When using Multiple SVN locations, User should be given option to Choose which Repo is to be Tagged and With customized "Tag Base URL" option.
[JIRA] [matrix-auth-plugin] (JENKINS-31860) java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31860 java.lang.ClassCastException: jenkins.branch.MultiBranchProject$3 cannot be cast to hudson.security.SidACL Change By: Jesse Glick Labels: multibranch 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-23378) Raise minimum requirement to servlet 3.1
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23378 Re: Raise minimum requirement to servlet 3.1 Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml war/pom.xml http://jenkins-ci.org/commit/jenkins/2b90f1c6cbd9fe9779a5e94b96f503fef5a08308 Log: JENKINS-23378 new version of hudson-dev plugin that supports Servlet 3.1 I had to disable annotation scanning or else it adds too much overhead to the startup time. 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-31153) Rename workflow to pipeline
Title: Message Title Jesse Glick commented on JENKINS-31153 Re: Rename workflow to pipeline The current multimodule repository is not named exactly according to any given artifactId, though the naming is of course analogous. Or are you also proposing to split out the ten different Pipeline plugins each into their own separate repos? I do in fact want to do this, at least for some of the plugins, and in that case yes I would expect the GH repo name to be artifactId-plugin. There is a bunch of work to be done here. 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title
Ryan Pavlik updated an issue
Jenkins / JENKINS-33088
Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Change By:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs.*After further investigation*, it turned out not to be related to the launch method, but to a configuration detail that didn't negatively affect upload from the master node, only from remote nodes. This upload task apparently had *an empty "metadata tag" key/value pair* added to it at some point in the past, which hadn't caused a problem until the actual promotion/upload occurred on a remote node. *Deleting the empty key/value pair* did allow for successful completion of the upload. (see screenshot)!screenshot-1.png|thumbnail! {noformat} Building remotely on jessie-cloud (8.3 linux-build amd64-Debian Debian jessie ndk build Debian-8.3 amd64 Linux Debian-8 amd64-Debian-8.3) in workspace /home/jenkins/root/workspace/OSVR-Core-DocsPromoting OSVR-Core-Docs #220Publish artifacts to S3 Bucket Using S3 profile: resource.osvr.comPublish artifacts to S3 Bucket bucket=resource.osvr.com/docs/OSVR-Core, file=APIBaseC_8h.html region=us-west-1, upload from slave=true managed=false , server encryption falseERROR: Failed to upload filesjava.io.IOException: put Destination [bucketName=resource.osvr.com, objectName=docs/OSVR-Core/APIBaseC_8h.html]: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f:: Failed after 1 tries. at hudson.plugins.s3.S3Profile.upload(S3Profile.java:202) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:182) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:345) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:287) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:232) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f at
[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title
Ryan Pavlik updated an issue
Jenkins / JENKINS-33088
Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Change By:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs.*After further investigation*, it turned out not to be related to the launch method, but to a configuration detail that didn't negatively affect upload from the master node, only from remote nodes. This upload task apparently had *an empty "metadata tag" key/value pair* added to it at some point in the past, which hadn't caused a problem until the actual promotion/upload occurred on a remote node. *Deleting the empty key/value pair* did allow for successful completion of the upload. (see screenshot)!screenshot-1.png|thumbnail!{noformat}Building remotely on jessie-cloud (8.3 linux-build amd64-Debian Debian jessie ndk build Debian-8.3 amd64 Linux Debian-8 amd64-Debian-8.3) in workspace /home/jenkins/root/workspace/OSVR-Core-DocsPromoting OSVR-Core-Docs #220Publish artifacts to S3 Bucket Using S3 profile: resource.osvr.comPublish artifacts to S3 Bucket bucket=resource.osvr.com/docs/OSVR-Core, file=APIBaseC_8h.html region=us-west-1, upload from slave=true managed=false , server encryption falseERROR: Failed to upload filesjava.io.IOException: put Destination [bucketName=resource.osvr.com, objectName=docs/OSVR-Core/APIBaseC_8h.html]: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f:: Failed after 1 tries. at hudson.plugins.s3.S3Profile.upload(S3Profile.java:202) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:182) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:345) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:287) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:232) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f at
[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title Ryan Pavlik commented on JENKINS-33088 Re: Can't upload to S3 direct from slaves if there is an empty "Metadata" field Updated to note that the issue was the presence of a configuration detail that didn't affect upload when the job/promotion ran on the master, but did affect it when it ran remotely. 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title Ryan Pavlik updated an issue Jenkins / JENKINS-33088 Can't upload to S3 direct from slaves if there is an empty "Metadata" field Change By: Ryan Pavlik Priority: Major Minor 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title
Ryan Pavlik updated an issue
Jenkins / JENKINS-33088
Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Change By:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs.*After further investigation*, it turned out not to be related to the launch method, but to a configuration detail that didn't negatively affect upload from the master node, only from remote nodes. This upload task apparently had *an empty "metadata tag" key/value pair* added to it at some point in the past, which hadn't caused a problem until the actual promotion/upload occurred on a remote node. *Deleting the empty key/value pair* did allow for successful completion of the upload. (see screenshot)!screenshot-1.png|thumbnail! {{ Building remotely on jessie-cloud (8.3 linux-build amd64-Debian Debian jessie ndk build Debian-8.3 amd64 Linux Debian-8 amd64-Debian-8.3) in workspace /home/jenkins/root/workspace/OSVR-Core-DocsPromoting OSVR-Core-Docs #220Publish artifacts to S3 Bucket Using S3 profile: resource.osvr.comPublish artifacts to S3 Bucket bucket=resource.osvr.com/docs/OSVR-Core, file=APIBaseC_8h.html region=us-west-1, upload from slave=true managed=false , server encryption falseERROR: Failed to upload filesjava.io.IOException: put Destination [bucketName=resource.osvr.com, objectName=docs/OSVR-Core/APIBaseC_8h.html]: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f:: Failed after 1 tries. at hudson.plugins.s3.S3Profile.upload(S3Profile.java:202) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:182) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:345) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:287) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:232) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f at
[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title
Ryan Pavlik updated an issue
Jenkins / JENKINS-33088
Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Change By:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs.*After further investigation*, it turned out not to be related to the launch method, but to a configuration detail that didn't negatively affect upload from the master node, only from remote nodes. This upload task apparently had *an empty "metadata tag" key/value pair* added to it at some point in the past, which hadn't caused a problem until the actual promotion/upload occurred on a remote node. *Deleting the empty key/value pair* did allow for successful completion of the upload. (see screenshot) !screenshot-1.png|thumbnail! {{Building remotely on jessie-cloud (8.3 linux-build amd64-Debian Debian jessie ndk build Debian-8.3 amd64 Linux Debian-8 amd64-Debian-8.3) in workspace /home/jenkins/root/workspace/OSVR-Core-DocsPromoting OSVR-Core-Docs #220Publish artifacts to S3 Bucket Using S3 profile: resource.osvr.comPublish artifacts to S3 Bucket bucket=resource.osvr.com/docs/OSVR-Core, file=APIBaseC_8h.html region=us-west-1, upload from slave=true managed=false , server encryption falseERROR: Failed to upload filesjava.io.IOException: put Destination [bucketName=resource.osvr.com, objectName=docs/OSVR-Core/APIBaseC_8h.html]: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f:: Failed after 1 tries. at hudson.plugins.s3.S3Profile.upload(S3Profile.java:202) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:182) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:345) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:287) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:232) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f at
[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title Ryan Pavlik updated an issue Jenkins / JENKINS-33088 Can't upload to S3 direct from slaves if there is an empty "Metadata" field Change By: Ryan Pavlik Attachment: screenshot-1.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] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title
Ryan Pavlik updated an issue
Jenkins / JENKINS-33088
Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Change By:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs. I haven't tried uploading other artifacts from this build node *After further investigation*, it turned out not to S3 that I can think of offhand be related to the launch method , and I haven't tried launching this node in another way, but this to a configuration detail that didn't happen when uploading negatively affect upload from the linux master node, nor only from the Java Web Start/service-launched Windows remote nodes that . This upload task apparently had *an empty "metadata tag" key/value pair* added to S3 (all of it at some point in the past, which are EC2 and all hadn't caused a problem until the actual promotion/upload occurred on a remote node. *Deleting the empty key/value pair* did allow for successful completion of which have " the upload from slave" checked) . {{Building remotely on jessie-cloud (8.3 linux-build amd64-Debian Debian jessie ndk build Debian-8.3 amd64 Linux Debian-8 amd64-Debian-8.3) in workspace /home/jenkins/root/workspace/OSVR-Core-DocsPromoting OSVR-Core-Docs #220Publish artifacts to S3 Bucket Using S3 profile: resource.osvr.comPublish artifacts to S3 Bucket bucket=resource.osvr.com/docs/OSVR-Core, file=APIBaseC_8h.html region=us-west-1, upload from slave=true managed=false , server encryption falseERROR: Failed to upload filesjava.io.IOException: put Destination [bucketName=resource.osvr.com, objectName=docs/OSVR-Core/APIBaseC_8h.html]: java.io.IOException: remote file operation failed: /home/jenkins/root/workspace/OSVR-Core-Docs/build/docs-external/html/APIBaseC_8h.html at hudson.remoting.Channel@763d94d0:jessie-cloud: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@5eda3a2f:: Failed after 1 tries. at hudson.plugins.s3.S3Profile.upload(S3Profile.java:202) at hudson.plugins.s3.S3BucketPublisher.perform(S3BucketPublisher.java:182) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:345) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:287) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.Run.run(Run.java:1676) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:232) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Caused by: java.io.IOException:
[JIRA] [s3-plugin] (JENKINS-33088) Can't upload to S3 direct from slaves if there is an empty "Metadata" field
Title: Message Title Ryan Pavlik updated an issue Jenkins / JENKINS-33088 Can't upload to S3 direct from slaves if there is an empty "Metadata" field Change By: Ryan Pavlik Summary: Can't upload to S3 directly direct from SSH-launched *nix slaves if there is an empty "Metadata" field 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 directly from SSH-launched *nix slaves
Title: Message Title Ryan Pavlik updated an issue Jenkins / JENKINS-33088 Can't upload to S3 directly from SSH-launched *nix slaves Change By: Ryan Pavlik Priority: Minor Major 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] [s3-plugin] (JENKINS-33088) Can't upload to S3 directly from SSH-launched *nix slaves
Title: Message Title
Ryan Pavlik created an issue
Jenkins / JENKINS-33088
Can't upload to S3 directly from SSH-launched *nix slaves
Issue Type:
Bug
Assignee:
Michael Watt
Components:
s3-plugin
Created:
22/Feb/16 6:48 PM
Environment:
Debian Wheezy x64 on EC2 running LTS Jenkins ver. 1.642.1 installed via the apt repo (master) running Java 7u95-2.6.4-1~deb7u1 (from debian package), Debian Jessie x64 on EC2 launched over SSH (build node) running Java 7u95-2.6.4-1~deb8u1 (from debian package)
Priority:
Minor
Reporter:
Ryan Pavlik
Recently added a Linux build node to our Jenkins setup to build on Jessie, as our upgraded Wheezy wasn't cutting it, so now a job that just runs a build target to generate documentation (doxygen, but not using Jenkins doxygen plugin), then has a "promotion" to upload it to S3 "from slave" is running on that machine instead of on our master node. This has resulted in the promotions failing, with this error that I'll paste in full below, but with the distinguishing line that I can see here: {{Caused by: java.io.NotSerializableException: hudson.plugins.s3.MetadataPair }} That appears to be the main difference between this log and other similar errors I've found when searching - and the line that I haven't found on other logs.
I haven't tried uploading other artifacts from this build node to S3 that I can think of
[JIRA] [core] (JENKINS-23378) Raise minimum requirement to servlet 3.1
Title: Message Title Kohsuke Kawaguchi commented on JENKINS-23378 Re: Raise minimum requirement to servlet 3.1 I've updated maven-hudson-dev-plugin to Jetty 9.2 as well, and the corresponding change to the 2.0 branch is going through the pipeline. The remaining work at this point is: Update maven-hpi-plugin Update web.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] [job-dsl-plugin] (JENKINS-32678) Add support for workflow Pipeline script from SCM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32678 Re: Add support for workflow Pipeline script from SCM Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Migration.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/CpsContext/script.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/WorkflowDefinitionContext/cps.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/CpsContext/script.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext/cps.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext/cpsScm.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/CpsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/WorkflowDefinitionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/CpsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/CpsScmContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/jobs/WorkflowJob.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/WorkflowJobSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/bc3ba2d93834cacccb6c3beb56faf3ac4f6fc63e Log: added support for loading pipeline definitions from SCM [FIXED JENKINS-32678] 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-32678) Add support for workflow Pipeline script from SCM
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32678 Add support for workflow Pipeline script from SCM Change By: SCM/JIRA link daemon 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] [job-dsl-plugin] (JENKINS-32678) Add support for workflow Pipeline script from SCM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32678 Re: Add support for workflow Pipeline script from SCM Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Migration.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/CpsContext/script.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/WorkflowDefinitionContext/cps.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/CpsContext/script.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext/cps.groovy job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext/cpsScm.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/CpsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/WorkflowDefinitionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/CpsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/CpsScmContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/workflow/WorkflowDefinitionContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/jobs/WorkflowJob.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/WorkflowJobSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/5c50750bc6658b55984608021a8244cd9c013af9 Log: Merge pull request #758 from daspilker/ JENKINS-32678 JENKINS-32678 added support for loading pipeline definitions from SCM Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/0ecae722112a...5c50750bc665 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
[JIRA] [durable-task-plugin] (JENKINS-27152) Store sh control files outside of workspace
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-27152
Re: Store sh control files outside of workspace
Some use cases:h3. (?)Linux user home(?)Maybe interesting to locate the linux {{user.home}} under this workspace working folder. /!\ It may break many things if a plugin does this without 'collaborating' with other plugins but it could be a "job config" or a "jenkins global config".* {{.ssh/config}} can only be defined under {{$HOME}}. Are there some config that we would like to define "per job"? See http://www.cyberciti.biz/faq/create-ssh-config-file-on-linux-unix/* git: most git configuration can be passed through environment variables and thus it is not required to specify a per workspace setup. Moreover, the {{PREFIX}} environment variable allow to define the "system wide" {{$PREFIX/etc/gitconfig}} https://git-scm.com/book/en/v2/Git-Internals-Environment-Variablesh3. credentials-binding-plugin* Use a "secrets" folder to store file based credentials: see [FileBinding.secretsDir(workspace)|https://github.com/jenkinsci/credentials-binding-plugin/blob/3cd54c0a07fcc36ded63a39a2455f1d7337a8934/src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/FileBinding.java#L93-L93]h3. ssh-agent* Creates a tmp file for the local socket in java.io.tmp: [AgentServer.createLocalSocketAddress()|https://github.com/jenkinsci/ssh-agent-plugin/blob/576fc86a7fa2c646e030f50abf67bdf3e0cefdcb/src/main/java/com/cloudbees/jenkins/plugins/sshagent/jna/AgentServer.java#L136-L136]{{File socket = File.createTempFile("jenkins", ".jnr");}}h3. config-file-provider* Creates a tmp folder to store config files [ManagedFileUtil. createTempFile()|https://github.com/jenkinsci/config-file-provider-plugin/blob/d69c1f5a6e400b54d356ba30cb42cd725db72025/src/main/java/org/jenkinsci/plugins/configfiles/buildwrapper/ManagedFileUtil.java#L57-L57]h3. Maven Pipeline Step Integration * Would need to create a tmp folder to prepend to the PATH in which we would create an ephemeral "mvn" file that would inject the proper command line parameters that cannot be passed as environment variables ({{\-\-settings}}, {{\-\-global-settings}}, {{\-\-debug}}, {{\-\-errors}}, {{\-\-batch\-mode}}...). See [Sonatype >>6.1. Maven Command Line Options|https://books.sonatype.com/mvnref-book/reference/running-sect-options.html]* (?) it would be interesting to optionally specify a local-repo under this specific folder (see {{\-Dmaven.repo.local=...}})h3. Gradle Pipeline Step* Maybe interesting to specify a custom {{GRADLE_USER_HOME}}, see [Gradle >> Chapter 11. The Build Environment|https://docs.gradle.org/current/userguide/build_environment.html]* (?) maybe interesting to have a per workspace local.repo
Add Comment
[JIRA] [google-container-registry-auth-plugin] (JENKINS-32700) 403 Forbidden
Title: Message Title Wei Z commented on JENKINS-32700 Re: 403 Forbidden Sorry for late reply. I have been on vacation. Are you expecting this plugin to work with docker command directly? Or are you also using it with a compatible plugin like "Docker Build Step Plugin" or "CloudBees Docker Custom Build Environment Plugin"? This plugin is not implemented for use with docker command directly. 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-31154) 2.0: provide better workflow visualization out of the box
Title: Message Title Baptiste Mathus commented on JENKINS-31154 Re: 2.0: provide better workflow visualization out of the box gitt apparently, the plugin has been released in alpha version. That means you should find in the experimental update center. My 2 cents 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] [amazon-ecs-plugin] (JENKINS-33087) HTTP proxy configuration in jenkins tool is faling
Title: Message Title dasari bhaskar created an issue Jenkins / JENKINS-33087 HTTP proxy configuration in jenkins tool is faling Issue Type: Bug Assignee: dasari bhaskar Attachments: Jenkins_configuration.JPG Components: amazon-ecs-plugin Created: 22/Feb/16 5:58 PM Environment: Sonar (Jenkins hosted server) Labels: jenkins Priority: Major Reporter: dasari bhaskar I have configured HTTP proxy settings in Jenkins tool(http://vs4bz.bc:8181/hudson/manage), in Manage Jenkins->Manage plugins->Advanced After I configured respective proxy details I am trying to install plugins from available plugins tab and I am facing the below issue "*java.io.IOException: Server returned HTTP response code: 403 for URL:
[JIRA] [core] (JENKINS-28155) Job fails with [An existing connection was forcibly closed by the remote host]
Title: Message Title Tim Jackson commented on JENKINS-28155 Re: Job fails with [An existing connection was forcibly closed by the remote host] Still an issue in Jenkins ver. 1.641 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] [monitoring-plugin] (JENKINS-31619) java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N
Title: Message Title Aditya Joshi commented on JENKINS-31619 Re: java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N I'm able to reproduce the issue in Jenkins 1.632. We have installed Jenkins in a custom location and use JENKINS_HOME. However, I couldn't find any directory called $JENKINS_HOME/.jenkins or $HOME/.jenkins (for the user running Jenkins instance). The error happens at runtime and we see it almost every hour in the Jenkins log files. Is there any env variable we can use before installing the Monitoring plugin (https://wiki.jenkins-ci.org/display/JENKINS/Monitoring), so to avoid seeing this error? Thanks. 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] [github-plugin] (JENKINS-33086) Successful build notification does not work
Title: Message Title Maciej Nowak created an issue Jenkins / JENKINS-33086 Successful build notification does not work Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 22/Feb/16 4:59 PM Environment: Windows 10 x64 Oracle JRE 1.7.0_79-b15 x64 Workflow plugin: 1.13 Github plugin: 1.17.0 GitHub API plugin: 1.72 Jenkins running from command line Labels: github-plugin multibranch Priority: Major Reporter: Maciej Nowak Minimal reproduction is here: https://github.com/Novakov/jenkins-github-test/pull/1 I've got Jenkins with multibranch job configured to watch GitHub repository. One of the branches (build) contains Jenkinsfile using GitHub plugin to set commit status at begin of build and at the end. After executing build GitHub pull request page shows 'Build successful' but still thinks that build is in progress.
[JIRA] [jira-plugin] (JENKINS-28946) JIRA support for Workflow jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28946 Re: JIRA support for Workflow jobs Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/56abe0f31eb1505ba2e66cd7b1d9bd4525d839b7 Log: JENKINS-28946 Noting release of https://github.com/jenkinsci/jira-plugin/pull/72. 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] [log-parser-plugin] (JENKINS-33085) Log Parser Plugin Not Honoring Regex Patterns that Span Multiple Lines in Console Output
Title: Message Title
Jacob Hoopes created an issue
Jenkins / JENKINS-33085
Log Parser Plugin Not Honoring Regex Patterns that Span Multiple Lines in Console Output
Issue Type:
Bug
Assignee:
Manuel Jesús Recena Soto
Components:
log-parser-plugin
Created:
22/Feb/16 4:30 PM
Environment:
Jenkins 1.649 Log Parser Plugin 2.0
Priority:
Major
Reporter:
Jacob Hoopes
Greetings,
I created the following rules file for the Log Parser Plugin to parse console output for the effectiveness of TLS certificates implemented on various sites leveraging Qualys's "ssllabs-scan" tool (found at https://github.com/ssllabs/ssllabs-scan):
# Fail
error /("grade"(:\s+|:)("D\+"|"D"|"D-"|"F")|Err: Certificate not valid for domain name|Err: Unable to connect to server)/
# Warn as TLS Certs Begin to Degrade
warning /"grade"(:\s+|:)("B\+"|"B"|"B-"|"C\+"|"C"|"C-")/
# Build Success
info /"grade"(:\s+|:)("A\+"|"A"|"A-")/
As an example, a job in Jenkins was created to execute the following shell command to analyze the TLS cert implementation of console.aws.amazon.com:
[JIRA] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Anton Kuznetsov edited a comment on JENKINS-26379 Re: Jenkins - ssh connection exception there are two workaround is to ways:1. update of "JSch dependency plugin" with jsch-0.1.53.jar2. modify key exchange algorithm for you on your slave sshd :vi /etc/ssh/sshd_config<<
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title Dan Tranter commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data Upon update from 1.57 -> 1.58 and restart, monitoring graphs are now displaying again.. However I'm still seeing warnings/exception collecting data, unsure if that's related to previous failure. Unfortunately the current debugging log no longer contains entries from the time of failure: Last collect time: 861 ms Display time: 678 ms Memory overhead estimate: < 5 Mb Disk usage: 39 Mb Purge the obsolete files JavaMelody 1.58.0 Debugging logs Only the last 50 messages are displayed Fri Feb 19 20:07:12 CST 2016 DEBUG Server: jetty/winstone-2.8 Fri Feb 19 20:07:12 CST 2016 DEBUG Webapp context: Fri Feb 19 20:07:12 CST 2016 DEBUG JavaMelody version: 1.58.0 Fri Feb 19 20:07:12 CST 2016 DEBUG JavaMelody classes loaded from: file:/auto/ncs-jenkins/ncs-jenkins/jenkins/plugins/monitoring/WEB-INF/lib/javamelody-core-1.58.0.jar Fri Feb 19 20:07:12 CST 2016 DEBUG Host: host5@123.123.123.123 Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: storage-directory=//auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: http-transform-pattern=/\d+/|/site/. |avadoc/. |/ws/. |obertura/. |estReport/. |iolations/file/. |/user/. |/static/\w /|/adjuncts/\w+/|/bound/[\w\-]+ Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: custom-reports=Jenkins Info,About Monitoring Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: no-database=true Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: gzip-compression-disabled=true Fri Feb 19 20:07:12 CST 2016 DEBUG parameter defined: system-actions-enabled=true Fri Feb 19 20:07:12 CST 2016 DEBUG log listeners initialized Fri Feb 19 20:07:12 CST 2016 DEBUG counters initialized Fri Feb 19 20:07:12 CST 2016 DEBUG counters data read from files in /auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring/_host5 Fri Feb 19 20:07:12 CST 2016 DEBUG collect task scheduled every 60s Fri Feb 19 20:07:13 CST 2016 DEBUG first collect of data done Fri Feb 19 20:07:13 CST 2016 DEBUG JavaMelody filter init done in 308 ms Fri Feb 19 20:07:13 CST 2016 DEBUG counters data read from files in /auto/ncs-jenkins/ncs-jenkins/jenkins/monitoring/nodes Sat Feb 20 00:00:29 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 14327 KB Sat Feb 20 00:00:32 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 134286 KB Sun Feb 21 00:00:35 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 27464 KB Sun Feb 21 00:00:39 CST 2016 DEBUG Obsolete files deleted. JavaMelody disk usage: 130530 KB Sun Feb 21 07:02:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:03:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:04:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:05:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:06:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:07:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:08:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:09:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:10:36 CST 2016 WARN exception while collecting data Sun Feb 21 07:11:36 CST 2016 WARN exception while collecting
[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches
Title: Message Title michael giroux created an issue Jenkins / JENKINS-33084 Git Parameter plugin should prune stale remote branches Issue Type: Bug Assignee: Niklaus Giger Components: git-parameter-plugin Created: 22/Feb/16 4:22 PM Priority: Minor Reporter: michael giroux The git-parameter plugin presents a list of branches based on the current workspace. The list can include remote branches that have been deleted. The plugin should prune the remote branches (similar to git plugin prune stale remote branches) before presenting the list. Add Comment
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-32542) Maven project failed with "Connection refused" when built in a docker Container
Title: Message Title Steven Dwyer commented on JENKINS-32542 Re: Maven project failed with "Connection refused" when built in a docker Container Having same issue. 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-32780) Parameterize Multibranch Pipeline via Jenkinsfile
Title: Message Title Jesse Glick commented on JENKINS-32780 Re: Parameterize Multibranch Pipeline via Jenkinsfile Michael Sharp see JENKINS-29711. 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-27152) Store sh control files outside of workspace
Title: Message Title Jesse Glick commented on JENKINS-27152 Re: Store sh control files outside of workspace Plan to file a core PR to not only introduce a formal API for this temporary location (currently planned as a helper method in WorkspaceList), but also to consider it in some places, like workspace cleanup. 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] [disk-usage-plugin] (JENKINS-33083) Missing Icons in the Job overview
Title: Message Title Volker Füßler created an issue Jenkins / JENKINS-33083 Missing Icons in the Job overview Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 22/Feb/16 3:06 PM Priority: Minor Reporter: Volker Füßler In a Job Overview the Icons of the disk usage plugins are missing. They 'plugin' icon is shown, but not the folder Images (See the attached screenshot). I think (without having tested it), its a bug in the jelly code: https://github.com/jenkinsci/disk-usage-plugin/blob/master/src/main/resources/hudson/plugins/disk_usage/ProjectDiskUsageAction/jobMain.jelly There you see: working: not working: /plugin/disk-usage/icons/directory16.png" ...
[JIRA] [durable-task-plugin] (JENKINS-27152) Store sh control files outside of workspace
Title: Message Title Jesse Glick commented on JENKINS-27152 Re: Store sh control files outside of workspace Maybe interesting to locate the Linux user.home under this workspace working folder. $HOME that is. Seems too dangerous, and anyway users may reasonably be expecting configuration files in ~slaveacct/ to be honored. .ssh/config can only be defined under $HOME If true, this is a limitation of SSH we would need to work around, if any plugin wishes to modify that configuration. According to man ssh, this is not true: -F configfile Specifies an alternative per-user configuration file. If a configuration file is given on the command line, the system-wide configuration file (/etc/ssh/ssh_config) will be ignored. The default for the per-user configuration file is ~/.ssh/config. BTW Docker used to have such a mandated location for registry credentials, but as of newer versions of the client this is no longer true. 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-32860) Performance issue when retrieving build details of a job run with many artifacts
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-32860 Performance issue when retrieving build details of a job run with many artifacts Change By: Daniel Beck Labels: api regression 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-27152) Store sh control files outside of workspace
Title: Message Title
Cyrille Le Clerc commented on JENKINS-27152
Re: Store sh control files outside of workspace
Some use cases:
(?)Linux user home
Maybe interesting to locate the linux user.home under this workspace working folder. /!\ It may break many things if a plugin does this without 'collaborating' with other plugins but it could be a "job config" or a "jenkins global config".
.ssh/config can only be defined under $HOME. Are there some config that we would like to define "per job"? See http://www.cyberciti.biz/faq/create-ssh-config-file-on-linux-unix/
git: most git configuration can be passed through environment variables and thus it is not required to specify a per workspace setup. Moreover, the PREFIX environment variable allow to define the "system wide" $PREFIX/etc/gitconfig https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables
credentials-binding-plugin
Use a "secrets" folder to store file based credentials: see FileBinding.secretsDir(workspace)
ssh-agent
Creates a tmp file for the local socket in java.io.tmp: AgentServer.createLocalSocketAddress() File socket = File.createTempFile("jenkins", ".jnr");
config-file-provider
Creates a tmp folder to store config files ManagedFileUtil. createTempFile()
Maven Pipeline Step
Would need to create a tmp folder to prepend to the PATH in which we would create an ephemeral "mvn" file that would inject the proper command line parameters that cannot be passed as environment variables (--settings, --global-settings, --debug, --errors, --batch-mode...). See Sonatype >>6.1. Maven Command Line Options
it would be interesting to optionally specify a local-repo under this specific folder (see -Dmaven.repo.local=...)
Gradle Pipeline Step
Maybe interesting to specify a custom GRADLE_USER_HOME, see Gradle >> Chapter 11. The Build Environment
[JIRA] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Release as build-pipeline-plugin-1.5.1. 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title Manuel Jesús Recena Soto resolved as Fixed Jenkins / JENKINS-31746 Build pipeline elements overflow without proper feedback Change By: Manuel Jesús Recena Soto 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] [docker-custom-build-environment-plugin] (JENKINS-32758) Docker build from Dockerfile requires full path to Dockerfile
Title: Message Title
Thomas Collignon commented on JENKINS-32758
Re: Docker build from Dockerfile requires full path to Dockerfile
Now with the new release 1.6.5 you don't have to set $ {WORKSPACE}
, just Dockerfile like you do at the beginning is good.
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] [docker-custom-build-environment-plugin] (JENKINS-32861) Checking Dockerfile in project doesn't work with Slave
Title: Message Title Thomas Collignon commented on JENKINS-32861 Re: Checking Dockerfile in project doesn't work with Slave Seem to be good in 1.6.5 for us. You can close this issue if you want. Thanks you for your quick release 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] [libvirt-slave-plugin] (JENKINS-30691) Unable to connect to remote server
Title: Message Title Ravindra Singh reopened an issue Already commented Jenkins / JENKINS-30691 Unable to connect to remote server Change By: Ravindra Singh Resolution: Not A Defect Status: Resolved 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] [libvirt-slave-plugin] (JENKINS-30691) Unable to connect to remote server
Title: Message Title Ravindra Singh commented on JENKINS-30691 Re: Unable to connect to remote server I am still facing the issue with Centos 6.5 , Centos 7 and Ubuntu 14.04 virsh -c qmue+ssh://root@servername/system list – works fine from commandline tried all possible combincation of credentials with both username/password and ssh name/phasphrase. Have already setup the password less ssh between my jenkins server and the hypervisor still facing the issue with 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] [ssh-credentials-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Anton Kuznetsov commented on JENKINS-26379 Re: Jenkins - ssh connection exception workaround is to modify key exchange algorithm for you slave sshd: vi /etc/ssh/sshd_config <<< KexAlgorithms curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 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] [remoting] (JENKINS-33082) Record PingThread diagnosis information on slave pingthread failure
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33082 Record PingThread diagnosis information on slave pingthread failure Change By: Félix Belzunce Arcos Summary: Record PinThread PingThread diagnosis information on slave pingthread 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] [remoting] (JENKINS-33082) Record PinThread diagnosis information on slave pingthread failure
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-33082 Record PinThread diagnosis information on slave pingthread failure Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: remoting Created: 22/Feb/16 1:47 PM Priority: Minor Reporter: Félix Belzunce Arcos For diagnosis purposes could be nice to record what is happening on the slave side once the pingThread has failed. Add Comment This message was sent
[JIRA] [remoting] (JENKINS-33082) Record PinThread diagnosis information on slave pingthread failure
Title: Message Title Félix Belzunce Arcos started work on JENKINS-33082 Change By: Félix Belzunce Arcos 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] [monitoring-plugin] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring It seems to be a classloader issue with some Log4J jar file. What other plugins are installed ? Is it reproduced if you restart Jenkins ? 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] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title Pavel Janoušek resolved as Fixed Jenkins / JENKINS-32273 Refactor and unify issue handling in CLI commands Change By: Pavel Janoušek Status: Open 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] [remoting] (JENKINS-20947) Failed to monitor for Free Swap Space
Title: Message Title evernat updated an issue Jenkins / JENKINS-20947 Failed to monitor for Free Swap Space Change By: evernat Component/s: monitoring-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] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title James Brown commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data We'll have to get back to you on the logs, but the version was 1.57 at the time the problem was initially raised. It has now been updated to 1.58. 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/webapp/css/main.css src/main/webapp/images/application_xp_terminal.png src/main/webapp/images/user-small.png src/main/webapp/images/user.png http://jenkins-ci.org/commit/build-pipeline-plugin/3e5708a16099c5b3eb1a1b75721ed987b329ddd2 Log: JENKINS-31746 More clean up 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/edead7096cd6a6240de301bf55a47f52d77c34c7 Log: JENKINS-31746 Michael Noack's comments were addressed 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/973ddcd928b7f1da4f150058bcb6f26a5efecdaf Log: JENKINS-31746 More clean up 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: pom.xml src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/main.jelly src/main/resources/index.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/cc2055409288ed8a7d840df6a29793d140c61025 Log: JENKINS-31746 Initial source code modifications 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/fb696a9fe5c9e11c7ac4ba0bb7f574f60dc36963 Log: JENKINS-31746 Clean up 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css src/main/webapp/images/application_view_list.png src/main/webapp/images/application_xp_terminal.png src/main/webapp/images/clock.png http://jenkins-ci.org/commit/build-pipeline-plugin/1b7a57c1168e3b25ac3d022a5b10ac3b3343924c Log: JENKINS-31746 Removing for layout 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: pom.xml src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/BuildSecurityTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/ParameterPassingTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/c33c9ff53022c7bffa451b23a432be927f4cd68f Log: JENKINS-31746 Upgraded Selenium to work with latest version of Firefox and some tests were ignored 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: pom.xml http://jenkins-ci.org/commit/build-pipeline-plugin/e565de51cbb5aae7b67ab962c51db177f8b1a6b0 Log: JENKINS-31746 Improve the layout 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/1154e83b5b34f1347bf5d7d4b80ae1b7927c06ba Log: JENKINS-31746 Polishing details 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/7ca49b7551756aeff0e3e54503dd82484911b824 Log: JENKINS-31746 Removing unnecessary CSS styles 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/webapp/css/main.css src/main/webapp/images/clock-small.png http://jenkins-ci.org/commit/build-pipeline-plugin/1dad74eb6a8a3474a4540cbce74336b5f244f129 Log: JENKINS-31746 Reviewing the semantic markup 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/58e4b19b19c8ca9a918bbeb3a444b59e41339493 Log: JENKINS-31746 Clean up 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-33037) hudson.model.Fingerprint.RangeSet.fromString(...) accepts malformed ranges
Title: Message Title Pavel Janoušek commented on JENKINS-33037 Re: hudson.model.Fingerprint.RangeSet.fromString(...) accepts malformed ranges PR sent. 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: pom.xml http://jenkins-ci.org/commit/build-pipeline-plugin/aa08acadba5a3d176bb127f449b744847d854e47 Log: JENKINS-31746 Unrelated change but easier to deploy 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] [build-pipeline-plugin] (JENKINS-31746) Build pipeline elements overflow without proper feedback
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31746 Re: Build pipeline elements overflow without proper feedback Code changed in jenkins User: Manuel Recena Path: pom.xml src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/main.jelly src/main/resources/index.jelly src/main/webapp/css/main.css src/main/webapp/images/application_view_list.png src/main/webapp/images/clock-small.png src/main/webapp/images/clock.png src/main/webapp/images/user-small.png src/main/webapp/images/user.png src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/BuildPipelineViewTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/BuildSecurityTest.java src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/functionaltest/ParameterPassingTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/e3fb57df01b30a36fc3f0d7888f834af22825b3f Log: Merge pull request #95 from recena/JENKINS-31746 JENKINS-31746[WiP] Improve the layout Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/d3dd54ef56bd...e3fb57df01b3 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-24121) Manual trigger in aggregated view
Title: Message Title Cristiano Fontes commented on JENKINS-24121 Re: Manual trigger in aggregated view Missing this as well, we have a multi environment pipeline and would be great to be able to trigger the latest possible manual job from the aggregated view. 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] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title evernat commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data And also can you copy here the "debugging logs" which are displayed at the botton of the /monitoring page? Thanks 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] [tap-plugin] (JENKINS-32729) TAP Extended Test Results page does not render properly
Title: Message Title Mattias Holmlund commented on JENKINS-32729 Re: TAP Extended Test Results page does not render properly We have the same problem. If you look at the html generated for the page you see that the output all less-than-signs have been replaced with , i.e. has been replaced with tr> which makes the html invalid and has the strange effect that the text is rendered above the table even though it is correctly placed inside the table. Complete snippet: DescriptionDirective # start and stop enabled test-service1Waiting for test t1 to be up failed. Last error: null tr> td colspan='4' class='yaml'> table width="100%" class="yaml">tr>td width='5%' class='hidden'> /td>td style="width: auto;">operator/td>td>pre>fail/pre>/td>/tr>tr>td width='5%' class='hidden'> /td>td style="width: auto;">at/td>td>pre>onRejected (/home/jenkins-slave/workspace/Backend/backend-system-test-ci3/node_modules/co/index.js:81:24)/pre>/td>/tr>/table> /td> /tr> Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [monitoring-plugin] (JENKINS-33050) Monitoring stopped working - exception collecting data
Title: Message Title evernat commented on JENKINS-33050 Re: Monitoring stopped working - exception collecting data Yes, what is the plugin version? 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-33081) Multiple Script Execution Order
Title: Message Title Daniel Dabah updated an issue Jenkins / JENKINS-33081 Multiple Script Execution Order Change By: Daniel Dabah When specifying multiple lines of script wildcards to execute (in the _DSL Scripts_ field), does the plugin make any guarantees about the execution order of the scripts? As of release *job-dsl-1.43*, the execution order has changed (apparently as a result of the fix for *JENKINS \- 30541*). Now, scripts execute in the order that they appear in the _DSL Scripts_ field. I can't rely on this ordering when creating DSL jobs because it's based on knowing the implementation (the .each closure together with the LinkedHashSet that stores the script request). I would like to be able to depend on the execution order. Is it possible to add documentation that will guarantee that scripts will be run in the same order as they appear? 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-33081) Multiple Script Execution Order
Title: Message Title Daniel Dabah updated an issue Jenkins / JENKINS-33081 Multiple Script Execution Order Change By: Daniel Dabah When specifying multiple lines of script wildcards to execute (in the _DSL Scripts_ field), does the plugin make any guarantees about the execution order of the scripts? As of release *job-dsl-1.43*, the execution order has changed (apparently as a result of the fix for *JENKINS - 30541*). Now, scripts execute in the order that they appear in the _DSL Scripts_ field. I can't rely on this ordering when creating DSL jobs because it's based on knowing the implementation (the .each closure together with the LinkedHashSet that stores the script request). I would like to be able to depend on the execution order. Is it possible to add documentation that will guarantee that scripts will be run in the same order as they appear? 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-33081) Multiple Script Execution Order
Title: Message Title Daniel Dabah created an issue Jenkins / JENKINS-33081 Multiple Script Execution Order Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 22/Feb/16 12:03 PM Priority: Minor Reporter: Daniel Dabah When specifying multiple lines of script wildcards to execute (in the DSL Scripts field), does the plugin make any guarantees about the execution order of the scripts? As of release job-dsl-1.43, the execution order has changed (apparently as a result of the fix for JENKINS-30541 ). Now, scripts execute in the order that they appear in the DSL Scripts field. I can't rely on this ordering when creating DSL jobs because it's based on knowing the implementation (the .each closure together with the LinkedHashSet that stores the script request). I would like to be able to depend on the execution order. Is it possible to add documentation that will guarantee that scripts will be run in the same order as they appear? Add Comment
[JIRA] [core] (JENKINS-33068) AsyncPeriodicWork log files are overwritten every execution
Title: Message Title stephenconnolly commented on JENKINS-33068 Re: AsyncPeriodicWork log files are overwritten every execution https://github.com/jenkinsci/jenkins/pull/2047 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.
