[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Jie Shen commented on JENKINS-59752 Re: Add support for ephemeral OS disk This should be useful in some cases. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6291.1570852800149%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-59752 Add support for ephemeral OS disk Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202475.1570808392000.6289.1570852740206%40Atlassian.JIRA.
[JIRA] (JENKINS-55943) Add possibility to select osDisk SKU
Title: Message Title Jie Shen commented on JENKINS-55943 Re: Add possibility to select osDisk SKU The "storageAccountType" is changed dynamically at https://github.com/jenkinsci/azure-vm-agents-plugin/blob/4a0960ef24fb9724968abb832d9b58b4380b0e86/src/main/java/com/microsoft/azure/vmagent/AzureVMManagementServiceDelegate.java#L517 . But it seems that not all the templates' OSdisk item has the "managedDisk" property. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197352.1549276857000.6284.1570852560315%40Atlassian.JIRA.
[JIRA] (JENKINS-55022) (windows10+jenkins 2.153) can build project with warnings, but (centos 7+jenkins 2.153) build failed
Title: Message Title p young updated an issue Jenkins / JENKINS-55022 (windows10+jenkins 2.153) can build project with warnings, but (centos 7+jenkins 2.153) build failed Change By: p young Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196035.1543912691000.6282.1570845300197%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title Jie Shen commented on JENKINS-59748 Re: Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded Thanks for reporting this issue. Could you please check the Jenkins log to find if there is more detailed logs in it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202471.1570798596000.6280.1570844820096%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-59748 Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202471.1570798596000.6278.1570844760271%40Atlassian.JIRA.
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title
Eric Engstrom updated an issue
Jenkins / JENKINS-59758
hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Change By:
Eric Engstrom
I believe I've found a bug in the way that {{hudson.model.UpdateSite.Plugin}} collects the warnings that may exist for a given plugin, as can be seen in this Groovy code sample:{code:title=Groovy Example}import jenkins.model.*import jenkins.security.*import hudson.security.*import static groovy.json.JsonOutput.*def instance = Jenkins.getInstance()def manager = instance.getPluginManager()def center = instance.getUpdateCenter()manager.doCheckUpdatesServer()updates = center.getUpdates(). each {}. collectEntries { ([ (it.getInstalled().getShortName()) :[ 'class': it.getClass().toString(), 'version': it.version, 'hasWarnings': it.hasWarnings(),] ])}println prettyPrint(toJson(updates)){code}When when run against my current setup, including at least one plugin with updates that ALSO has warnings, yields _(pruned slightly, eliding some irrelevant plugins)_:{code:title=output}{"git-client": {"class": "class hudson.model.UpdateSite$Plugin","version": "2.9.0","hasWarnings": false},"script-security": {"class": "class hudson.model.UpdateSite$Plugin","version": "1.66","hasWarnings": false}}{code}However, perusing the code of {{hudson.model.UpdateSite}}, I manually walked the (applicable) warnings a different way:{code:title=Groovy Example (continued)}def wc = ExtensionList.lookupSingleton(UpdateSiteWarningsConfiguration.class)warnings = wc.getApplicableWarnings().collectEntries { ([ (it.component): [ 'class': it.getClass().toString(), 'message': (it.message), 'version' : (wc.getPlugin(it).getVersion()), 'ignored': (wc.isIgnored(it)), 'isPluginWarning' : (it.isPluginWarning(it.component)), 'isRelevant': (it.isRelevant()), 'isRelevantToVersion' : (it.isRelevantToVersion(wc.getPlugin(it).getVersionNumber())),] ])}println prettyPrint(toJson(warnings)){code}Which yields (unpruned, as there is only one, currently):{code:title=output (continued)}{"script-security": {"class": "class hudson.model.UpdateSite$Warning","message": "Sandbox bypass vulnerability","version": "1.64","ignored": false,"isPluginWarning": true,"isRelevant": true,"isRelevantToVersion": true}}{code}It seems to me the failure lies on [line 1265 of UpdateSite.java|https://github.com/jenkinsci/jenkins/blob/24d0cf90ab82f89aadd2b54c84c7fcab093b0d37/core/src/main/java/hudson/model/UpdateSite.java#L1265], specifically:{code:title=UpdateSite.java, line 1265:}if (!warning.isRelevantToVersion(new VersionNumber(this.version))) {{code}and
[JIRA] (JENKINS-59758) hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Title: Message Title
Eric Engstrom created an issue
Jenkins / JENKINS-59758
hudson.model.UpdateSite.Plugin:getWarnings() using incorrect plugin version, resulting in no warnings found
Issue Type:
Bug
Assignee:
Unassigned
Components:
core, update-sites-manager-plugin
Created:
2019-10-11 22:37
Environment:
Jenkins 2.199 (and LTS / 2.190.1)
Labels:
plugins jenkins update-center
Priority:
Major
Reporter:
Eric Engstrom
I believe I've found a bug in the way that hudson.model.UpdateSite.Plugin collects the warnings that may exist for a given plugin, as can be seen in this Groovy code sample:
Groovy Example
import jenkins.model.*
import jenkins.security.*
import hudson.security.*
import static groovy.json.JsonOutput.*
def instance = Jenkins.getInstance()
def manager = instance.getPluginManager()
def center = instance.getUpdateCenter()
manager.doCheckUpdatesServer()
updates = center.getUpdates().each {
}.collectEntries {
([ (it.getInstalled().getShortName()) :
[
'class': it.getClass().toString(),
'version': it.version,
'hasWarnings': it.hasWarnings(),
]
])
}
println prettyPrint(toJson(updates))
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier commented on JENKINS-59697 Re: Add an Apply button and enhance the UX https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6273.1570832040057%40Atlassian.JIRA.
[JIRA] (JENKINS-58969) Input step: BlueOcean UI does not recognize node, results in "This stage has no steps"
Title: Message Title Dan Alvizu commented on JENKINS-58969 Re: Input step: BlueOcean UI does not recognize node, results in "This stage has no steps" I'm seeing this with the kubernetes plugin, where our nodes are ephemeral Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201316.1565971722000.6272.1570831680280%40Atlassian.JIRA.
[JIRA] (JENKINS-58969) Input step: BlueOcean UI does not recognize node, results in "This stage has no steps"
Title: Message Title
Dan Alvizu updated an issue
Jenkins / JENKINS-58969
Input step: BlueOcean UI does not recognize node, results in "This stage has no steps"
Change By:
Dan Alvizu
When waiting for user input (via the Input step), the BlueOcean UI does not correctly show that step, and thus the user input buttons are missing. It seems that the BlueOcean UI cannot pick up on the third node/stage in the job. The node ID according to the JSON output (GET /blue/rest/organizations/jenkins/pipelines/Continuous%20Deployment/runs/144/nodes/) is 72, but BlueOcean won't let me click on that node. Perhaps it is not making the request to that node ID (or an incorrect one) and thus cannot get the data for the step. Attached is a screenshot and a .har archive of the network requests. !Captura de pantalla 2019-08-16 a la(s) 9.03.34 a. m..png|width=691,height=565! {code:java} {{[ \ {"_class":"io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl","_links":{"self": {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/21/"} ,"actions": \ {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/21/actions/"},"steps": \ {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/21/steps/"}},"actions":[],"displayDescription":null,"displayName":"Notify Slack","durationInMillis":216,"id":"21","input":null,"result":"SUCCESS","startTime":"2019-08-16T15:51:05.153+","state":"FINISHED","type":"STAGE","causeOfBlockage":null,"edges":[\{"_class":"io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl","id":"38","type":"STAGE"}],"firstParent":null,"restartable":true}, \ {"_class":"io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl","_links":{"self": {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/38/"} ,"actions": \ {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/38/actions/"},"steps": \ {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/38/steps/"}},"actions":[],"displayDescription":null,"displayName":"Cut release branch","durationInMillis":3971,"id":"38","input":null,"result":"SUCCESS","startTime":"2019-08-16T15:51:05.404+","state":"FINISHED","type":"STAGE","causeOfBlockage":null,"edges":[\{"_class":"io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl","id":"72","type":"STAGE"}],"firstParent":"21","restartable":true}, \ {"_class":"io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl","_links":{"self": {"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/Continuous Deployment/runs/144/nodes/72/"} ,"actions": \
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier started work on JENKINS-59697 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6267.1570831560333%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated JENKINS-59697 Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6268.1570831560351%40Atlassian.JIRA.
[JIRA] (JENKINS-45852) Bitbucket project icons not displaying properly since 2.2.2.
Title: Message Title Michael Lasevich commented on JENKINS-45852 Re: Bitbucket project icons not displaying properly since 2.2.2. BUMP Hard to believe it takes more than two years to address a basic bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184064.1501247779000.6266.1570831560317%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Jesse Glick commented on JENKINS-59668 Re: Run wrapper process in the background fails with the latest changes Using sh 'env | sort' is obviously not going to help diagnosis if the problem is a broken sh step! You can try echo "PATH set to $PATH" which is not quite as convincing but may pinpoint your issue: either something in your build or Jenkins node configuration corrupting $PATH, or an accidental usage of sh inside a Windows node (without a properly configured Cygwin environment or whatever). Can probably be closed as this looks like a user error, not related to recent changes except to the extent that for technical reasons we had to turn off LAUNCH_DIAGNOSTICS by default to avoid wasting system resources in the normal case that $PATH is OK. Maybe it could be automatically enabled for the rest of the JVM session upon encountering one of these errors, or something like that. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-59757) Discovered project-repositories should have Run button
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59757 Discovered project-repositories should have Run button Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin, branch-api-plugin, github-branch-source-plugin Created: 2019-10-11 21:38 Priority: Minor Reporter: Josh Soref If we go to: /jenkins/blue/organizations/jenkins/standalone-project/activity There are two buttons: [ Run ] [ Disable ] above the Status/Run/Commit/Message/Duration/Completed/(replay) table If we go to /jenkins/blue/organizations/jenkins/GitHub%2Frepo/activity The Run & Disable buttons are missing. Disable being missing is understandable as the repository was discovered by project discovery. Run being missing is unfortunate. /jenkins/job/GitHub/job/repo/job/master/ has a [ Build ] or [ Build with parameters ] button (depending on whether or not the job supports parameters) – And for the standalone-project the Run button works as Build or Build with parameters as applicable. Add Comment
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Victor Martinez commented on JENKINS-59668
Re: Run wrapper process in the background fails with the latest changes
Much appreciated for the debugging and answers. Although I've found the current pipeline might be a bit too complicated, but that's likely another story. I was able to narrow down the issue a bit more based on your feedback, for some reason the PATH environment variable get corrupted, so the below snippet produces
def forLinux() (
return {
node('linux'){
try {
sh label: 'Pre-Environment', script: 'env | sort' // only for debugging purposes
deleteDir()
unstash 'source'
retry(2){
sleep 23
sh(label: "Run Tests"...
}
sh label: 'Post-Environment', script: 'env | sort' // only for debugging purposes
} catch(e){
error(e.toString())
} finally {
sh label: 'Environment', script: 'env | sort' // only for debugging purposes
...
}
}
}
}
I just managed to add the withEnv to ensure the PATH is defined, although not sure how it gets corrupted though, as that particular behaviour does not happen when the above snippet in a parallel step without any other references but calls to the forLinux For instance, the below snippet shows how the parallel is configured for the issue with the nohup and a similar one which does not fail with the nohup.
stage('FailedWithNoHup') {
environment {
HOME = "${env.WORKSPACE}"
}
steps {
def parallelTasks = [:]
parallelTasks["Linux-1"] = forLinux(version: 1)
parallelTasks["Linux-2"] = forLinux(version: 2)
parallelTasks["Windows-1"] = forWindows(version: 1)
}
}
stage('Works') {
environment {
HOME = "${env.WORKSPACE}"
}
steps {
def parallelTasks = [:]
parallelTasks["Linux-1"] = forLinux(version: 1)
parallelTasks["Linux-2"] = forLinux(version: 2)
parallel(parallelTasks)
}
}
def forLinux(Map params = [:]){
def version = params?.version
return {
node('linux'){
try {
sh label: 'Pre-Environment', script: 'env | sort' // only for debugging purposes
deleteDir()
unstash 'source'
retry(2){
sleep 23
sh(label: "Run Tests"...
}
sh label: 'Post-Environment', script: 'env | sort' // only for debugging purposes
} catch(e){
error(e.toString())
} finally {
sh label: 'Environment', script: 'env | sort' // only for debugging purposes
...
}
}
}
}
def forWindows(Map params = [:]){
return {
node('windows'){
...
}
}
}
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Attachment: image-2019-10-11-22-12-00-367.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6254.1570828380648%40Atlassian.JIRA.
[JIRA] (JENKINS-59756) NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-59756
NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt
Change By:
Karl Shultz
*Summary*Branch names with [reserved URL characters|https://www.w3.org/Addressing/URL/4_URI_Recommentations.html] in them, such as {{/}}, surface a bug in {{NameEncoder.decode()}}. Other characters can surface this bug too, such as {{.}}, {{..}}, and an empty space. It appears to only affect jobs which were migrated, back in the timeframe of [JENKINS-41124|https://issues.jenkins-ci.org/browse/JENKINS-41124]. This hasn't been recreated on a "real" environment with post-41124 projects. *Details*With multibranch pipelines that have branch names including these reserved URL characters, such as the {{/}} in {{feature/branch-name}}, this method gets called as part of the creation of a file called {{name-utf8.txt}}, which defines the computed folders for the branch jobs containing these special characters. The bug causes this file to essentially double in size.The issue lies [here|https://github.com/jenkinsci/branch-api-plugin/blob/847348f6c741f9ac350c138d6267e41a081b89e4/src/main/java/jenkins/branch/NameEncoder.java#L209-L240].
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier In addition of the Save button (like many others plugins) to be able to apply the configuration change without leaving the configuration screen .Improving the validation logic to make the setup easier Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6249.1570827780072%40Atlassian.JIRA.
[JIRA] (JENKINS-59697) Add an Apply button and enhance the UX
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59697 Add an Apply button and enhance the UX Change By: Arnaud Héritier Summary: Add an Apply button and enhance the UX Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202396.1570523376000.6248.1570827720062%40Atlassian.JIRA.
[JIRA] (JENKINS-59756) NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-59756 NameEncoder.decode can introduce duplicate characters per build to name-utf8.txt Issue Type: Bug Assignee: Unassigned Components: branch-api-plugin Created: 2019-10-11 20:52 Priority: Critical Reporter: Karl Shultz Summary Branch names with reserved URL characters in them, such as /, surface a bug in NameEncoder.decode(). Other characters can surface this bug too, such as ., .., and an empty space. Details With multibranch pipelines that have branch names including these reserved URL characters, such as the / in feature/branch-name, this method gets called as part of the creation of a file called name-utf8.txt, which defines the computed folders for the branch jobs containing these special characters. The bug causes this file to essentially double in size. The issue lies here. Add Comment
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Attachment: image-2019-10-11-21-48-35-471.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6246.1570826940242%40Atlassian.JIRA.
[JIRA] (JENKINS-59755) Perforce Stream support in Job-DSL-plugin
Title: Message Title AJ Sharpe updated JENKINS-59755 https://github.com/jenkinsci/job-dsl-plugin/pull/1206 Jenkins / JENKINS-59755 Perforce Stream support in Job-DSL-plugin Change By: AJ Sharpe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59755) Perforce Stream support in Job-DSL-plugin
Title: Message Title AJ Sharpe created an issue Jenkins / JENKINS-59755 Perforce Stream support in Job-DSL-plugin Issue Type: New Feature Assignee: AJ Sharpe Components: job-dsl-plugin Created: 2019-10-11 20:40 Environment: jenkins:lts in docker with plugins: jcasc, job-dsl-plugin, and p4 Priority: Minor Reporter: AJ Sharpe Add support for specifying a stream in Job DSL definition. This has been added to the perforce (p4) plugin, so you can specify a stream instead of a workspace mapping, but job-dsl-plugin currently has no method of specifying any workspace spec other than manually defined workspace mappings. Add Comment
[JIRA] (JENKINS-9244) Support Upcoming Peforce Stream Features
Title: Message Title AJ Sharpe updated JENKINS-9244 Jenkins / JENKINS-9244 Support Upcoming Peforce Stream Features Change By: AJ Sharpe Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139405.1301929563000.6232.1570826220697%40Atlassian.JIRA.
[JIRA] (JENKINS-9244) Support Upcoming Peforce Stream Features
Title: Message Title AJ Sharpe edited a comment on JENKINS-9244 Re: Support Upcoming Peforce Stream Features This functionality was added to the perforce plugin , and at some point; this Jira ticket hasn't been viewed since 2012 . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139405.1301929563000.6240.1570826220912%40Atlassian.JIRA.
[JIRA] (JENKINS-9244) Support Upcoming Peforce Stream Features
Title: Message Title AJ Sharpe updated JENKINS-9244 This was added to the perforce plugin, and hasn't been viewed since 2012 Jenkins / JENKINS-9244 Support Upcoming Peforce Stream Features Change By: AJ Sharpe Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web
[JIRA] (JENKINS-44616) groovy increment does not work
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-44616 groovy increment does not work Change By: Jesse Glick Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182471.1496315497000.6211.1570825500301%40Atlassian.JIRA.
[JIRA] (JENKINS-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title Jesse Glick resolved as Fixed Ljubisa Punosevac it is hard to know offhand what your issue is. If you are consistently missing timestamps, it would be better to file a fresh bug with complete, self-contained steps to reproduce your problem from scratch, and link it to this one. Jenkins / JENKINS-54081 Timestamps missing for agent-based steps in Pipeline Job 2.26 Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Jesse Glick commented on JENKINS-59668
Re: Run wrapper process in the background fails with the latest changes
Sometimes this results from script mistakes like
withEnv(["PATH=${tool 'whatever'}/bin"]) {
sh 'whatever'
}
when what was meant was
withEnv(["PATH+WHATEVER=${tool 'whatever'}/bin"]) {
sh 'whatever'
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6174.1570823940397%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Attachment: image-2019-10-11-20-54-36-634.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6170.1570823700225%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Attachment: image-2019-10-11-20-41-24-095.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6166.1570822920288%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Attachment: image-2019-10-11-15-20-00-163.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6156.1570821660182%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun commented on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) Going back to the issue where in Configure System page, I could not add a GitHub Server Config. I just noticed that when I try to click the GitHub Server Config button to add a new GitHub Server Config, the Console in developer tools is showing a 500 error. This occurs in prototype.js on line 1585 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6158.1570821660359%40Atlassian.JIRA.
[JIRA] (JENKINS-59754) Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines
Title: Message Title Joshua Yates created an issue Jenkins / JENKINS-59754 Jenkins Micro Focus Application Automation Tools Plugin losing connection with Octane after running pipelines Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-10-11 19:11 Labels: MicroFocusApplicationAutomationTools Priority: Major Reporter: Joshua Yates We have configured Octane / Jenkins integration by installing ALM Octane plugin in Jenkins. The connection works for a day and then drops. Jenkins is setup as a CI server in Octane, we have found that if we run a pipeline everyday with a Jenkins build that the connection between Jenkins and Octane drops and the Jenkins plugin for Octane cannot get a new connection to the Octane server. A few things we have noticed: The issue only happens if we run a build once a day, if we have a pipeline running every hour the issue does not seem to happen. We believe that the plugin may not be managing the sessions (cookies/tokens) with Octane correctly and that by running a build every hour might be keeping the session "alive" When this happens our only fix seems to be restarting the Jenkins server which we think might make the plugin renegotiate the session with Octane We tried the newest plugin 5.9 to see if it might resolve the issue but it did not
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Jesse Glick commented on JENKINS-59668 Re: Run wrapper process in the background fails with the latest changes I presume the issue is trying to run sh on Windows and it not existing. BTW the full Pipeline script does not seem to make much sense: you are grabbing a Linux node, then holding an executor lock while also grabbing a Windows node? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6150.1570821000219%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun edited a comment on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) Looking at the error, looks like we have a Java NullPointerException here on line 228!image-2019-10-11-14-35-38-430.png! I can confirm that we do have a valid jenkinsUrl!image-2019-10-11-14-42-27-639.png!That leaves me to think that the GitHubWebHook.get().getUrlName() is causing the NullPointerException. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6144.1570819380134%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Attachment: image-2019-10-11-14-35-38-430.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6140.1570818960310%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun commented on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) Looking at the error, looks like we have a Java NullPointerException here on line 228 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6142.1570818960337%40Atlassian.JIRA.
[JIRA] (JENKINS-59750) Quiet all Perforce file list output when quiet:true.
Title: Message Title Heather Mardis commented on JENKINS-59750 Re: Quiet all Perforce file list output when quiet:true. In my 100's of job configurations and with the size of my source code, the '-q' on p4 reconcile puts 43,156 lines in EVERY jenkins log file. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202473.1570806978000.6138.1570818120120%40Atlassian.JIRA.
[JIRA] (JENKINS-5597) symlinks in archive trees lead to double archiving
Title: Message Title Abhishek Sharma commented on JENKINS-5597 Re: symlinks in archive trees lead to double archiving Hi, Can someone please merge the changes to mains. We're very badly hurt by this issue, and currently building Jenkins manually for this change. There is a pending merge request https://github.com/jenkinsci/jenkins/pull/3947 that makes follow symlinks configurable. Thanks, Abhishek Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.135686.1265799663000.6109.1570816320775%40Atlassian.JIRA.
[JIRA] (JENKINS-59546) Git submodule checkout not working
Title: Message Title Liam Newman commented on JENKINS-59546 Re: Git submodule checkout not working Does this work on 2.5.6 or earlier? Also did you upgrade git client plugin at the same time? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202176.1569504096000.6105.1570813320239%40Atlassian.JIRA.
[JIRA] (JENKINS-59743) A pipeline job hitting the timeout ending up hanging
Title: Message Title Liam Newman commented on JENKINS-59743 Re: A pipeline job hitting the timeout ending up hanging We'll need to see your full Jenkinsfile, but if you have a try-catch make sure you handle InterruptedException to bubble it out. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202462.1570784822000.6103.1570813140113%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated Allan BURDAJEWICZ could we discuss about this ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.6101.1570812960053%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59732 Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Change By: Ivan Fernandez Calvo Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.6100.1570812300790%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-59732 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.6096.1570812300677%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59732 Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.6098.1570812300737%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Ivan Fernandez Calvo assigned an issue to Nick Jones Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo Nick Jones Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202450.1570725387000.6094.1570812300617%40Atlassian.JIRA.
[JIRA] (JENKINS-54275) (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-54275 Re: (Google Apps/SAML) org.pac4j.saml.exceptions.SAMLException: Authentication issue instant is too old *Maximum Session Lifetime* setting was removed because you should manage the session timeout on the servlet container see https://stackoverflow.com/questions/26407541/increase-the-jenkins-login-timeout Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194921.154057234.6089.1570812240172%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title
koffi AGOKLA updated an issue
Jenkins / JENKINS-59748
Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Change By:
koffi AGOKLA
Hi,After a migration from the version 0.3.11 to 1.1.1, I followed the tutorial described in the link: [http://go.microsoft.com/fwlink/?LinkId=280058]However, although i'm able to download the artifacts from my blob, i'm not able to upload artifacts to this same blob.I'm getting the error:{code:java}MicrosoftAzureStorage - Container name: azuretemplatesMicrosoftAzureStorage - share name: MicrosoftAzureStorage - File path: text/*.txtMicrosoftAzureStorage - Virtual path: MicrosoftAzureStorage - Exclude path: MicrosoftAzureStorage - Uploading files to Microsoft AzureMicrosoftAzureStorage - Need uploaded/archived file count = 2ERROR: MicrosoftAzureStorage - Error occurred while uploading to Azure - xxxdwesxxxcom.microsoftopentechnologies.windowsazurestorage.exceptions.WAStorageException: Only 0/2 files are successfully uploaded. at com.microsoftopentechnologies.windowsazurestorage.service.UploadService.execute(UploadService.java:729) at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:438) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)ERROR: Step 'Upload artifacts to Microsoft Azure Storage' aborted due to exception: java.io.IOException: MicrosoftAzureStorage - Error occurred while uploading to Azure - sastdwe1scr at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:469) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code} I tried with the version 1.0.4 and the artifacts were uploaded. But it
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Valencia Serrao commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Hi All, We are also seeing the same issue since the last 3-4 days. Current Jenkins version 2.176.2. Any pointers on this issue ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.6070.1570810620247%40Atlassian.JIRA.
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title
Guillaume Dupin updated an issue
Jenkins / JENKINS-59753
Error cloning remote repo
Change By:
Guillaume Dupin
Since we use the (great) GitLab Branch Source Plugin, we poncutally have the following error in our jobs : {code:java}Current revision of branch master is 885ffa6c168411f6b0f2209d819aa29187e328cfObtained Jenkinsfile from 885ffa6c168411f6b0f2209d819aa29187e328cfRunning in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeStill waiting to schedule taskWaiting for next available executorRunning on EC2 (aws-tooling) - Default (i-x) in /home/jenkins/workspace/ z_master z [Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential gitlab-jenkins-sshCloning the remote Git repositoryCloning with configured refspecs honoured and without tagsERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https:// code.tooling.prod.cdsf.io URL / teh group / metadata projet . deploy. git +refs/heads/master:refs/remotes/origin/master" returned status code 128:stdout: stderr: remote: HTTP Basic: Access deniedfatal: Authentication failed for 'https:// code.tooling.prod.cdsf.io URL / teh group / metadata projet . deploy. git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1905) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:488) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:712) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (aws-1119-gtp-tooling) - Default (i-09ea841682cf1bd26) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor775.invoke(Unknown Source) at
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title
Guillaume Dupin created an issue
Jenkins / JENKINS-59753
Error cloning remote repo
Issue Type:
Bug
Assignee:
Parichay Barpanda
Components:
gitlab-branch-source-plugin
Created:
2019-10-11 16:10
Environment:
Jenkins ver. 2.190.1 GitLab Branch Source Plugin 1.4.0
Priority:
Major
Reporter:
Guillaume Dupin
Since we use the (great) GitLab Branch Source Plugin, we poncutally have the following error in our jobs :
Current revision of branch master is 885ffa6c168411f6b0f2209d819aa29187e328cf
Obtained Jenkinsfile from 885ffa6c168411f6b0f2209d819aa29187e328cf
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor
Running on EC2 (aws-tooling) - Default (i-x) in /home/jenkins/workspace/z_master
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential gitlab-jenkins-ssh
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "git fetch --no-tags --progress https://code.tooling.prod.cdsf.io/teh/metadata.deploy.git +refs/heads/master:refs/remotes/origin/master" returned status code 128:
stdout:
stderr: remote: HTTP Basic: Access denied
fatal: Authentication failed for 'https://code.tooling.prod.cdsf.io/teh/metadata.deploy.git/'
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318)
at
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title
Stefan Scherer updated an issue
Jenkins / JENKINS-59752
Add support for ephemeral OS disk
Change By:
Stefan Scherer
Recently, Microsoft introduced the concept of [Ephemeral OS disk|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/ephemeral-os-disks] for certain types of VMs. An Ephemeral OS disk is stored on local storage and is therefore faster and free, but it is not persistent. It is therefore only used in situations where the VM is based on an [image|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/capture-image-resource] and every time it is started the OS disk will get “regenerated” from the generalized image and any changes made to the OS disk (C: ) will be lost if the VM moves to another host or is reallocated. [https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks] This would be super helpful for ephemeral Jenkins agents to have the best performance like the temporary disk (D: ) and have no cost for this disk.What I can see it's only a small change in the json. The diffDiskSettings with option Local seems to be the key.Machine sizes must be big enough to carry the disk image (127 GB for Windows from Marketplace) in their cache.{code}{"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#","contentVersion": "1.0.0.0","parameters": {"virtualMachines_redacted_name": {"defaultValue": "redacted","type": "String"},"redacted_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/PackerImages/providers/Microsoft.Compute/images/redacted","type": "String"},"disks_redacted_disk1_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/ ci-docker-com redacted /providers/Microsoft.Compute/disks/redacted","type": "String"},"networkInterfaces_redacted41_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/ ci-docker-com redacted /providers/Microsoft.Network/networkInterfaces/redacted","type": "String"}},"variables": {},"resources": [{"type": "Microsoft.Compute/virtualMachines","apiVersion": "2019-03-01","name": "[parameters('virtualMachines_redacted_name')]","location": "westus","properties": {"hardwareProfile": {"vmSize": "Standard_D4s_v3"},"storageProfile": {"imageReference": { "id": "[parameters('redacted_externalid')]"},"osDisk": { "osType": "Windows", "diffDiskSettings": { "option": "Local" }, "name": "[concat(parameters('virtualMachines_redacted_name'), '_disk1_')]", "createOption": "FromImage",
[JIRA] (JENKINS-59480) Automatically label SUSE Linux Enterprise Server agents
Title: Message Title Mark Waite updated JENKINS-59480 Jenkins / JENKINS-59480 Automatically label SUSE Linux Enterprise Server agents Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202095.1569240565000.6060.1570808700596%40Atlassian.JIRA.
[JIRA] (JENKINS-59480) Automatically label SUSE Linux Enterprise Server agents
Title: Message Title Mark Waite updated JENKINS-59480 Jenkins / JENKINS-59480 Automatically label SUSE Linux Enterprise Server agents Change By: Mark Waite Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202095.1569240565000.6062.1570808700845%40Atlassian.JIRA.
[JIRA] (JENKINS-55943) Add possibility to select osDisk SKU
Title: Message Title Stefan Scherer commented on JENKINS-55943 Re: Add possibility to select osDisk SKU I've also created JENKINS-59752 which is about the same topic, having better disk performance for the OS disk. This would be even more interesting for us. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197352.1549276857000.6057.1570808640190%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title
Stefan Scherer updated an issue
Jenkins / JENKINS-59752
Add support for ephemeral OS disk
Change By:
Stefan Scherer
Recently, Microsoft introduced the concept of [Ephemeral OS disk|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/ephemeral-os-disks] for certain types of VMs. An Ephemeral OS disk is stored on local storage and is therefore faster and free, but it is not persistent. It is therefore only used in situations where the VM is based on an [image|https://docs.microsoft.com/en-us/azure/virtual-machines/windows/capture-image-resource] and every time it is started the OS disk will get “regenerated” from the generalized image and any changes made to the OS disk (C:) will be lost if the VM moves to another host or is reallocated. [https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks] This would be super helpful for ephemeral Jenkins agents to have the best performance like the temporary disk (D:) and have no cost for this disk.What I can see it's only a small change in the json. The diffDiskSettings with option Local seems to be the key.Machine sizes must be big enough to carry the disk image (127 GB for Windows from Marketplace) in their cache.{code}{"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#","contentVersion": "1.0.0.0","parameters": {"virtualMachines_redacted_name": {"defaultValue": "redacted","type": "String"},"redacted_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/PackerImages/providers/Microsoft.Compute/images/redacted","type": "String"},"disks_redacted_disk1_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/ci-docker-com/providers/Microsoft.Compute/disks/redacted","type": "String"},"networkInterfaces_redacted41_externalid": {"defaultValue": "/subscriptions/redacted/resourceGroups/ci-docker-com/providers/Microsoft.Network/networkInterfaces/redacted","type": "String"}},"variables": {},"resources": [{"type": "Microsoft.Compute/virtualMachines","apiVersion": "2019-03-01","name": "[parameters('virtualMachines_redacted_name')]","location": "westus","properties": {"hardwareProfile": {"vmSize": "Standard_D4s_v3"},"storageProfile": {"imageReference": { "id": "[parameters('redacted_externalid')]"},"osDisk": { "osType": "Windows", "diffDiskSettings": { "option": "Local" }, "name": "[concat(parameters('virtualMachines_redacted_name'), '_disk1_')]", "createOption": "FromImage", "caching": "ReadOnly",
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title
Stefan Scherer created an issue
Jenkins / JENKINS-59752
Add support for ephemeral OS disk
Issue Type:
Improvement
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-10-11 15:39
Priority:
Minor
Reporter:
Stefan Scherer
Recently, Microsoft introduced the concept of Ephemeral OS disk for certain types of VMs. An Ephemeral OS disk is stored on local storage and is therefore faster and free, but it is not persistent. It is therefore only used in situations where the VM is based on an image and every time it is started the OS disk will get “regenerated” from the generalized image and any changes made to the OS disk (C will be lost if the VM moves to another host or is reallocated. https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks This would be super helpful for ephemeral Jenkins agents to have the best performance like the temporary disk (D and have no cost for this disk. What I can see it's only a small change in the json. The diffDiskSettings with option Local seems to be the key. Machine sizes must be big enough to carry the disk image (127 GB for Windows from Marketplace) in their cache.
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"virtualMachines_redacted_name": {
"defaultValue": "redacted",
"type": "String"
},
"redacted_externalid": {
"defaultValue": "/subscriptions/redacted/resourceGroups/PackerImages/providers/Microsoft.Compute/images/redacted",
"type": "String"
},
"disks_redacted_disk1_externalid": {
"defaultValue":
[JIRA] (JENKINS-55943) Add possibility to select osDisk SKU
Title: Message Title Stefan Scherer commented on JENKINS-55943 Re: Add possibility to select osDisk SKU Thanks, I searched through the codebase and I think this variable "storageAccountType": "Standard_LRS", in https://github.com/jenkinsci/azure-vm-agents-plugin/blob/dev/src/main/resources/customImageTemplateWithManagedDisk.json#L15 doesn't get changed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197352.1549276857000.6049.1570807680328%40Atlassian.JIRA.
[JIRA] (JENKINS-59751) Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Title: Message Title
Aaron Franssell updated an issue
Jenkins / JENKINS-59751
Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Change By:
Aaron Franssell
When I create a project through the pipeline DSL plugin (code snippet below is for a multibranch pipeline) the credentials I created are not passed correctly through to Github and authentication fails.Once I navigate to the newly created project and click "Configure" and then "Save" the configuration, Jenkins then scans Github successfully and everything works as expected.I would like to spin up Jenkins completely through Chef and Groovy DSLs so that no manual intervention (like having to click "Save") is required.Here is the DSL script I'm using: ``` UUID uuid = UUID.fromString("dd847135-8391-4f66-a54c-7f8781dc3119")multibranchPipelineJob('test3') { displayName "test3" description "test3" branchSources { github { { id(uuid.toString()) scanCredentialsId('gitusername_password') repoOwner('my_user') repository('my-repo') buildForkPRMerge(false) repository("my-repo.git") } }}queue("test3") ``` Here is the relevant portion of the logs:[Fri Oct 11 14:56:44 UTC 2019] Starting branch indexing...14:56:44 Connecting to [ https://api.github.com |https://api.github.com/] using my_user/** (gitusername_password)ERROR: [Fri Oct 11 14:56:45 UTC 2019] Could not update folder level actions from source dd847135-8391-4f66-a54c-7f8781dc3119hudson.AbortException: Invalid scan credentials when using my_user/** (gitusername_password) to connect to my_user/my-repo.git on [https://api.github.com|https://api.github.com/] My Jenkins version is: 2.190.1Job DSL Plugin version: 1.76OS:Operating System: Amazon Linux 2 CPE OS Name: cpe:2.3:o:amazon:amazon_linux:2 Kernel: Linux 4.14.138-114.102.amzn2.x86_64
Add Comment
[JIRA] (JENKINS-59751) Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Title: Message Title
Aaron Franssell updated an issue
Jenkins / JENKINS-59751
Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Change By:
Aaron Franssell
When I create a project through the pipeline DSL plugin (code snippet below is for a multibranch pipeline) the credentials I created are not passed correctly through to Github and authentication fails.Once I navigate to the newly created project and click "Configure" and then "Save" the configuration, Jenkins then scans Github successfully and everything works as expected.I would like to spin up Jenkins completely through Chef and Groovy DSLs so that no manual intervention (like having to click "Save") is required.Here is the DSL script I'm using: ``` UUID uuid = UUID.fromString("dd847135-8391-4f66-a54c-7f8781dc3119") multibranchPipelineJob('test3') { displayName "test3" description "test3" branchSources { github{ id(uuid.toString()) scanCredentialsId('gitusername_password') repoOwner('my_user') repository('my-repo') buildForkPRMerge(false) repository("my-repo.git") } } } queue("test3") ``` Here is the relevant portion of the logs:[Fri Oct 11 14:56:44 UTC 2019] Starting branch indexing... 14:56:44 Connecting to [https://api.github.com|https://api.github.com/] using my_user/** (gitusername_password) ERROR: [Fri Oct 11 14:56:45 UTC 2019] Could not update folder level actions from source dd847135-8391-4f66-a54c-7f8781dc3119 hudson.AbortException: Invalid scan credentials when using my_user/** (gitusername_password) to connect to my_user/my-repo.git on [https://api.github.com|https://api.github.com/] My Jenkins version is: 2.190.1Job DSL Plugin version: 1.76OS:Operating System: Amazon Linux 2 CPE OS Name: cpe:2.3:o:amazon:amazon_linux:2 Kernel: Linux 4.14.138-114.102.amzn2.x86_64
Add Comment
[JIRA] (JENKINS-59750) Quiet all Perforce file list output when quiet:true.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-59750 Quiet all Perforce file list output when quiet:true. Change By: Karl Wirth Summary: Quiet all Perforce file list output when quiet: false true . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202473.1570806978000.6044.1570807140268%40Atlassian.JIRA.
[JIRA] (JENKINS-59751) Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Title: Message Title
Aaron Franssell created an issue
Jenkins / JENKINS-59751
Projects Created Through Pipeline DSL Plugin Do Not Pass Credentials Correctly When Connecting to Github
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-10-11 15:17
Priority:
Major
Reporter:
Aaron Franssell
When I create a project through the pipeline DSL plugin (code snippet below is for a multibranch pipeline) the credentials I created are not passed correctly through to Github and authentication fails. Once I navigate to the newly created project and click "Configure" and then "Save" the configuration, Jenkins then scans Github successfully and everything works as expected. I would like to spin up Jenkins completely through Chef and Groovy DSLs so that no manual intervention (like having to click "Save") is required. Here is the DSL script I'm using: UUID uuid = UUID.fromString("dd847135-8391-4f66-a54c-7f8781dc3119") multibranchPipelineJob('test3') { displayName "test3" description "test3" branchSources { github { id(uuid.toString()) scanCredentialsId('gitusername_password') repoOwner('my_user') repository('my-repo') buildForkPRMerge(false) repository("my-repo.git") } } } queue("test3") Here is the relevant portion of the logs: [Fri Oct 11 14:56:44 UTC 2019] Starting branch indexing... 14:56:44 Connecting to https://api.github.com using my_user/** (gitusername_password) ERROR: [Fri Oct 11 14:56:45 UTC 2019] Could not update folder level actions from source dd847135-8391-4f66-a54c-7f8781dc3119 hudson.AbortException: Invalid scan credentials when using my_user/** (gitusername_password) to connect to my_user/my-repo.git on https://api.github.com My Jenkins version is: 2.190.1 Job DSL Plugin version: 1.76 OS: Operating System: Amazon Linux 2 CPE OS Name: cpe:2.3:o:amazon:amazon_linux:2 Kernel: Linux 4.14.138-114.102.amzn2.x86_64
[JIRA] (JENKINS-59750) Quiet all Perforce file list output when quiet:false.
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-59750
Quiet all Perforce file list output when quiet:false.
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-10-11 15:16
Environment:
p4-plugin 1.10.4 Jenkins 1.176.1
Labels:
P4_VERIFY
Priority:
Major
Reporter:
Karl Wirth
When 'quiet' is set to true 'p4 reconcile' and preferably other commands also need to have the file list quashed. For example hide the 'refreshed' below :
P4 Task: cleaning workspace to match have list.
... p4 reconcile -f -w /var/lib/jenkins/workspace/Pipeline_Quiet_True/... -p4 reconcile -f -w /var/lib/jenkins/workspace/Pipeline_Quiet_True/...
//depot/Project1/sub1/f564#1 - /var/lib/jenkins/workspace/Pipeline_Quiet_True/sub1/f564 refreshed
duration: (2ms)
P4 Task: syncing files at change: 565
... p4 sync -q /var/lib/jenkins/workspace/Pipeline_Quiet_True/...@565 -p4 sync -q /var/lib/jenkins/workspace/Pipeline_Quiet_True/...@565
duration: (2ms)
Code:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
p4sync charset: 'none',
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Devin Nusbaum commented on JENKINS-59668 Re: Run wrapper process in the background fails with the latest changes IIRC, using LAUNCH_DIAGNOSTICS restores the previous behavior, so if enabling that does not fix the problem, I don't think JENKINS-58290 is the cause. The other change in that release was PR 95, which changes how the default shell is selected. I would check how the default shell is configured on the agents in your examples, since "nohup: failed to run command 'sh': No such file or directory" definitely seems like the problem is related to the shell being used, which I believe previously would have defaulted to /bin/sh, now defaults to sh, so maybe your agents need sh on PATH or something? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6037.1570806840160%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.6035.1570806360578%40Atlassian.JIRA.
[JIRA] (JENKINS-59749) [AppCenter-Plugin] resolve app file by search pattern
Title: Message Title Alexander Siemer-Schmetzke created an issue Jenkins / JENKINS-59749 [AppCenter-Plugin] resolve app file by search pattern Issue Type: New Feature Assignee: Alexander Siemer-Schmetzke Components: appcenter-plugin Created: 2019-10-11 14:42 Priority: Minor Reporter: Alexander Siemer-Schmetzke Currently the appcenter-plugin needs to have a specific filename defined to be uploaded. The previous hockeyapp plugin allowed to use a search pattern like myapp-*.apk which will take the first result found. This functionality can be relatively easily added to the appcenter plugin. Add Comment
[JIRA] (JENKINS-59749) [AppCenter-Plugin] resolve app file by search pattern
Title: Message Title Alexander Siemer-Schmetzke started work on JENKINS-59749 Change By: Alexander Siemer-Schmetzke Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202472.157080495.6033.1570804980225%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Jonathan B commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.6030.1570804560164%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Oleg Nenashev commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml Please see https://github.com/jenkinsci/configuration-as-code-plugin/issues/191 Jonathan B Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.6028.1570804320186%40Atlassian.JIRA.
[JIRA] (JENKINS-59734) mailer/email-ext settings persist after removing from JCasC yaml
Title: Message Title Jonathan B commented on JENKINS-59734 Re: mailer/email-ext settings persist after removing from JCasC yaml Okay, thanks for your input. Tim Jacomb Oleg Nenashev does this behavior sound correct to you? Would you consider it a bug in configuration-as-code? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202452.1570740669000.6025.1570803840115%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.6022.1570803720259%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title koffi AGOKLA updated an issue Jenkins / JENKINS-59748 Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded Change By: koffi AGOKLA Environment: Jenkins ver. 2.190.1Windows Azure Storage Plugin Version 1.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202471.1570798596000.6020.1570801800237%40Atlassian.JIRA.
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title
koffi AGOKLA updated an issue
Jenkins / JENKINS-59748
Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Change By:
koffi AGOKLA
Hi, After a migration from the version 0.3.11 to 1.1.1, I followed the tutorial described in the link: [http://go.microsoft.com/fwlink/?LinkId=280058]However, although i'm able to download the artifacts from my blob, i'm not able to upload artifacts to this same blob.I'm getting the error:{code:java}MicrosoftAzureStorage - Container name: azuretemplatesMicrosoftAzureStorage - share name: MicrosoftAzureStorage - File path: text/*.txtMicrosoftAzureStorage - Virtual path: MicrosoftAzureStorage - Exclude path: MicrosoftAzureStorage - Uploading files to Microsoft AzureMicrosoftAzureStorage - Need uploaded/archived file count = 2ERROR: MicrosoftAzureStorage - Error occurred while uploading to Azure - xxxdwesxxxcom.microsoftopentechnologies.windowsazurestorage.exceptions.WAStorageException: Only 0/2 files are successfully uploaded. at com.microsoftopentechnologies.windowsazurestorage.service.UploadService.execute(UploadService.java:729) at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:438) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)ERROR: Step 'Upload artifacts to Microsoft Azure Storage' aborted due to exception: java.io.IOException: MicrosoftAzureStorage - Error occurred while uploading to Azure - sastdwe1scr at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:469) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title
Brice Dutheil edited a comment on JENKINS-7139
Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files
In the meantime, you can write : script { color code : #9876aa java } { script { color}{color:#cc7832} def {color} docFilesdir {color:#9876aa} ( {color}{color:#6a8759} 'build/docs/asciidoc/' {color}{color:#9876aa} ) { {color} docFiles = findFiles {color:#6a8759} glob {color} : {color:#6a8759} '**' {color } {color:#9876aa}} {color} publishHTML {color:#6a8759} target {color} : {color:#9876aa} [ {color}{color:#6a8759} allowMissing {color} : {color:#cc7832} false {color} , {color:#6a8759} alwaysLinkToLastBuild {color} : {color:#cc7832} false {color} , {color:#6a8759} keepAll {color} : {color:#cc7832} true {color} , {color:#6a8759} reportDir {color} : {color:#6a8759} 'build/docs/asciidoc/' {color} , {color:#6a8759} reportFiles {color} : docFiles.join {color:#9876aa} ( {color}{color:#6a8759} ',' {color}{color:#9876aa} ) {color} , {color:#6a8759} reportName {color} : {color:#6a8759} 'Documentation' {color}{color:#9876aa} ] {color } {color:#9876aa}} { color code }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title
Brice Dutheil commented on JENKINS-7139
Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files
In the meantime, you can write : script { def docFiles dir ('build/docs/asciidoc/') { docFiles = findFiles glob: '**' {color:#9876aa}} publishHTML target: [ allowMissing : false, alwaysLinkToLastBuild: false, keepAll : true, reportDir : 'build/docs/asciidoc/', reportFiles : docFiles.join(','), reportName : 'Documentation' ]{color:#9876aa}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137236.1280999333000.5980.1570799881633%40Atlassian.JIRA.
[JIRA] (JENKINS-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title
Ljubisa Punosevac edited a comment on JENKINS-54081
Re: Timestamps missing for agent-based steps in Pipeline Job 2.26
Hi, Unfortunately, this problem still prevails on Jenkins ver. 2.190.1 and timestamper [version 1.10|https://updates.jenkins.io/2.190/latest/timestamper.hpi]. I tried also older versions of this plugin for which has been written here to work, but again with the same results. Also, the following option has been set on Jenkins master as JVM parameter, but again with the same outcome:{code:java}-Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false{code} All our jobs are pipelines and timestamps appear only in a few places. Most of the time they are gone. {code}[Pipeline] configFileProvider[2019-10-11T11:22:10.289Z] provisioning config files...[2019-10-11T11:22:10.299Z] copy managed file [live-env-configuration.properties] to file:/var/lib/jenkins/workspace/generic-test-junit@tmp/config11258587709499260226tmp[Pipeline] {[Pipeline] readProperties[Pipeline] }[2019-10-11T11:22:10.350Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] sh[2019-10-11T11:22:09.383Z] Creating folder: /var/lib/jenkins/.m2[2019-10-11T11:22:09.388Z] Creating file: /var/lib/jenkins/.m2/settings.xml[2019-10-11T11:22:09.395Z] Creating folder: /var/lib/jenkins/workspace/generic-test-junit/.repository[2019-10-11T11:22:10.683Z] `s3/ec-test-release-pipeline/191011019/pipeline.properties` -> `pipeline.properties`[2019-10-11T11:22:10.683Z] Total: 962 B, Transferred: 962 B, Speed: 37.11 KiB/s[Pipeline] script[Pipeline] {[Pipeline] readProperties[Pipeline] }[Pipeline] // script[Pipeline] lock[2019-10-11T11:22:10.789Z] Trying to acquire lock on [Label: s3, Quantity: 1][2019-10-11T11:22:10.789Z] Lock acquired on [Label: s3, Quantity: 1][Pipeline] {[Pipeline] configFileProvider[2019-10-11T11:22:10.852Z] provisioning config files...[2019-10-11T11:22:10.862Z] copy managed file [live-env-configuration.properties] to file:/var/lib/jenkins/workspace/generic-test-junit@tmp/config1796990335769048953tmp[Pipeline] {[Pipeline] readProperties[Pipeline] }[2019-10-11T11:22:10.916Z] Deleting 1 temporary files[Pipeline] // configFileProvider[Pipeline] withCredentials[2019-10-11T11:22:10.958Z] Masking supported pattern matches of $S3_USERNAME or $S3_PASSWORD[Pipeline] {[Pipeline] shAdded `s3` successfully.[Pipeline] }[Pipeline] // withCredentials[Pipeline] withEnv[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] fileExists[Pipeline] dirRunning in /var/lib/jenkins/ramdisk[Pipeline] {[Pipeline] configFileProviderprovisioning config files...copy managed file [live-env-configuration.properties] to file:/var/lib/jenkins/ramdisk@tmp/config2573695607279314921tmp[Pipeline] {[Pipeline] readProperties[Pipeline] }Deleting 1 temporary files[Pipeline] // configFileProvider{code} Is there a solution to this problem?Best, Ljubisa.
Add Comment
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title
koffi AGOKLA updated an issue
Jenkins / JENKINS-59748
Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Change By:
koffi AGOKLA
Hi,I followed the tutorial described in the link: [http://go.microsoft.com/fwlink/?LinkId=280058]However, although i'm able to download the artifacts from my blob, i'm not able to upload artifacts to this same blob.I'm getting the error:{code:java}MicrosoftAzureStorage - Container name: azuretemplatescicddev azuretemplates MicrosoftAzureStorage - share name: MicrosoftAzureStorage - File path: text/*.txtMicrosoftAzureStorage - Virtual path: MicrosoftAzureStorage - Exclude path: MicrosoftAzureStorage - Uploading files to Microsoft AzureMicrosoftAzureStorage - Need uploaded/archived file count = 2ERROR: MicrosoftAzureStorage - Error occurred while uploading to Azure - sastdwe1scr xxxdwesxxx com.microsoftopentechnologies.windowsazurestorage.exceptions.WAStorageException: Only 0/2 files are successfully uploaded. at com.microsoftopentechnologies.windowsazurestorage.service.UploadService.execute(UploadService.java:729) at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:438) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)ERROR: Step 'Upload artifacts to Microsoft Azure Storage' aborted due to exception: java.io.IOException: MicrosoftAzureStorage - Error occurred while uploading to Azure - sastdwe1scr at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:469) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
[JIRA] (JENKINS-59748) Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded
Title: Message Title koffi AGOKLA created an issue Jenkins / JENKINS-59748 Error occurred while uploading to Azure - WAStorageException: Only 0/2 files are successfully uploaded Issue Type: Bug Assignee: Azure DevOps Components: windows-azure-storage-plugin Created: 2019-10-11 12:56 Priority: Major Reporter: koffi AGOKLA Hi, I followed the tutorial described in the link: http://go.microsoft.com/fwlink/?LinkId=280058 However, although i'm able to download the artifacts from my blob, i'm not able to upload artifacts to this same blob. I'm getting the error: MicrosoftAzureStorage - Container name: azuretemplatescicddev MicrosoftAzureStorage - share name: MicrosoftAzureStorage - File path: text/*.txt MicrosoftAzureStorage - Virtual path: MicrosoftAzureStorage - Exclude path: MicrosoftAzureStorage - Uploading files to Microsoft AzureMicrosoftAzureStorage - Need uploaded/archived file count = 2 ERROR: MicrosoftAzureStorage - Error occurred while uploading to Azure - sastdwe1scr com.microsoftopentechnologies.windowsazurestorage.exceptions.WAStorageException: Only 0/2 files are successfully uploaded. at com.microsoftopentechnologies.windowsazurestorage.service.UploadService.execute(UploadService.java:729) at com.microsoftopentechnologies.windowsazurestorage.WAStoragePublisher.perform(WAStoragePublisher.java:438) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Attachment: JenkinsGitHubPluginSystemConfigurationBug.gif Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.5927.1570798264498%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun commented on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) What's also strange is that in Configure System page, if I try to click the Add GitHub Server Config dropdown under the Github Plugin Configuration section, I can click on the Github Server Config. However, nothing happens. Is this a bug or is this as expected? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.5925.1570798200166%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun edited a comment on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) [~lanwen] Any ideas?So far, I've read the following posts[https://stackoverflow.com/questions/35062789/mailformed-github-plugin-configuration-no-protocol] I confirmed that our Jenkins URL is correct.[https://stackoverflow.com/questions/33533440/jenkins-save-configure-error-mailformed-github-plugin-configuration] We do not have a Jira plugin.Some additional info:This is what we have for our Github Plugin configuration in System Configuration page:!image-2019-10-11-08-24-14-724.png!Below are some additional version info for plugins:||Plugin Name||Version|||Git|2.4.2||Git client|1.19.5||GitHub|1.17.1||GitHub API|1.72| If you need more context, here are the rest of our plugins and their versions:||Plugin Name||Version|||Active Directory|2.6||AnsiColor|0.4.1||Ant|1.2||Credentials|1.25||CVS|2.12||Email Extension|2.39.3||Environment Injector|1.91.1||External Monitor Job Type|1.4||Icon Shim Plugin|2.0.3||Javadoc|1.3||Job Configuration History|2.12||JUnit|1.8||Kerberos SSO|1.0.2||LDAP|1.11||Mailer|1.16||MapDB API|1.0.6.0||Matrix Authorization Strategy|1.2||Matrix Project|1.6||Maven Integration|2.9||MSTestRunner|1.1.2||NAnt Plugin|1.4.3||NUnit|0.16||OWASP Markup Formatter|1.3||PAM Authentication|1.2||Pipeline: Step API|1.13||Plain Credentials|1.1||promoted builds|2.25||Promoted Builds (Simple)|1.9||SCM API|1.0||Script Security|1.13||SSH Agent|1.9||SSH Credentials|1.11||SSH Slaves|1.9||Subversion|2.5||TAP|1.23||Token Macro|1.12.1||Translation Assistance|1.12||WMI Windows Agents|1.0||Workspace Cleanup|0.25||xUnit|1.96| Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59747) Json api crashes
Title: Message Title Lars Rökman created an issue Jenkins / JENKINS-59747 Json api crashes Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-11 12:29 Environment: Linux version 2.190.1 Labels: jenkins Priority: Minor Reporter: Lars Rökman Json api crashes on command https://jenkins.xx.fi/api/json. Api displays first 3840 jobs. The same thing occurs in xml - api https://jenkins.xx.fi/api/xml/prettyprint=true Stack trace java.lang.NullPointerException Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:219) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun edited a comment on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) [~lanwen] Any ideas?So far, I've read the following posts[https://stackoverflow.com/questions/35062789/mailformed-github-plugin-configuration-no-protocol] I confirmed that our Jenkins URL is correct.[https://stackoverflow.com/questions/33533440/jenkins-save-configure-error-mailformed-github-plugin-configuration] We do not have a Jira plugin.Some additional info:This is what we have for our Github Plugin configuration in System Configuration page:!image-2019-10-11-08-24-14-724.png!Below are some additional version info for plugins:||Plugin Name||Version|||Git|2.4.2||Git client|1.19.5||GitHub|1.17 / . 1||GitHub API|1.72| Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.5916.1570796820157%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun commented on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) Kirill Merkushev Any ideas? So far, I've read the following posts https://stackoverflow.com/questions/35062789/mailformed-github-plugin-configuration-no-protocol I confirmed that our Jenkins URL is correct. https://stackoverflow.com/questions/33533440/jenkins-save-configure-error-mailformed-github-plugin-configuration We do not have a Jira plugin. Some additional info: This is what we have for our Github Plugin configuration in System Configuration page: Below are some additional version info for plugins: Plugin Name Version Git 2.4.2 Git client 1.19.5 GitHub 1.17/1 GitHub API 1.72 Add Comment
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Attachment: image-2019-10-11-08-24-14-724.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.5912.1570796700314%40Atlassian.JIRA.
[JIRA] (JENKINS-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title
Ljubisa Punosevac edited a comment on JENKINS-54081
Re: Timestamps missing for agent-based steps in Pipeline Job 2.26
Hi, Unfortunately, this problem still prevails on Jenkins ver. 2.190.1 and timestamper [version 1.10|https://updates.jenkins.io/2.190/latest/timestamper.hpi]. I tried also older versions of this plugin for which has been written here to work, but again with the same results. Also, the following option has been set on Jenkins master as JVM parameter, but again with the same outcome:{code:java}-Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false{code}Is there a solution for to this problem?Best, Ljubisa.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194704.153961761.5894.1570795820560%40Atlassian.JIRA.
[JIRA] (JENKINS-59746) i am unable to build because of the STACK TRACE issue. it is showing Loading but nothing comes.
Title: Message Title manisha kumari created an issue Jenkins / JENKINS-59746 i am unable to build because of the STACK TRACE issue. it is showing Loading but nothing comes. Issue Type: Bug Assignee: manisha kumari Attachments: 1.PNG, 2.PNG, 3.PNG Components: capitomcat-plugin, core, gitlab-hook-plugin Created: 2019-10-11 12:05 Environment: Jenkins ver. 2.196 window 10 Chrome java8 jre1.8.0_202 Labels: jenkins performance Priority: Blocker Reporter: manisha kumari Stack trace org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.196.jar!/hudson/model/View/index.jelly:42:43: JSONObject["displayStrategy"] not found. at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] (JENKINS-52611) Multi-job phase unable to launch - Pending - Description
Title: Message Title Goran Stuc commented on JENKINS-52611 Re: Multi-job phase unable to launch - Pending - Description Maybe it helps someone: I had the same issue with multijobs my jobs only started after i killed the main job until i unchecked the option on the options for child Jobs "Block builds ..." in Job Notifications After that it worked as intended Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192458.153185250.5890.1570794540109%40Atlassian.JIRA.
[JIRA] (JENKINS-55943) Add possibility to select osDisk SKU
Title: Message Title Jie Shen commented on JENKINS-55943 Re: Add possibility to select osDisk SKU Stefan Scherer Feel free to create a PR. Some useful pages : https://docs.microsoft.com/en-us/azure/templates/microsoft.compute/2019-03-01/virtualmachines#OSDisk and https://docs.microsoft.com/en-us/azure/templates/microsoft.compute/2019-03-01/virtualmachines#ManagedDiskParameters. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197352.1549276857000.5886.1570794480299%40Atlassian.JIRA.
[JIRA] (JENKINS-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title Ljubisa Punosevac reopened an issue Hi, Unfortunately, this problem still prevails on Jenkins ver. 2.190.1 and timestamper version 1.10. I tried also older versions of this plugin for which has been written here to work, but again with the same results. Also, following option has been set on Jenkins master as JVM parameter, but again with the same outcome: -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false Is there a solution for this problem? Best, Ljubisa. Jenkins / JENKINS-54081 Timestamps missing for agent-based steps in Pipeline Job 2.26 Change By: Ljubisa Punosevac Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Nick Jones commented on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I'm seeing what Guy Banay sees. I'm now testing a Declarative Pipeline workaround as Kyle Walker suggested – namely, putting the properties block outside the pipeline altogether – and it works, but it only honors the maxConcurrentTotal property, not the maxConcurrentNode one. Very simple repro (assuming a "ThrottleTest" category is configured globally):
properties([
[
$class: 'ThrottleJobProperty',
categories: ['ThrottleTest'],
throttleEnabled: true,
throttleOption: 'category'
],
])
pipeline {
agent any
stages {
stage('Long-running') {
steps {
input message: 'Shall we continue?'
echo "Thanks! Continuing."
}
}
}
}
If I configure a maximum of 5 concurrent builds across all nodes, but only 1 per node, the only limit enforced is the total limit; a single build agent can still run as many builds of this job as it has executors. Only the maxConcurrentTotal takes effect.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code} If anybody has come up with something better I would love to hear it!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code} If anybody has come up with something better I would love to hear it!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely edited a comment on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing: {code:java}def getBlueOceanLink(obj, jobName) { def buildNumber if(obj instanceof Exception) {obj.toString().split(" ").each { if(it.contains("#")) {buildNumber = it.substring(1) }} } else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {buildNumber = obj.getNumber() } else {return "Can not determine Blue Ocean link!!!" } return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"}// Wrapper:def linkBuild(job, parameters) {def buildInfotry {buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)} catch (Exception e) {println getBlueOceanLink(e, job)throw e}println getBlueOceanLink(buildInfo, job)}// Usage:stage ("My stage") { linkBuild("My job", [ string(name: "my param", value: some_value) ])}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (TEST-182) This is Bug
Title: Message Title chaithanya reddy created an issue test / TEST-182 This is Bug Issue Type: Bug Assignee: Oleg Nenashev Components: foo10 Created: 2019-10-11 10:48 Priority: Minor Reporter: chaithanya reddy Testing purose Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title
Werner Wessely commented on JENKINS-38339
Re: UI for downstream jobs launched with 'build' step
For anybody struggling with this and in need of some inspiration for a workaround, we are using a wrapper for the job step which prints a link to the downstream build until this issue is fixed. Better than nothing:
def getBlueOceanLink(obj, jobName) {
def buildNumber
if(obj instanceof Exception) {
obj.toString().split(" ").each {
if(it.contains("#")) {
buildNumber = it.substring(1)
}
}
} else if(obj instanceof org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper) {
buildNumber = obj.getNumber()
} else {
return "Can not determine Blue Ocean link!!!"
}
return "For detailed information see: http:///blue/organizations/jenkins/${jobName}/detail/${jobName}/${buildNumber}/pipeline"
}
// Wrapper:
def linkBuild(job, parameters) {
def buildInfo
try {
buildInfo = build(job: job, parameters: parameters, wait: true, propagate: true)
} catch (Exception e) {
println getBlueOceanLink(e, job)
throw e
}
println getBlueOceanLink(buildInfo, job)
}
// Usage:
stage ("My stage") {
linkBuild("My job", [
string(name: "my param", value: some_value)
])
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title Thomas Draebing updated an issue Jenkins / JENKINS-59745 Error when trying to vote on label in multibranch pipeline (0.3.4) Change By: Thomas Draebing Environment: Jenkins 2.60.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202464.1570786202000.5587.1570790580705%40Atlassian.JIRA.
