[JIRA] (JENKINS-40261) Sauce connect process not stopping as part of Jenkins pipeline
Title: Message Title Gavin Mogan commented on JENKINS-40261 Re: Sauce connect process not stopping as part of Jenkins pipeline Hi Ashutosh Mittal Your best bet will be to contact sauce labs support, Please email supp...@saucelabs.com with a link to this ticket. I'm also going to close it as it doesn't seem like a plugin 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-40289) "Verify Template" with a custom storage account name doesn't properly verify the storage account name
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-40289
"Verify Template" with a custom storage account name doesn't properly verify the storage account name
Issue Type:
Bug
Assignee:
Claudiu Guiman
Components:
azure-vm-agents-plugin
Created:
2016/Dec/07 7:25 PM
Priority:
Minor
Reporter:
R. Tyler Croy
I manually entered a storage account name ("jenkinsvmagents_storage") and clicked "Verify Template" which worked properly and said that the template was verified. However upon the deployment of an agent, there is an ARM Deployment failure in the portal:
"error": {
"code": "AccountNameInvalid",
"message": "jenkinsvmagents_storage is not a valid storage account name. Storage account name must be between 3 and 24 characters in length and use numbers and lower-case letters only."
}
Add Comment
[JIRA] (JENKINS-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Title: Message Title
Kevin Browder commented on JENKINS-40286
Re: EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Specifically i think EncryptedSlaveAgentJnlpFile should change it from being an AccessControlled to being a SlaveComputer and the line with JnlpSlaveAgentProtocol.SLAVE_SECRET.mac(slaveName.getBytes("UTF-8")) should become byte[] jnlpMac = Util.fromHexString(it.getJnlpMac()) Thus making the SlaveComputer the one-and-only authority on the secret.
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-40288) Generated storage account name is only using "resource group" for generation of GUID
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40288 Generated storage account name is only using "resource group" for generation of GUID Issue Type: Bug Assignee: Claudiu Guiman Components: azure-vm-agents-plugin Created: 2016/Dec/07 7:22 PM Priority: Minor Reporter: R. Tyler Croy I have two subscriptions for difference Jenkins masters, when I used the same "Resource Group" in the UI, the automatically generated "Storage Account Name" created the same name on both Jenkins masters leading to an ARM template deployment failure. I think the fix would be to use a hash of the Subscription ID and the Resource Group name to generate the storage acocunt name since that must be globally unique Add Comment
[JIRA] (JENKINS-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title
Prabhu Inbarajan edited a comment on JENKINS-39695
Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Thanks [~iocanel] . That was super fast. Appreciate the quick turn around.Can you point out where the fix is ? seems like it is in the kubernetes-plugin? if it is in a branch , I would be happy to test it out. I looked at the commit histories , but couldnt locate seems like this is the fix branch one . {code} https://github.com/jenkinsci/kubernetes-plugin/commit/2be70ba43db9c00ab872e8d2c1eac7db27f084e0{code} Thanksprabhu
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-40287) Log information on template verification is incorrect
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-40287
Log information on template verification is incorrect
Issue Type:
Bug
Assignee:
Claudiu Guiman
Components:
azure-vm-agents-plugin
Created:
2016/Dec/07 7:02 PM
Priority:
Minor
Reporter:
R. Tyler Croy
INFO: Verify configuration:
subscriptionId: dff2ec18-6a8e-405c-8e45-b7df7465acf0;
clientId: ;
clientSecret: ;
serviceManagementURL: jenkinsvmagents;
resourceGroupName: jenkins-infra-ubuntu-1604;
.templateName: linux java;
labels: East US;
location: Standard_D2_v2;
virtualMachineSize: jngqppqjt1w41z2jsual3yzw;
storageAccountName: 1;
noOfParallelJobs: ;
image: Linux;
osType: Canonical;
imagePublisher: UbuntuServer;
imageOffer: 16.04-LTS;
imageSku: latest;
imageVersion: SSH;
agentLaunchMethod: sudo apt-get update -qy; sudo apt-get install -qy default-jre;
initScript: jenkinsvmagents-userpass;
credentialsId: ;
virtualNetworkName: ;
subnetName: 5;
retentionTimeInMin: ;
jvmOptions: {24};
There seems to be some misplaced fields here, for example my "labels" are not "EastUS", that's the location. And my "templateName" is not "linux docker" (those are the labels )
[JIRA] (JENKINS-28629) Fix Apache Maven 3.3 support
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-28629
Re: Fix Apache Maven 3.3 support
Looking for some workarounds I wonder: - will {{-Dmaven.ext.class.path}} work? - will modifying {{maven33- agent.jar}} or {{maven33- interceptor.jar}} or {{maven3-interceptor-commons.jar}}? - will putting it under {{lib}} instead of {{lib/ext}} work? - is there any way to load the extensions by modifying the Maven installation (e.g. it seems {{ conf/logging}} is on the classpath too)? - is there any way to load {{ EventSpy}} clients at all, even globally for the whole Jenkins? - are *build* extensions (https://maven.apache.org/guides/mini/guide-using-extensions.html) supported?
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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it
Title: Message Title Kevin Browder updated an issue Jenkins / JENKINS-40286 EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of reimplementing it Change By: Kevin Browder Summary: EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of implementing reimplementing it 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-40286) EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of implementing it
Title: Message Title
Kevin Browder created an issue
Jenkins / JENKINS-40286
EncryptedSlaveAgentJnlpFile should use SlaveComputer.getJnlpMac() instead of implementing it
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Dec/07 6:38 PM
Priority:
Minor
Reporter:
Kevin Browder
Basically getJnlpMac() does JnlpSlaveAgentProtocol.SLAVE_SECRET.mac(getName()), and EncryptedSlaveAgentJnlpFile.generateResponse does: JnlpSlaveAgentProtocol.SLAVE_SECRET.mac(slaveName.getBytes("UTF-8")) I'd like to be able to override getJnlpMac and have the key used consistently.
Add Comment
[JIRA] (JENKINS-28629) Fix Apache Maven 3.3 support
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-28629
Re: Fix Apache Maven 3.3 support
Looking for some workarounds I wonder: - will {{-Dmaven.ext.class.path}} work? - will modifying {{maven33-interceptor.jar}} or {{maven3-interceptor-commons.jar}}? - will putting it under {{lib}} instead of {{lib/ext}} work? - is there any way to load {{EventSpy}} clients at all, even globally for the whole Jenkins? - are *build* extensions (https://maven.apache.org/guides/mini/guide-using-extensions.html) supported?
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-40094) Global config.xml only contains a exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40094 Re: Global config.xml only contains a exception Code changed in jenkins User: Steven Christou Path: src/main/java/com/cloudbees/jenkins/support/api/TemporaryFileContent.java src/main/java/com/cloudbees/jenkins/support/configfiles/ConfigFileComponent.java src/main/java/com/cloudbees/jenkins/support/configfiles/OtherConfigFilesComponent.java http://jenkins-ci.org/commit/support-core-plugin/b7c4fa5ebaa24a68fadc6792fded8076d121b808 Log: Merge pull request #95 from amuniz/JENKINS-40094 [FIX JENKINS-40094] Fix global config.xml content Compare: https://github.com/jenkinsci/support-core-plugin/compare/ba3a50362652...b7c4fa5ebaa2 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-40094) Global config.xml only contains a exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40094 Re: Global config.xml only contains a exception Code changed in jenkins User: Antonio Muñiz Path: src/main/java/com/cloudbees/jenkins/support/api/TemporaryFileContent.java src/main/java/com/cloudbees/jenkins/support/configfiles/ConfigFileComponent.java src/main/java/com/cloudbees/jenkins/support/configfiles/OtherConfigFilesComponent.java http://jenkins-ci.org/commit/support-core-plugin/c8df4a8d28a68ed89f144276c2c9756537d86976 Log: JENKINS-40094 Fix global config.xml content 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-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title Ioannis Canellos commented on JENKINS-39695 Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error It was merged to master! So if you could try out the latest master that would be great! 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-28629) Fix Apache Maven 3.3 support
Title: Message Title Jakub Bochenski commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support Looking for some workarounds I wonder: will -Dmaven.ext.class.path work? are build extensions (https://maven.apache.org/guides/mini/guide-using-extensions.html) supported? 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-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title Jesse Glick commented on JENKINS-40083 Re: Blueocean fails to show pipelines due to analysis-core failure Marked lts-candidate for core since I have a proposed Stapler change which would have been prevented this error from being fatal; if accepted, I think it would be a candidate for 2.32.2. 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-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title Prabhu Inbarajan commented on JENKINS-39695 Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error Thanks Ioannis Canellos . That was super fast. Appreciate the quick turn around. Can you point out where the fix is ? seems like it is in the kubernetes-plugin? if it is in a branch , I would be happy to test it out. I looked at the commit histories , but couldnt locate the fix branch. Thanks prabhu 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-28629) Fix Apache Maven 3.3 support
Title: Message Title Jakub Bochenski commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support > It should require load these extensions in the pom resolution which is done by jenkins (and thus with its classloader which isn't really allowing dynamic updates). The extensions doesn't work even if I put them in the Maven installation under lib/ext so I don't think it's about dynamic class loading. 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-34616) Snippet generator fails on AuthorizationMatrixProperty
Title: Message Title Rudy Gevaert commented on JENKINS-34616 Re: Snippet generator fails on AuthorizationMatrixProperty I noticed that reading properties from the jenkinsfile will reset the matrix. So you can't read the properties (like parameters) from Jenkinsfile and set the matrix through the GUI. How can we set the the permissions through the Jenkinsfile. 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-28629) Fix Apache Maven 3.3 support
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-28629
Re: Fix Apache Maven 3.3 support
> It should require load these extensions in the pom resolution which is done by jenkins (and thus with its classloader which isn't really allowing dynamic updates).The extensions doesn't work even if I put them in the Maven installation under {{lib/ext}} so I don't think it's about dynamic class loading . -- static isn't working either
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-40261) Sauce connect process not stopping as part of Jenkins pipeline
Title: Message Title Ashutosh Mittal commented on JENKINS-40261 Re: Sauce connect process not stopping as part of Jenkins pipeline I think this issue is not with Sauce Connect process. It is with Protractor process not exiting properly. I ran scenario again which failed for different reasons and i can see everything exists properly. Below is the log - 3 scenarios ( 3 failed ) 82 steps ( 3 failed , 67 skipped , 12 passed ) 0m43.166s Report created successfully! [12:49:21] I/sauce - SauceLabs results available at http://saucelabs.com/jobs/d8ae19d775a14d4282c1a9b21bf162a4 [12:49:22] I/launcher - 0 instance(s) of WebDriver still running [12:49:22] I/launcher - Chrome - English failed 3 test(s) [12:49:22] I/launcher - overall: 3 failed spec(s) [12:49:22] E/launcher - Process exited with error code 1 When i am seeing the issue with Protractor not exiting is when i see below error from sauce for my scenario execution - UnsupportedOperationError: ERROR The test with session id bf581e0a69274cb9acb4920c8cddea47 has already finished, and can't receive further commands. You can learn more at https://saucelabs.com/jobs/bf581e0a69274cb9acb4920c8cddea47 For help, please check https://wiki.saucelabs.com/display/DOCS/Common+Error+Messages at WebDriverError (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/error.js:27:10) at UnsupportedOperationError (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/error.js:448:10) at parseHttpResponse (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:552:11) at /var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/http/index.js:472:11 at ManagedPromise.invokeCallback_ (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:1379:14) at TaskQueue.execute_ (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2913:14) at TaskQueue.executeNext_ (/var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2896:21) at /var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:2820:25 at /var/lib/jenkins/node-v4.4.7-linux-x64/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/promise.js:639:7 at process._tickCallback (node.js:369:9) Below is my flow - 1. Scenario 1 failed due to some error 2. Scenario 2 failed with above error 3. Scenario 3 step just timed out Any idea how can i get support for above Sauce Labs error. Add Comment
[JIRA] (JENKINS-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure Change By: Jesse Glick Component/s: blueocean-plugin Labels: blueocean lts-candidate rest robustness stapler 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-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure Change By: Jesse Glick Labels: lts-candidate rest robustness stapler 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-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure Change By: Jesse Glick Component/s: core 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-40083) Blueocean fails to show pipelines due to analysis-core failure
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40083 Blueocean fails to show pipelines due to analysis-core failure Change By: Jesse Glick Labels: lts-candidate robustness stapler 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26828 Add support for installing the NodeJS windows msi Change By: SCM/JIRA link daemon Status: In Progress Resolved 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-26828) Add support for installing the NodeJS windows msi
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26828 Re: Add support for installing the NodeJS windows msi Code changed in jenkins User: Nikolas Falco Path: src/main/java/jenkins/plugins/nodejs/tools/CPU.java src/main/java/jenkins/plugins/nodejs/tools/DetectionFailedException.java src/main/java/jenkins/plugins/nodejs/tools/InstallerPathResolver.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersion.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSVersionRange.java src/main/java/jenkins/plugins/nodejs/tools/Platform.java src/main/java/jenkins/plugins/nodejs/tools/pathresolvers/LatestInstallerPathResolver.java src/test/java/jenkins/plugins/nodejs/tools/InstallerPathResolversTest.java http://jenkins-ci.org/commit/nodejs-plugin/9ba06f17ab1272bf3afdd963dfe3d0c0fd265c8d Log: [FIXED JENKINS-26828] Add support for installing the NodeJS windows msi Remove unused old method. Update some old duplicate code from jenkins core code. Extend version with range capabilities to check which version has only an msi installer. 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-40282) JAVA_HOME from pipeline not respected in artifactory maven run
Title: Message Title Eyal Ben Moshe commented on JENKINS-40282 Re: JAVA_HOME from pipeline not respected in artifactory maven run This issue has been fixed in version 2.8.2 of the Artifactory Plugin, which was released two days ago: https://www.jfrog.com/jira/browse/HAP-848 All you need configure in your Pipeline script is: env.JAVA_HOME = 'your JAVA_HOME path' We will soon document this as part of the Artifactory Pipeline DSL documentation: https://wiki.jenkins-ci.org/display/JENKINS/Artifactory+-+Working+With+the+Pipeline+Jenkins+Plugin 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-40254) Testcase trend charts display the values for last sample
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40254 Re: Testcase trend charts display the values for last sample Code changed in jenkins User: Tõnis Pool Path: src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/TestSuiteReportDetail.java src/test/java/hudson/plugins/performance/TestSuiteReportDetailTest.java http://jenkins-ci.org/commit/performance-plugin/5832ec79a5dd63d0bd8e11e8011bb4a05b2e9d9c Log: Added test for JENKINS-40254 Had to refactor doRespondingTimeGraphPerTestCaseMode method and extracted getChartDatasetBuilderForBuilds from it to make it a bit easier to test. Also I removed some unused parameters from the constructor of TestSuiteReportDetail. 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-40254) Testcase trend charts display the values for last sample
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40254 Re: Testcase trend charts display the values for last sample Code changed in jenkins User: Andrey Pokhilko Path: src/main/java/hudson/plugins/performance/PerformanceProjectAction.java src/main/java/hudson/plugins/performance/TestSuiteReportDetail.java src/test/java/hudson/plugins/performance/TestSuiteReportDetailTest.java http://jenkins-ci.org/commit/performance-plugin/aaeb73573159ec88cf61e6b6ca91ce434ae9c11e Log: Merge pull request #76 from poolik/master Added test for JENKINS-40254 Compare: https://github.com/jenkinsci/performance-plugin/compare/22c7f1760fe6...aaeb73573159 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-28629) Fix Apache Maven 3.3 support
Title: Message Title Jakub Bochenski edited a comment on JENKINS-28629 Re: Fix Apache Maven 3.3 support > From my POV it can work only in classical freestyle jobs where we don't have the advanced integration.I don't think it's a matter of POV when the plugin claims to provide "advanced integration for Maven 2/3 projects" with no information about it's many incompatibilities.Please inform people clearly what they are getting into. This might "discourage people from using the Maven integration project type " but I think it's better than setting wrong expectations. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Paul Kordes commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Yes, PLEASE! Which plugin and what version fixes this and where do you specify the change. I have a bunch of plugins that all refer to Pipeline and I don't see this option anywhere. 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-28629) Fix Apache Maven 3.3 support
Title: Message Title Jakub Bochenski commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support > From my POV it can work only in classical freestyle jobs where we don't have the advanced integration. I don't think it's a matter of POV when the plugin claims to provide "advanced integration for Maven 2/3 projects" with no information about it's many incompatibilities. Please inform people clearly what they are getting into. This might "discourage people from using the Maven integration" but I think it's better than setting wrong expectations. 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-40285) global libraries test harness
Title: Message Title Zhelyan Panchev created an issue Jenkins / JENKINS-40285 global libraries test harness Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2016/Dec/07 5:03 PM Labels: test-harness Priority: Major Reporter: Zhelyan Panchev related to JENKINS-33925 There aren't any standards and guidelines regarding the testing of shared pipeline libraries. The expected folder structure (https://issues.jenkins-ci.org/browse/JENKINS-33925) doesn't play well with Maven or Gradle and it isn't clear whether committing and pushing anything else but the expected folder tree would break the implementation. I couldn't find any examples apart from https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.java Tried to integrate a similar approach into an example standard shared library but it's of limited use, see https://github.com/zhelyan/jenkins-pipeline-test-harness Any hints? Add
[JIRA] (JENKINS-40260) Active JNLP Sessions are maintained if the JNLP Port is disabled or changed
Title: Message Title recampbell commented on JENKINS-40260 Re: Active JNLP Sessions are maintained if the JNLP Port is disabled or changed This is working as designed. We feel like it is natural for a server to continue processing open connections until they are closed even if you disable or change the listening port. 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-40260) Active JNLP Sessions are maintained if the JNLP Port is disabled or changed
Title: Message Title recampbell closed an issue as Won't Fix Jenkins / JENKINS-40260 Active JNLP Sessions are maintained if the JNLP Port is disabled or changed Change By: recampbell Status: Open Closed Resolution: Won't Fix 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-28629) Fix Apache Maven 3.3 support
Title: Message Title Arnaud Héritier commented on JENKINS-28629 Re: Fix Apache Maven 3.3 support Maven extensions + Maven Job ? From my POV (cc @olamy) it's not possible to have this supported. It should require load these extensions in the pom resolution which is done by jenkins (and thus with its classloader which isn't really allowing dynamic updates). From my POV it can work only in classical freestyle jobs where we don't have the advanced integration. 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-40284) Fair Queuing strategy levels out to an identical weight for all jobs
Title: Message Title
David Raymond created an issue
Jenkins / JENKINS-40284
Fair Queuing strategy levels out to an identical weight for all jobs
Issue Type:
Bug
Assignee:
Magnus Sandberg
Attachments:
PrioritySorterPluginLog.txt
Components:
prioritysorter-plugin
Created:
2016/Dec/07 4:54 PM
Environment:
Jenkins 1.609. Jenkins Enterprise extensions (Folders). Priority Sorter Plugin 3.4.1.
Priority:
Minor
Reporter:
David Raymond
It seems the Fair Queuing strategy does not work, at least for us. In the global configuration, we specified the Fair Queuing stragegy, with 5 priorities, the default being 1. We created two folders, priority1 and priority2. De defined the global Job Priorities so that priority 1 is assigned to (jobs in) folder priority1, and priority 2 is assigned to (jobs in) folder priority2. In each folder, we created 4 jobs which simply wait for 30 seconds before terminating in success ("sleep 30" in shell script). We specified only one executor in order to have jobs queued. We manually start the 4 jobs in folder priority1 and immediately after, we start the 4 jobs in folder priority2, before the first jobs in folder priority1 terminates. We expect to have in the queue the jobs from the 2 folders intermixed, which we do. But if we repeat the experiment a few times, we end up in a state where jobs get queued in the order in which they are started, meaning that the Priority Sorter Plugin does not do its jos properly. I have attached part of a log produced by the plugin, in which we see that the weight assigned to jobs levels out at 0.7 and does not
[JIRA] (JENKINS-28629) Fix Apache Maven 3.3 support
Title: Message Title Jakub Bochenski reopened an issue Maven core extensions are still not working in a Maven project even with Maven Integration plugin 2.14 and apache-maven-3.4.0-20161124.073639-240, which has a fix for https://issues.apache.org/jira/browse/MNG-5889 Jenkins / JENKINS-28629 Fix Apache Maven 3.3 support Change By: Jakub Bochenski Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-30058) Support Maven Core Extensions
Title: Message Title Jakub Bochenski commented on JENKINS-30058 Re: Support Maven Core Extensions apache-maven-3.4.0-20161124.073639-240 seems to behave exactly the same as 3.3.9 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-30058) Support Maven Core Extensions
Title: Message Title
Jakub Bochenski edited a comment on JENKINS-30058
Re: Support Maven Core Extensions
@chris_mh3 I was testing it in a Maven Project, which had a {{.mvn}} folder at workspace root, by adding a "Invoke Top-Level Maven targets" step. So it also works in a Maven Project, but not in the main step.Updated results: - Invoke Top-Level Maven targets works with {{.mvn}} folder at workspace root in both Freestyle and Maven Projects - Main Maven Project build *doesn't* work with neither {{.mvn}} folder at workspace root nor a custom Maven installationI'm going to test further: - Invoke Top-Level Maven targets with a custom Maven installation and w/o {{.mvn}} folder - Maven 2 3 .4.0-SNAPSHOT build as it includes fix for https://issues.apache.org/jira/browse/MNG-5889
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-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Yang Li commented on JENKINS-38105 Re: Fail to set reference parameters with different type of drop down list will do, as long as 1.7.3 is released and available. 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-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Patrick Wolf assigned an issue to Unassigned Jenkins / JENKINS-34268 Lock multiple resources using the Pipeline lock step Change By: Patrick Wolf Assignee: CloudBees Inc. 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-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title Patrick Wolf assigned an issue to CloudBees Inc. Jenkins / JENKINS-34268 Lock multiple resources using the Pipeline lock step Change By: Patrick Wolf Assignee: Antonio Muñiz CloudBees Inc. 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-40283) Job cannot be invoked from TFS Release Management
Title: Message Title
David Staheli created an issue
Jenkins / JENKINS-40283
Job cannot be invoked from TFS Release Management
Issue Type:
Bug
Assignee:
David Staheli
Components:
tfs-plugin
Created:
2016/Dec/07 4:26 PM
Priority:
Minor
Reporter:
David Staheli
When the TFS build/release task "Jenkins Queue Job" runs in a TFS Release Management process, the environment variable "Build.Repository.Uri" is not available. This results in a crash with the following stack trace: {{java.lang.Error: java.net.URISyntaxException: Cannot parse Git URI-ish: The uri was empty or null at hudson.plugins.tfs.model.GitCodePushedEventArgs.getRepoURIish(GitCodePushedEventArgs.java:23) at hudson.plugins.tfs.CommitParameterAction.(CommitParameterAction.java:20) at hudson.plugins.tfs.model.BuildCommand.contributeTeamBuildParameterActions(BuildCommand.java:227) at hudson.plugins.tfs.model.BuildCommand.perform(BuildCommand.java:110)}}
Add Comment
[JIRA] (JENKINS-40118) Many script approvals pending after upgrading Jenkins
Title: Message Title
Philippe Nobili updated an issue
Jenkins / JENKINS-40118
Many script approvals pending after upgrading Jenkins
Dirty workaround to the issue we have found:
On the scriptApproval page, open a Console (developers tools)
In the console run:
* jQuery("button.approve").trigger("click")
A real fix would be useful though...
Change By:
Philippe Nobili
Priority:
Blocker Major
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40282) JAVA_HOME from pipeline not respected in artifactory maven run
Title: Message Title
Marc Robinson created an issue
Jenkins / JENKINS-40282
JAVA_HOME from pipeline not respected in artifactory maven run
Issue Type:
Bug
Assignee:
Eyal Ben Moshe
Components:
artifactory-plugin
Created:
2016/Dec/07 4:19 PM
Environment:
build agent: centos 7.2 default JDK: 1.7
Priority:
Major
Reporter:
Marc Robinson
The maven.run uses the system default JAVA instead of the JAVA_HOME configured in the pipeline. env.JAVA_HOME = tool name: 'JAVA8', type: 'jdk' env.PATH = "$ {env.JAVA_HOME} /bin:$ {env.PATH} " def rtMaven = Artifactory.newMavenBuild() rtMaven.tool = 'mvn' rtMaven.run pom: 'pom.xml', goals: ' -Dmaven.repo.local=.repository install javadoc:jar source:jar' The build fails with error Fatal error compiling: invalid target release: 1.8 as the java command used is the system default 1.7
Add Comment
[JIRA] (JENKINS-40265) Promotion badge icon not showing after jenkins latest update
Title: Message Title John Williams commented on JENKINS-40265 Re: Promotion badge icon not showing after jenkins latest update As well as having this issue, seeing similar issue for build.badgeActions. WARNING: Caught exception evaluating: build.badgeActions in ... Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor450.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) ... Caused by: java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection.add(Collections.java:1055) at hudson.model.Run.getBadgeActions(Run.java:483) 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-40281) No Badge shown, Exception build.badgeActions depending on KeepBuildForever
Title: Message Title Horst Hermanns created an issue Jenkins / JENKINS-40281 No Badge shown, Exception build.badgeActions depending on KeepBuildForever Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/07 4:15 PM Environment: Ubuntu 14.04 JAVA_DEBIAN_VERSION 8u111-b14-2~bpo8+1 JAVA_HOME /usr/lib/jvm/java-8-openjdk-amd64 JAVA_VERSION 8u111 JENKINS_HOME /var/jenkins_home JENKINS_VERSION 2.34 (or 2.35) LANG C.UTF-8 Plugins No plugins installed. Browsers: Chrome, Firefox Labels: exception Priority: Minor Reporter: Horst Hermanns After Update to Jenkins 2.34 and 2.35 we see several exceptions "WARNING: Caught exception evaluating: build.badgeActions" (see below) in the log file. We could easily reproduce this in a fresh new setup without additional installed plugins by: Setup a new Build-Job and activate "Discard old builds". Execute this job. Navigate to the build and activate "Keep this build forever" Access the job site. => Exception in log file (see below) => Lock icon "KeepBuild" not shown. In case of promotions the icons also not
[JIRA] (JENKINS-40280) HP Application Automation Tools Reports Incorrect Test Results that Don't Match HP ALM
Title: Message Title Matthew Gessler created an issue Jenkins / JENKINS-40280 HP Application Automation Tools Reports Incorrect Test Results that Don't Match HP ALM Issue Type: Bug Assignee: Ofir Shaked Attachments: HP-ALM-Screenshot.png Components: hp-application-automation-tools-plugin Created: 2016/Dec/07 4:06 PM Environment: Jenkins version 1.651.3.1 (CloudBees Jenkins Enterprise 16.06) HP Application Automation Tools version 4.0.1 (also tested with 4.5.0 in our TEST environment with the same results) HP ALM version 12.01 Priority: Minor Reporter: Matthew Gessler The HP Application Automation Tools plugin, specifically the com.hp.application.automation.tools.run.RunFromAlmBuilder build step, is reporting incorrect test run results that do not match with the HP ALM web client. Snippet from impacted results xml:14/11/2016 11:04:01 Running: [1]WebEZ 2.0 14/11/2016 11:04:01 Running test: [1]WebEZ 2.0, Test id: 1167, Test instance id: 456 Test: [1]WebEZ 2.0, Id: 456, Execution status: Running Test: [1]WebEZ 2.0, Id: 456, Execution status: Passed, Message: Test run passed. host: # Step: Start Test Start Test WebEZ 2.0 Step: Start Action Start Action Main [WebEZ_2.0_Mstr_Web] Step: Agency Portal, Status: Failed Agency Portal did not load. Step: End Action End Action Main [WebEZ_2.0_Mstr_Web] Step: End Test End Test WebEZ 2.0 Link:###=IRun=317516 14/11/2016 11:05:44 Test complete: [1]WebEZ 2.0, Run ID: 317516 Snippet from the job's console output: Passed : Root\Deployment_Checks\LifeQuotingEAR\TST\Checkout2[1]WebEZ 2.0 As shown in
[JIRA] (JENKINS-30058) Support Maven Core Extensions
Title: Message Title Jakub Bochenski commented on JENKINS-30058 Re: Support Maven Core Extensions @chris_mh3 I was testing it in a Maven Project, which had a .mvn folder at workspace root, by adding a "Invoke Top-Level Maven targets" step. So it also works in a Maven Project, but not in the main step. Updated results: Invoke Top-Level Maven targets works with .mvn folder at workspace root in both Freestyle and Maven Projects Main Maven Project build doesn't work with neither .mvn folder at workspace root nor a custom Maven installation I'm going to test further: Invoke Top-Level Maven targets with a custom Maven installation and w/o .mvn folder Maven 2.4.0-SNAPSHOT build as it includes fix for https://issues.apache.org/jira/browse/MNG-5889 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-24402) jsch version
Title: Message Title Emiliano m commented on JENKINS-24402 Re: jsch version All day I have at least 5 of this exceptions, it make me mad I have Jenkins 2.19.2 SSH plugin 2.4 java java version "1.7.0_101" OpenJDK Runtime Environment (IcedTea 2.6.6) (7u101-2.6.6-2~deb7u1) OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) as far I can see I found several versions of this package (jsch) in different plugins ./publish-over-ssh/WEB-INF/lib/jsch-0.1.53.jar ./database/WEB-INF/lib/jsch-0.1.44-1.jar ./gitlab-plugin/WEB-INF/lib/jsch-0.1.50.jar ./git-client/WEB-INF/lib/jsch-0.1.53.jar ./maven-plugin/WEB-INF/lib/jsch-0.1.44-1.jar ./cvs/WEB-INF/lib/jsch-0.1.50.jar ./tfs/WEB-INF/lib/jsch-0.1.44-1.jar ./ssh/WEB-INF/lib/jsch-0.1.42.jar ./ssh/WEB-INF/lib/jsch-0.1.53.jar 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-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Kamil P commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin Hi, Just to say it would be useful for me too. 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-36168) Jacoco pluging does not read values from environment varibles
Title: Message Title Arsenii Lisunov commented on JENKINS-36168 Re: Jacoco pluging does not read values from environment varibles So, here's the pull request for the functionality: https://github.com/jenkinsci/jacoco-plugin/pull/77 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-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Raul Arabaolaza updated JENKINS-23273
Jenkins / JENKINS-23273
RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Change By:
Raul Arabaolaza
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-23273) RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
Title: Message Title
Raul Arabaolaza commented on JENKINS-23273
Re: RPM post-install should not do a "chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}"
I have linked a PR to solve this, any comments, suggestions or bugs are welcome
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-14520) LDAP Plugin should support StartTLS extension
Title: Message Title Colin Silcock commented on JENKINS-14520 Re: LDAP Plugin should support StartTLS extension +1 would like this 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-30058) Support Maven Core Extensions
Title: Message Title chris_mh3 commented on JENKINS-30058 Re: Support Maven Core Extensions For me it works with Freestyle projects and a .mvn folder in the root of the job's workspace. That seems to be the maven execution directory for "Invoke Top-Level Maven targets" even if the pom is in a sub folder. But yes this issue makes maven jobs useless for me. 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-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Mark Waite edited a comment on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions [~hermescheng] can you please explain why you can't use the elastic axis plugin (as described in my [earlier reply|https://issues.jenkins-ci.org/browse/JENKINS-22494?focusedCommentId=229776=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-229776]) or the NodeLabel parameter plugin to achieve the results you want? Also, you may want to refer to my [much earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-22494?focusedCommentId=199241=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-199241] explaining why I believe the multiconfiguration projects behave this way. 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-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Mark Waite commented on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions Hermes Cheng can you please explain why you can't use the elastic axis plugin (as described in my earlier reply) or the NodeLabel parameter plugin to achieve the results you want? 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-40279) Disabling of Jenkins setup wizard not working as expected
Title: Message Title Thomas Wikström created an issue Jenkins / JENKINS-40279 Disabling of Jenkins setup wizard not working as expected Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/07 1:37 PM Environment: - Docker version 1.10.3, build 20f81dd - CentOS Linux release 7.2.1511 (Core) - Java(TM) SE Runtime Environment, 1.8.0_45-b14 - Tomcat 8.5.5 - Jenkins 2.19.1, -Djenkins.runSetupWizard=false Priority: Major Reporter: Thomas Wikström We are deploying and installing Jenkins for customers using a framework of ours, where we are packaging Tomcat, Jenkins, plugins and other maintenance tools to have a full server up and running. To be able to do this in a controlled manner for the customer, in for example an upgrade situation, we want to disable the setup wizard. https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties jenkins.install.runSetupWizard: "Set to false to skip install and upgrade wizards." We are setting the system property jenkins.install.runSetupWizard to false to skip both install and upgrade wizards. JAVA_OPTS: -Xms500m -Xmx500m -XX:MetaspaceSize=128M -XX:MaxMetaspaceSize=1024M -XX:+HeapDumpOnOutOfMemoryError -XX:+UseCompressedOops -XX:+UseG1GC -XX:MaxGCPauseMillis=400 -XX:GCPauseIntervalMillis=8000 -Djava.awt.headless=true -Dhudson.model.ParametersAction.keepUndefinedParameters=true -Djenkins.install.runSetupWizard=false -javaagent:./dist/ssl/sys-props-agent.jar=props:./dist/ssl/private/syspropsagent.properties -XX:HeapDumpPath=//logs/
[JIRA] (JENKINS-28767) Cucumber Performance Reporting Not generating project performance graph
Title: Message Title Usman Hussain commented on JENKINS-28767 Re: Cucumber Performance Reporting Not generating project performance graph does anyone know how to resolve this issue? I have tried several things but am unable to see the graphs. It looks like all the data is being accumulated from the builds, i just cannot view it because the graphs are not appearing. 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-40257) Artifactory plugin DSL generic uploader does not resolve credentialsId
Title: Message Title Tamir Hadad commented on JENKINS-40257 Re: Artifactory plugin DSL generic uploader does not resolve credentialsId Mark R , Thank you for reporting this issue. I opened an issue in Jenkins Artifactory Plug-in jira HAP-856. A fix for this issue will be included in our next release. 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-34445) Auto cleanup and sync does not clean workspace properly using custom workspace
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Hi Staffan, Thanks for looking at this again. Hopefully later changes have resolved the issue; as suggested I have closed it as Cannot Reproduce. Feel free to reopen the issue if you seen a new occurrence. Kind regards, Paul Jenkins / JENKINS-34445 Auto cleanup and sync does not clean workspace properly using custom workspace Change By: Paul Allen Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-40030) Big delay before a job is started in TestSuite
Title: Message Title Pavel Janoušek resolved as Done Merged. Jenkins / JENKINS-40030 Big delay before a job is started in TestSuite Change By: Pavel Janoušek Status: Open Resolved Resolution: Done 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-39355) API improvements based on real-world implementation and usage
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39355 Re: API improvements based on real-world implementation and usage Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/branch-api-plugin/6dc29d6791159f1b9b3ba37c9319a76fdf19ca03 Log: [JENKINS-39355 follow up] Pick up SCM API 2.0 release Also mark the on-disk configuration format as having changed since 1.11, if you upgrade to 2.0 and downgrade again you will need to run a full index / scan to fix the actions etc. 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-40276) artifactory-plugin's Docker setup requires dedicated Jenkins machines
Title: Message Title
Ali Sadik Kumlali updated an issue
Jenkins / JENKINS-40276
artifactory-plugin's Docker setup requires dedicated Jenkins machines
Change By:
Ali Sadik Kumlali
As [documentation|https://wiki.jenkins-ci.org/x/0YQABg] says,{quote}...the Jenkins Artifactory Plugin can collect build info for your Docker builds in Jenkins by setting up an internal proxy server through which the Docker daemon routes its traffic.{quote}This approach requires dedicated Jenkins machines:* Every pull and push request on the machine goes through the Artifactory Plugin's internal proxy. That is why a simple {{docker pull artifactory.mycompany.com/my-app}} command fails if Jenkins does not run. In this approach, Jenkins must be running all the time although our work is not related with the build system.* Docker daemon has to use Artifactory Plugin's internal proxy. That is why only one Jenkins can run on a machine. Even if we have more than one Jenkins servers running on different ports and proxy ports, Docker daemon must use only one of them.If Docker swarm cluster is used for containerized applications (myApp1Jenkins, myApp1, myApp1DB, myApp2Jenkins, myApp2, myApp2DB, etc. ), all swarm nodes , so the applications, becomes dependent on Jenkins Artifactory Plugin's internal proxy:* Swarm nodes are shared by Jenkins and other applications. New versions of the applications cannot be pulled when Jenkins does not run. * More than one Jenkins servers can be run on the same swarm node. But the node's Docker daemon can use only one of them as proxy. * It is required to add proxy certificates to each swarm node and repeat this for all containerized Jenkins'.
Add Comment
[JIRA] (JENKINS-40278) Emails are not sent from pipeline
Title: Message Title
Pavel Polivka updated an issue
Jenkins / JENKINS-40278
Emails are not sent from pipeline
Change By:
Pavel Polivka
We started migrating our Jenkins jobs to pipeline jobs and our build status emails stopped working.SMTP configuration is working OK I received test email and non pipeline jobs are still sending emails.If I do something like this{code}node {mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'}{code}Email not sent.I start digging into mailer plugin and figured out how emails work.I did some basic debugging out in pipeline code{code}node {def transportClass = javax.mail.Session.getDefaultInstance(java.lang.System.getProperties(), (javax.mail.Authenticator)null).getTransport(new javax.mail.internet.InternetAddress("ppoli...@xxx.com")).getClass();echo transportClass.toString();mail body: 'test', subject: 'test', to: 'ppolivka@ idc xxx .com'}{code}and figured out that email transported used in this instance is org.jvnet.mock_javamail.MockTransport{code}[Pipeline] {[Pipeline] echoclass org.jvnet.mock_javamail.MockTransport[Pipeline] mail[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}Again emails are working fine in non pipeline jobs. Configuration to use MockTransport is going from mock-javamail.jar based on classpath scanning. Is is possible that pipeline exposes this test jar to the classpath somehow?Is there any easy workaround this configuration?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40030) Big delay before a job is started in TestSuite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40030 Re: Big delay before a job is started in TestSuite Code changed in jenkins User: Ing. Pavel Janousek Path: src/test/java/com/redhat/foreman/ForemanTestRule.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/37006d86bfe43e85dfd0a4db9d7e1d2f254fcbdd Log: JENKINS-40030 Re-defined delays defined in hudson.slaves.NodeProvisioner.NodeProvisionerInvoker 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-40276) artifactory-plugin's Docker setup requires dedicated Jenkins machines
Title: Message Title
Ali Sadik Kumlali updated an issue
Jenkins / JENKINS-40276
artifactory-plugin's Docker setup requires dedicated Jenkins machines
Change By:
Ali Sadik Kumlali
As [documentation|https://wiki.jenkins-ci.org/x/0YQABg] says,{quote}...the Jenkins Artifactory Plugin can collect build info for your Docker builds in Jenkins by setting up an internal proxy server through which the Docker daemon routes its traffic.{quote}This approach requires dedicated Jenkins machines:* Every pull and push request on the machine goes through the Artifactory Plugin's internal proxy. That is why a simple {{docker pull artifactory.mycompany.com/my-app}} command fails if Jenkins does not run. In this approach, Jenkins must be running all the time although our work is not related with the build system.* Docker daemon has to use Artifactory Plugin's internal proxy. That is why only one Jenkins can run on a machine. Even if we have more than one Jenkins servers running on different ports and proxy ports, Docker daemon must use only one of them.If Docker swarm cluster is used for containerized applications (myApp1Jenkins, myApp1, myApp1DB, myApp2Jenkins, myApp2, myApp2DB, etc. ) ; , all swarm nodes becomes dependent on Jenkins Artifactory Plugin's internal proxy: * Swarm nodes are shared by Jenkins and other applications. New versions of the applications cannot be pulled when Jenkins does not run. * More than one Jenkins servers can be run on the same swarm node. But the node's Docker daemon can use only one of them as proxy.
Add Comment
[JIRA] (JENKINS-40030) Big delay before a job is started in TestSuite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40030 Re: Big delay before a job is started in TestSuite Code changed in jenkins User: Pavel Janousek Path: src/test/java/com/redhat/foreman/ForemanTestRule.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/0b562c396d349abe1b10a10cda4d3ec36f0aee1a Log: Merge pull request #34 from pjanouse/JENKINS-40030-testdelay JENKINS-40030 Re-defined delays defined in hudson.slaves.NodeProvisioner.NodeProvisionerInvoker Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/35a7199d7df7...0b562c396d34 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-27882) JAVA_HOME with forward slashes on Windows
Title: Message Title Daniel Zabel commented on JENKINS-27882 Re: JAVA_HOME with forward slashes on Windows To be able to use the automatic jdk install feature, my workaround is to fix the JAVA_HOME enviroment variable, write it to a file and import this file as properties file. batchFile code: set "JAVA_HOME=%JAVA_HOME:/=\%" echo JAVA_HOME=%JAVA_HOME% > %WORKSPACE%/FIX_JAVA_PATH 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-40030) Big delay before a job is started in TestSuite
Title: Message Title Pavel Janoušek edited a comment on JENKINS-40030 Re: Big delay before a job is started in TestSuite [PR|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/ 33 34 ] sent. 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-40030) Big delay before a job is started in TestSuite
Title: Message Title
Pavel Janoušek edited a comment on JENKINS-40030
Re: Big delay before a job is started in TestSuite
{ [ PR|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/33] sent.
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-40030) Big delay before a job is started in TestSuite
Title: Message Title
Pavel Janoušek commented on JENKINS-40030
Re: Big delay before a job is started in TestSuite
{PR|https://github.com/jenkinsci/foreman-node-sharing-plugin/pull/33] sent.
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-39881) waitUntil block never gets called back
Title: Message Title sébastien glon commented on JENKINS-39881 Re: waitUntil block never gets called back I have the same error on Jenkins 2.34 and Pipeline basic step 2.3 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-39355) API improvements based on real-world implementation and usage
Title: Message Title Stephen Connolly updated JENKINS-39355 Jenkins / JENKINS-39355 API improvements based on real-world implementation and usage Change By: Stephen Connolly Status: In Review Resolved 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-39213) Add ability for computed folders to control the views in the folder
Title: Message Title Stephen Connolly resolved as Fixed Jenkins / JENKINS-39213 Add ability for computed folders to control the views in the folder Change By: Stephen Connolly Status: In Progress Resolved 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-32407) Crash on Chrome + Firefox
Title: Message Title Michael Göhler edited a comment on JENKINS-32407 Re: Crash on Chrome + Firefox Seams Seems to be fixed with JENKINS-39856 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-40138) SCMHead.getActions() must die
Title: Message Title Stephen Connolly updated JENKINS-40138 Jenkins / JENKINS-40138 SCMHead.getActions() must die Change By: Stephen Connolly Status: In Review Resolved 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-32407) Crash on Chrome + Firefox
Title: Message Title Michael Göhler commented on JENKINS-32407 Re: Crash on Chrome + Firefox Seams to be fixed with JENKINS-39856 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-40278) Emails are not sent from pipeline
Title: Message Title
Pavel Polivka updated an issue
Jenkins / JENKINS-40278
Emails are not sent from pipeline
Change By:
Pavel Polivka
We started migrating our Jenkins jobs to pipeline jobs and our build status emails stopped working.SMTP configuration is working OK I received test email and non pipeline jobs are still sending emails.If I do something like this{code}node {mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'}{code}Email not sent.I start digging into mailer plugin and figured out how emails work.I did some basic debugging out in pipeline code{code}node {def transportClass = javax.mail.Session.getDefaultInstance(java.lang.System.getProperties(), (javax.mail.Authenticator)null).getTransport(new javax.mail.internet.InternetAddress("ppolivka@ idc xxx .com")).getClass();echo transportClass.toString();mail body: 'test', subject: 'test', to: 'ppoli...@idc.com'}{code}and figured out that email transported used in this instance is org.jvnet.mock_javamail.MockTransport{code}[Pipeline] {[Pipeline] echoclass org.jvnet.mock_javamail.MockTransport[Pipeline] mail[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}Again emails are working fine in non pipeline jobs. Configuration to use MockTransport is going from mock-javamail.jar based on classpath scanning. Is is possible that pipeline exposes this test jar to the classpath somehow?Is there any easy workaround this configuration?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40278) Emails are not sent from pipeline
Title: Message Title
Pavel Polivka created an issue
Jenkins / JENKINS-40278
Emails are not sent from pipeline
Issue Type:
Bug
Assignee:
Unassigned
Components:
mailer-plugin, pipeline
Created:
2016/Dec/07 12:39 PM
Environment:
Jenkins: 2.7.2 Pipeline plugin 2.2 Mailer plugin 1.17
Priority:
Major
Reporter:
Pavel Polivka
We started migrating our Jenkins jobs to pipeline jobs and our build status emails stopped working. SMTP configuration is working OK I received test email and non pipeline jobs are still sending emails. If I do something like this
node {
mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'
}
Emails is still not sent. I start digging into mailer plugin and figured out how emails work. I did some basic debugging out in pipeline code
node {
def transportClass = javax.mail.Session.getDefaultInstance(java.lang.System.getProperties(), (javax.mail.Authenticator)null).getTransport(new javax.mail.internet.InternetAddress("ppoli...@idc.com")).getClass();
echo transportClass.toString();
mail body: 'test', subject: 'test', to: 'ppoli...@idc.com'
}
and figured out that email transported used in this instance is
[JIRA] (JENKINS-40278) Emails are not sent from pipeline
Title: Message Title
Pavel Polivka updated an issue
Jenkins / JENKINS-40278
Emails are not sent from pipeline
Change By:
Pavel Polivka
We started migrating our Jenkins jobs to pipeline jobs and our build status emails stopped working.SMTP configuration is working OK I received test email and non pipeline jobs are still sending emails.If I do something like this{code}node {mail body: 'test', subject: 'test', to: 'ppoli...@xxx.com'}{code} Emails is still Email not sent.I start digging into mailer plugin and figured out how emails work.I did some basic debugging out in pipeline code{code}node {def transportClass = javax.mail.Session.getDefaultInstance(java.lang.System.getProperties(), (javax.mail.Authenticator)null).getTransport(new javax.mail.internet.InternetAddress("ppoli...@idc.com")).getClass();echo transportClass.toString();mail body: 'test', subject: 'test', to: 'ppoli...@idc.com'}{code}and figured out that email transported used in this instance is org.jvnet.mock_javamail.MockTransport{code}[Pipeline] {[Pipeline] echoclass org.jvnet.mock_javamail.MockTransport[Pipeline] mail[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}Again emails are working fine in non pipeline jobs. Configuration to use MockTransport is going from mock-javamail.jar based on classpath scanning. Is is possible that pipeline exposes this test jar to the classpath somehow?Is there any easy workaround this configuration?
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40276) artifactory-plugin's Docker setup requires dedicated Jenkins machines
Title: Message Title Ali Sadik Kumlali created an issue Jenkins / JENKINS-40276 artifactory-plugin's Docker setup requires dedicated Jenkins machines Issue Type: Improvement Assignee: Eyal Ben Moshe Components: artifactory-plugin, docker Created: 2016/Dec/07 12:35 PM Environment: RHEL 7.2, Docker version 1.12.3, Jenkins 2.19.3(running in Docker, no agents, only master), Artifactory 4.14.2, Artifactory Plugin 2.8.2 Priority: Major Reporter: Ali Sadik Kumlali As documentation says, ...the Jenkins Artifactory Plugin can collect build info for your Docker builds in Jenkins by setting up an internal proxy server through which the Docker daemon routes its traffic. This approach requires dedicated Jenkins machines: Every pull and push request on the machine goes through the Artifactory Plugin's internal proxy. That is why a simple docker pull artifactory.mycompany.com/my-app command fails if Jenkins does not run. In this approach, Jenkins must be running all the time although our work is not related with the build system. Docker daemon has to use Artifactory Plugin's internal proxy. That is why only one Jenkins can run on a machine. Even if we have more than one Jenkins servers running on different ports and proxy ports, Docker daemon must use only one of them. If Docker swarm cluster is used for containerized applications (myApp1Jenkins, myApp1, myApp1DB,
[JIRA] (JENKINS-40277) Allow Jenkins to see k8s nodes as available executor
Title: Message Title
Jeroen Wolff created an issue
Jenkins / JENKINS-40277
Allow Jenkins to see k8s nodes as available executor
Issue Type:
Improvement
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2016/Dec/07 12:35 PM
Priority:
Minor
Reporter:
Jeroen Wolff
When i have 5 executors available and in my script i make use of a maven node like: node('maven') { [code] } When i fire 5 build jobs, they are not build in parallel. It looks like Jenkins is thinking that there is only 1 node available all the time. Instead with kube you could start multiple nodes at the same time. I would like to see that Jenkins is always starting to use a node one kube instead of only one at the time.
Add Comment
[JIRA] (JENKINS-38899) ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection
Title: Message Title Pavel Janoušek updated JENKINS-38899 Merged. Jenkins / JENKINS-38899 ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection Change By: Pavel Janoušek Status: In Review Resolved Resolution: Done 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-40119) no updates any more after update to jenkins 2.7.4
Title: Message Title Uwe Wenglewski closed an issue as Fixed Two steps were necessary: 1. add in /etc/nginx/nginx.conf the following: client_max_body_size 100m; systemctl restart nginx Now the update center will update again! 2. Update artifactory plugin: I choosed Update Artifactory Plugin 2.8.2 and after installation and restart jenkins service the Artifactory Plugin does respect the http proxy settings. The connection test to the artifactory worked again! Jenkins / JENKINS-40119 no updates any more after update to jenkins 2.7.4 Change By: Uwe Wenglewski Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33765) Configure S3 at folder level
Title: Message Title Stephen Connolly commented on JENKINS-33765 Re: Configure S3 at folder level https://issues.jenkins-ci.org/browse/JENKINS-40275 is what would be needed 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-40275) Support hierarchical configuration attached to ItemGroups
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-40275 Support hierarchical configuration attached to ItemGroups Issue Type: New Feature Assignee: Unassigned Components: cloudbees-folder-plugin, core Created: 2016/Dec/07 12:10 PM Priority: Minor Reporter: Stephen Connolly The original Jenkins configuration model did not have an implementation ItemGroup for TopLevelItem instances other than the root node. When the folders plugin was released, however, this changed... the configuration model of core did not. There are lots of configuration options in the Jenkins global configuration where it would make sense to allow a hierarchical configuration model. The credentials plugin had such a critical need for this that it contains its own home-grown implementation of a hierarchical credentials store (if this feature is implemented, then the credentials plugin could be refactored to use this for the ItemGroup based stores - more correctly the folders plugin could be refactored to store the folder scoped credentials in this ItemGroup configuration stores) Other configuration elements where it makes sense to have hierarchical configuration: Tool installers - or at least Tool Installer mapping so that teams in one folder can call their JDK's jdk8 and jdk9 with java8 and java9 pointing to pure JREs while teams in another folder can call the exact same JDKs java8 and java9 respectively Maven / Ivy / Ant default project configurations Any of the server list types, e.g. SonarQube servers, S3 configuration, etc Any plugin that has default configuration for it's behaviour so that teams do not need global admin permissions to tweak the defaults within one folder...
[JIRA] (JENKINS-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Hermes Cheng updated an issue Jenkins / JENKINS-22494 Multiconfiguration project does not respect label restrictions Change By: Hermes Cheng Priority: Major Critical 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-22494) Multiconfiguration project does not respect label restrictions
Title: Message Title Hermes Cheng commented on JENKINS-22494 Re: Multiconfiguration project does not respect label restrictions Multiconfiguration project is a default feature of Jenkins v2.0, and I believe this feature is very important for a smooth CI process. 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-38899) ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38899 Re: ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection Code changed in jenkins User: Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java src/test/java/com/redhat/foreman/ForemanSharedNodeCloudTest.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/35a7199d7df763eb4a0fc454a41d2c670ec65bf1 Log: Merge pull request #29 from pjanouse/JENKINS-38899-Provision-interate-over-collection JENKINS-38899 ForemanSharedNodeCloud.provision(Label) iterates over the whole collection Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/bf324662fdb3...35a7199d7df7 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-38899) ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38899 Re: ForemanSharedNodeCloud.provision(Label) has to iterate over the whole collection Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java src/test/java/com/redhat/foreman/ForemanSharedNodeCloudTest.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/42228b67fb8fb07cee285e07d5d052362c7596ea Log: JENKINS-38899 ForemanSharedNodeCloud.provision(Label) iterates over the whole collection 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-30167) Improve current behavior of description concatenation
Title: Message Title Pavel Janoušek commented on JENKINS-30167 Re: Improve current behavior of description concatenation Filipe Silva I'm not a maintainer of this plug-in you should ask 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-30167) Improve current behavior of description concatenation
Title: Message Title Filipe Silva commented on JENKINS-30167 Re: Improve current behavior of description concatenation Please release this. I really need it urgently! 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-30058) Support Maven Core Extensions
Title: Message Title Jakub Bochenski commented on JENKINS-30058 Re: Support Maven Core Extensions The only way to make extensions work is to use the "Invoke Top-Level Maven targets" step from Freestyle project and a custom Maven installation. It will the pick-up extensions from lib/ext. It doesn't work in a Maven Project main step even with a custom Maven installation. It doesn't work for extensions declared in .mvn folder. 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-30058) Support Maven Core Extensions
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-30058 Support Maven Core Extensions Change By: Jakub Bochenski Priority: Critical Blocker 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-35336) SSH agent not starting because file not created
Title: Message Title kutzi commented on JENKINS-35336 Re: SSH agent not starting because file not created We get occasionally the same problem on our build nodes. Would be good if the error message could have some more details - e.g. what's actually the path of the file trying to be created. BTW: in our case it was an issue of no more inodes available on the node, so we just had to delete some workspaces on it. 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-36793) Need Support to queue when node is not a direct input parameter
Title: Message Title Dominik Bartholdi commented on JENKINS-36793 Re: Need Support to queue when node is not a direct input parameter no sorry, so far I had not the time to look into this any further... 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-39695) Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error
Title: Message Title Ioannis Canellos commented on JENKINS-39695 Re: Shell stop in a pipeline job: Java.net.UnknownHostException: kubernetes.default.svc: unknown error It's seems that its already 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.
