[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise commented on JENKINS-49794 Re: BooleanParam default value is always true So say I run a build without specifying parameters, it takes the default ones. Then I replay the same but I modify the script to have different default parameters. From a user perspective it s confusing if it does not take the new default values. Maybe there should be condition for which if the replayed run was using the default parameters, those have to be computed again as the script may have changed. In any case it s a minor, I let you decide if to close it or put it lowest priority. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise commented on JENKINS-49794 Re: BooleanParam default value is always true yeah makes sense but it's not ideal. Is there something we can do or you think it's a non-defect? It makes testing harder Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise edited a comment on JENKINS-49794 Re: BooleanParam default value is always true Ok I can reproduce it in this way. * create the pipeline job and set the default to true. * hit on REPLAY but in the script section, modify the default to false * execute Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise commented on JENKINS-49794 Re: BooleanParam default value is always true Ok I can reproduce it in this way. create the pipeline job and set the default to true. hit on REPLAY but in the script section, modify the default to false execute Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise commented on JENKINS-49794 Re: BooleanParam default value is always true mm I could reproduce when hitting on REPLAY (as opposite of starting a new build). Can it make any difference? I can do some more tests Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise commented on JENKINS-49794 Re: BooleanParam default value is always true plugin versions are attached as screenshot Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-49794 BooleanParam default value is always true Change By: valentina armenise Attachment: Screen Shot 2018-02-28 at 15.12.16.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-49794 BooleanParam default value is always true Change By: valentina armenise Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-49794
BooleanParam default value is always true
Change By:
valentina armenise
My pipeline defines a parameter with sth like: {noformat}parameters { booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?') }{noformat} Printing the param value with{code:java}script { if (params.RUN_TESTS) { echo "true: $RUN_TESTS" } else echo "false: $RUN_TESTS" }{code}shows that the value is always TRUE and the tests are always executed. I think this is somewhat related to I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title
valentina armenise created an issue
Jenkins / JENKINS-49794
BooleanParam default value is always true
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-28 14:09
Priority:
Minor
Reporter:
valentina armenise
My pipeline defines a parameter with sth like:
parameters {
booleanParam(name: 'RUN_TESTS', defaultValue: false, description: 'Do you want to run the build with tests?')
}
Printing the param value with
script {
if (params.RUN_TESTS) {
echo "true: $RUN_TESTS"
}
else echo "false: $RUN_TESTS"
}
shows that the value is always TRUE and the tests are always executed. I think this is somewhat related to I think this is somewhat related to https://issues.jenkins-ci.org/browse/JENKINS-36543
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title valentina armenise commented on JENKINS-49500 Re: In every pipeline build with triggers, a new trigger is created and the old one is stopped Andrew Bayer just had the time to do some tests. With both. Everytime you execute the pipeline with a trigger, the trigger is stopped and re-started (meaning the Trigger `stop` function is called). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title valentina armenise commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered Andrew Bayer sorry for the late. core 2.89 workflow-job 2.17 workflow-multibranch NA (not installed in my tests) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-49502 trigger properties in scripted pipeline require 2 builds to get registered Change By: valentina armenise Summary: trigger properties in scripted pipeline require 2 builds to be get registered in the UI Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to be registered in the UI
Title: Message Title
valentina armenise created an issue
Jenkins / JENKINS-49502
trigger properties in scripted pipeline require 2 builds to be registered in the UI
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-job-plugin
Created:
2018-02-12 11:03
Priority:
Minor
Reporter:
valentina armenise
When defining trigger in a declarative pipeline, it will suffice to write
pipeline {
agent any
triggers {
cron('H H(0-7) * * *')
}
}
and build once. After the first build accessing the job config UI will show the trigger configuration. However if you do the same thing with a scripted pipeline
node {
properties([pipelineTriggers([cron('H H(0-7) * * *')])])
}
you need two builds to register the trigger (it won't appear in the UI and won't be working until the second manual build).
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-49500 In every pipeline build with triggers, a new trigger is created and the old one is stopped Issue Type: Improvement Assignee: Unassigned Components: workflow-job-plugin Created: 2018-02-12 10:16 Priority: Minor Reporter: valentina armenise Pipeline trigger job properties get recreated (deleted and re-added) from scratch in each build. This is not ideal and could also cause some trigger downtime, ad there seems to be a period of time where a job could have no trigger at all. Add Comment
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise updated JENKINS-43086 Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise commented on JENKINS-43076 Re: dropdownlist element does not define html name tag PR here https://github.com/jenkinsci/jenkins/pull/2820. However I closed it cause fixing it will cause too much headache. I am not sure we should fix it but at least this JIRA will track the behaviour of dropdownList with form path plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise After [https://github.com/jenkinsci/ssh-slaves-plugin/commit/11ec7e7a10ae97ba7bef02dcc3a353136ccc576d] the ssh-slave plugin requires to select a verification strategy to control how Jenkins verifies the SSH key presented by the remote host whilst connecting.The ssh-slave plugins test in the acceptance-test-harness suite will then fail when using version of ssh-slave plugin higher than 1.15 cause the default verification strategy is `Known host verification strategy` which implies to add the ssh keys of the slave to the known hosts file of the host.So we either need to refactor the tests to take further steps and ensure verification is successful or enforce a Non verification strategy. Although the enforced plugin version is 1.11 I think we should align the test to latest release and upgrade it to use 1.15 to make sure that other tests which use the latest version of the ssh-slave plugin run successfull. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise started work on JENKINS-43086 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise Assignee: Oliver Gondža valentina armenise Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Issue Type: Improvement Assignee: Oliver Gondža Components: acceptance-test-harness, ssh-slaves-plugin Created: 2017/Mar/24 10:28 AM Priority: Minor Reporter: valentina armenise After https://github.com/jenkinsci/ssh-slaves-plugin/commit/11ec7e7a10ae97ba7bef02dcc3a353136ccc576d the ssh-slave plugin requires to select a verification strategy to control how Jenkins verifies the SSH key presented by the remote host whilst connecting. The ssh-slave plugins test in the acceptance-test-harness suite will then fail when using version of ssh-slave plugin higher than 1.15 cause the default verification strategy is `Known host verification strategy` which implies to add the ssh keys of the slave to the known hosts file of the host. So we either need to refactor the tests to take further steps and ensure verification is successful or enforce a Non verification strategy. Although the enforced plugin version is 1.11 I think we should align the test to latest release and upgrade it to use 1.15 to make sure that other tests which use the latest version of the ssh-slave plugin run successfull.
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise commented on JENKINS-43076 Re: dropdownlist element does not define html name tag Note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-43076
dropdownlist element does not define html name tag
Change By:
valentina armenise
The Dropdown jelly form does not use [the name attribute|https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/resources/lib/form/dropdownList.jelly#L34]. This makes it difficult to reference in selenium tests. Similarly to what [dropDownListSelector does|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/dropdownDescriptorSelector.jelly#L54] it should have something like{noformat} {noformat}in its jelly file.For all config files using a dropDownList in fact the [Form Element Path plugin|https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin] does not generate the path correctly (it would simply add "/" or "/" followed by a number cause it cannot compute the unique id using its name). For an example see [ https://github.com/jenkinsci/acceptance-test-harness/blob/47ae4d5cd6e1c17308c1dc2e28ee6b3b11bc3a0d/src/main/java/org/jenkinsci/test/acceptance/po/DumbSlave.java#L23 ] Besides that, the name field is defined and not used in the jelly file so .However, note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path. I think am not sure it should be fixed anyways 's worth it .
Add Comment
This message was sent by
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-43076 dropdownlist element does not define html name tag Change By: valentina armenise Comment: Note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-43076
dropdownlist element does not define html name tag
Change By:
valentina armenise
The Dropdown jelly form does not use [the name attribute|https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/resources/lib/form/dropdownList.jelly#L34]. This makes it difficult to reference in selenium tests. Similarly to what [dropDownListSelector does|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/dropdownDescriptorSelector.jelly#L54] it should have something like{noformat} {noformat}in its jelly file.For all config files using a dropDownList in fact the [Form Element Path plugin|https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin] does not generate the path correctly (it would simply add "/" or "/" followed by a number cause it cannot compute the unique id using its name). For an example see https://github.com/jenkinsci/acceptance-test-harness/blob/47ae4d5cd6e1c17308c1dc2e28ee6b3b11bc3a0d/src/main/java/org/jenkinsci/test/acceptance/po/DumbSlave.java#L23 Besides that, the name field is defined and not used in the jelly file so I think it should be fixed anyways.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-43076
dropdownlist element does not define html name tag
Change By:
valentina armenise
The Dropdown jelly form does not use [the name attribute|https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/resources/lib/form/dropdownList.jelly#L34]. This makes it difficult to reference in selenium tests. Similarly to what [dropDownListSelector does|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/dropdownDescriptorSelector.jelly#L54] it should have something like { { noformat} }} {{ }} {{ \ {attrs.name}"> }} {{ }} {{ }} {{ }} {{ {noformat } } in its jelly file.For all config files using a dropDownList in fact the [Form Element Path plugin|https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin] does not generate the path correctly (it would simply add "/" or "/" followed by a number cause it cannot compute the unique id using its name).Besides that, the name field is defined and not used in the jelly file so I think it should be fixed anyways.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-43076
dropdownlist element does not define html name tag
Change By:
valentina armenise
The Dropdown jelly form does not use [the name attribute|https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/resources/lib/form/dropdownList.jelly#L34]. This makes it difficult to reference in selenium tests. Similarly to what [dropDownListSelector does|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/dropdownDescriptorSelector.jelly#L54] it should have something like ``` {{ }} {{ }} {{ }} {{ }} {{ }} {{ }} {{ }} ``` in its jelly file. For all config files using a dropDownList in fact the [Form Element Path plugin|https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin] does not generate the path correctly (it would simply add "/" or "/" followed by a number cause it cannot compute the unique id using its name).Besides that, the name field is defined and not used in the jelly file so I think it should be fixed anyways.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise moved an issue Jenkins / JENKINS-43076 dropdownlist element does not define html name tag Change By: valentina armenise Project: Security Issues Jenkins Key: SECURITY JENKINS - 476 43076 Issue Type: Improvement Bug Workflow: Security v1.2 JNJira + In-Review Status: Untriaged Open Component/s: core Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41264) better javadocs for new remoting protocol
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-41264
better javadocs for new remoting protocol
Change By:
valentina armenise
We should better explain the workflow of the {{JnlpAgentReceiver}} which hands over to {{JnlpChannelReceiver}} 's implementations . 1) {{owns}} is called on all the extension points, if no owner is found exception is thrown2) if {{owner}} is found, then {{afterProperties}} is called on all the extension points, when we find one which changesthe listener (e.g. approved or rejected) {{JnlpConnectionState}} sets the current listener as {{owner}}3) subsequent steps of the lifecycle are only called on the {{owner}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-41264) better javadocs for new remoting protocol
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-41264
better javadocs for new remoting protocol
Change By:
valentina armenise
We should better explain the workflow of the ` {{ JnlpAgentReceiver ` }} which hands over to {{ JnlpChannelReceiver }} implementations.1) ` {{ owns ` }} is called on all the extension points, if no owner is found exception is thrown2) if ` {{ owner ` }} is found, then ` {{ afterProperties ` }} is called on all the extension points, when we find one which changesthe listener (e.g. approved or rejected) ` {{ JnlpConnectionState ` }} sets the current listener as ` {{ owner ` }} 3) subsequent steps of the lifecycle are only called on the ` {{ owner ` }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-41264) better javadocs for new remoting protocol
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-41264 better javadocs for new remoting protocol Change By: valentina armenise Assignee: valentina armenise Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41264) better javadocs for new remoting protocol
Title: Message Title valentina armenise started work on JENKINS-41264 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41264) better javadocs for new remoting protocol
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-41264 better javadocs for new remoting protocol Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/20 4:15 PM Priority: Minor Reporter: valentina armenise We should better explain the workflow of the `JnlpAgentReceiver` which hands over to JnlpChannelReceiver implementations. 1) `owns` is called on all the extension points, if no owner is found exception is thrown 2) if `owner` is found, then `afterProperties` is called on all the extension points, when we find one which changes the listener (e.g. approved or rejected) `JnlpConnectionState` sets the current listener as `owner` 3) subsequent steps of the lifecycle are only called on the `owner` Add Comment
[JIRA] (JENKINS-40546) JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent
Title: Message Title valentina armenise closed an issue as Not A Defect Jenkins / JENKINS-40546 JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent Change By: valentina armenise Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40546) JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent
Title: Message Title valentina armenise assigned an issue to Oliver Gondža Jenkins / JENKINS-40546 JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent Change By: valentina armenise Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40546) JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-40546 JnlpAgentReceiver `afterProperties` is called when the specific implementation does not own the agent Change By: valentina armenise Summary: JnlpAgentReceiver `afterProperties` is called even when the specific implementation does not own the agent Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40546) JnlpAgentReceiver `afterProperties` is called even when the specific implementation does not own the agent
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-40546 JnlpAgentReceiver `afterProperties` is called even when the specific implementation does not own the agent Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/19 2:53 PM Environment: Jenkins core 2.32.1 LTS Priority: Major Reporter: valentina armenise Jenkins core 2.32.1 LTS. trying to implement a `JnlpAgentReceiver`, the method `AfterProperties` is invoked on the same extension point even if the `owns` method of the same returns `false`. Add Comment
[JIRA] (JENKINS-39823) Update Version History for 2.1.9 on Credentials+Plugin wiki page
Title: Message Title valentina armenise commented on JENKINS-39823 Re: Update Version History for 2.1.9 on Credentials+Plugin wiki page Stephen Connolly aha fair enough Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39720) Gracefully handle option deleted in Select Widget
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-39720 Gracefully handle option deleted in Select Widget Change By: valentina armenise Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39720) Gracefully handle option deleted in Select Widget
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-39720 Gracefully handle option deleted in Select Widget Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Nov/14 4:26 PM Priority: Minor Reporter: valentina armenise When an option of a Select widget (e.g. JDK, Maven tool) does not exist anymore, the UI displays a wrong value, the first one in the list. The config.xml will preserve the old value until we save the new configuration - causing failures and confusion since UI and config.xml mismatch. Also, since the UI automatically changes to the new value without warning the user, the user does not know the tool/item/option the job/operation was configured to use does not exist anymore. Add Comment
[JIRA] (JENKINS-39720) Gracefully handle option deleted in Select Widget
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-39720 Gracefully handle option deleted in Select Widget Change By: valentina armenise When an option of a Select widget (e.g. JDK, Maven tool) does not exist anymore, the UI displays a wrong value in the dropdown, specificallt specifically the first one in the list.The config.xml will preserve the old value until we save the new configuration - causing failures and confusion since UI and config.xml mismatch.Also, since the UI automatically changes to the new value without warning the user, the user does not know the tool/item/option the job/operation was configured to use does not exist anymore. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39720) Gracefully handle option deleted in Select Widget
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-39720 Gracefully handle option deleted in Select Widget Change By: valentina armenise When an option of a Select widget (e.g. JDK, Maven tool) does not exist anymore, the UI displays a wrong value in the dropdown , specificallt the first one in the list.The config.xml will preserve the old value until we save the new configuration - causing failures and confusion since UI and config.xml mismatch.Also, since the UI automatically changes to the new value without warning the user, the user does not know the tool/item/option the job/operation was configured to use does not exist anymore. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39381) Jenkins Support Bundle should propose to bundle config.xml (and other config files)
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-39381 Jenkins Support Bundle should propose to bundle config.xml (and other config files) Issue Type: Improvement Assignee: valentina armenise Components: support-core-plugin Created: 2016/Oct/31 12:03 PM Priority: Minor Reporter: valentina armenise We should filter out secrets and exclude credentials.xml. Also config.xml will be enabled by default in the UI, whereas the option to add other config files will be unchecked. Add Comment
[JIRA] (JENKINS-39381) Jenkins Support Bundle should propose to bundle config.xml (and other config files)
Title: Message Title valentina armenise started work on JENKINS-39381 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36537) UpdateNow function on metadata should consider a custom json signature validator
Title: Message Title valentina armenise updated JENKINS-36537 Jenkins / JENKINS-36537 UpdateNow function on metadata should consider a custom json signature validator Change By: valentina armenise Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise started work on JENKINS-37968 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-37968 schedule build on parametrised jobs randomly fails when the form is not loaded before timeout Change By: valentina armenise Assignee: Oliver Gondža valentina armenise Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37968) schedule build on parametrised jobs randomly fails when the form is not loaded before timeout
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-37968 schedule build on parametrised jobs randomly fails when the form is not loaded before timeout Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2016/Sep/05 4:24 PM Priority: Minor Reporter: valentina armenise Sometimes when executing `job.scheduleBuild()` on a parametrised job selenium test fails with org.openqa.selenium.NoSuchElementException: Unable to locate By.xpath: .//input[./@type = 'submit' or ./@type = 'reset' or ./@type = 'image' or ./@type = 'button'][((./@id = 'Build' or ./@name = 'Build' or contains(./@value, 'Build')) or contains(./@title, 'Build'))] | .//input[./@type = 'image'][contains(./@alt, 'Build')] | .//button[(((./@id = 'Build' or contains(./@value, 'Build')) or contains(normalize-space(.), 'Build')) or contains(./@title, 'Build'))] | .//input[./@type = 'image'][contains(./@alt, 'Build')] in http://172.17.0.1:55457/job/matrixJob/build?delay=0sec For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46' System info: host: 'ip-172-18-64-125', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.2.0-42-generic', java.version: '1.8.0_40' Driver info: driver.version: unknown at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:292) at org.jenkinsci.test.acceptance.junit.Wait.timeoutException(Wait.java:143) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:261) at org.jenkinsci.test.acceptance.junit.Wait.until(Wait.java:74) at org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.find(CapybaraPortingLayerImpl.java:197) at
[JIRA] (JENKINS-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise started work on JENKINS-37941 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise updated JENKINS-37941 Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Change By: valentina armenise Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Change By: valentina armenise Assignee: Jesse Glick valentina armenise Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37941) folder plugin missing norefresh=true in RelocationAction
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-37941 folder plugin missing norefresh=true in RelocationAction Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 2016/Sep/02 6:08 PM Priority: Minor Reporter: valentina armenise RelocationAction index.jelly is missing norefresh=true https://github.com/jenkinsci/cloudbees-folder-plugin/blob/master/src/main/resources/com/cloudbees/hudson/plugins/folder/relocate/RelocationAction/index.jelly#L6 Add Comment
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title valentina armenise commented on JENKINS-37232 Re: ATH test fails on NEW ITEM Wizard on Jenkins 2.7 Jenkins 2.0 seems working instead Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard on Jenkins 2.7
Change By:
valentina armenise
Summary:
ATH test fails on NEW ITEM Wizard on Jenkins 2.7
When running ATH tests agains Jenkins 2. 0 7 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected.Some investigation and debugging showed that:1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet).2) the item type is selected3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name")3) the OK button is not shown case now the validation fails on the item name (empty).If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead.Looks like this condition is false https://github.com/jenkinsci/jenkins/blob/5f9614433ec3bd9057097bbe2af7d445e6cd918e/war/src/main/js/add-item.js#L178.The ATH tests are failing here https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java#L25
Add Comment
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard
Change By:
valentina armenise
When running ATH tests agains Jenkins 2.0 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected.Some investigation and debugging showed that:1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet).2) the item type is selected3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name")3) the OK button is not shown case now the validation fails on the item name (empty).If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead. Looks like this condition is false https://github.com/jenkinsci/jenkins/blob/5f9614433ec3bd9057097bbe2af7d445e6cd918e/war/src/main/js/add-item.js#L178.The ATH tests are failing here https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java#L25
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37232) ATH test fails on NEW ITEM Wizard
Title: Message Title
valentina armenise created an issue
Jenkins / JENKINS-37232
ATH test fails on NEW ITEM Wizard
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
acceptance-test-harness
Created:
2016/Aug/05 11:46 PM
Environment:
Firefox 41, same behaviour detected on 46. Mac OSX
Priority:
Minor
Reporter:
valentina armenise
When running ATH tests agains Jenkins 2.0 the New Item Wizard fails to enable the OK button after the name is inserted and the type of item selected. Some investigation and debugging showed that: 1) the item name is inserted and stored with jquery, no warning shown. Validation of OK button fails cause the item time has not been selected yet (OK button not shown yet). 2) the item type is selected 3) right after selecting the item type a red warning is show on the item name input text ("The field cannot be empty, please enter a valid name") 3) the OK button is not shown case now the validation fails on the item name (empty). If while debugging, you click anywhere on the page after the item type is selected, the red warning goes away and the OK button shown. Sending Keys.TAB with selenium (or changing focus) does not work instead.
[JIRA] (JENKINS-36537) UpdateNow function on metadata should consider a custom json signature validator
Title: Message Title valentina armenise updated JENKINS-36537 Jenkins / JENKINS-36537 UpdateNow function on metadata should consider a custom json signature validator Change By: valentina armenise Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36537) UpdateNow function on metadata should consider a custom json signature validator
Title: Message Title valentina armenise started work on JENKINS-36537 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36537) UpdateNow function on metadata should consider a custom json signature validator
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-36537 UpdateNow function on metadata should consider a custom json signature validator Change By: valentina armenise Assignee: valentina armenise Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36537) UpdateNow function on metadata should consider a custom json signature validator
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-36537 UpdateNow function on metadata should consider a custom json signature validator Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jul/08 2:36 PM Priority: Minor Reporter: valentina armenise the getJsonSignatureValidator was added in UpdateSite to give the possibility to UpdateSite subclasses to define a custom JsonSignatureValidator. However the updateNow function on metadata does not using it . This results in `signature validations exceptions` on signature checks. Add Comment
[JIRA] [core] (JENKINS-34883) DefaultUpdateSiteID option from JENKINS-34674 does not really switch default
Title: Message Title valentina armenise started work on JENKINS-34883 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34883) DefaultUpdateSiteID option from JENKINS-34674 does not really switch default
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-34883 DefaultUpdateSiteID option from JENKINS-34674 does not really switch default Change By: valentina armenise Assignee: valentina armenise 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-34880) When using multiple updateSites, tool installer download fails if one UC is missing installers
Title: Message Title valentina armenise started work on JENKINS-34880 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34880) When using multiple updateSites, tool installer download fails if one UC is missing installers
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-34880 When using multiple updateSites, tool installer download fails if one UC is missing installers Change By: valentina armenise Assignee: valentina armenise 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-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-32831 "None of the Update Sites passed the signature check" w/ Jenkins v1.647 Change By: valentina armenise Assignee: valentina armenise 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-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title valentina armenise started work on JENKINS-32831 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32831) "None of the Update Sites passed the signature check" w/ Jenkins v1.647
Title: Message Title valentina armenise commented on JENKINS-32831 Re: "None of the Update Sites passed the signature check" w/ Jenkins v1.647 So, this happens cause now the updates site checks for updates on tool installers for all the updates centers configured in the system. Before this fix the tool installers updates were always checked against the default update center e.g. http://updates.jenkins-ci.org/updates/hudson.tasks.Maven.MavenInstaller.json.html?id=hudson.tasks.Maven.MavenInstaller=1.642.2-SNAPSHOT+%28private-02%2F08%2F2016+23%3A10+GMT-valentinaarmenise%29 Now, tools installers are checked against the update centers actually configured. If the experimental update center is the only one configured, there are no json files available for ant, maven and jdk (the tool installers). So we return the validation error, although the experimental update center has been successfully consulted for what concerns the plugins. The error message is misleading, the problem is not the signature but the update json files for tool installers not being found. I could probably catch this case and avoid returning a validation error in case there are no json files for tool installers. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-32417) User credentials not available in jobs
Title: Message Title valentina armenise closed an issue as Not A Defect Indeed after some reasoning this looked as a not-a-defect since personal credentials should not appear in a job configuration. Personal credentials, as opposite, correctly appear if the build is parametrised with a credential parameter: when building a job you can successfully select the credentials belonging to your user. Jenkins / JENKINS-32417 User credentials not available in jobs Change By: valentina armenise Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-32417) User credentials not available in jobs
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-32417 User credentials not available in jobs Issue Type: Bug Assignee: stephenconnolly Components: credentials-plugin Created: 12/Jan/16 8:19 PM Priority: Major Reporter: valentina armenise Looks like the credentials defined by doing People->User->Credentials are not available in jobs (for example when opening the drop-down menu in GIT configuration). Step to reproduce: enable security and create an `admin` user login with `admin` browse to People/Admin and `add credentials` with no domain and global scope create a job and configure the GIT section (or the ssh-agent section if you had created an ssh key) open the drop-down menu for credentials all global and folder-specific credentials will be shown but personal credentials won't be there.
[JIRA] [core] (JENKINS-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title valentina armenise started work on JENKINS-32328 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-32328 A custom update center is not consulted for Tool installer metadata Change By: valentina armenise Basically OSS Jenkins does not consult our update center at all, the whole functionality of proxying tool installers doesn't work. This issue will need to fix Jenkins Core to consult and possibly merge downloads from multiple sources and validate those sources against the correct signatures... 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-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-32328 A custom update center is not consulted for Tool installer metadata Change By: valentina armenise Basically OSS Jenkins does not consult our update center at all, the whole functionality of proxying tool installers doesn't work.This issue will need to fix Jenkins Core to consult and possibly merge downloads from multiple sources and validate those sources against the correct signatures... Then we need to fix our infra and the custom update center plugin to ensure that everything is correct.The functional impact is that users who can't access the internet will be unable to download tool installers. 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-30456) Executor.getIdleStartMilliseconds throws NPE when executor == null
Title: Message Title valentina armenise commented on JENKINS-30456 Re: Executor.getIdleStartMilliseconds throws NPE when executor == null yes, this one https://github.com/jenkinsci/jenkins/commit/67e2637a57be9b6817621dbfcdec2b2dc27afdb9. I forgot 'FIX' sry 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] [dimensionsscm-plugin] (JENKINS-26165) Workflow integration with Dimensions SCM
Title: Message Title valentina armenise assigned an issue to Unassigned Jenkins / JENKINS-26165 Workflow integration with Dimensions SCM Change By: valentina armenise Assignee: valentina armenise 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-30456) Executor.getIdleStartMilliseconds throws NPE when executor == null
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-30456 Executor.getIdleStartMilliseconds throws NPE when executor == null Change By: valentina armenise Assignee: valentina armenise 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-30456) Executor.getIdleStartMilliseconds throws NPE when executor == null
Title: Message Title valentina armenise started work on JENKINS-30456 Change By: valentina armenise Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30084) FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever.
Title: Message Title valentina armenise resolved as Fixed Jenkins / JENKINS-30084 FlyWeightTasks tied to a label will not cause node provisioning and will be blocked forever. Change By: valentina armenise 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] [credentials-plugin] (JENKINS-28864) Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-28864 Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials Change By: valentina armenise Environment: Jenkins1.609and1.580,Chromeviewwith720pxinheigh,13inchesmonitor .Credentialsplugin1.22 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-28864) Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-28864 Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials Change By: valentina armenise Environment: Jenkins1.609and1.580 ,Chromeviewwith720pxinheigh,13inchesmonitor Toreproduce:-createaNODE-gotoconfigureNODE-frominsidetheconfigurationpageofthenodeselectSSHnode-frominsidetheconfigurationpageofthenodeselectAddCredentials-fromtheCredentialsformview,selectSSH-keytypeandinsertdirectly-trytoinsertakey-itisimpossibletoscrolldowntosaveorcanceltheconfigurationTheworkaround:generateCredentialstobeusedfromtheSlavefromthemainCredentialssectionintheleftpanelofJenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-28864) Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-28864 Impossible to scroll down Credentials window when opened from inside the Node configuration Page and when selecting ssh credentials Issue Type: Bug Assignee: stephenconnolly Attachments: impossibleToScrollDownThisWindow.png Components: credentials-plugin Created: 11/Jun/15 9:19 AM Environment: Jenkins 1.609 and 1.580 Labels: Credentials Slave Priority: Minor Reporter: valentina armenise To reproduce: create a NODE
[JIRA] [workflow-plugin] (JENKINS-26121) Input step should maintain audit record
valentina armenise edited a comment on JENKINS-26121 Input step should maintain audit record The rejected action was already audited in the summary UI since it extends the CauseOfInterruption: https://github.com/jenkinsci/workflow-plugin/blob/0294f3305d665170931c781abca47aa40f46c25a/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/Rejection.java#L12 which is in the core: https://github.com/jenkinsci/jenkins/blob/68b383e0b2cdd2b1403a13a4284dc1a2d3e03e12/core/src/main/resources/jenkins/model/CauseOfInterruption/summary.groovy The rejected action was also logged by the FlowInterruptedExpection class: https://github.com/jenkinsci/workflow-plugin/blob/master/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/InputStepExecution.java#L179 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26121) Input step should maintain audit record
valentina armenise commented on JENKINS-26121 Input step should maintain audit record The rejected action was already audited since it extends the CauseOfInterruption: https://github.com/jenkinsci/workflow-plugin/blob/0294f3305d665170931c781abca47aa40f46c25a/support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/input/Rejection.java#L12 which is in the core: https://github.com/jenkinsci/jenkins/blob/68b383e0b2cdd2b1403a13a4284dc1a2d3e03e12/core/src/main/resources/jenkins/model/CauseOfInterruption/summary.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27355) Move several jobs into a folder at the same time
valentina armenise started work on JENKINS-27355 Move several jobs into a folder at the same time Change By: valentina armenise (16/Mar/15 10:45 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-27355) Move several jobs into a folder at the same time
valentina armenise assigned JENKINS-27355 to valentina armenise Move several jobs into a folder at the same time Change By: valentina armenise (16/Mar/15 10:45 AM) Assignee: FélixBelzunceArcos valentinaarmenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27308) execution aborted by input step when submitter approves it
valentina armenise
created JENKINS-27308
execution aborted by input step when submitter approves it
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
10/Mar/15 10:10 AM
Description:
if you are NOT logged in and try to approve, you are prompted with the error message which says "you need to be X to submit".
if you log in, then you are asked to "try POST" and if you click POST an empty request(request has not parameters) is SENT causing the doSubmit to abort the input step (even if you have approved instead).
@RequirePOST
public HttpResponse doSubmit(StaplerRequest request) throws IOException, ServletException, InterruptedException {
if (request.getParameter("proceed")!=null) {
User user= User.current();
doProceed(request, user);
} else {
doAbort();
}
// go back to the Run console page
return HttpResponses.redirectTo("../../console");
}
Project:
Jenkins
Labels:
workflow
input
step
Priority:
Minor
Reporter:
valentina armenise
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27308) execution aborted by input step when submitter approves it
valentina armenise assigned JENKINS-27308 to valentina armenise execution aborted by input step when submitter approves it Change By: valentina armenise (10/Mar/15 10:12 AM) Assignee: JesseGlick valentinaarmenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dimensionsscm-plugin] (JENKINS-26165) Workflow integration
valentina armenise assigned JENKINS-26165 to valentina armenise Workflow integration Change By: valentina armenise (04/Feb/15 1:14 PM) Assignee: valentinaarmenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26224) REST API for Workflow not documented in _api.jelly
valentina armenise created JENKINS-26224 REST API for Workflow not documented in _api.jelly Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 24/Dec/14 11:22 AM Description: In order to restart from a checkpoint it is possible to POST to …/restart and do this via REST API. (There is not yet an _api.jelly documenting that fact; file a bug for it.) In order to approve a workflow input step, you can POST to …/submit?proceed and do so via REST API (again not yet documented in _api.jelly, file a bug). Project: Jenkins Priority: Minor Reporter: valentina armenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26179) workflow job abort does not work if error in the syntax of the script
valentina armenise commented on JENKINS-26179 workflow job abort does not work if error in the syntax of the script any syntax error indeed (at least in my case), adding a comma in the script should make you able to reproduce it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26179) workflow job abort does not work if error in the syntax of the script
valentina armenise created JENKINS-26179 workflow job abort does not work if error in the syntax of the script Issue Type: Bug Assignee: Unassigned Components: workflow-plugin Created: 19/Dec/14 3:45 PM Description: When having an error in the groovy script and launching the job, the job would hang forever, even if a manual abortion is issued. Project: Jenkins Labels: workflow Priority: Minor Reporter: valentina armenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task-plugin] (JENKINS-25727) Occasional exit status -1 with long latencies
valentina armenise commented on JENKINS-25727 Occasional exit status -1 with long latencies tested with the plugin version 1.0. It worked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25727) parallel steps of workflow executions randomly fail
valentina armenise created JENKINS-25727 parallel steps of workflow executions randomly fail Issue Type: Bug Assignee: Unassigned Components: workflow-plugin Created: 21/Nov/14 11:01 AM Description: org.jenkinsci.plugins.workflow.cps.steps.ParallelStepException: Parallel step long running test task failed at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.checkAllDone(ParallelStep.java:126) at org.jenkinsci.plugins.workflow.cps.steps.ParallelStep$ResultHandler$Callback.onFailure(ParallelStep.java:105) at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$FailureAdapter.receive(CpsBodyExecution.java:295) at com.cloudbees.groovy.cps.impl.ThrowBlock$1.receive(ThrowBlock.java:68) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:145) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:164) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:262) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$000(CpsThreadGroup.java:70) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:174) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:172) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:47) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: hudson.AbortException: script returned exit code -1 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:205) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:159) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) ... 3 more Finished: FAILURE Environment: Jenkins ver. 1.580.1.1-beta-6 (Jenkins Enterprise by CloudBees 14.11) Project: Jenkins Labels: parallel workflow Priority: Minor Reporter: valentina armenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25632) workflow cps-global-lib workflowLibs.git issues
valentina armenise commented on JENKINS-25632 workflow cps-global-lib workflowLibs.git issues tested: All the issues are resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker] (JENKINS-23400) Docker and Jenkins on the same machine need TCP port open
valentina armenise created JENKINS-23400 Docker and Jenkins on the same machine need TCP port open Issue Type: Bug Assignee: Unassigned Components: docker Created: 11/Jun/14 10:19 AM Description: From the docker plugin wiki page https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin "If your host needs to allow connections from a jenkins instance hosted on a different machine, you will need to open up the TCP port" However if you do not open the TCP port and do not configure docker to listen for TCP connections (-H tcp://127.0.0.1:4243) it does not work. If you try to create a job and restrict the build on a docker container, it would stick waiting for an executor forever. Once I opened the TCP port, jenkins and docker started to communicate. NOTE: I am using CentOS on ec2 with jenkins and docker installed on it. Project: Jenkins Priority: Minor Reporter: valentina armenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker] (JENKINS-23401) docker plugin requires ssh key pair credentials
valentina armenise created JENKINS-23401 docker plugin requires ssh key pair credentials Issue Type: Bug Assignee: Unassigned Components: docker Created: 11/Jun/14 11:02 AM Description: I was trying to set up the docker plugin https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin to use the ready-made slave everga https://registry.hub.docker.com/u/evarga/jenkins-slave According to the documentation it should work smoothly but for me it does not work how it is. In the docker file it defines the user jenkins:jenkins. However trying to connect from Jenkins to your everga container image using username and password won't work: I needed to create an ssh key pair and modify the /etc/ssh/ssh_config file to point to the private key and /etc/ssh/sshd_config to point to the authorized_key file. Project: Jenkins Labels: ssh docker Priority: Minor Reporter: valentina armenise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
