[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title
Christoph Linder edited a comment on JENKINS-30296
Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build
Can confirm this bug.Some more detail:We had a string parameter containing named BRANCH with ' \ */feature/ \ *' ( without the quotes, at least that's what is visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}.Some developer created the branch "feature/feature/foobar".The bug only got triggered as long as the branch with the duplicate "feature" was present. We did lots of tests with different variations of wildcards but the problem mainly got solved when we * removed the string parameter * and used this wildcard directly in branch spec: origin/feature/**(Unfortunately, I cannot spend more time on testing this but my gut feeling tells me: string params with wildcards would be the next thing to investigate)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3332.1567176360292%40Atlassian.JIRA.
[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title
Christoph Linder edited a comment on JENKINS-30296
Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build
Can confirm this bug.Some more detail:We had a string parameter containing BRANCH '\ */feature/ \ *' (at least that's visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}.Some developer created the branch "feature/feature/foobar".The bug only got triggered as long as the branch with the duplicate "feature" was present. We did lots of tests with different variations of wildcards but the problem mainly got solved when we * removed the string parameter * and used this wildcard directly in branch spec: origin/feature/**(Unfortunately, I cannot spend more time on testing this but my gut feeling tells me: string params with wildcards would be the next thing to investigate)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3323.1567176300306%40Atlassian.JIRA.
[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build
Title: Message Title
Christoph Linder commented on JENKINS-30296
Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build
Can confirm this bug. Some more detail: We had a string parameter containing BRANCH /feature/' (at least that's visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}. Some developer created the branch "feature/feature/foobar". The bug only got triggered as long as the branch with the duplicate "feature" was present. We did lots of tests with different variations of wildcards but the problem mainly got solved when we
removed the string parameter
and used this wildcard directly in branch spec: origin/feature/**
(Unfortunately, I cannot spend more time on testing this but my gut feeling tells me: string params with wildcards would be the next thing to investigate)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3314.1567176240338%40Atlassian.JIRA.
[JIRA] (JENKINS-57823) allow customization of date/time format
Title: Message Title Christoph Linder created an issue Jenkins / JENKINS-57823 allow customization of date/time format Issue Type: Improvement Assignee: Martin Spielmann Components: schedule-build-plugin Created: 2019-06-03 15:45 Priority: Minor Reporter: Christoph Linder It'd be nice to have a configurable date/time format for the scheduled build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder commented on JENKINS-50992 Re: Cannot add folder properties Thanks for the explanations!!! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder closed an issue as Not A Defect Jenkins / JENKINS-50992 Cannot add folder properties Change By: Christoph Linder Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder commented on JENKINS-50992 Re: Cannot add folder properties sorry for the misunderstanding... feeling a little bit stupid right now So... to have environment variables defined on folder level, I'd have to place an feature request on EnvInjector to support the AbstractFolderProperty extensin point? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder updated an issue Jenkins / JENKINS-50992 Cannot add folder properties Change By: Christoph Linder Attachment: jenkins-plugins.csv Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder commented on JENKINS-50992 Re: Cannot add folder properties Probably lots EnvInjector is the first I'm thinking of, then some tools See attachment jenkins-plugins.csv Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50992) Cannot add folder properties
Title: Message Title Christoph Linder created an issue Jenkins / JENKINS-50992 Cannot add folder properties Issue Type: Bug Assignee: Devin Nusbaum Attachments: Folder Properties.png Components: cloudbees-folder-plugin Created: 2018-04-25 09:56 Priority: Major Reporter: Christoph Linder As per Docs (https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#folder) there is a possibility to configure folder properties. In the folder configuration, I see a "properties" section, but there is nothing (no button, no form-fields, ...) See attached screenshot. I'd expect an "add" button or similar. Add Comment
[JIRA] (JENKINS-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Christoph Linder assigned an issue to Andrew Bayer Jenkins / JENKINS-46105 Docker 17.05 ARG in FROM breaks docker inspect Change By: Christoph Linder Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Christoph Linder updated JENKINS-46105 Jenkins / JENKINS-46105 Docker 17.05 ARG in FROM breaks docker inspect Change By: Christoph Linder Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Christoph Linder started work on JENKINS-46105 Change By: Christoph Linder Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Christoph Linder commented on JENKINS-46105 Re: Docker 17.05 ARG in FROM breaks docker inspect Peter Grayson: Confirmed and fixed in PR https://github.com/jenkinsci/docker-workflow-plugin/pull/136 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Christoph Linder reopened an issue Jenkins / JENKINS-46105 Docker 17.05 ARG in FROM breaks docker inspect Change By: Christoph Linder Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-35920) Build parameter not passed on for Maven Repository Artifact
Title: Message Title Christoph Linder commented on JENKINS-35920 Re: Build parameter not passed on for Maven Repository Artifact Affected plugin: Repository Connector Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin) Steps to reproduce: Configure the plugin (i.e.: setup the maven repo) Create new job (freestyle) Select "This project is parameterized" Add "Maven Repository Artifact" and setup something suitable (i.E.: property "FOO", group "org.apache.commons", artifact "commons-lang3" Add Build Step -> Execute shell On a Linux-Jenkins: echo found: $FOO On a Windows-Jenkins: echo found: %FOO% Start the build with the parameter. Expected result: somewhere in the build log, the chosen parameter value shoud appear, e.g.: "found RELEASE" Actual result (value missing): "found" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35920) Build parameter not passed on for Maven Repository Artifact
Title: Message Title Christoph Linder commented on JENKINS-35920 Re: Build parameter not passed on for Maven Repository Artifact Using the system-properties mentioned here is (for us) a viable temporary workaround for this problem https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-35920) Build parameter not passed on for Maven Repository Artifact
Title: Message Title Christoph Linder created an issue Jenkins / JENKINS-35920 Build parameter not passed on for Maven Repository Artifact Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/15 11:18 AM Priority: Major Reporter: Christoph Linder We are using parametrized Builds. Since short (not sure exactly when), the Build-Paramters from the Maven Repository Artifact do not get passed on. Other Parameter types (e.G.: "text") do work. Might be related to JENKINS-34996 (Sec-170-related) Add Comment
[JIRA] [vncviewer-plugin] (JENKINS-32857) Make port range configurable
Title: Message Title Christoph Linder created an issue Jenkins / JENKINS-32857 Make port range configurable Issue Type: New Feature Assignee: Dimitri Tenenbaum Components: vncviewer-plugin Created: 09/Feb/16 3:06 PM Priority: Major Reporter: Christoph Linder Our Jenkins lives behind a firewall and we do not want to open the whole ephemeral port-range for incoming requests. So it would be really nice if we could configure a port-range that is available to the vnc viewer plugin. Add Comment
[JIRA] [customtools-plugin] (JENKINS-32771) Support .tar.bz2 on download
Title: Message Title Christoph Linder created an issue Jenkins / JENKINS-32771 Support .tar.bz2 on download Issue Type: Improvement Assignee: Oleg Nenashev Attachments: customtools-stacktrace.txt Components: customtools-plugin Created: 04/Feb/16 1:48 PM Priority: Minor Reporter: Christoph Linder Trying to install this tool: http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/44.0/linux-x86_64/en-US/firefox-44.0.tar.bz2 Seems like .tar.bz2 is not supported and gives an exception in the build log (complete stacktrace see Attachment): Caused by: java.io.IOException: incorrect header check at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:112) at org.apache.commons.compress.utils.IOUtils.readFully(IOUtils.java:160) Quick workaround ist to wget and unpack manually. Custom Tools Plugin version: 0.4.4 Jenkins Version: 1.646 running on JDK8
[JIRA] [core] (JENKINS-13171) Unstable builds due to "SEVERE: I/O error in channel Channel to Maven"
Title: Message Title Christoph Linder reopened an issue Still exists in 1.6.32 Jenkins / JENKINS-13171 Unstable builds due to "SEVERE: I/O error in channel Channel to Maven" Change By: Christoph Linder Resolution: Incomplete 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-13171) Unstable builds due to "SEVERE: I/O error in channel Channel to Maven"
Title: Message Title Christoph Linder edited a comment on JENKINS-13171 Re: Unstable builds due to "SEVERE: I/O error in channel Channel to Maven" Still exists in 1. 6.32 632 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-13171) Unstable builds due to "SEVERE: I/O error in channel Channel to Maven"
Title: Message Title Christoph Linder commented on JENKINS-13171 Re: Unstable builds due to "SEVERE: I/O error in channel Channel to Maven" Current error message: Oct 21, 2015 8:37:50 AM SEVERE hudson.remoting.SynchronousCommandTransport$ReaderThread run I/O error in channel Channel to Maven [/apps/jenkins/data/tools/hudson.model.JDK/JDK_1.6_32_x64/bin/java, -XX:MaxPermSize=256m, -cp, /apps/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.7.jar:/apps/jenkins/data/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /apps/jenkins/data/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.4, /apps/jenkins/data/war/WEB-INF/lib/remoting-2.52.jar, /apps/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.7.jar, /apps/jenkins/data/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.7.jar, 48727] java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2304) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2773) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:798) at java.io.ObjectInputStream.(ObjectInputStream.java:298) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 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] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Christoph Linder
created JENKINS-26992
WebLogic deployer does not expand variables
Issue Type:
Bug
Assignee:
Raphael CHAUMIER
Components:
weblogic-deployer-plugin
Created:
17/Feb/15 12:41 PM
Description:
I would like to use a base directory relative to ${WORKSPACE}.
In other plugins, I can just write ${WORKSPACE}/foo/bar/baz.
This does not work on the wl-deployer.
It would be nice to have this in all configuration options (e.g. global + per-job options)
See first answer here for a hint on how to implement this:
http://stackoverflow.com/questions/23800416/jenkins-inject-environment-variable-in-jelly-field
Environment:
Jenkins 1.598, Linux, Deploy WebLogic Plugin 2.13
Project:
Jenkins
Labels:
weblgoc-deployer-plugin-2.13
Priority:
Major
Reporter:
Christoph Linder
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] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Christoph Linder
commented on JENKINS-7411
Slave environment variables are not used during Git Polling
Also: setting the tool location on the slave via environment variables is not considered during polling.
Steps to reproduce using Jenking Git Plugin 1.3.0 on Jenkins 1.510:
Set environment variable on master:
PATH_TO_TOOLS=c:\somewhere\tools
On the Slave:
PATH_TO_TOOLS=d:\elsewhere\tools
Tool-Location for default git installation: ${PATH_TO_TOOLS}/git/git.exe
During polling, jenkins always tries to execute git.exe in c:\somewhere\tools, although it is run on the slave
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-5408) Quoting Issue with JDK Installer with Windows Slave
Christoph Linder commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Pretty please? 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.
