[JIRA] [slave-utilization] (JENKINS-29616) java.lang.Exception: The server rejected the connection: None of the protocols were accepted
Title: Message Title Neil Wang commented on JENKINS-29616 Re: java.lang.Exception: The server rejected the connection: None of the protocols were accepted I have got the same error. But this issue is not reproduced 100%. 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] [gerrit-trigger-plugin] (JENKINS-31740) Doesn't take empty passphrases anymore
Title: Message Title Scott Hebert resolved as Duplicate Jenkins / JENKINS-31740 Doesn't take empty passphrases anymore Change By: Scott Hebert Status: Open Resolved Resolution: Duplicate 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] [gerrit-trigger-plugin] (JENKINS-31740) Doesn't take empty passphrases anymore
Title: Message Title Scott Hebert assigned an issue to Scott Hebert Jenkins / JENKINS-31740 Doesn't take empty passphrases anymore Change By: Scott Hebert Assignee: rsandell Scott Hebert Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-31749) Bitbucket pullrequest builder plugin not compatible with Workflow
Title: Message Title
Owen Wood updated an issue
Jenkins / JENKINS-31749
Bitbucket pullrequest builder plugin not compatible with Workflow
Change By:
Owen Wood
Summary:
Bitbucket pullrequest builder plugin not compatible with Jenkins core 1.6* Workflow
Plugin still relies on core 1.509.4. Causes the following issue loading a job when used Using plugin with workflow 1.11 and Jenkins core 1.6*.Throws causes the following when loading job:{code}SEVERE: Failed Loading job my-workflow-jobjava.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.BitbucketBuildTrigger.start(BitbucketBuildTrigger.java:23) at org.jenkinsci.plugins.workflow.job.WorkflowJob.onLoad(WorkflowJob.java:132) at hudson.model.Items.load(Items.java:320) at jenkins.model.Jenkins$17.run(Jenkins.java:2651) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:904) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){code}Plugins:* bitbucket-pullrequest-builder@1.4.7* workflow-job@1.11"Jenkins: Jenkins ver. 1.609.3.1 (CloudBees Jenkins Enterprise 15.05)See attached job config.xml to reproduce
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [envinject-plugin] (JENKINS-23905) Jenkins Slaves launched with the incorrect environment variables
Title: Message Title Andrew Cecil commented on JENKINS-23905 Re: Jenkins Slaves launched with the incorrect environment variables We are seeing the same issue almost every day. Unfortunately this causes the build to fail at the first step for us, before we can even detect the problem and possible do something about it. This only affects our Windows slaves, not Linux slaves. As for others, the "Environment variables" menu displays the correct values, but the slave process is obviously not seeing them. No errors or useful messages are seen in either the build log or the default jenkins system log. On 1.92.1 in Jenkins version 1.638. 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Björn Pedersen commented on JENKINS-31458 Re: Exception when saving job configuration Going back to 1.636 is not an option, as 1.638 fixes some critical security bugs! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-31542) Add Extension-Name field in MANIFEST.MF
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31542 Re: Add Extension-Name field in MANIFEST.MF Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/a72a93a368b8743a56fa60c4bad18ad92df591a9 Log: Merge pull request #676 from daspilker/ JENKINS-31542 updated to gradle-jpi-plugin 0.14.1 Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/1b5e7811b848...a72a93a368b8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-31542) Add Extension-Name field in MANIFEST.MF
Title: Message Title Daniel Spilker resolved as Fixed Will be fixed in job-dsl-plugin 1.41. Jenkins / JENKINS-31542 Add Extension-Name field in MANIFEST.MF Change By: Daniel Spilker 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] [build-environment-plugin] (JENKINS-31793) Jenkins should load build environment data on demand
Title: Message Title Yoav Miles created an issue Jenkins / JENKINS-31793 Jenkins should load build environment data on demand Issue Type: Improvement Assignee: Unassigned Components: build-environment-plugin Created: 30/Nov/15 8:26 AM Environment: Windows Server 2012 R2 (VM, 8 cores, 4.5GB RAM) Jenkins LTS 1.625.2 Chrome 46 Git 2.5.1 Installed plugins: active-directory-1.41 antisamy-markup-formatter-1.3 build-environment-1.6 build-with-parameters-1.3 chucknorris-0.9.1 cloudbees-folder-5.1 credentials-1.24 cvs-2.12 envinject-1.92.1 external-monitor-job-1.4 ghprb-1.29.5 git-2.4.0 git-client-1.19.0 github-1.14.0 github-api-1.69 github-oauth-0.22.2 git-tag-message-1.4 groovy-1.27 javadoc-1.3 jenkins-multijob-plugin-1.20 junit-1.9 ldap-1.11 linenumbers-1.1 mailer-1.16 mapdb-api-1.0.6.0 matrix-project-1.6 maven-plugin-2.12.1 msbuild-1.24 pam-auth-1.2 parameterized-trigger-2.29 parameter-separator-0.8 plain-credentials-1.1 rebuild-1.25 scm-api-1.0 script-security-1.15 seleniumhtmlreport-1.0 ssh-agent-1.8 ssh-credentials-1.11 ssh-slaves-1.10 subversion-2.5.4 token-macro-1.11 translation-1.12 versionnumber-1.6 windows-slaves-1.1 zentimestamp-4.2 Priority: Major Reporter: Yoav Miles Currently I have 1700+ jobs in Jenkins and each of them has its build environment XML file, all they all weigh more th
[JIRA] [wildfly-deployer-plugin] (JENKINS-31794) Wildfly Deployer plugin error
Title: Message Title Peter Nhu created an issue Jenkins / JENKINS-31794 Wildfly Deployer plugin error Issue Type: Bug Assignee: Dan Dillingham Components: wildfly-deployer-plugin Created: 30/Nov/15 8:30 AM Priority: Blocker Reporter: Peter Nhu I'm working in a project using Jenkins. I tried to deploy a War file to Jboss server with Wildfly Deployer plugin. When I deploy with Jboss AS 8 server (renamed to Wildfly) => It worked. But when I deploy with Jboss AS 7(or older) or Jboss EAP => It failed(Error: FATAL: Unable to connect to controller.). In the main page of Wildfly Deployer plugin(https://wiki.jenkins-ci.org/display/JENKINS/WildFly+Deployer+Plugin) they said: "Deploys an application to a WildFly/JBoss server or server group." Why it is not work with me. Add Comment
[JIRA] [installshield-plugin] (JENKINS-31795) Slaves can't find InstallShield SAB
Title: Message Title
Hans Meyer created an issue
Jenkins / JENKINS-31795
Slaves can't find InstallShield SAB
Issue Type:
Bug
Assignee:
Tomáš Bambas
Attachments:
InstallShield Jenkins Config.PNG
Components:
installshield-plugin
Created:
30/Nov/15 8:31 AM
Environment:
Master: Windows Server 2012R2 Slave: Windows 7 Pro SP1
Priority:
Major
Reporter:
Hans Meyer
I try to build an installer for several projects on a slave machine. Sometimes the jobs get triggered by the workflowplugin, other times they are Freestyle projects.
The InstallShield plugin is configured to point to the right InstallShield installation on the slave and I restrict the jobs to only run on the correct slave.
However, when the build starts, the following console output happens:
{{Building remotely on InstallShield (InstallShield2014) in workspace C:\Buildjobs\workspace\Test_InstallShield-Blitz > git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching ch
[JIRA] [installshield-plugin] (JENKINS-31795) Slaves can't find InstallShield SAB
Title: Message Title
Hans Meyer updated an issue
Jenkins / JENKINS-31795
Slaves can't find InstallShield SAB
Change By:
Hans Meyer
I try to build an installer for several projects on a slave machine. Sometimes the jobs get triggered by the workflowplugin, other times they are Freestyle projects.The InstallShield plugin is configured to point to the right InstallShield installation on the slave and I restrict the jobs to only run on the correct slave.However, when the build starts, the following console output happens: {{ Building remotely on InstallShield (InstallShield2014) in workspace C:\Buildjobs\workspace\Test_InstallShield-Blitz > git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git.exe config remote.origin.url http://path/to/git/repo.git # timeout=10Cleaning workspace > git.exe rev-parse --verify HEAD # timeout=10Resetting working tree > git.exe reset --hard # timeout=10 > git.exe clean -fdx # timeout=10Fetching upstream changes from http://path/to/git/repo.git > git.exe --version # timeout=10 > git.exe -c core.askpass=true fetch --tags --progresshttp://path/to/git/repo.git +refs/heads/*:refs/remotes/origin/*Seen branch in repository origin/masterSeen branch in repository origin/registry-backupSeen 2 remote branchesChecking out Revision 6c368f2733bd951394e6dda27d136619a08116fa (origin/registry-backup) > git.exe config core.sparsecheckout # timeout=10 > git.exe checkout -f 6c368f2733bd951394e6dda27d136619a08116fa > git.exe rev-list 6c368f2733bd951394e6dda27d136619a08116fa # timeout=10Executing command: "C:\Program Files (x86)\InstallShield\2014 SAB\System\IsCmdBld.exe" -p "C:\Buildjobs\workspace\Test_InstallShield-Blitz\Tests\InstallShield-Blitzpaket-Testsetup.ism" ERROR: Build step failed with exceptionTraceback (most recent call last): File "", line 1, in File "C:\Jenkins\plugins\installshield\WEB-INF\lib\python\install_shield_builder.py", line 82, in performpopen = subprocess.Popen(command, shell=False, File "C:\Jenkins\plugins\python-wrapper\WEB-INF\lib\jython-standalone-2.5.3.jar\Lib\subprocess.py", line 751, in __init__ File "C:\Jenkins\plugins\python-wrapper\WEB-INF\lib\jython-standalone-2.5.3.jar\Lib\subprocess.py", line 1265, in _execute_childOSError: Cannot run program ""C:\Program Files (x86)\InstallShield\2014 SAB\System\IsCmdBld.exe"" (in directory "C:\Jenkins"): CreateProcess error=2, The system cannot find the file specified at org.python.core.PyException.doRaise(PyException.java:219) at org.python.core.Py.makeException(Py.java:1239) at org.python.core.Py.makeException(Py.java:1243) at org.python.core.Py.makeException(Py.java:1247) at subprocess$py._execute_child$36(C:\Jenkins\plugins\python-wrapper\WEB-INF\lib\jython-standalone-2.5.3.jar\Lib\subprocess.py:1266) at subprocess$py.call_function(C:\Jenkins\plugins\python-wrapper\WEB-INF\lib\jython-standalone-2.5.3.jar\Lib\subprocess.py) at org.python.core.PyTableCode.call(PyTableCode.java:165) at org.python.core.PyBaseCode.call(PyBaseCode.java:301) at org.python.core.PyBaseCode.call(PyBaseCode.java:194) at org.python.core.PyFunction.__call__(PyFunction.java:387) at org.python.core.PyMethod.instancemethod___call__(PyMethod.java:220) at org.python.core.PyMethod.__call__(PyMethod.java:211) at org.python.core.PyMethod.__call_
[JIRA] [subversion-plugin] (JENKINS-31796) no change infos are displayed although poll says there are changes
Title: Message Title Patrik Fuerer created an issue Jenkins / JENKINS-31796 no change infos are displayed although poll says there are changes Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 30/Nov/15 8:50 AM Environment: Jenkins 1.638 Subversion Plugin 2.5.4 Priority: Minor Reporter: Patrik Fuerer When updating subversion plugin to 2.5.4 we have the following inconsistent buildinformation: for changes it says "No changes" while it says "Started by an SCM change". When looking at the poll information we see that there have been changes in subversion. When we downgrade the subversion plugin to version 2.4.5 we don't see this. Add Comment
[JIRA] [subversion-plugin] (JENKINS-31796) no change infos are displayed although poll says there are changes
Title: Message Title Patrik Fuerer updated an issue Jenkins / JENKINS-31796 no change infos are displayed although poll says there are changes Change By: Patrik Fuerer When updating subversion plugin to 2.5.4 we have the following inconsistent buildinformation:for changes it says "No changes" while it says "Started by an SCM change". When looking at the poll information we see that there have been changes in subversion.When we downgrade the subversion plugin to version 2.4.5 we don't see this . (Change information are displayed on build page) 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] [subversion-plugin] (JENKINS-31796) no change infos are displayed although poll says there are changes
Title: Message Title Patrik Fuerer updated an issue Jenkins / JENKINS-31796 no change infos are displayed although poll says there are changes Change By: Patrik Fuerer When updating subversion plugin to 2.5.4 we have the following inconsistent buildinformation:for changes it says "No changes" while it says "Started by an SCM change". When looking at the poll information we see that there have been changes in subversion.When we downgrade the subversion plugin to version 2.4.5 we don't see this ( Change change information are is displayed on build page) 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-31015) Failure when downloading zipped artifacts
Title: Message Title Serg Pr reopened an issue The new version 1.639 is available, but on Jenkins (windows) I don`t see this new version via Jenkins web. Here is the link with available 1.639 version: http://updates.jenkins-ci.org/download/war/1.639/jenkins.war Jenkins / JENKINS-31015 Failure when downloading zipped artifacts Change By: Serg Pr Resolution: Fixed 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] [core] (JENKINS-31015) Failure when downloading zipped artifacts
Title: Message Title Serg Pr updated JENKINS-31015 Jenkins / JENKINS-31015 Failure when downloading zipped artifacts Change By: Serg Pr Status: Reopened Open 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-31015) Failure when downloading zipped artifacts
Title: Message Title Serg Pr resolved as Fixed I don`t understand what happens, but after reopen this ticket, I saw the new version on Jenkins. Sorry for inconvenience. Jenkins / JENKINS-31015 Failure when downloading zipped artifacts Change By: Serg Pr 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] [github-plugin] (JENKINS-31797) GitHub plugin does not update build status when repository is accessed with a custom SSH configuration entry
Title: Message Title Michael Grünewald created an issue Jenkins / JENKINS-31797 GitHub plugin does not update build status when repository is accessed with a custom SSH configuration entry Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-plugin Created: 30/Nov/15 9:18 AM Environment: - Jenkins 1.638 - GitHub plugin 1.14.0 Labels: plugin git configuration Priority: Minor Reporter: Michael Grünewald The recommended way to use deployment keys with GitHub is to prepare a special entry in the configuration file, like this: Host github-myproject User git Hostname github.com IdentityFile ~/.ssh/id_rsa_deployment_key_for_myproject The corresponding git URL reads `github-myproject:myorganization/myproject.git`. When
[JIRA] [parameterized-trigger-plugin] (JENKINS-31798) Projects to build "can not find the project"
Title: Message Title Lu Qi created an issue Jenkins / JENKINS-31798 Projects to build "can not find the project" Issue Type: Bug Assignee: huybrechts Attachments: red line.png Components: parameterized-trigger-plugin Created: 30/Nov/15 9:24 AM Environment: Jenkins ver. 1.540 linux chrome java 1.7 Labels: jenkins Priority: Minor Reporter: Lu Qi When I want to trigger builds on other projects after my build , I fill in another project name with prefix ,the selector gives me some suggestions and I choose one. Then , a red line says "no such project '***' ,did you mean '**'?" . Then I click on the page ,and the red line goes away. Looks like when I'm chosing the suggested item ,jekins tries to use my prefix to find a matched project an
[JIRA] [copyartifact-plugin] (JENKINS-31563) Latest successful artifact cannot be copied from Maven build
Title: Message Title ritzmann commented on JENKINS-31563 Re: Latest successful artifact cannot be copied from Maven build How do you archive artifacts in job1? It is a Maven project. The advanced settings are: Disable automatic artifact archiving And then the post-build actions have this action: Archive the artifacts And I can see from the job page that the artifacts are archived. "lastSuccessfulBuild" is build #510? Yes, and it does have downloadable artifacts. Are there files in D:\jenkins\jobs\job1\modules\my.package$myapp\builds\510\archive ? No, because module archiving was disabled. The 510 directory exists but not the archive subdirectory. The archived artifacts are in D:\jenkins\jobs\job1\builds\510\archive. 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] [cloudformation-plugin] (JENKINS-31777) A job instance will delete other instance's Stack
Title: Message Title lsb want updated an issue Jenkins / JENKINS-31777 A job instance will delete other instance's Stack Change By: lsb want Attachment: Untitled2.png Attachment: Untitled.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] [cloudformation-plugin] (JENKINS-31777) A job instance will delete other instance's Stack
Title: Message Title
lsb want updated an issue
Jenkins / JENKINS-31777
A job instance will delete other instance's Stack
Change By:
lsb want
My situation is that one job launch two job instance concurrently and job configurate to check 'Automatically delete the stack when the job completes' box. I have use a environment variable as a part of Stack name. for example (ABC${BUILD_NUMBER} ) The two job instance runing in same windows slave. issue:The one job instance will delete all Stack created by the two job instance after itself completes. The attachment show build 6 delete stack of build 5. another strange phenomenon is last build's environment variable will appear on this build's environment .
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] [cloudformation-plugin] (JENKINS-31777) A job instance will delete other instance's Stack
Title: Message Title lsb want updated an issue Jenkins / JENKINS-31777 A job instance will delete other instance's Stack Change By: lsb want Environment: Jenkins ver. 1.616 sun JDK 1.7 jenkins-cloudformation-plugin: 1.0window slave git bash in window slave 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-27739) Changes to slave environment variables are ignored by master
Title: Message Title KY Lee commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master This issue still persists on my 1.606 instance with EnvInject uninstalled. Had both server and slaves rebooted without avail. I am more inclined to think that this issue is with Jenkins' core than with EnvInject. 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] [gerrit-trigger-plugin] (JENKINS-30370) Cant save http password for REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30370 Re: Cant save http password for REST API Code changed in jenkins User: Scott Hebert Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/9bd6637c4456d01c4519540b6cf3ca89f139f100 Log: Fix Config Page Auth validation This fixes a problem whereby Test Connection (SSH and REST) fails AFTER you have saved and re-loaded the config page. [FIXED JENKINS-30370] 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] [gerrit-trigger-plugin] (JENKINS-30370) Cant save http password for REST API
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30370 Cant save http password for REST API 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] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title Sergey Kadaner created an issue Jenkins / JENKINS-31799 Errors during gradlew server command Issue Type: Bug Assignee: Daniel Spilker Components: gradle-jpi-plugin Created: 30/Nov/15 11:21 AM Environment: Java 1.7, Gradle 2.7, Jenkins 1.509.3 Labels: gradle Priority: Major Reporter: Sergey Kadaner After I moved from Maven to Gradle I started getting errors during server startup via gradlew server command. I did not see these errors with maven hpi:run ``` Failed to instantiate SLF4J LoggerFactory Reported exception: java.lang.NoClassDefFoundError: org/slf4j/spi/LoggerFactoryBinder at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:800) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.ja
[JIRA] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title
Sergey Kadaner updated an issue
Jenkins / JENKINS-31799
Errors during gradlew server command
Change By:
Sergey Kadaner
After I moved from Maven to Gradle I started getting errors during server startup via _gradlew server_ command. I did not see these errors with _maven hpi:run_ ``` {code:java} Failed to instantiate SLF4J LoggerFactoryReported exception:java.lang.NoClassDefFoundError: org/slf4j/spi/LoggerFactoryBinderat java.lang.ClassLoader.defineClass1(Native Method)at java.lang.ClassLoader.defineClass(ClassLoader.java:800)at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)at java.net.URLClassLoader.access$100(URLClassLoader.java:71)at java.net.URLClassLoader$1.run(URLClassLoader.java:361)at java.net.URLClassLoader$1.run(URLClassLoader.java:355)at java.security.AccessController.doPrivileged(Native Method)at java.net.URLClassLoader.findClass(URLClassLoader.java:354)at java.lang.ClassLoader.loadClass(ClassLoader.java:425)at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)at java.lang.ClassLoader.loadClass(ClassLoader.java:358)at winstone.classLoader.WebappClassLoader.loadClass(WebappClassLoader.java:55)at java.lang.ClassLoader.loadClass(ClassLoader.java:358)at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108)at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279)at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:252)at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:265)at org.apache.sshd.common.AbstractFactoryManager.(AbstractFactoryManager.java:40)at org.apache.sshd.SshServer.(SshServer.java:144)at org.apache.sshd.SshServer.setUpDefaultServer(SshServer.java:446)at org.jenkinsci.main.modules.sshd.SSHD.start(SSHD.java:82)at org.jenkinsci.main.modules.sshd.SSHD.init(SSHD.java:144)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)at jenkins.model.Jenkins$7.runTask(Jenkins.java:888)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.ClassNotFoundException: org.slf4j.spi.LoggerFactoryBinderat java.net.URLClassLoader$1.run(URLClassLoader.java:366)at java.net.URLClassLoader$1.run(URLClassLoader.java:355)at java.securi
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master still persists on my 1.606 instance This is to be expected, as this issue was fixed in 1.617. 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] [jacoco-plugin] (JENKINS-30808) Empty trend chart
Title: Message Title Grzegorz Kotarski commented on JENKINS-30808 Re: Empty trend chart That's it! So simple Thanks a lot Mathias! 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] [jacoco-plugin] (JENKINS-30808) Empty trend chart
Title: Message Title Grzegorz Kotarski closed an issue as Not A Defect debug flag was not set. Jenkins / JENKINS-30808 Empty trend chart Change By: Grzegorz Kotarski Status: Open Closed Assignee: Ognjen Bubalo Grzegorz Kotarski Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-31800) Continuous "gerrit.ls-projects" requets
Title: Message Title John V created an issue Jenkins / JENKINS-31800 Continuous "gerrit.ls-projects" requets Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 30/Nov/15 12:23 PM Priority: Major Reporter: John V After upgrading from version 2.17.2 to version 2.17.4 my Gerrit server is continuously getting "gerrit.ls-projects" requests from jenkins. (I've downgraded the plugin to the old version as a workaround) Add Comment
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-31801) Using Throttle Concurrent Builds in a WorkFlow
Title: Message Title Dave Lawrence created an issue Jenkins / JENKINS-31801 Using Throttle Concurrent Builds in a WorkFlow Issue Type: Improvement Assignee: Andrew Bayer Components: throttle-concurrent-builds-plugin Created: 30/Nov/15 12:27 PM Environment: Jenkins v1.634 WorkFlow: Aggregator v1.11 Throttle Concurrent Builds Plug-in v1.8.4 Labels: jenkins workflow throttle concurrent Priority: Minor Reporter: Dave Lawrence I am looking to use Throttle Concurrent Builds in a WorkFlow. I have jobs that perform automated, scheduled testing, as well as user-initiated jobs. All these jobs compete for the same set of hardware resources to run tests against. I'm currently using BuildFlows for all this and Throttle Concurrent Builds works fine. My problem is that I want to use the WorkFlow plugin for the automated jobs but TCB does not natively support WorkFlows. I've read that people dedicate a Node per unit of hardware to solve this problem. That's not a good solution for me since I can have 10-20 hardware units. I've
[JIRA] [envinject-plugin] (JENKINS-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
Title: Message Title
Aaron Marasco commented on JENKINS-19754
Re: Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
I hit this bug as well with Jenkins 1.634 and EnvInject 1.92.1. The workaround above worked for me as well.
Before workaround, slave's "root" workspace used:
Building remotely on xilinx_builder (x86_64 hdlbuilder-ml605) in workspace /data/jenkins_workspace_xilinx_1/workspace/build_hdl + env + sort WORKSPACE=/data/jenkins_workspace_xilinx_1
After:
Building remotely on xilinx_builder (x86_64 hdlbuilder-ml605) in workspace /data/jenkins_workspace_xilinx_1/workspace/build_hdl + env + sort WORKSPACE=/data/jenkins_workspace_xilinx_1/workspace/build_hdl
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title
Jens Doose commented on JENKINS-24824
Re: Asynchronous cleanup not removing renamed workspace directories on slaves
I have the same behaviour in a non-slave environment, I don't know if this is the same or a new issue. A lot of directories like workspace_ws-cleanup_1447277714463 get created and never deleted.
In the log of the jenkins job there is the output that everything is ok: {{ [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done }}
The job is building node projects and loading npm componentes as well as bower components which result in quite huge directory structures, might that be a problem?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title
Sergey Kadaner updated an issue
Jenkins / JENKINS-31799
Errors during gradlew server command
Change By:
Sergey Kadaner
After I moved from Maven to Gradle I started getting errors during server startup via _gradlew server_ command. I did not see these errors with _maven _mvn hpi:run_{code:java}Failed to instantiate SLF4J LoggerFactoryReported exception:java.lang.NoClassDefFoundError: org/slf4j/spi/LoggerFactoryBinderat java.lang.ClassLoader.defineClass1(Native Method)at java.lang.ClassLoader.defineClass(ClassLoader.java:800)at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)at java.net.URLClassLoader.access$100(URLClassLoader.java:71)at java.net.URLClassLoader$1.run(URLClassLoader.java:361)at java.net.URLClassLoader$1.run(URLClassLoader.java:355)at java.security.AccessController.doPrivileged(Native Method)at java.net.URLClassLoader.findClass(URLClassLoader.java:354)at java.lang.ClassLoader.loadClass(ClassLoader.java:425)at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)at java.lang.ClassLoader.loadClass(ClassLoader.java:358)at winstone.classLoader.WebappClassLoader.loadClass(WebappClassLoader.java:55)at java.lang.ClassLoader.loadClass(ClassLoader.java:358)at org.slf4j.LoggerFactory.bind(LoggerFactory.java:128)at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108)at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279)at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:252)at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:265)at org.apache.sshd.common.AbstractFactoryManager.(AbstractFactoryManager.java:40)at org.apache.sshd.SshServer.(SshServer.java:144)at org.apache.sshd.SshServer.setUpDefaultServer(SshServer.java:446)at org.jenkinsci.main.modules.sshd.SSHD.start(SSHD.java:82)at org.jenkinsci.main.modules.sshd.SSHD.init(SSHD.java:144)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)at jenkins.model.Jenkins$7.runTask(Jenkins.java:888)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.ClassNotFoundException: org.slf4j.spi.LoggerFactoryBinderat java.net.URLClassLoader$1.run(URLClassLoader.java:366)at java.net.URLClassLoader$1.run(URLClassLoader.java:355)at java.secur
[JIRA] [ws-cleanup-plugin] (JENKINS-24824) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title
Jens Doose edited a comment on JENKINS-24824
Re: Asynchronous cleanup not removing renamed workspace directories on slaves
I have the same behaviour in a *non-slave* environment, I don't know if this is the same or a new issue.A lot of directories like workspace_ws-cleanup_1447277714463 get created and never deleted.In the log of the jenkins job there is the output that everything is ok: {{ \ [WS-CLEANUP \ ] Deleting project workspace... \ [WS-CLEANUP \ ] Done }} The job is building node projects and loading npm componentes as well as bower components which result in quite huge directory structures, might that be a problem?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-31802) Allow TFS Plugin to use Global Credentials
Title: Message Title Sunil Fernandes created an issue Jenkins / JENKINS-31802 Allow TFS Plugin to use Global Credentials Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 30/Nov/15 1:39 PM Priority: Critical Reporter: Sunil Fernandes Allow TFS Plugin to use Global Credentials so that passwords can be changed in just one location. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [deploy-plugin] (JENKINS-14949) Deploy several wars/ears to several servers
Title: Message Title Bob Kubista commented on JENKINS-14949 Re: Deploy several wars/ears to several servers Can't you use a separate multi-configurable build job to do this? You could have 1 axis as the wars to be deployed and 1 axis as the servers to be deployed to?! 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-31783) Add support for Ruby plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.41. Jenkins / JENKINS-31783 Add support for Ruby plugin Change By: Daniel Spilker 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-31783) Add support for Ruby plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31783 Re: Add support for Ruby plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/step/StepContext/ruby.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f86021560ba7d72cb609cf3d112f2eb1e662d5db Log: JENKINS-31783 Added support for Ruby 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] [core] (JENKINS-31753) Fields are aligned at the bottom in the view of the parameters of a job
Title: Message Title Frederic bonerandi commented on JENKINS-31753 Re: Fields are aligned at the bottom in the view of the parameters of a job Reproduce in version 1.639. 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-31748) Check comment text truncated from recent changes detail pages
Title: Message Title Paul Allen commented on JENKINS-31748 Re: Check comment text truncated from recent changes detail pages Thank you for confirming the fix. 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] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger
Title: Message Title Jesse Glick commented on JENKINS-28632 Re: Workflow support for Deployment Notification trigger For the record what was fixed here was the basic Workflow compatibility (feature parity with freestyle), not the awaitDeployment step which I suppose should be tracked with a separate 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] [teamconcert-plugin] (JENKINS-30245) Missing Credentials in Global Team Concert/RTC configuration
Title: Message Title Gabriel Lopez commented on JENKINS-30245 Re: Missing Credentials in Global Team Concert/RTC configuration Hi. I had the same issue; RTC global credentials didn't get saved: You selected one credentials, save or apply, everything went fine, but then you refresh the page and the credentials aren't selected anymore. On the XML configuration on the server, the ID saved was Github's.com plain credentials, an OAuth token configured through https://wiki.jenkins-ci.org/display/JENKINS/Plain+Credentials+Plugin. After several tests, I disabled plain credentials plugin (and Github plugin, since it depends on it), restarted the server and then they it worked fine again. So, I think there is a compatibility issue with Plain Credentials plugin and Rational Team Concert global 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] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title Daniel Spilker commented on JENKINS-31799 Re: Errors during gradlew server command Do you have a public repo that I can use for reproducing the issue? For a workaround, you can try to add the SLF4J API to the runtime dependencies in your project: runtime 'org.slf4j:slf4j-api:1.7.13' 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-31788) Add support for Bitbucket Plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.41. Jenkins / JENKINS-31788 Add support for Bitbucket Plugin Change By: Daniel Spilker 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-31788) Add support for Bitbucket Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31788 Re: Add support for Bitbucket Plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/triggers/TriggerContext/bitbucketPush.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/5436f27b45ed6f1ae438c26cb20e7866e25dc22e Log: JENKINS-31788 Added support for Bitbucket 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] [tfs-plugin] (JENKINS-31803) Workflow support for TFS plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31803 Re: Workflow support for TFS plugin Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/f0d2a74d61af628a310c5a525351bb372801ea76 Log: JENKINS-31803 Noting. 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-31803) Workflow support for TFS plugin
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-31803 Workflow support for TFS plugin Issue Type: New Feature Assignee: redsolo Components: tfs-plugin Created: 30/Nov/15 2:35 PM Labels: workflow Priority: Major Reporter: Jesse Glick Guide Add Comment
[JIRA] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Title: Message Title dhananjaya arisetti commented on JENKINS-25330 Re: Folders should offer to use a hash for workspace path (like matrix does) HI how to resolve the following issue ? "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters." i installed short workspace plugin. i don't know how to configure the path. or please suggest any other way to resolve the issue. and how to change hash workspace? please do need helpful. Thanks, Dhananjaya 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-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-31804 After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 500 31804 Workflow: classic default workflow JNJira Component/s: ec2-plugin Component/s: ci Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [ec2-plugin] (JENKINS-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time
Title: Message Title R. Tyler Croy commented on JENKINS-31804 Re: After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time I moved this into the JENKINS project, for future reference the INFRA project is for our internal infrastructure. 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-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time
Title: Message Title R. Tyler Croy assigned an issue to Unassigned Jenkins / JENKINS-31804 After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time Change By: R. Tyler Croy Assignee: R. Tyler Croy 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-31804) After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time
Title: Message Title R. Tyler Croy assigned an issue to Francis Upton Jenkins / JENKINS-31804 After a while the ec2-plugin stops spinning up nodes, and spits out stacktraces. It also stops terminating nodes after their idle time Change By: R. Tyler Croy Assignee: Francis Upton 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-31784) Add support for Subversion Tagging Plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.41. Jenkins / JENKINS-31784 Add support for Subversion Tagging Plugin Change By: Daniel Spilker 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-31784) Add support for Subversion Tagging Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31784 Re: Add support for Subversion Tagging Plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/svnTag.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/SubversionTagContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/da4a0324e4933ed08b7ce674cbba53534a7848a7 Log: JENKINS-31784 Added support for Subversion Tagging 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] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title Sergey Kadaner commented on JENKINS-31799 Re: Errors during gradlew server command There is already slf4j-api-1.6.2.jar and slf4j-jdk14-1.6.2.jar under work/war/WEB-INF/lib directory. However the same directory is used by Maven plugin, so it should not be the problem. The workaround you suggested did not made a difference. I currently cannot provide sources of the project, but I may be able to do it later. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-29494) IRC plug-in throws org.acegisecurity.userdetails.UsernameNotFoundException during onMessage
Title: Message Title Thomas Sowerby commented on JENKINS-29494 Re: IRC plug-in throws org.acegisecurity.userdetails.UsernameNotFoundException during onMessage Seeing the same here under the same conditions. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-31799) Errors during gradlew server command
Title: Message Title Sergey Kadaner edited a comment on JENKINS-31799 Re: Errors during gradlew server command There is already slf4j-api-1.6.2.jar and slf4j-jdk14-1.6.2.jar under _work/war/WEB-INF/lib_ directory. However the same directory is used by Maven plugin, so it should not be the problem.The workaround you suggested did not made a difference help .I currently cannot provide sources of the project, but I may be able to do it later. 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] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Title: Message Title Daniel Beck commented on JENKINS-25330 Re: Folders should offer to use a hash for workspace path (like matrix does) This is an issue tracker, not a support website. Please ask your questions in #jenkins on Freenode, or the jenkinsci-users mailing list. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-31805) Allow environent variables for triggering gerrit projects
Title: Message Title Thiago Crepaldi created an issue Jenkins / JENKINS-31805 Allow environent variables for triggering gerrit projects Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 30/Nov/15 3:06 PM Priority: Minor Reporter: Thiago Crepaldi When creating a job, we have to specify what Gerrit project(s) to trigger a build on based on the following rules: At least one project and branch pattern needs to be specified for a build to be triggered,and you can specify as many gerrit project to trigger on as you want. Start by specifying the name of the Gerrit project in the left hand text field. You can specify the name pattern in three different ways, as provided by the "Type" drop-down menu. Plain: The exact name in Gerrit, case sensitive equality. Path: ANT style pattern. Ex: "/base/*" RegExp: Regular _expression_. Then provide the name of the branch(es) to trigger on. The same "pattern types" is available as above. So for example to trigger on all branches in the project you can specify: Type: Path Pattern: ** You can add more branch patterns by clicking on "Add Branch" and more projects by clicking "Add Project". The same syntax works for specifying which file(s) to trigger on (this is only available in version 2.3 or higher of Gerrit). However, in order to improve its power even further, it could be possible to use $GERRIT_PROJECT as project pattern and $GERRIT_BRANCH as branch pattern (or any other environment variable). That would enable the user
[JIRA] [gitbucket-plugin] (JENKINS-31806) Jenkins job does not detect a gitbucket change via webhook.
Title: Message Title Tony Owens created an issue Jenkins / JENKINS-31806 Jenkins job does not detect a gitbucket change via webhook. Issue Type: Bug Assignee: Tony Owens Components: gitbucket-plugin Created: 30/Nov/15 3:19 PM Environment: Linux Jenkins 1.638 w/gitbucket plugin v0.8. Gitbucket 3.8 Priority: Major Reporter: Tony Owens Security is enabled on Jenkins via ldap. Any authenticated user can do anything. Jenkins job is configured with Build Trigger "Build when a change is pushed to GitBucket". Gitbucket webhook is configured with "https:// (when i test this address i get a page telling me (POST is required for org.jenkinsci.plugins.gitbucket.GitBucketWebHook.doIndex) There are no entries in the "Gitbucket Hook Log". I can send a POST request via curl to the webhook address so I assume that authorizations isn't stopping me?
[JIRA] [gitbucket-plugin] (JENKINS-31806) Jenkins job does not detect a gitbucket change via webhook.
Title: Message Title Tony Owens updated an issue Jenkins / JENKINS-31806 Jenkins job does not detect a gitbucket change via webhook. Change By: Tony Owens Gitbucket and Jenkins servers are separated and not running on the same server. Security is enabled on Jenkins via ldap. Any authenticated user can do anything.Jenkins job is configured with Build Trigger "Build when a change is pushed to GitBucket".Gitbucket webhook is configured with "https://(when i test this address i get a page telling me (POST is required for org.jenkinsci.plugins.gitbucket.GitBucketWebHook.doIndex)There are no entries in the "Gitbucket Hook Log".I am updating gitbucket project via git bash client on workstation.I can send a POST request via curl to the webhook address so I assume that authorizations isn't stopping me? 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-31762) Add support for Cucumber Reports Plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.41. Jenkins / JENKINS-31762 Add support for Cucumber Reports Plugin Change By: Daniel Spilker 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-31762) Add support for Cucumber Reports Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31762 Re: Add support for Cucumber Reports Plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/cucumberReports.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/CucumberReportsContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/d5a67fa961eddc00ea93a7345c9077fbb51410d5 Log: JENKINS-31762 Added support for Cucumber Reports Plugin Added missing attribute Added Test Cases for cucumber report plugin Fixed codenarc defect JENKINS-31762 Added support for Cucumber Reports Plugin Renamed DSL cucumberReports method Renamed DSL cucumberReports doc 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] [teamconcert-plugin] (JENKINS-30245) Missing Credentials in Global Team Concert/RTC configuration
Title: Message Title Billy Foss commented on JENKINS-30245 Re: Missing Credentials in Global Team Concert/RTC configuration Unfortunately we need to pull source from GitHub Enterprise. For now, we use the override RTC configuration option in each job. It works well enough for those using more GitHub than RTC. As a reference, we have updated to Jenkins LTS 1.625.2 with related plugins at the version listed Team Concert Plugins 1.1.9.7 GitHub plugin 1.14.0 Plain Credentials Plugin 1.1 and we still see the global RTC credentials revert to none on reload of the Jenkins Configuration page. Thanks, Billy 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] [cucumber-reports-plugin] (JENKINS-31807) Sort 'All Tags' Reporting
Title: Message Title Marsel Tadjer created an issue Jenkins / JENKINS-31807 Sort 'All Tags' Reporting Issue Type: Improvement Assignee: Damian Szczepanik Attachments: Screen Shot 2015-11-30 at 10.36.23 AM.png Components: cucumber-reports-plugin Created: 30/Nov/15 3:40 PM Priority: Minor Reporter: Marsel Tadjer The way tags are reported right now seem to be based on first occurrence, it will be handy and very beneficial if they are sorted alphabetically. See screenshot. Add Comment
[JIRA] [core] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/bytecode/ClassWriter.java src/main/java/org/jenkinsci/bytecode/NonClassLoadingClassWriter.java src/main/java/org/jenkinsci/bytecode/Transformer.java src/test/java/org/jenkinsci/bytecode/NonClassLoadingClassWriterTest.java http://jenkins-ci.org/commit/bytecode-compatibility-transformer/44ca3cf1f84946ccf2b4798cf417423378fedf29 Log: WIP JENKINS-31019 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-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/bytecode/NonClassLoadingClassWriter.java src/main/java/org/jenkinsci/bytecode/helper/ClassLoadingReferenceTypeHierachyReader.java src/main/java/org/jenkinsci/bytecode/helper/TypeHierarchyReader.java src/test/java/org/jenkinsci/bytecode/NonClassLoadingClassWriterTest.java http://jenkins-ci.org/commit/bytecode-compatibility-transformer/285039ef5bb9a0e4988bc683a6d6f5abb48ea8d5 Log: JENKINS-31019 Compute the common super class without loading classes. Loading classes to compute the common super classes did indeed cause issues as I suspected it would. Use a third party helper from https://github.com/Grundlefleck/ASM-NonClassloadingSimpleVerifier to help us to do this and further customize it so that it can locate the bytecode via the correct ClassLoader. 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-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/bytecode/ClassWriter.java src/main/java/org/jenkinsci/bytecode/NonClassLoadingClassWriter.java src/main/java/org/jenkinsci/bytecode/Transformer.java src/main/java/org/jenkinsci/bytecode/helper/ClassLoadingReferenceTypeHierachyReader.java src/main/java/org/jenkinsci/bytecode/helper/TypeHierarchyReader.java src/test/java/org/jenkinsci/bytecode/NonClassLoadingClassWriterTest.java http://jenkins-ci.org/commit/bytecode-compatibility-transformer/f75efe8bf757532c416e53ce3a8766ec4bfcaf1d Log: Merge pull request #7 from jtnord/JENKINS-31019 JENKINS-31019 Compute the common super class without loading classes. Compare: https://github.com/jenkinsci/bytecode-compatibility-transformer/compare/4b26c39562ab...f75efe8bf757 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] [extended-choice-parameter-plugin] (JENKINS-31733) Extended Choice Parameter throw exception for Check Boxes type
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-31733 Extended Choice Parameter throw exception for Check Boxes type Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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] [scoverage-plugin] (JENKINS-31809) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56
Title: Message Title Peter lai created an issue Jenkins / JENKINS-31809 java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56 Issue Type: Bug Assignee: Unassigned Components: scoverage-plugin Created: 30/Nov/15 4:45 PM Priority: Critical Reporter: Peter lai When using the scoverage plugin you get something like this. Publishing Scoverage XML and HTML report ... ERROR: Build step failed with exception java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56 href="" /> ^ at java.util.regex.Pattern.error(Unknown Source) Add Comment
[JIRA] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31458 Exception when saving job configuration Change By: Jesse Glick Labels: 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Jesse Glick commented on JENKINS-31458 Re: Exception when saving job configuration This commit does not suffice. The newInstance override needs to be deleted and plain old form binding used in config.jelly rather than the complex customized code currently there. See ui-samples-plugin for conventional usage. The broader issue is that Descriptor.newInstance overrides are not supported by Stapler itself; this method is called only from certain places in Jenkins, but not generally for nested objects. The old ParametersDefinitionProperty.DescriptorImpl.newInstance happened to call Descriptor.newInstancesFromHeteroList, which does call Descriptor.newInstance on direct children, in this case ParameterDescriptor instances. 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title
Peter lai commented on JENKINS-30409
Re: Don't fail the build when scoverage data is missing
I've previously mendtion this on https://github.com/shanbin/scoverage-plugin/issues/8 but just thought i'll post it here as well in case others are having the same problem.
It seems the offending bug is here In ScoveragePublisher.java String relativeFix = content.replaceAll("href="" "href="" /> .replaceAll("href="" + pattern + "/", "href="">
I've replaced this string with String relativeFix = content.replaceAll("href="" "href="" /> .replaceAll(Matcher.quoteReplacement("href="" + pattern + "/"), "href="">
and it fixed the problem, after talking to Shanbin, he wants a more robust fix to the way html is handled. So for those who's having this problem, i recommend you download the code and change this line and produce you own scoverage plugin in the meant 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title
Peter lai edited a comment on JENKINS-30409
Re: Don't fail the build when scoverage data is missing
I've previously mendtion this on https://github.com/shanbin/scoverage-plugin/issues/8 but just thought i'll post it here as well in case others are having the same problem. It seems the offending bug is here In ScoveragePublisher.java String relativeFix = content.replaceAll("href="" />.replaceAll("href="" /> I've replaced this string with String relativeFix = content.replaceAll("href="" />.replaceAll(Matcher.quoteReplacement("href="" /> and it fixed the problem, after talking to Shanbin, he wants a more robust fix to the way html is handled. So for those who's having this problem, i recommend you download the code and change this line and produce you own scoverage plugin in the meant 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title
Peter lai edited a comment on JENKINS-30409
Re: Don't fail the build when scoverage data is missing
I've previously mendtion this on https://github.com/shanbin/scoverage-plugin/issues/8 but just thought i'll post it here as well in case others are having the same problem. It seems the offending bug is here In ScoveragePublisher.java < { code > :java} String relativeFix = content.replaceAll("href="" />.replaceAll("href="" /> < { code > :java} I've replaced this string with < { code > :java} String relativeFix = content.replaceAll("href="" />.replaceAll(Matcher.quoteReplacement("href="" /> < { code > :java} and it fixed the problem, after talking to Shanbin, he wants a more robust fix to the way html is handled. So for those who's having this problem, i recommend you download the code and change this line and produce you own scoverage plugin in the meant 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title
Peter lai edited a comment on JENKINS-30409
Re: Don't fail the build when scoverage data is missing
I've previously mendtion this on https://github.com/shanbin/scoverage-plugin/issues/8 but just thought i'll post it here as well in case others are having the same problem. It seems the offending bug is here In ScoveragePublisher.java{code:java}String relativeFix = content.replaceAll("href="" />.replaceAll("href="" />{code :java }I've replaced this string with {code:java}String relativeFix = content.replaceAll("href="" />.replaceAll(Matcher.quoteReplacement("href="" />{code :java }and it fixed the problem, after talking to Shanbin, he wants a more robust fix to the way html is handled. So for those who's having this problem, i recommend you download the code and change this line and produce you own scoverage plugin in the meant 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] [publish-over-ssh-plugin] (JENKINS-31810) Publish over SSH plugin : cannot use build parameters filters in transfer set fields
Title: Message Title
Franck Grenier created an issue
Jenkins / JENKINS-31810
Publish over SSH plugin : cannot use build parameters filters in transfer set fields
Issue Type:
Improvement
Assignee:
bap
Components:
publish-over-ssh-plugin
Created:
30/Nov/15 4:53 PM
Environment:
Jenkins 1.626 Publish Over SSH plugin 1.13
Labels:
plugin ssh filters parameters
Priority:
Minor
Reporter:
Franck Grenier
Hello, while trying to send build results over SSH, I found that it's not possible to use filters on build parameters.
For example, I use $ {GIT_TAG*##*/*}
in order to transform a branch name "release/2.1.5" in "2.1.5" in shell scripts.
It does not work in "Publish over SSH" transfer sets fields like "Source files". It looks like the plugin does not find any file to upload but does not throw any error. By the way, the verbose output of this plugin is not that much "verbose"...
Improvement
[JIRA] [scoverage-plugin] (JENKINS-31809) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56
Title: Message Title
Peter lai commented on JENKINS-31809
Re: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56
I've previously mendtion this on https://github.com/shanbin/scoverage-plugin/issues/8 but just thought i'll post it here as well in case others are having the same problem.
It seems the offending bug is here In ScoveragePublisher.java
String relativeFix = content.replaceAll("href="">/", "href=""
.replaceAll("href="">.*" + pattern + "/", "href=""
I've replaced this string with
String relativeFix = content.replaceAll("href="">/", "href=""
.replaceAll(Matcher.quoteReplacement("href="">.*" + pattern + "/"), "href=""
and it fixed the problem, after talking to Shanbin, he wants a more robust fix to the way html is handled. So for those who's having this problem, i recommend you download the code and change this line and produce you own scoverage plugin in the meant 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] [scoverage-plugin] (JENKINS-31809) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56
Title: Message Title Peter lai commented on JENKINS-31809 Re: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56 Crap, completely commented on the wrong ticket, My bad. Ignore everything above. 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] [scoverage-plugin] (JENKINS-31809) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56
Title: Message Title Peter lai updated an issue Jenkins / JENKINS-31809 java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 56 Change By: Peter lai Comment: Crap, completely commented on the wrong ticket, My bad. Ignore everything above. 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title Peter lai edited a comment on JENKINS-30409 Re: Don't fail the build when scoverage data is missing Crap, completely commented on the wrong ticket, My bad. Ignore everything above. P.s. I agree, it shouldn't fail the build if the scoverage plugin fails. 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] [scoverage-plugin] (JENKINS-30409) Don't fail the build when scoverage data is missing
Title: Message Title Peter lai commented on JENKINS-30409 Re: Don't fail the build when scoverage data is missing Crap, completely commented on the wrong ticket, My bad. Ignore everything above. 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] [gerrit-trigger-plugin] (JENKINS-31805) Allow environent variables for triggering gerrit projects
Title: Message Title Thiago Crepaldi commented on JENKINS-31805 Re: Allow environent variables for triggering gerrit projects Jenkins ver. 1.638 gerrit-trigger 2.17.4 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] [jclouds-plugin] (JENKINS-31811) Parse time with timezone
Title: Message Title Sebastian Rettenberger created an issue Jenkins / JENKINS-31811 Parse time with timezone Issue Type: Bug Assignee: Fritz Elfert Components: jclouds-plugin Created: 30/Nov/15 5:23 PM Environment: Jenkins version: 1.634 Labels: plugin Priority: Minor Reporter: Sebastian Rettenberger Hi, I am trying to connect to an OpenNebula system which has EC2 capabilities. However, when I test the connection I get the following error message: Cannot connect to specified cloud, please check the identity and credentials: Invalid format: "2015-07-31T18:58:18+0200" is malformed at "+0200" Here is a stack trace when I try to manage the cloud node: javax.servlet.ServletException: java.lang.IllegalArgumentException: Invalid format: "2015-07-31T18:58:18+0200" is malformed at "+0200
[JIRA] [gitbucket-plugin] (JENKINS-31806) Jenkins job does not detect a gitbucket change via webhook.
Title: Message Title Tony Owens commented on JENKINS-31806 Re: Jenkins job does not detect a gitbucket change via webhook. I have enabled http on all interfaces and configured webhook url in gitbucket as http:// 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-31458 Exception when saving job configuration Change By: Jesse Glick Assignee: vimil Jesse Glick 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] [extended-choice-parameter-plugin] (JENKINS-31458) Exception when saving job configuration
Title: Message Title Jesse Glick started work on JENKINS-31458 Change By: Jesse Glick 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] [core] (JENKINS-20019) deadlock in jenkins.model.Jenkins.setNodes
Title: Message Title Jesse Glick resolved as Won't Do This code has been heavily refactored in the past few months so this issue is probably obsolete. Jenkins / JENKINS-20019 deadlock in jenkins.model.Jenkins.setNodes Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20019) deadlock in jenkins.model.Jenkins.setNodes
Title: Message Title Charles Stephens commented on JENKINS-20019 Re: deadlock in jenkins.model.Jenkins.setNodes Jesse Glick has this code refactoring landed on LTS yet? 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] [throttle-concurrent-builds-plugin] (JENKINS-31801) Using Throttle Concurrent Builds in a WorkFlow
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-31801 Using Throttle Concurrent Builds in a WorkFlow Change By: Andrew Bayer Labels: community-bee concurrent jenkins throttle workflow 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-31812) Set reference build explicitly
Title: Message Title Elena Laskavaia created an issue Jenkins / JENKINS-31812 Set reference build explicitly Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 30/Nov/15 6:30 PM Priority: Major Reporter: Elena Laskavaia While its nice to have an option to calculate reference build it does not always work or its not a policy of the company. There should be an option to explicitly set a reference build #, so all new warnings/errors calculated from that reference point on. Obviously this build should be locked but it will be an admin issue. Add Comment
[JIRA] [workflow-plugin] (JENKINS-31813) [withCredentials] NPE in snippet generator
Title: Message Title
Cyrille Le Clerc created an issue
Jenkins / JENKINS-31813
[withCredentials] NPE in snippet generator
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
cloudbees-support_2015-11-30_18.59.07.zip, npe-snippet-generator.png
Components:
workflow-plugin
Created:
30/Nov/15 7:03 PM
Environment:
Jenkins ver. 1.625.2.2 (CloudBees Jenkins Enterprise 15.11)
Labels:
exception
Priority:
Minor
Reporter:
Cyrille Le Clerc
java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.credentialsbinding.impl.BindingStep from {"bindings":{"usernameVariable":"MVN_USERNAME","passwordVariable":"MVN_PASSWORD","credent
[JIRA] [workflow-plugin] (JENKINS-31813) [withCredentials] NPE in snippet generator
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-31813 [withCredentials] NPE in snippet generator Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-31458) NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31458 Re: NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStep.java step-api/src/test/java/org/jenkinsci/plugins/workflow/steps/StepConfigTester.java http://jenkins-ci.org/commit/workflow-plugin/393aa3abca8e6fa974e4ae02ce30e96ab8f4c7c6 Log: JENKINS-31458 Noting places where https://github.com/jenkinsci/jenkins/pull/1936 might allow for simplifications. 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-31089) Signature verification failed in update site 'default'
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-31089 Signature verification failed in update site 'default' Change By: R. Tyler Croy Assignee: Kohsuke Kawaguchi R. Tyler Croy 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-31089) Signature verification failed in update site 'default'
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-31089 Signature verification failed in update site 'default' Change By: R. Tyler Croy Labels: community-bee 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.
