[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title Jochen Hinrichsen created an issue Jenkins / JENKINS-36570 Implement pipeline compatibility Issue Type: Improvement Assignee: Magnus Sandberg Components: prioritysorter-plugin Created: 2016/Jul/11 11:09 AM Priority: Minor Reporter: Jochen Hinrichsen The priority sorter plugin is not listed in the compatible plugin README.md. In addition, when using the "Run Exclusive" option, pipeline jobs get stuck in the queue. Unchecking the option leads to successful job migrations from the build queue to executors. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-33093) Support new feature of upcoming Gradle Plugin 1.25
Title: Message Title Jochen Hinrichsen created an issue Jenkins / JENKINS-33093 Support new feature of upcoming Gradle Plugin 1.25 Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 22/Feb/16 11:48 PM Priority: Trivial Reporter: Jochen Hinrichsen Gradle Plugin up to version 1.24 passes job parameters as system properties (-D). The new Gradle Plugin 1.25 (yet to be released) will offer an option to pass job parameters as Gradle Properties (-P). The new feature is version agnostic and will only kick in for versions >= 1.25. For compatibility reasons, the default is to use the old behaviour (system properties). The PR for the Gradle Plugin feature itself is https://github.com/jenkinsci/gradle-plugin/pull/27 Add Comment
[JIRA] [core] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
Title: Message Title Jochen Hinrichsen commented on JENKINS-26257 Re: ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException Same issue. This one is extremely devilish, because the build is reported as 'Succesful' but OOMs somewhere in the middle of nowhere. 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] [credentials-plugin] (JENKINS-25874) Maven Project plugin to use Credentials plugin
Title: Message Title
Jochen Hinrichsen commented on JENKINS-25874
Re: Maven Project plugin to use Credentials plugin
Give $ {env.PASSWORD}
a try. Note the env qualifier.
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] [credentials-binding-plugin] (JENKINS-24805) Mask credentials in Build Log
Title: Message Title Jochen Hinrichsen commented on JENKINS-24805 Re: Mask credentials in Build Log Jesse, i'm looking for just this particular workaround until this issue is resolved. My jobs are not using credentials as parameters, but the credentialsBinding DSL/ "Build environment -> Bindings" setup. My combination of Jenkins Credentials Binding Plugin and Mask Passwords plugin (LTS/ latest/ latest) shows credential passwords. Could you please elaborate on what you did to mask those? Any insights greatly appreciated. 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] [nodejs-plugin] (JENKINS-27513) Nodejs plugin breaks node's require() mechanism
Jochen Hinrichsen created JENKINS-27513 Nodejs plugin breaks node's require() mechanism Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 19/Mar/15 6:07 PM Description: Executing code entered direclty into the text fields runs like a charm. This procedure works fine for small adhoc snippets, but has its limitations in an enterprise strength setup. Sooner or later one might want to keep the code under SCM control and only use a 'run' stub to execute. A workspace local, node module compliant directory 'node_modules' is not taken into account when require()ing modules, because the script is executed in /tmp using a unique ID as filename. Copying the local node_modules folder to /tmp resolves the issue, but this is a rather clumsy workaround because (a) you have to remember to remove it afterwards, and (b) what if two jobs need different node_module folder. Is it a viable option to have a '[x] Stay local' option for scripts that require require()? Environment: Any Project: Jenkins Priority: Minor Reporter: Jochen Hinrichsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-metadata-plugin] (JENKINS-22996) Parameter not working in combination with Jenkins Release Plugin
Jochen Hinrichsen created JENKINS-22996 Parameter not working in combination with Jenkins Release Plugin Issue Type: Bug Affects Versions: current Assignee: Gesh Markov Components: maven-metadata-plugin Created: 13/May/14 1:47 PM Description: When using 'Build with parameter', the selection is passed to the build job. When using 'Release' via the Jenkins release plugin, nothing is passed. All other build/ releaes parameter types can be used like this. Project: Jenkins Priority: Major Reporter: Jochen Hinrichsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Jochen Hinrichsen commented on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade +1: same problem that $HOME/.gradle/gradle.properties is used for credentials. What's the reason for setting GRADLE_USER_HOME to job's workspace? We are making heavy use of gradle wrapper. Gradle distributions being installed per job instead of being shared nastily impacts the storage size. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13815) scm-sync-configuration raises unexpectedError() loading job configuration in IE8
Jochen Hinrichsen commented on JENKINS-13815 scm-sync-configuration raises unexpectedError() loading job configuration in IE8 The same problem occurs using IE 7.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16550) Existing defaultTasks not executed
Jochen Hinrichsen commented on JENKINS-16550 Existing defaultTasks not executed While working on a workaround, i found the problem: if the project is not checked out into the workspace directly, but into a subfolder (say: trunk), the gradle wrapper ist started, the project is found and run, but gradle gets bent out of shape w/ regard to its internal root project/ project/ module/ folder setup, and does not find default tasks. Weird. Would expect an error message at least. When checking out into the workspace directly, everything works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16550) Existing defaultTasks not executed
Jochen Hinrichsen
created JENKINS-16550
Existing defaultTasks not executed
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
gradle
Created:
30/Jan/13 1:23 PM
Description:
defaultTasks for a project are not taken into account and not executed.
Output of a commandline call './gradlew tasks':
All tasks runnable ...
Default tasks: check, package
Help tasks
--
Output of the same project inside jenkins ("Use gradle wrapper"):
All tasks runnable ...
Help tasks
--
The default tasks are missing, and are therefore not executed.
Environment:
Jenkins 1.480.2
Gradle 1.0, Gradle 1.4
Project:
Jenkins
Labels:
plugin
Priority:
Minor
Reporter:
Jochen Hinrichsen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12630) Solaris tar does not support gzip (z option)
Jochen Hinrichsen commented on JENKINS-12630 Solaris tar does not support gzip (z option) The issue remains in version 1.466.2. It happens on a SunOS master installation as well. The downloaded file is named 'jdk.sh', but it is a zipped tar. Standard Sun tar does not support zipped tars. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
