[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Thorsten Meinl created an issue Jenkins / JENKINS-34267 Email-ext doesn'r replace all tokens any more Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2016/Apr/15 7:57 AM Environment: Jenkins 1.651.1 email-ext-plugin 2.41.3 Priority: Major Reporter: Thorsten Meinl After updating to version 2.41.3, tokens in email subjects are not replaced any more. Instead they are sent plain: $PROJECT_NAME - Build # 137 - $BUILD_STATUS! After downgrading to 2.40.5 they are again replaced correctly. Add Comment
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Antonio Muñiz created an issue
Jenkins / JENKINS-34268
Lock multiple resources using the Pipeline lock step
Issue Type:
Improvement
Assignee:
Antonio Muñiz
Components:
lockable-resources-plugin
Created:
2016/Apr/15 7:59 AM
Priority:
Major
Reporter:
Antonio Muñiz
The current implementation of Pipeline lock step allows to block a single resource.
It should be extended to cover all the functionality of the plugin (applicable to non-freestyle jobs) such as blocking resources by label or request a lock for N resources.
The DSL must be something like this:
lock (resources: ['resource1', 'resource2']) {
... execution block ...
}
or
lock (label: 'my-resources') {
... execution block ...
}
The behavior of the label parameter would be equivalent to:
lock (resources: ['resource3', 'resource4']) { // if both resource3 and resource4 are labeled as 'my-resources'
... execution block ...
}
[JIRA] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title Antonio Muñiz commented on JENKINS-30269 Re: Add workflow support for resource locking As far as I have understood the documentation and from trying to understand the source code, the workflow support is limited to request a specific resource by name. Right. Wouldn't it be great to have the full functionality available in workflows? Especially as these use cases were also mentioned by the issue reporter. Yes. I've tried to cover the most common use-case in a Pipeline world (which is a replacement for stage concurrency: 1). The lock step has been designed to allow the addition of labels and multiple locking in future releases (filed as JENKINS-34268). 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-34260) slave.jar missing -secret feature
Title: Message Title Daniel Beck commented on JENKINS-34260 Re: slave.jar missing -secret feature Is the slave configured to use the JNLP launcher? (possibly called "Java WebStart") If not, no support for secrets. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-34263) The Jenkins Pipeline Bat command does not create an exception on exit code 1
Title: Message Title Antonio Muñiz assigned an issue to Unassigned Jenkins / JENKINS-34263 The Jenkins Pipeline Bat command does not create an exception on exit code 1 Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-34263) The Jenkins Pipeline Bat command does not create an exception on exit code 1
Title: Message Title Antonio Muñiz updated an issue Jenkins / JENKINS-34263 The Jenkins Pipeline Bat command does not create an exception on exit code 1 Change By: Antonio Muñiz Component/s: durable-task-plugin Component/s: pipeline-utility-steps-plugin Component/s: pipeline-stage-view-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] [extended-choice-parameter-plugin] (JENKINS-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z commented on JENKINS-34199 Re: Cannot use a simple Groovy Script Tried to look around in the Jenkins setup. I have this page "In-process Script Approval Allows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions." But when I enter I just got an empty fields [as per screenshot attached]. There are no links listed there, am I looking in the right place ? 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-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z edited a comment on JENKINS-34199 Re: Cannot use a simple Groovy Script Tried to look around in the Jenkins setup. I have this page "In-process Script ApprovalAllows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions." But when I enter I just got an empty fields [as per screenshot attached]. ! see here for screenshot: https://www.dropbox.com/s/ho9rrvztb4b7viq/Selection_009.png?dl=0 ! There are no links listed there, am I looking in the right place ? 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-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z edited a comment on JENKINS-34199 Re: Cannot use a simple Groovy Script Tried to look around in the Jenkins setup. I have this page "In-process Script ApprovalAllows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions." But when I enter I just got an empty fields [ as per screenshot attached]. see here for screenshot: https://www.dropbox.com/s/ho9rrvztb4b7viq/Selection_009.png?dl=0 ] There are no links listed there, am I looking in the right place ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-32349) Entering a newline in a Label description makes "slave" matrix axis unavailable
Title: Message Title
Christian Walther commented on JENKINS-32349
Re: Entering a newline in a Label description makes "slave" matrix axis unavailable
I just ran into this as well on Jenkins 1.646. It seems to me that the reason is that the hudson.Functions.jsStringEscape() function (https://github.com/jenkinsci/jenkins/blob/ac566a91e44e3482083355bd5cde3cf65610c4a3/core/src/main/java/hudson/Functions.java#L1333 called from hudson.matrix.LabelAxis.DescriptorImpl.buildLabelCheckBox() called from matrix-project-plugin/src/main/resources/hudson/matrix/LabelAxis/config.jelly) does not escape newlines, so that executing the generated _javascript_ code fails with a syntax error. The following patch might therefore fix it (I have not tested this however and don’t have time to):
diff --git a/core/src/main/java/hudson/Functions.java b/core/src/main/java/hudson/Functions.java
index 188412b..dd74ada 100644
--- a/core/src/main/java/hudson/Functions.java
+++ b/core/src/main/java/hudson/Functions.java
@@ -1344,6 +1344,9 @@ public class Functions {
case '"':
buf.append("\\\"");
break;
+case '\n':
+buf.append("\\n");
+break;
default:
buf.append(ch);
}
However, maybe showing only the first line of the description would be better – something like this (not tested either):
diff --git a/src/main/java/hudson/matrix/LabelAxis.java b/src/main/java/hudson/matrix/LabelAxis.java
index de8b6d1..672cad7 100644
--- a/src/main/java/hudson/matrix/LabelAxis.java
+++ b/src/main/java/hudson/matrix/LabelAxis.java
@@ -79,7 +79,7 @@ public class LabelAxis extends Axis {
Functions.htmlAttributeEscape(la.getName()))
+String.format("+has(%s)+",jsstr(la.getName()))
+jsstr("/>%s (%s)",
-la.getName(),la.getDescription());
+la.getName(),la.getDescription().split("[\\r\\n]", 2)[0]);
// '${h.jsStringEscape('"checkbox" name="values" json="'+h.htmlAttributeEscape(l.name)+'" ')}'+has("${h.jsStringEscape(l.name)}")+'${h.jsStringEscape('/>"attach-previous">'+l.name+' ('+l.description+')')}'
}
}
Add Comment
[JIRA] [core] (JENKINS-32349) Entering a newline in a Label description makes "slave" matrix axis unavailable
Title: Message Title Christian Walther updated an issue Jenkins / JENKINS-32349 Entering a newline in a Label description makes "slave" matrix axis unavailable Change By: Christian Walther Component/s: core 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-34260) slave.jar missing -secret feature
Title: Message Title Gunter Grodotzki commented on JENKINS-34260 Re: slave.jar missing -secret feature Where is this documented though? Not that I am not believing you, but I would like to learn more about it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter-plugin] (JENKINS-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z edited a comment on JENKINS-34199 Re: Cannot use a simple Groovy Script ! Tried to look around in the Jenkins setup. I have this page "In-process Script ApprovalAllows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions." But when I enter I just got an empty fields [see here for screenshot: https://www.dropbox.com/s/ho9rrvztb4b7viq/Selection_009.png?dl=0]There are no links listed there, am I looking in the right place ? ! 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-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z edited a comment on JENKINS-34199 Re: Cannot use a simple Groovy Script ! Tried to look around in the Jenkins setup. I have this page "In-process Script ApprovalAllows a Jenkins administrator to review proposed scripts (written e.g. in Groovy) which run inside the Jenkins process and so could bypass security restrictions." But when I enter I just got an empty fields [see here for screenshot: https://www.dropbox.com/s/ho9rrvztb4b7viq/Selection_009.png?dl=0]There are no links listed there, am I looking in the right place ? ! 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] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Florian Hug commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Besides the actual label functionality, also the possibility to request a certain amount of resources from this label would be essential.
I would personally prefer something like
lock(label: 'fooBar', quantity: 2) {
// whatever
}
Actually this is what keeps us from using pipelines.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-34263) The Jenkins Pipeline Bat command does not create an exception on exit code 1
Title: Message Title Scott Richmond closed an issue as Cannot Reproduce Jenkins / JENKINS-34263 The Jenkins Pipeline Bat command does not create an exception on exit code 1 Change By: Scott Richmond Status: Open Closed Resolution: Cannot Reproduce 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Antonio Muñiz commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart As github-organization-folder 1.2 is picked up by the setup wizard this is not happening anymore (manually tested). 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Antonio Muñiz commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart However the message Warning: This Jenkins instance requires a restart. Changing the state of plugins at this time is strongly discouraged. Restart Jenkins before proceeding. is still there, but it seems to be worked out in JENKINS-33950, so I think this issue can be closed. 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-34260) slave.jar missing -secret feature
Title: Message Title Daniel Beck commented on JENKINS-34260 Re: slave.jar missing -secret feature Let me filter and reorder the parameter documentation you quoted, maybe it makes sense then… -jnlpUrl URL : instead of talking to the master via stdin/stdout, emulate a JNLP client by making a TCP connection to the master. Connection parameters are obtained by parsing the JNLP file. -jnlpCredentials USER:PASSWORD : HTTP BASIC AUTH header to pass in for making HTTP requests. -secret HEX_SECRET : Slave connection secret to use instead of -jnlpCredentials. So unless you're using a launcher that "emulate[s] a JNLP client by making a TCP connection to the master", no need for jnlpCredentials/secret. Of course it's not impossible that a plugin may change this around a bit, but since you're not answering my question, I can't provide more specific advice. 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Daniel Beck commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart As github-organization-folder 1.2 is picked up by the setup wizard this is not happening anymore (manually tested). Antonio Muñiz The plugin 1.2 was released four weeks ago. This issue was filed yesterday. 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-34239) GitHub Organization Folder not available as a new item without a restart
Title: Message Title Antonio Muñiz commented on JENKINS-34239 Re: GitHub Organization Folder not available as a new item without a restart Mmmm, right, I thought this https://github.com/jenkinsci/github-organization-folder-plugin/pull/9 was already released. At any rate, Github Organization new item type is showing up now (without restarting), not sure what have changed since yesterday. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-34269) Suspected deadlock in SupportLogHandler.publish
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-34269 Suspected deadlock in SupportLogHandler.publish Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 2016/Apr/15 8:46 AM Environment: Jenkins 1.642.3, support-core-plugin 2.31 Priority: Critical Reporter: Marcin Zajączkowski We encountered a situation when 80+ threads were blocked on a lock acquired in SupportLogHandler.publish making the Jenkins instance irresponsible. Most of the threads go through the Pipeline Delivery plugin (which is heavily used by our users), but in the end everything tries to use Jenkins.getItem(java.lang.String). This is not the same as already fixed JENKINS-32622 . Analyzing thread dump I don't see a classic deadlock - all SupportLogHandler calls hang in the same place. Unfortunately the stack trace I have was taken with -F switch and does not have additional information about locks - like who owns the lock. The support-core plugin had been installed a few hours before the accident which happened twice separated by a restart and disappeared after the plugin was removed. I can sen
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Antonio Muñiz commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Florian Hug Could you explain a real use case where the quantity configuration makes sense please? It's not clear to me why one would want to acquire 2 resources but do not caring about which ones specifically. 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-34260) slave.jar missing -secret feature
Title: Message Title Gunter Grodotzki commented on JENKINS-34260 Re: slave.jar missing -secret feature Ah I think it makes more sense now (I guess). My Jenkins setup has "Jenkins’ own user database" & "Role-Based Strategy" activated, meaning there are no guest activities allowed. So I am running "normal" nodes/slaves as "dumb slave" + "launch slave agents on unix via ssh" - which works perfectly. Per log I only see the following: code [04/14/16 12:25:27] [SSH] Starting slave process: cd "/var/lib/jenkins" && java -jar slave.jar code Which looks like it is not passing through any credentials, but it still works? When using the EC2 Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin) and Spot Instances however, I need to start the slave.jar from within the node, there I get a 403 (and I'd be surprised if it just worked, or else any machine could propagate itself as a slave/node). I am trying to figure out now which parameters I need to use, and as said I am too stupid to find a proper documentation except running java -jar slave.jar --help - which btw. is also not documented but a common way under unix/linux to get some kind of help. Googleling on those options I am getting mixed information - so it would be great to know which option to use to authenticate the slave.jar, and if it is indeed true that the "password" must be replaced by a users api key. 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-34260) slave.jar missing -secret feature
Title: Message Title
Gunter Grodotzki edited a comment on JENKINS-34260
Re: slave.jar missing -secret feature
Ah I think it makes more sense now (I guess). My Jenkins setup has "Jenkins’ own user database" & "Role-Based Strategy" activated, meaning there are no guest activities allowed. So I am running "normal" nodes/slaves as "dumb slave" + "launch slave agents on unix via ssh" - which works perfectly.Per log I only see the following:{{ code}} [04/14/16 12:25:27] [SSH] Starting slave process: cd "/var/lib/jenkins" && java -jar slave.jar {{code }}Which looks like it is not passing through any credentials, but it still works?When using the EC2 Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin) and Spot Instances however, I need to start the slave.jar from within the node, there I get a 403 (and I'd be surprised if it just worked, or else any machine could propagate itself as a slave/node).I am trying to figure out now which parameters I need to use, and as said I am too stupid to find a proper documentation except running java -jar slave.jar --help - which btw. is also not documented but a common way under unix/linux to get some kind of help.Googleling on those options I am getting mixed information - so it would be great to know which option to use to authenticate the slave.jar, and if it is indeed true that the "password" must be replaced by a users api key.
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] [promoted-builds-plugin] (JENKINS-34270) List Subversion tags parameter only available on Re-execute promotion
Title: Message Title Michael Göhler created an issue Jenkins / JENKINS-34270 List Subversion tags parameter only available on Re-execute promotion Issue Type: Bug Assignee: Oleg Nenashev Attachments: job-config.xml, promotion-config.xml Components: promoted-builds-plugin, subversion-plugin Created: 2016/Apr/15 8:57 AM Environment: Jenkins: 1.609.2 Jenkins Promoted builds plugin: 2.21 Jenkins Subversion Plugin: 2.5.2 Priority: Major Reporter: Michael Göhler Steps to reproduce: Create a job according to the attached config.xml's Execute Build Execute Promotion
[JIRA] [promoted-builds-plugin] (JENKINS-34270) List Subversion tags parameter only available on Re-execute promotion
Title: Message Title Michael Göhler updated an issue Jenkins / JENKINS-34270 List Subversion tags parameter only available on Re-execute promotion Change By: Michael Göhler Steps to reproduce:* Create a job according to the attached config.xml's* Execute Build* Execute Promotion* Re-execute Promotion* Compare the console output of both both promotion builds** The "List Subversion tags" parameter is available in at re-execution onlyNo exceptions in jenkins.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28086) JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts)
Title: Message Title zsolt Somogyi commented on JENKINS-28086 Re: JNLP slave connection does not consider java non-proxy settings (http.nonProxyHosts) This is a huge pain when having a corporate proxy. This is still a bug in jenkins 2.0 rc. So I was actually trying out Jenkins running on the LAN, where the proxy shouldn't be used, but the http_proxy is set by some corporate scripts, and reset every few minutes. I tried using cntlm which was configured to skip the corporate proxy on LAN. The only workaround was to put the whole jnpl launch in a batch file and set the http_proxy to the cntlm one forcefully before launching the slave/agent, this way the shell scrips would also use a working proxy. So not hard, but not really trivial. Fixing the bug in Jenkins should be easier, right? 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] [promoted-builds-plugin] (JENKINS-34270) List Subversion tags parameter only available on Re-execute promotion
Title: Message Title Michael Göhler updated an issue Jenkins / JENKINS-34270 List Subversion tags parameter only available on Re-execute promotion Change By: Michael Göhler Steps to reproduce:* Create a job according to the attached config.xml's* Execute Build* Execute Promotion* Re-execute Promotion* Compare the console output of both promotion builds** The "List Subversion tags" parameter is available in at re-execution onlyNo exceptions in jenkins.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34230) Display the reason when branch indexing failse
Title: Message Title Thomas Johansen commented on JENKINS-34230 Re: Display the reason when branch indexing failse FYI: the reason was most likely that the branch indexing process was killed by Linux due to lack of physical memory. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-34230) Display the reason when branch indexing failse
Title: Message Title Thomas Johansen updated an issue Jenkins / JENKINS-34230 Display the reason when branch indexing failse Change By: Thomas Johansen Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Florian Hug commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Background: We dynamically create virtual machines which acts as jenkins slave (using the swarm-plugin) to perform the actual build steps. Thereby, if an error occurs we can archive the whole VM such that a developer can investigate and solve the problem. Using linked snapshots the whole purpose of creating such a new VM takes simply seconds and works very well.
Problem solved by lockable resources: Since the overall amount of memory and cores on the host machine is limited, we used the lockable resources plugin to manage the distribution of memory (slices) and cpu cores.
For example, let's say we have configured 16 resources (Memory Slice 1, Memory Slice 2, ..., Memory Slice 3), each representing e.g. 4 GB Memory. that is a total of 64 GB being available for virtual machines. When a job starts and wants to create a VM with e.g. 16 GB virtual memory, the job simply tries to request 4 slices of memory
lock(label: 'memory', quantity: 4) {
// actual build steps
}
If this succeeds there is enough memory available, and the job can continue. If not, the job blocks until the necessary amount of memory is available again (since other jobs have finished and shut down their VMs).
The same principle applies to CPU (cores) as well.
Does this explanation help?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more opt
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Florian Hug edited a comment on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
*Background:*We dynamically create virtual machines which acts as jenkins slave (using the {{swarm-plugin}}) to perform the actual build steps. Thereby, if an error occurs we can archive the whole VM such that a developer can investigate and solve the problem. Using linked snapshots the whole purpose of creating such a new VM takes simply seconds and works very well.*Problem solved by lockable resources:*Since the overall amount of memory and cores on the host machine is limited, we used the lockable resources plugin to manage the distribution of memory (slices) and cpu cores.For example, let's say we have configured 16 resources (Memory Slice 1, Memory Slice 2, ..., Memory Slice 3), each representing e.g. 4 GB Memory. that is a total of 64 GB being available for virtual machines. When a job starts and wants to create a VM with e.g. 16 GB virtual memory, the job simply tries to request 4 slices ({{ = quantity }}) of 4 GB memory{code:java}lock(label: 'memory', quantity: 4) { // actual build steps}{code}If this succeeds there is enough memory available, and the job can continue. If not, the job blocks until the necessary amount of memory is available again (since other jobs have finished and shut down their VMs).The same principle applies to CPU (cores) as well.Does this explanation help?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Martin Skogevall commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Since there is no known workaround, this is a critical issue if not blocker on Windows at least. I am eagerly waiting to test the pipelines/workflows because initial tests have shown that we can reduce our build times a lot with the added flexibility of workflows. 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] [multiple-scms-plugin] (JENKINS-34271) Cannot Retrieve Commit Hashes when Using Multiple Get Repositories
Title: Message Title Will Buckner created an issue Jenkins / JENKINS-34271 Cannot Retrieve Commit Hashes when Using Multiple Get Repositories Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms-plugin Created: 2016/Apr/15 9:07 AM Environment: Jenkins 1.656, Ubuntu 14.04, Multiple SCM Plugin version 0.7-SNAPSHOT, 9e61a8d Priority: Major Reporter: Will Buckner I need to access the Git commit hash for each of my 4 multiple Git repositories configured using the Multiple SCMs Plugin. Each repository is also configured to trigger the build. I need to ensure that my build is triggered using the exact same versions of the repository from the point that Jenkins triggered the build. When I run env inside my Build Script Task, I see GIT_URL_1 through GIT_URL_4, but only one GIT_COMMIT (even after PR#19, I just GIT_COMMIT and GIT_COMMIT_1). What's worse, GIT_COMMIT is neither from Repository 1 nor Repository 4... it seems to consistently be from Repository 3. I am not sure if this will actually remain consistent, so my commit hash is effectively useless. The expected result is to see the latest hash from each repository, numbered according to the GIT_URL_* numbering. Thanks for taking a look, and I'm happy to provide any needed information.
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Florian Hug edited a comment on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
*Background:*We dynamically create virtual machines which acts as jenkins slave (using the {{swarm-plugin}}) to perform the actual build steps. Thereby, if an error occurs we can archive the whole VM such that a developer can investigate and solve the problem. Using linked snapshots the whole purpose of creating such a new VM takes simply seconds and works very well.*Problem solved by lockable resources:*Since the overall amount of memory and cores on the host machine is limited, we used the lockable resources plugin to manage the distribution of memory (slices) and cpu cores.For example, let's say we have configured 16 resources (Memory Slice 1, Memory Slice 2, ..., Memory Slice 3), each representing e.g. 4 GB Memory. that is a total of 64 GB being available for virtual machines. When a job starts and wants to create a VM with e.g. 16 GB virtual memory, the job simply tries to request 4 slices ({{ = quantity }}) of 4 GB memory{code:java}lock(label: 'memory', quantity: 4) { // actual build steps}{code}If this succeeds there is enough memory available, and the job can continue. If not, the job blocks until the necessary amount of memory is available again (since other jobs have finished and shut down their VMs).The same principle applies to CPU (cores) as well.Does this explanation help?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-34272) Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
Title: Message Title Fernando Miguelez created an issue Jenkins / JENKINS-34272 Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6) Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 2016/Apr/15 9:09 AM Environment: Jenkins 1.609.3 Labels: plugin java7 Priority: Minor Reporter: Fernando Miguelez After upgrading from 1.8.4 to 1.9.0, Throttle Concurrent Builds Plug-in started displaying following error: FINEST|20230/0|Service jenkins|16-04-15 10:44:35|java.lang.InstantiationException: java.lang.UnsupportedClassVersionError: hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions : unsupported classversion 51.0 We use JDK6 and this plugin does not document that it requires JDK7. We use latest required Jenkins core 1.609.3, which does not require JDK7 either. The fix could be as simple as regenerate plug
[JIRA] [core] (JENKINS-33926) Jenkins no longer appears to shutdown correctly
Title: Message Title James Nord assigned an issue to Unassigned Jenkins / JENKINS-33926 Jenkins no longer appears to shutdown correctly Change By: James Nord Assignee: James Nord 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-33926) Jenkins no longer appears to shutdown correctly
Title: Message Title James Nord commented on JENKINS-33926 Re: Jenkins no longer appears to shutdown correctly Not saving the queue on windows was fixed recently on master. I'm unassigning from myself for the moment as I'm not looking at this. If I get to look at it and it's not taken I will re-assign it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27530) ISE from RunMap.put after reloading configuration from disk
Title: Message Title Jeff Miller commented on JENKINS-27530 Re: ISE from RunMap.put after reloading configuration from disk If "Reload Configuration from disk" isn't going to be fully supported then it should be removed entirely. I've worked around this issue by downloading the code and modifying the java.hudson.model.Job.java class to force it to read from the file "nextBuildNumber" every time it needs nextBuildNumber. However this has the side effect of builds that enter the Pending Build Queue while a reload is occurring, will not show up in the build history until another "Reload configuration from disk" is performed. Some legacy support maybe needed to added back in on the onLoad() method. /* * The MIT License * * Copyright (c) 2004-2009, Sun Microsystems, Inc., Kohsuke Kawaguchi, Martin Eigenbrodt, Matthew R. Harrah, Red Hat, Inc., Stephen Connolly, Tom Huybrechts, CloudBees, Inc. * * Permission is hereby granted, free of charge, to any person obtaining a copy * of this software and associated documentation files (the "Software"), to deal * in the Software without restriction, including without limitation the rights * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell * copies of the Software, and to permit persons to whom the Software is * furnished to do so, subject to the following conditions: * * The above copyright notice and this permission notice shall be included in * all copies or substantial portions of the Software. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN * THE SOFTWARE. */ package hudson.model; import com.google.common.base.Function; import com.google.common.collect.Collections2; import com.infradna.tool.bridge_method_injector.WithBridgeMethods; import hudson.BulkChange; import hudson.EnvVars; import hudson.Extension; import hudson.ExtensionPoint; import hudson.PermalinkList; import hudson.Util; import hudson.cli.declarative.CLIResolver; import hudson.model.Descriptor.FormException; import hudson.model.Fingerprint.Range; import hudson.model.Fingerprint.RangeSet; import hudson.model.PermalinkProjectAction.Permalink; import hudson.model.listeners.ItemListener; import hudson.search.QuickSilver; import hudson.search.SearchIndex; import hudson.search.SearchIndexBuilder; import hudson.search.SearchItem; import hudson.search.SearchItems; import hudson.security.ACL; import hudson.tasks.LogRotator; import hudson.util.AlternativeUiTextProvider; import hudson.util.ChartUtil; import hudson.util.ColorPalette; import hudson.util.CopyOnWriteList; import hudson.util.DataSetBuilder; import hudson.util.DescribableList; import hudson.util.FormApply; import hudson.util.Graph; import hudson.util.ProcessTree; import hudson.util.QuotedStringTokenizer; import hudson.util.RunList; import hudson.util.ShiftedCategoryAxis; import hudson.util.StackedAreaRenderer2; import hudson.util.TextFile; import hudson.widgets.HistoryWidget; import hudson.widgets.HistoryWidget.Adapter; import hudson.widgets.Widget; import jenkins.model.BuildDiscarder; import jenkins.model.DirectlyModifiableTopLevelItemGroup; import jenkins.model.Jenkins; import jenkins.model.ProjectNamingStrategy; import jenkins.security.HexStringConfidentialKey; import jenkins.util.io.OnMaster; import net.sf.json.JSONExcep
[JIRA] [core] (JENKINS-34197) OutOfMemoryError when archiving large artifacts
Title: Message Title Yngve Hammersland commented on JENKINS-34197 Re: OutOfMemoryError when archiving large artifacts I tried increasing -Xmx to 1500m but it still runs out of memory. 2000m does not work because I run 32 bit java. I will try to upgrade to 64 bit java to see if it helps go to 2000m and beyond. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Martin S. commented on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Looks to be caused under the same circumstances. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-33164) Pipeline bat stuck on Windows Server 2012
Title: Message Title Martin S. edited a comment on JENKINS-33164 Re: Pipeline bat stuck on Windows Server 2012 Looks JENKINS-28759 seems to be caused under the same circumstances a similar 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] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Antonio Muñiz commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Thanks for take the time to explain! Makes sense, although nothing is preventing the steps inside the lock block to consume more CPU/RAM than virtually acquired, right? 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-34199) Cannot use a simple Groovy Script
Title: Message Title Nanda Kishore commented on JENKINS-34199 Re: Cannot use a simple Groovy Script I face this problem even after approving my groovy script. 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-34260) slave.jar missing -secret feature
Title: Message Title Daniel Beck resolved as Not A Defect Which looks like it is not passing through any credentials, but it still works? Well, the connection has been established from the master, so it's assumed that's legitimate, and the default mode of operation is… talking to the master via stdin/stdout I need to start the slave.jar from within the node, there I get a 403 (and I'd be surprised if it just worked, or else any machine could propagate itself as a slave/node). Seems like an oversight in the documentation for the plugin. Also, it should in theory show the secret, but… JNLP: https://github.com/jenkinsci/jenkins/blob/944571f9b5242b1d1419cdfcd1a4a7d62bc33904/core/src/main/resources/hudson/slaves/JNLPLauncher/main.jelly#L69 EC2: https://github.com/jenkinsci/ec2-plugin/blob/a6d2c874daf999362d827430e419d38cefaa7c81/src/main/resources/hudson/plugins/ec2/EC2SpotComputerLauncher/main.jelly#L27...L36 FWIW the secret was only added as an alternative means to connect three years ago. Workarounds: Use jnlpCredentials. Figure out how to get the secret from the script console. Resolving as not a defect, because it isn't. You should consider filing an improvement request for the EC2 Plugin. Jenkins / JENKINS-34260 slave.jar missing -secret feature Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Florian Hug commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Yes and no No: Once the VM is configured to a certain amount of CPU/RAM, that amount is fixed and no process inside the VM can use more. If a process inside such a VM want's to consume more memory it simply receives an OutOfMemory exception. Yes: However, in theory, you can lock a different amount than you configure the VM. However, in our pipeline scripts we define a variable, e.g. required_memory_slices and use this variable to specify the necessary quantity as well as use this variable when setting up the virtual machine. Hence, in this case, it is guaranteed that we lock the same amount that we configure the VM to use, and hence no process can consume more CPU/RAM. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-branch-project-plugin] (JENKINS-34234) Add task to override child jobs configuration
Title: Message Title Miguel Ángel García commented on JENKINS-34234 Re: Add task to override child jobs configuration It is a good idea, but currently it doesn't happen. Anyway, that might be a problem when the change relates to the own build, such as the labels where the job can be ran. I've tried by adding a new build step, waiting for it to be updated and it didn't update the child jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Alex Earl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more Did you also upgrade token-macro? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Thorsten Meinl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more Yes, it's on the latest version 1.12.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Alex Earl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more Can you share your job configuration? I haven't heard of anyone else with three same issue, so there must be something unique in your setup 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] [lockable-resources-plugin] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title
Antonio Muñiz created an issue
Jenkins / JENKINS-34273
Extend quantity configuration to Pipeline lock step
Issue Type:
Improvement
Assignee:
Antonio Muñiz
Components:
lockable-resources-plugin
Created:
2016/Apr/15 9:58 AM
Priority:
Minor
Reporter:
Antonio Muñiz
Extend the use of quantity configuration parameter to the lock step.
The behavior should be the same than defined for freestyle builds.
The DSL should look like this:
lock (resource: 'RAM', quantity: 3) { ... }
quantity must be applicable to any of resource, resources or label (see JENKINS-34268).
Add Comment
[JIRA] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Antonio Muñiz commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Ok, looks good. I've created a separate issue (JENKINS-34273) for quantity support in Pipeline as it can be handled independently of this one. BTW you have there a nice CI configuration 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-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z commented on JENKINS-34199 Re: Cannot use a simple Groovy Script Nanda Kishore where did you approve the script ? I have nothing appearing in the "In-process Script Approval" 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] [teamconcert-plugin] (JENKINS-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah commented on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655#https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284 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-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [ 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655 #https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284] 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-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [# 388284: Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1.655 ] 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-34117) java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655
Title: Message Title Sridevi Sangaiah edited a comment on JENKINS-34117 Re: java.lang.UnsupportedOperationException when checking out code in Jenkins 1.655 Tracked in [#388284 https : Loading a jenkins build workspace with a RTC build definition configuration fails in Jenkins 1 //jazz . 655] net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388284. 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-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Sridevi Sangaiah commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Is the build toolkit configured in the slave node? If not, I believe it should be available in the same path as in the master. 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] [lockable-resources-plugin] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Florian Hug commented on JENKINS-34268 Re: Lock multiple resources using the Pipeline lock step Thanks And we are keen on switching to the new Pipeline - but JENKINS-34273 is absolutely necessary for us. 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-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Wulf-Thilo Schreiter commented on JENKINS-34181 Re: NullPointerException in BuildNameSetter.setup The NPE is still in version 1.6.1 I've created a pull request to have the auto unboxing NULL save. https://github.com/jenkinsci/build-name-setter-plugin/pull/11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Thorsten Meinl updated an issue Jenkins / JENKINS-34267 Email-ext doesn'r replace all tokens any more Jenkins configuration files Change By: Thorsten Meinl Attachment: hudson.plugins.emailext.ExtendedEmailPublisher.xml Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Thorsten Meinl edited a comment on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more Jenkins configuration files are attached.BTW, if you perform a search on the internet for "$BUILD_STATUS" and "Jenkins" you will find quite a lot of hits that seem to indicate the same or a similar 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] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Lev Mishin commented on JENKINS-34181 Re: NullPointerException in BuildNameSetter.setup Thanks a lot! I just forgot about constructor parameters since on my PC all work fine Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Alex Earl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more I didn't see any hits that related to email-ext 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-34199) Cannot use a simple Groovy Script
Title: Message Title Nanda Kishore commented on JENKINS-34199 Re: Cannot use a simple Groovy Script At the of the "In-process Script Approval" page, where you have "No pending script approvals" as per your picture. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Stefan Rademacher commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure This issue also ocurrs in the current Jenkins 2.0 release candidate 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] [junit-plugin] (JENKINS-34274) Duration testsuite is not read from report.
Title: Message Title Alexei Moussatov created an issue Jenkins / JENKINS-34274 Duration testsuite is not read from report. Issue Type: Bug Assignee: Unassigned Attachments: result.xml Components: junit-plugin Created: 2016/Apr/15 11:22 AM Priority: Major Reporter: Alexei Moussatov Duration of testsuite cannot be read from the report file, but instead summarizes all the values of tests execution times. Feature was announced in v1.11 Add Comment
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-34272) Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
Title: Message Title
Fernando Miguelez commented on JENKINS-34272
Re: Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
I downloaded the sources and tried to generate it locally.
If found it is not possible to use a JDK6 to compile due to other plugin compatibility:
[ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate (default-validate) on project throttle-concurrents: Execution default-validate of goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate failed: Unable to load the mojo 'validate' in the plugin 'org.jenkins-ci.tools:maven-hpi-plugin:1.117' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: org/jenkinsci/maven/plugins/hpi/ValidateMojo : unsupported classversion 51.0
The problem lies in the pom.xml configuration. "compileSource" and "compileTarget" no longer work but "java.level" and "java.level.test". So pom.xml should be updated: {{ 6 6 }}
There was another issue with xml-apis. It did not compile due to a missing class. I had to force a higher version:
{{ xml-apis xml-apis 1.4.01 test }}
And finally one of the classes would now compile due to Java7 syntax: {{ [ERROR] /O:/oip/ws/oip/throttle-concurrent-builds-plugin-throttle-concurrents-1.9.0/src/test/java/hudson/plugins/throttleconcurrents/testutils/HtmlUnitHelper.java:[56,46] diamond operator is not supported in -source 1.6 }}
Just replace following line (65) of HtmlUnitHelper.java : {{ List res = new ArrayList<>(buttons.size()); }} by {{ List res = new ArrayList(buttons.size()); }}
And it works.
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 gr
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-34272) Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
Title: Message Title
Fernando Miguelez edited a comment on JENKINS-34272
Re: Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
I downloaded the sources and tried to generate it locally.If found it is not possible to use a JDK6 to compile due to other plugin compatibility:{{[ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate (default-validate) on project throttle-concurrents: Execution default-validate of goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate failed: Unable to load the mojo 'validate' in the plugin 'org.jenkins-ci.tools:maven-hpi-plugin:1.117' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: org/jenkinsci/maven/plugins/hpi/ValidateMojo : unsupported classversion 51.0}}The problem lies in the pom.xml configuration. "compileSource" and "compileTarget" no longer work but "java.level" and "java.level.test". So pom.xml should be updated: {{ 6 6}}There was another issue with xml-apis. It did not compile due to a missing class. I had to force a higher version:{{ xml-apis xml-apis 1.4.01 test }}And finally one of the classes would now compile due to Java7 syntax: {{ [ERROR] /O:/oip/ws/oip/throttle-concurrent-builds-plugin-throttle-concurrents-1.9.0/src/test/java/hudson/plugins/throttleconcurrents/testutils/HtmlUnitHelper.java:[56,46] diamond operator is not supported in -source 1.6}} Just replace following line (65) of HtmlUnitHelper.java : {{ List res = new ArrayList<>(buttons.size());}}by {{ List res = new ArrayList(buttons.size());}} And it works.
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-34272) Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
Title: Message Title
Fernando Miguelez edited a comment on JENKINS-34272
Re: Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
I downloaded the sources and tried to generate it locally.If found it is not possible to use a JDK6 to compile due to other plugin compatibility:{{[ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate (default-validate) on project throttle-concurrents: Execution default-validate of goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate failed: Unable to load the mojo 'validate' in the plugin 'org.jenkins-ci.tools:maven-hpi-plugin:1.117' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: org/jenkinsci/maven/plugins/hpi/ValidateMojo : unsupported classversion 51.0}}The problem lies in the pom.xml configuration. "compileSource" and "compileTarget" no longer work but "java.level" and "java.level.test". So pom.xml should be updated:{{ 6 6 }}There was another issue with xml-apis. It did not compile due to a missing class. I had to force a higher version:{{xml-apis xml-apis 1.4.01 test }}And finally one of the classes would now compile due to Java7 syntax:{{[ERROR] /O:/oip/ws/oip/throttle-concurrent-builds-plugin-throttle-concurrents-1.9.0/src/test/java/hudson/plugins/throttleconcurrents/testutils/HtmlUnitHelper.java:[56,46] diamond operator is not supported in -source 1.6}}Just replace following line (65) of HtmlUnitHelper.java :{{List res = new ArrayList<>(buttons.size()); }}by {{List res = new ArrayList(buttons.size()); }} And it works.
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-34272) Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
Title: Message Title
Fernando Miguelez edited a comment on JENKINS-34272
Re: Throttle Concurrent Builds Plug-in 1.9 requires Java7 (it should work with Java6)
I downloaded the sources and tried to generate it locally.If found it is not possible to use a JDK6 to compile due to other plugin compatibility:{{[ERROR] Failed to execute goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate (default-validate) on project throttle-concurrents: Execution default-validate of goal org.jenkins-ci.tools:maven-hpi-plugin:1.117:validate failed: Unable to load the mojo 'validate' in the plugin 'org.jenkins-ci.tools:maven-hpi-plugin:1.117' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: org/jenkinsci/maven/plugins/hpi/ValidateMojo : unsupported classversion 51.0}}The problem lies in the pom.xml configuration. "compileSource" and "compileTarget" no longer work but "java.level" and "java.level.test". So pom.xml should be updated:{{ 6 6}}There was another issue with xml-apis. It did not compile due to a missing class. I had to force a higher version: {{ xml-apis xml-apis 1.4.01 test }}And finally one of the classes would now compile due to Java7 syntax:{{[ERROR] /O:/oip/ws/oip/throttle-concurrent-builds-plugin-throttle-concurrents-1.9.0/src/test/java/hudson/plugins/throttleconcurrents/testutils/HtmlUnitHelper.java:[56,46] diamond operator is not supported in -source 1.6 }} Just replace following line (65) of HtmlUnitHelper.java :{{List res = new ArrayList<>(buttons.size());}}by {{List res = new ArrayList(buttons.size());}}And it works.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Stefan Rademacher edited a comment on JENKINS-26481 Re: Mishandling of binary methods accepting Closure This issue also ocurrs in the current Jenkins 2.0 release candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-14618) ignore the checkout on the master
Title: Message Title Tommi Kiviniemi commented on JENKINS-14618 Re: ignore the checkout on the master Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. I see it if not a bug, then a huge oversight that there is not a checkbox for whether master should do an SCM checkout as well. I am in the exact same boat as Alexander, the master does a lengthy unnecessary SCM checkout before the slaves start building. I tried to work around this by using a custom workspace for the slaves and reuse it from the master, but the workspace name can not be constructed from the axis values as they are not initialised there yet. The current behaviour is 1) unexpected 2) increases build times by tens of percent for no gain. What good does it do to do two SCM syncs, where one is discarded? 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-32703) Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin
Title: Message Title Gunter Grodotzki commented on JENKINS-32703 Re: Unable to use LDAP accounts as remote user to connect slaves using EC2 plugin Having problems when launching Spot Instances as the slave.jar does not get any credentials passed through. Normal EC2 instances works perfectly. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-34267) Email-ext doesn'r replace all tokens any more
Title: Message Title Alex Earl commented on JENKINS-34267 Re: Email-ext doesn'r replace all tokens any more I just tried running with a maven project locally and the tokens were replaced correctly. Did you restart Jenkins after upgrading email-ext and token-macro? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-34275) CLONE - Workflow/Pipeline Support for Checkmarx Plugin
Title: Message Title Philipp Meier assigned an issue to Unassigned Jenkins / JENKINS-34275 CLONE - Workflow/Pipeline Support for Checkmarx Plugin Change By: Philipp Meier Assignee: Bruno P. Kinoshita Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-34275) CLONE - Workflow/Pipeline Support for Checkmarx Plugin
Title: Message Title Philipp Meier updated an issue Jenkins / JENKINS-34275 CLONE - Workflow/Pipeline Support for Checkmarx Plugin Change By: Philipp Meier TAP Chechmarx plugin should support the workflow plugin (aka 'pipelines').See: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-34275) CLONE - Workflow/Pipeline Support for Checkmarx Plugin
Title: Message Title Philipp Meier created an issue Jenkins / JENKINS-34275 CLONE - Workflow/Pipeline Support for Checkmarx Plugin Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: tap-plugin Created: 2016/Apr/15 11:51 AM Priority: Minor Reporter: Philipp Meier TAP plugin should support the workflow plugin (aka 'pipelines'). See: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md Add Comment
[JIRA] [checkmarx-plugin] (JENKINS-34275) CLONE - Workflow/Pipeline Support for Checkmarx Plugin
Title: Message Title Philipp Meier updated an issue Jenkins / JENKINS-34275 CLONE - Workflow/Pipeline Support for Checkmarx Plugin Change By: Philipp Meier Component/s: checkmarx-plugin Component/s: tap-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-plugin] (JENKINS-24402) jsch version
Title: Message Title David Del Signore commented on JENKINS-24402 Re: jsch version This problem is happening with greater frequency for me recently. Jenkins 1.654 SSH Plugin 2.4 Oracle JDK 1.7.0_67 CentOS 5 x64 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-14618) ignore the checkout on the master
Title: Message Title Daniel Beck commented on JENKINS-14618 Re: ignore the checkout on the master Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. This has been reopened in late 2014 and not closed since. 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-34199) Cannot use a simple Groovy Script
Title: Message Title vimil updated an issue Jenkins / JENKINS-34199 Cannot use a simple Groovy Script Change By: vimil Attachment: config.png Attachment: build.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] [extended-choice-parameter-plugin] (JENKINS-34199) Cannot use a simple Groovy Script
Title: Message Title vimil commented on JENKINS-34199 Re: Cannot use a simple Groovy Script Dav z, do you have security enabled in Jenkins? You will see entries there only if security is enabled.If you don't have security enabled then you don't need to approve groovy scripts. They should work without script approval. I couldn't repro this issue on my machine. I use 0.63 version of the plugin on jenkins 1.654. here is how my configuration screen looks like. here is how the build page looks like 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-34199) Cannot use a simple Groovy Script
Title: Message Title vimil edited a comment on JENKINS-34199 Re: Cannot use a simple Groovy Script Dav z, do you have security enabled in Jenkins? You will see entries there only if security is enabled.If you don't have security enabled then you don't need to approve groovy scripts. They should work without script approval.I couldn't repro this issue on my machine. I use 0.63 version of the plugin on jenkins 1.654.here is how my configuration screen looks like.!config.png|thumbnail!here is how the build page looks like!build.png|thumbnail! Can you check the Jenkins system log to see there are any exceptions there?You can find this under 'Manage Jenkins' Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-34181) NullPointerException in BuildNameSetter.setup
Title: Message Title Lev Mishin commented on JENKINS-34181 Re: NullPointerException in BuildNameSetter.setup PR is merged, new release is created, new version will be 1.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-34276) docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Title: Message Title
Radesh Rao created an issue
Jenkins / JENKINS-34276
docker.inside within a withRegistry block seems to use image.id instead of image.imageName()
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin, workflow-plugin
Created:
2016/Apr/15 1:16 PM
Priority:
Major
Reporter:
Radesh Rao
I'm trying to execute a maven build inside of my custom container (my.registry.com/build-env:jdk8-maven3):
node('docker') {
docker.withRegistry('https://my.registry.com', 'docker-registry-login') {
def maven = docker.image("my-build-env:jdk8-maven3")
sh "echo ${maven.imageName()} -- ${maven.id}"
maven.pull()
maven.inside() {
sh "echo Hello"
}
}
}
It goes well until the pull, which uses the imageName (my.registry.com/build-env:jdk8-maven3) but the run command uses id (build-env:jdk8-maven3)
Abbreviated logs:
Started by user Radesh Rao
[Pipeline] Allocate node : Start
Running on docker in /data/jenkins/workspace/My pipeline
[Pipeline] node {
[Pipeline] Set environment variables : Start
[Pipeline] withEnv {
[Pipeline] Sets up Docker registry endpoint : Start
[Pipeline] withDockerRegistry {
[Pipeline] sh
[Cloud pipeline] Running shell script
+ echo my.r
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title Antonio Mansilla resolved as Fixed Jenkins / JENKINS-32548 Support for mercurial repositories Change By: Antonio Mansilla 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] [js-builder] (JENKINS-34277) Glyphicons wont work using CSS adjuncts
Title: Message Title Raphael Pionke created an issue Jenkins / JENKINS-34277 Glyphicons wont work using CSS adjuncts Issue Type: Improvement Assignee: Tom FENNELLY Components: js-builder Created: 2016/Apr/15 1:18 PM Environment: Jenkins 1.642.4 @jenkins-cd/js-builder: 0.0.29 Priority: Minor Reporter: Raphael Pionke While playing around with bootstrap less files and css adjuncts. i came to the conclusion that glyphicons can not be loaded, even they are in the same adjunct folder: There is my less & css file: \target\classes\org\jenkins\ui\jsmodules\css\bootstrapprefix.less same spot for the glyphicon font: \target\classes\org\jenkins\ui\jsmodules\css\glyphicons-halflings-regular.woff2 I can load js or css files, but i cant use fonts like this. To debug this i used the @icon-font-path: "fonts/"; parameter.
[JIRA] [js-builder] (JENKINS-34277) Glyphicons wont work using CSS adjuncts
Title: Message Title Raphael Pionke updated an issue Jenkins / JENKINS-34277 Glyphicons wont work using CSS adjuncts Change By: Raphael Pionke Labels: ui 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-34199) Cannot use a simple Groovy Script
Title: Message Title Dav z commented on JENKINS-34199 Re: Cannot use a simple Groovy Script vimil, yes I have security enabled in /configureSecurity/ Digging a bit int the log show that a script required approval, so wend back to the approval page and this time there was an approval button. So now I can embed a groovy script. But it seems that I cannot load it . I tried both using the the absolute path and relative to the Job but nothing shows up. Also nothing comes up in the log file when the file cannot be found 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] [checkmarx-plugin] (JENKINS-34275) Workflow/Pipeline Support for Checkmarx Plugin
Title: Message Title Philipp Meier updated an issue Jenkins / JENKINS-34275 Workflow/Pipeline Support for Checkmarx Plugin Change By: Philipp Meier Summary: CLONE - Workflow/Pipeline Support for Checkmarx 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] [build-flow-plugin] (JENKINS-34278) Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class
Title: Message Title Alex Domoradov created an issue Jenkins / JENKINS-34278 Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow-plugin Created: 2016/Apr/15 1:39 PM Priority: Minor Reporter: Alex Domoradov Default z-index value (10) Can only create thumbnails for attached images Fixed (2) Can only create thumbnails for attached images Add Comment
[JIRA] [build-flow-plugin] (JENKINS-34278) Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class
Title: Message Title Alex Domoradov updated an issue Jenkins / JENKINS-34278 Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class Change By: Alex Domoradov Default z-index value (10) ! http://i.imgur.com/j7qOI4R.png |thumbnail! Fixed (2) ! http://i.imgur.com/woZ6OVT.png |thumbnail! 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-flow-plugin] (JENKINS-34278) Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class
Title: Message Title Alex Domoradov updated an issue Jenkins / JENKINS-34278 Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class Change By: Alex Domoradov Default z-index value (10) ! http://i.imgur.com/j7qOI4R.png |width=300,height=400! Fixed (2)http://i.imgur.com/woZ6OVT.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] [authorize-project-plugin] (JENKINS-34279) Fails with Active Directory
Title: Message Title larsskj created an issue Jenkins / JENKINS-34279 Fails with Active Directory Issue Type: Bug Assignee: Unassigned Components: authorize-project-plugin Created: 2016/Apr/15 1:43 PM Environment: Freshly installed 1.656 with only Authorize Project and Active Directory plugins installed. Priority: Major Reporter: larsskj When authentication is set to use the Active Directory plugin, Authorize Plugin fails if job authorization is set to anything but SYSTEM. Setting a job to "Run as user who triggered the build", the job just hangs in the job queue indefinitely waiting for access to an executor - when triggered by a logged-in user. Add Comment
[JIRA] [build-flow-plugin] (JENKINS-34278) Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class
Title: Message Title Alex Domoradov updated an issue Jenkins / JENKINS-34278 Build-flow-plugin: Incorrect z-index value in CodeMirror-gutter class Change By: Alex Domoradov Default z-index value (10) ! http://i.imgur.com/j7qOI4R.png |width=300,height=400! Fixed (2) http://i.imgur.com/woZ6OVT.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] [parameterized-trigger-plugin] (JENKINS-11577) Matrix axis are not recognixed as parameter
Title: Message Title
Tommi Kiviniemi commented on JENKINS-11577
Re: Matrix axis are not recognixed as parameter
I can not access axes before SCM sync. I have a multi-configuration job where I want to define a custom workspace for the master's checkout and reuse that for the child (child workspace "."). Setting custom workspace to $ {BRANCH_NAME}${PLATFORM}${BUILD_TYPE} results in a workspace called "${BRANCH_NAME}
_$ {PLATFORM}
_$ {BUILD_TYPE}
". Trying to access the axes in "Prepare an environment for this run" can not access them yet either, nor via properties or a Groovy script. Right now there is no way for me to construct the workspace name due to this. Could you please make the axes available already at that point?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-11577) Matrix axis are not recognixed as parameter
Title: Message Title
Tommi Kiviniemi edited a comment on JENKINS-11577
Re: Matrix axis are not recognixed as parameter
I can not access axes before SCM sync. I have a multi-configuration job where I want to define a custom workspace for the master's checkout and reuse that for the child (child workspace "."). Setting custom workspace to $ {BRANCH_NAME}_ BRANCH_NAME_ $ {PLATFORM}_ PLATFORM_ $ { BUILD_TYPE } results in a workspace called "$ {BRANCH_NAME}_ BRANCH_NAME_ $ {PLATFORM}_ PLATFORM_ $ { BUILD_TYPE } ". Trying to access the axes in "Prepare an environment for this run" can not access them yet either, nor via properties or a Groovy script. Right now there is no way for me to construct the workspace name due to this. Could you please make the axes available already at that point?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title
Marc Rufer commented on JENKINS-34150
Re: Pipeline Batch hangs
I had the same issue with the following Jenkinsfile
node {
checkout scm
bat 'Powershell.exe -executionpolicy remotesigned -File Build.ps1'
}
Batch only hangs if there are several executions running in parallel
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.
