[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Michael Neale commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Sorry - my confusion, I didn't see that image for some reason. Right that is interesting. Unfortunately can't diagnose enough from that, but it implies that there is something being stripped (maybe a cookie) when the link is pasted into a new tab. Given I can't reproduce, or others I have asked, can I get you to try a few things (lets pretend we are doing a support ticket): Is there any more js/browser errors than the one you pasted? Is there anything in the server log for jenkins What do you have installed in your jenkins instance (I can tell you are using a look and feel plugin) Could you possibly get from the browser the headers (request and response) for that 400 error? (assuming nothing confidential or can be scrubbed) Try it with another browser on your machine Are you able to download and run LTS jenkins locally, and install blue ocean into it - create a freestyle job in a folder (all locally)? Are you using a reverse proxy - if so, what one (headers may tell more) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline
Title: Message Title Florian Manschwetus commented on JENKINS-26660 Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline Keep in mind a pipeline with multiple scms can and SHOULD set clean for each repo used in its own scm step, the behavior you sketched will wipe the others completely. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34250) Inconsistent "Manage Jenkins" icon on Plugin Manager screen
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-34250 Inconsistent "Manage Jenkins" icon on Plugin Manager screen Change By: Daniel Beck Labels: 2.0 community-bee lts-candidate testfest Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37997) NPE in Descriptor when not registered Extension
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-37997 NPE in Descriptor when not registered Extension Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38397) Regarding aws device farm error
Title: Message Title
Sanyasirao Mopada created an issue
Jenkins / JENKINS-38397
Regarding aws device farm error
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
aws-device-farm-plugin
Created:
2016/Sep/21 4:28 AM
Priority:
Blocker
Reporter:
Sanyasirao Mopada
publishers { archiveArtifacts { // If set, does not fail the build if archiving returns nothing. allowEmpty(true) // Uses default excludes. defaultExcludes(true) // Specifies files that will not be archived. exclude(null) // Fingerprints all archived artifacts. fingerprint(false) // Archives artifacts only if the build is successful. onlyIfSuccessful(false) // Specifies the files to archive. pattern(archiveArtifactPattern) } androidApkUpload { // Specifies filenames or patterns matching one or more APKs that should be uploaded to Google Play. apkFilesPattern(googlePlayApkPattern) // Specifies filenames or patterns matching zero or more expansion files that should be associated with the APK files being uploaded to Google Play. expansionFilesPattern(null) googleCredentialsId(googlePlayCredentialId) // You can optionally apply "What's new" text to the uploaded APK(s), in order to inform your user of changes contained in the new app version. recentChangeList{} // The percentage of existing production users to which the uploaded APK(s) should be rolled out. rolloutPercentage(null) // The release track to which the given APK file(s) will be assigned. trackName(googlePlayReleaseTrack) usePreviousExpansionFilesIfMissing(false) } awsDeviceFarmRecorder { projectName('BoilerPlate') devicePoolName('Test') appArtifact('example') runName('$ {BUILD_TAG} ') testToRun('example') storeResults(true) isRunUnmetered(true) eventCount('example') eventThrottle('example') seed('example') username('example') password('example') appiumJavaJUnitTest('example') appiumJavaTestNGTest('example') appiumPythonTest('example') calabashFeatures('example') calabashTags('example') calabashProfile('example') junitArtifact('example')
[JIRA] (JENKINS-20292) Option to specify an else-block
Title: Message Title ohad r commented on JENKINS-20292 Re: Option to specify an else-block +1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38396) Finalize JSON format for pipeline model
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38396 Finalize JSON format for pipeline model Issue Type: Story Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/21 3:51 AM Priority: Major Reporter: Michael Neale We need to lock down the JSON serialization format of pipeline model Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38363) Investigate slow loading experience
Title: Message Title Michael Neale commented on JENKINS-38363 Re: Investigate slow loading experience Keith Zantow as shown by Vivek, the slowness at least in the case of dogfood is NOT due to search and fetching of data from disk Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38001) Cannot rename a GitHub Org Folder
Title: Message Title Christian Stewart commented on JENKINS-38001 Re: Cannot rename a GitHub Org Folder Any updates on this? I can reproduce. I need to rename a folder but can't. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Michael Neale commented on JENKINS-38335 Re: Search API too slow for dashboard Punting this to keith for now as Vivek away. Looks like until we get a JENKINS_HOME that shows the search slowness, there are probably other avenues to explore to optimise. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Michael Neale assigned an issue to Keith Zantow Jenkins / JENKINS-38335 Search API too slow for dashboard Change By: Michael Neale Assignee: Vivek Pandey Keith Zantow Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38391) Administrative monitors should be more noticeable
Title: Message Title Daniel Beck updated JENKINS-38391 Jenkins / JENKINS-38391 Administrative monitors should be more noticeable Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38391) Administrative monitors should be more noticeable
Title: Message Title Daniel Beck started work on JENKINS-38391 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36017) Hpi trojan
Title: Message Title
Daniel Beck resolved as Not A Defect
Actually, that's very likely because of the plugin's design, using java agents to inject code into the Maven process. https://github.com/jenkinsci/maven-interceptors The Virus Total results indicate this is actually what they detect ("generic, java, agent"). From http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html
adds a whole lot of hooks and can even modify the build in ways that Maven did not intend.
Nothing to do here but not use the plugin.
Jenkins / JENKINS-36017
Hpi trojan
Change By:
Daniel Beck
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title
Sanyasirao Mopada edited a comment on JENKINS-38351
Re: Add job DSL script support for aws device farm plugin
{{ freeStyleJob(projectName) { scm {git { remote {url(gitUrl)credentials(gitCredentialsId) } extensions {submoduleOption { // By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist. disableSubmodules(false) // Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5) recursiveSubmodules(true) // Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2) trackingSubmodules(true) // Specify a folder containing a repository that will be used by Git as a reference during clone operations. reference(null) // Specify a timeout (in minutes) for submodules operations. timeout(subModuleTimeOut) // Use credentials from the default remote of the parent project. parentCredentials(false)} }} } triggers {bitbucketPush() } steps{shell(readFileFromWorkspace('shellScript.sh')) } publishers {archiveArtifacts { // If set, does not fail the build if archiving returns nothing. allowEmpty(true) // Uses default excludes. defaultExcludes(true) // Specifies files that will not be archived. exclude(null) // Fingerprints all archived artifacts. fingerprint(false) // Archives artifacts only if the build is successful. onlyIfSuccessful(false) // Specifies the files to archive. pattern(archiveArtifactPattern)} androidApkUpload { // Specifies filenames or patterns matching one or more APKs that should be uploaded to Google Play. apkFilesPattern(googlePlayApkPattern) // Specifies filenames or patterns matching zero or more expansion files that should be associated with the APK files being uploaded to Google Play. expansionFilesPattern(null) googleCredentialsId(googlePlayCredentialId) // You can optionally apply "What's new" text to the uploaded APK(s), in order to inform your user of changes contained in the new app version. recentChangeList{} // The percentage of existing production users to which the uploaded APK(s) should be rolled out. rolloutPercentage(null) // The release track to which the given APK file(s) will be assigned. trackName(googlePlayReleaseTrack) usePreviousExpansionFilesIfMissing(false)}awsDeviceFarmRecorder { projectName('BoilerPlate') devicePoolName('Test') appArtifact('example') runName('${BUILD_TAG}') testToRun('example') storeResults(true) isRunUnmetered(true) eventCount('example') eventThrottle('example') seed('example') username('example') password('example') appiumJavaJUnitTest('example') appiumJavaTestNGTest('example') appiumPythonTest('example') calabashFeatures('example') calabashTags('example') calabashProfile('example') junitArtifact('example') junitFilter('example') uiautomatorArtifact('example') uiautomatorFilter('example') uiautomationArtifact('example') xctestArtifact('example') xctestUiArtifact('example') ignoreRunError(true)}mailer(emailList, false, true) } wrappers {maskPasswords()artifactoryMaven3NativeConfigurator { details {artifactoryName(mavenArtifactoryName)artifactoryUrl(mavenArtifactoryUrl)
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title
Sanyasirao Mopada edited a comment on JENKINS-38351
Re: Add job DSL script support for aws device farm plugin
{{ freeStyleJob(projectName) { scm {git { remote {url(gitUrl)credentials(gitCredentialsId) } extensions {submoduleOption { // By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist. disableSubmodules(false) // Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5) recursiveSubmodules(true) // Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2) trackingSubmodules(true) // Specify a folder containing a repository that will be used by Git as a reference during clone operations. reference(null) // Specify a timeout (in minutes) for submodules operations. timeout(subModuleTimeOut) // Use credentials from the default remote of the parent project. parentCredentials(false)} }} } triggers {bitbucketPush() } steps{shell(readFileFromWorkspace('shellScript.sh')) } publishers {archiveArtifacts { // If set, does not fail the build if archiving returns nothing. allowEmpty(true) // Uses default excludes. defaultExcludes(true) // Specifies files that will not be archived. exclude(null) // Fingerprints all archived artifacts. fingerprint(false) // Archives artifacts only if the build is successful. onlyIfSuccessful(false) // Specifies the files to archive. pattern(archiveArtifactPattern)} androidApkUpload { // Specifies filenames or patterns matching one or more APKs that should be uploaded to Google Play. apkFilesPattern(googlePlayApkPattern) // Specifies filenames or patterns matching zero or more expansion files that should be associated with the APK files being uploaded to Google Play. expansionFilesPattern(null) googleCredentialsId(googlePlayCredentialId) // You can optionally apply "What's new" text to the uploaded APK(s), in order to inform your user of changes contained in the new app version. recentChangeList{} // The percentage of existing production users to which the uploaded APK(s) should be rolled out. rolloutPercentage(null) // The release track to which the given APK file(s) will be assigned. trackName(googlePlayReleaseTrack) usePreviousExpansionFilesIfMissing(false)}awsDeviceFarmRecorder { projectName('BoilerPlate') devicePoolName('Test') appArtifact('example') runName('${BUILD_TAG}') testToRun('example') storeResults(true) isRunUnmetered(true) eventCount('example') eventThrottle('example') seed('example') username('example') password('example') appiumJavaJUnitTest('example') appiumJavaTestNGTest('example') appiumPythonTest('example') calabashFeatures('example') calabashTags('example') calabashProfile('example') junitArtifact('example') junitFilter('example') uiautomatorArtifact('example') uiautomatorFilter('example') uiautomationArtifact('example') xctestArtifact('example') xctestUiArtifact('example') ignoreRunError(true)}mailer(emailList, false, true) } wrappers {maskPasswords()artifactoryMaven3NativeConfigurator { details {artifactoryName(mavenArtifactoryName)artifactoryUrl(mavenArtifactoryUrl)
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title
Sanyasirao Mopada commented on JENKINS-38351
Re: Add job DSL script support for aws device farm plugin
freeStyleJob(projectName) { scm { git { remote { url(gitUrl) credentials(gitCredentialsId) } extensions { submoduleOption { // By disabling support for submodules you can still keep using basic git plugin functionality and just have Jenkins to ignore submodules completely as if they didn't exist. disableSubmodules(false) // Retrieve all submodules recursively (uses '--recursive' option which requires git>=1.6.5) recursiveSubmodules(true) // Retrieve the tip of the configured branch in .gitmodules (Uses '--remote' option which requires git>=1.8.2) trackingSubmodules(true) // Specify a folder containing a repository that will be used by Git as a reference during clone operations. reference(null) // Specify a timeout (in minutes) for submodules operations. timeout(subModuleTimeOut) // Use credentials from the default remote of the parent project. parentCredentials(false) } } } } triggers { bitbucketPush() } steps { shell(readFileFromWorkspace('shellScript.sh')) } publishers { archiveArtifacts { // If set, does not fail the build if archiving returns nothing. allowEmpty(true) // Uses default excludes. defaultExcludes(true) // Specifies files that will not be archived. exclude(null) // Fingerprints all archived artifacts. fingerprint(false) // Archives artifacts only if the build is successful. onlyIfSuccessful(false) // Specifies the files to archive. pattern(archiveArtifactPattern) } androidApkUpload { // Specifies filenames or patterns matching one or more APKs that should be uploaded to Google Play. apkFilesPattern(googlePlayApkPattern) // Specifies filenames or patterns matching zero or more expansion files that should be associated with the APK files being uploaded to Google Play. expansionFilesPattern(null) googleCredentialsId(googlePlayCredentialId) // You can optionally apply "What's new" text to the uploaded APK(s), in order to inform your user of changes contained in the new app version. recentChangeList{} // The percentage of existing production users to which the uploaded APK(s) should be rolled out. rolloutPercentage(null) // The release track to which the given APK file(s) will be assigned. trackName(googlePlayReleaseTrack) usePreviousExpansionFilesIfMissing(false) } awsDeviceFarmRecorder { projectName('BoilerPlate') devicePoolName('Test') appArtifact('example') runName('$ {BUILD_TAG} ') testToRun('example') storeResults(true) isRunUnmetered(true) eventCount('example') eventThrottle('example') seed('example') username('example') password('example') appiumJavaJUnitTest('example') appiumJavaTestNGTest('example') appiumPythonTest('example') calabashFeatures('example') calabashTags('example') calabashProfile('example') junitArtifact('example') junitFilter('example') uiautomatorArtifact('example') uiautomatorFilter('example') uiautomationArtifact('example') xctestArtifact('example') xctestUiArtifact('example') ignoreRunError(true) } mailer(emailList, false, true) } wrappers { maskPasswords() artifactoryMaven3NativeConfigurator { details { artifactoryName(mavenArtifactoryName) artifactoryUrl(mavenArtifactoryUrl) deployReleaseRepository { keyFromText(mavenArtifactoryTargetRelease) keyFromSelect(mavenArtifactoryTargetRelease) dynamicMode(true) } deploySnapshotRepository{ keyFromText(mavenArtifactoryTargetSnapshot) keyFromSelect(mavenArtifactoryTargetSnapshot) dynamicMode(true) } resolveReleaseRepository { keyFromText(mavenArtifactoryTargetRelease) keyFromSelect(mavenArtifactoryTargetRelease) dynamicMode(true) } resolveSnapshotRepository { keyFromText(mavenArtifactoryTargetSnapshot)
[JIRA] (JENKINS-38351) Add job DSL script support for aws device farm plugin
Title: Message Title Sanyasirao Mopada updated JENKINS-38351 Jenkins / JENKINS-38351 Add job DSL script support for aws device farm plugin Change By: Sanyasirao Mopada Status: Resolved In Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31829) Evaluated Groovy script should expose the current hudson.model.TaskListener
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31829 Re: Evaluated Groovy script should expose the current hudson.model.TaskListener Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectEnvVars.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-groovyScriptContent.html src/test/java/org/jenkinsci/plugins/envinject/EnvInjectEvaluatedGroovyScriptTest.java http://jenkins-ci.org/commit/envinject-plugin/83f2ee3ef6fa74599fe2b5701b2d393a657aa9f7 Log: Merge branch 'JENKINS-31829' Compare: https://github.com/jenkinsci/envinject-plugin/compare/caed755d7920...83f2ee3ef6fa Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31829) Evaluated Groovy script should expose the current hudson.model.TaskListener
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31829 Re: Evaluated Groovy script should expose the current hudson.model.TaskListener Code changed in jenkins User: Fiouz Path: src/main/java/org/jenkinsci/plugins/envinject/service/EnvInjectEnvVars.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-groovyScriptContent.html src/test/java/org/jenkinsci/plugins/envinject/EnvInjectEvaluatedGroovyScript.java http://jenkins-ci.org/commit/envinject-plugin/434ab11da3e59ab102a186b4cae3a5916248f8c8 Log: JENKINS-31829 Add currentListener Groovy variable Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38395) Can't start Jenkins
Title: Message Title Jarosław Maciejewski created an issue Jenkins / JENKINS-38395 Can't start Jenkins Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Sep/21 1:33 AM Priority: Minor Reporter: Jarosław Maciejewski After update Jenkins (via apt-get update && apt-get upgrade -y) Jenkins can't start on WWW I have errror: hudson.util.HudsonFailedToLoad: java.lang.NoClassDefFoundError: Could not initialize class javax.crypto.JceSecurity at hudson.WebAppMain$3.run(WebAppMain.java:241) Caused by: java.lang.NoClassDefFoundError: Could not initialize class javax.crypto.JceSecurity at javax.crypto.Mac.getInstance(java.base@9-ea/Mac.java:184) at jenkins.security.HMACConfidentialKey.createMac(HMACConfidentialKey.java:111) at jenkins.security.HMACConfidentialKey.mac(HMACConfidentialKey.java:69) at jenkins.security.HMACConfidentialKey.mac(HMACConfidentialKey.java:85) at jenkins.security.ApiTokenProperty$DescriptorImpl.newInstance(ApiTokenProperty.java:178) at jenkins.security.ApiTokenProperty$DescriptorImpl.newInstance(ApiTokenProperty.java:163) at hudson.model.User.load(User.java:196) at hudson.model.User.(User.java:148) at hudson.model.User.getOrCreate(User.java:456) at hudson.model.User.getById(User.java:527) at hudson.security.HudsonPrivateSecurityRealm.createAccount(HudsonPrivateSecurityRealm.java:398) at jenkins.install.SetupWizard.init(SetupWizard.java:106) at jenkins.install.InstallState$3.initializeState(InstallState.java:105) at jenkins.model.Jenkins.setInstallState(Jenkins.java:970) at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:94) at jenkins.model.Jenkins.(Jenkins.java:887) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:227)
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey commented on JENKINS-38335 Re: Search API too slow for dashboard Keith Zantow My initial investigation report: PipelineSearch calls, Jenkins.getInstance().getAllItems(). Jenkins keeps all these items in memory so its all in memory cost PipelineSearch does few (at least 2 iteration) of all items and wraps them in BluePipeline implementation object Only pagination size limit, for example 26 BluePipeline items gets serialized over wire Most cost is paid during serialization Things like get build id, get last build, run details, actions attached to pipeline job, actions attached to jenkins.model.Run etc, where the real cost is. I tried ci.blueocean.io jobs locally (using downloaded jenkins home content of dogfood ci server) as well as the one running over ci.blueocean.io - but they do not indicate expensiv e search API calls. 95ms local, 364ms at ci.blueocean.io. See attached images. I tried profiling running instance blueocean locally with dogfood home directory, but the cost paid during fetching pipeline results was negligible. I suspect there are some plugins, who contribute to actions that contribute to the slow behavior so if Ben Walding could his work load that can help us identify why its slow on his instance. search-perf-dogfood-remote.tiff Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38335 Search API too slow for dashboard Change By: Vivek Pandey Attachment: search-perf-dogfood-local.tiff Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey edited a comment on JENKINS-38335 Re: Search API too slow for dashboard [~kzantow] My initial investigation report:* PipelineSearch calls, Jenkins.getInstance().getAllItems(). Jenkins keeps all these items in memory so its all in memory cost* PipelineSearch does few (at least 2 iteration) of all items and wraps them in BluePipeline implementation object* Only pagination size limit, for example 26 BluePipeline items gets serialized over wire* Most cost is paid during serialization** Things like get build id, get last build, run details, actions attached to pipeline job, actions attached to jenkins.model.Run etc, where the real cost is.* I tried ci.blueocean.io jobs locally (using downloaded jenkins home content of dogfood ci server) as well as the one running over ci.blueocean.io - but they do not indicate expensiv !search-perf-dogfood-remote.tiff|thumbnail! e search API calls. 95ms local, 364ms at ci.blueocean.io. See attached images.* I tried profiling running instance blueocean locally with dogfood home directory, but the cost paid during fetching pipeline results was negligible.* I suspect there are some plugins, who contribute to actions that contribute to the slow behavior so if [~bwalding] could his work load that can help us identify why its slow on his instance. ! [^ search-perf-dogfood- local remote .tiff |thumbnail! ] [^search-perf-dogfood- remote local .tiff] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38335 Search API too slow for dashboard Change By: Vivek Pandey Attachment: search-perf-dogfood-remote.tiff Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38208) Display parameters in pipeline-stage-view
Title: Message Title James Dumay commented on JENKINS-38208 Re: Display parameters in pipeline-stage-view We should take this into account when we pick up JENKINS-38393 in Blue Ocean. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38394) Ability to set output of a step to environment variable(s)
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38394 Ability to set output of a step to environment variable(s) Issue Type: Story Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Sep/21 12:37 AM Priority: Major Reporter: Michael Neale When using steps like input that capture data from a user, it makes sense to be able to set the resultant values to environment variables. This could be generalised to other steps that return values (perhaps as maps). In pipeline-model, the way data is passed around is via (environment) variables as there are no local variables, so the ability to set environment variables to the output is required. Add Comment
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: James Dumay Sprint: 1.0-b05/b-06 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37024) Opening the result modal should open over the existing content
Title: Message Title James Dumay commented on JENKINS-37024 Re: Opening the result modal should open over the existing content Keith Zantow would be good if we can bump the priority of this one to unblock Josh McDonald (he's going to refactor a bunch of stuff) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38325) We need a logo mark for Blue Ocean
Title: Message Title Brody Maclean started work on JENKINS-38325 Change By: Brody Maclean Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title James Dumay assigned an issue to Brody Maclean Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: James Dumay Assignee: Brody Maclean Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37425) Rework the behavior of Toasts for Run, Stop and Replay
Title: Message Title Cliff Meyers started work on JENKINS-37425 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37319) Add "maxlines" to "FILE" token macro
Title: Message Title Alex Earl resolved as Fixed This is fixed in token-macro 2.0 Jenkins / JENKINS-37319 Add "maxlines" to "FILE" token macro Change By: Alex Earl Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34013) Errors after upgrading Jenkins from "1.0" to 2.0-beta-2
Title: Message Title Daniel Beck commented on JENKINS-34013 Re: Errors after upgrading Jenkins from "1.0" to 2.0-beta-2 Brian Wilson Ignore it. Doesn't mean anything. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Michael Neale commented on JENKINS-38393 Re: Capturing of build parameters for parametrised builds cc James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38393) Capturing of build parameters for parametrised builds
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38393 Capturing of build parameters for parametrised builds Issue Type: Story Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/20 11:26 PM Priority: Minor Reporter: Michael Neale Multibranch builds, as well as normal pipeline, can take parameters before the build starts (this is distinct from input steps). WE need a design as to where this is captured and how Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-30300) Unable to specify a branch to build when using parameterized job with multiple branches
Title: Message Title Puneeth Nanjundaswamy commented on JENKINS-30300 Re: Unable to specify a branch to build when using parameterized job with multiple branches I have the same issue. Any updates on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38392) Input step implies that values are set to environment variables when they are not
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-38392 Input step implies that values are set to environment variables when they are not Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2016-09-21 at 9.03.49 AM.png Components: pipeline-input-step-plugin Created: 2016/Sep/20 11:05 PM Priority: Minor Reporter: Michael Neale referring to The help doc implies that parameter values will be set in environment variables (the captured values). This is not the case. Either the doc needs to be cleaned up or (perhaps better?) environment variables are set for parameters. Add Comment
[JIRA] (JENKINS-37779) Pipeline Config: Add support for overriding "agent" per-stage
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-37779 Pipeline Config: Add support for overriding "agent" per-stage Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38391) Administrative monitors should be more noticeable
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-38391 Administrative monitors should be more noticeable Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 2016/Sep/20 10:36 PM Priority: Minor Reporter: Daniel Beck Right now, administrative monitors are not very noticeable. They require administrators to navigate to the /manage URL, and with the hierarchical bread crumb menu, that is very easy to skip. Administrative monitors really should show up on all, or at least most, URLs for admins. Add Comment
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title Patrick Wolf commented on JENKINS-38331 Re: per stage agent directives I'm fine with this approach. It gives us a lot more room to grow instead of an every growing map that gets unwieldy. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38390) Timestamp background color white
Title: Message Title Ben Dean created an issue Jenkins / JENKINS-38390 Timestamp background color white Issue Type: Bug Assignee: Steven G Brown Attachments: console output.png Components: ansicolor-plugin, simple-theme-plugin, timestamper-plugin Created: 2016/Sep/20 9:34 PM Environment: Jenkins 2.20 timestamper-plugin 1.8.6 ansicolor-plugin 0.4.2 simple-theme-plugin 0.3 material theme 1.3.1 Priority: Minor Reporter: Ben Dean This is the theme URL I'm using: https://jenkins-contrib-themes.github.io/jenkins-material-theme/dist/material-light-blue.css Then I have a build with the timestamp and ansi color wrappers and one shell step that does this: #!/bin/bash echo "This looks terrible" echo -e "\e[31m This is red\e[0m" echo -e "\e[32m This doesn't reset" echo "The end" The attached screenshot is the build output. It does not do this with timestamper 1.8.4 (which we had previously). This seems to be related to JENKINS-34019
[JIRA] (JENKINS-38389) jenkins restart fails after installing ec2 plugin
Title: Message Title marlene cote closed an issue as Fixed retried it multiple times and then manually deleted the plugin from the filesystem and then it installed and jenkins restarted Jenkins / JENKINS-38389 jenkins restart fails after installing ec2 plugin Change By: marlene cote Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38308) Changing type of parameter isn't updating
Title: Message Title Marc Carter started work on JENKINS-38308 Change By: Marc Carter Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38389) jenkins restart fails after installing ec2 plugin
Title: Message Title marlene cote commented on JENKINS-38389 Re: jenkins restart fails after installing ec2 plugin You can close this. I was able to delete the plugin directory and reinstall it and it worked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37399) Updates to a Choice Parameter are not synchronised
Title: Message Title Danila Balaganskiy commented on JENKINS-37399 Re: Updates to a Choice Parameter are not synchronised This would be awesome, thanks a lot. Should I submit a feature request in another ticket? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38308) Changing type of parameter isn't updating
Title: Message Title Marc Carter commented on JENKINS-38308 Re: Changing type of parameter isn't updating Confirmed. The merge occurs using the name only. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38308) Changing type of parameter isn't updating
Title: Message Title Marc Carter assigned an issue to Marc Carter Jenkins / JENKINS-38308 Changing type of parameter isn't updating Change By: Marc Carter Assignee: Joel Johnson Marc Carter Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title Andrew Bayer commented on JENKINS-38331 Re: per stage agent directives Yes, it would, and yes we do want to support that. For Kubernetes...well, I don't know the config enough to say exactly what it would look like, but...similar. For just a label, the existing agent label:'foo' would still work, hopefully. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37399) Updates to a Choice Parameter are not synchronised
Title: Message Title Marc Carter commented on JENKINS-37399 Re: Updates to a Choice Parameter are not synchronised I didn't implement any of the complex stuff - choices sync from template. Apologies for not mentioning it. I go through the cases in the next day or two to see if there is a deterministic rule that can be applied. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36499) Migrate openid to parent pom
Title: Message Title Kristin Whetstone commented on JENKINS-36499 Re: Migrate openid to parent pom All tests are passing. I'd appreciate some reviews and eventually a merge from the plugin maintainer. There are still changes that the openid plugin maintainer will want to review. PR10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36499) Migrate openid to parent pom
Title: Message Title Kristin Whetstone updated JENKINS-36499 Jenkins / JENKINS-36499 Migrate openid to parent pom Change By: Kristin Whetstone Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38389) jenkins restart fails after installing ec2 plugin
Title: Message Title marlene cote updated an issue Jenkins / JENKINS-38389 jenkins restart fails after installing ec2 plugin Change By: marlene cote Attachment: jenkins-ec2plugin.docx Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35263) non resizable Execute Shell text filed leads to clutter in job configuration page
Title: Message Title Miro Lago commented on JENKINS-35263 Re: non resizable Execute Shell text filed leads to clutter in job configuration page Another workaround is to divide long command to multiple lines. I did it for linux execute shell and it's an acceptable sollution Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38389) jenkins restart fails after installing ec2 plugin
Title: Message Title marlene cote created an issue Jenkins / JENKINS-38389 jenkins restart fails after installing ec2 plugin Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Sep/20 8:49 PM Environment: centos 7 server latest jenkins Priority: Critical Reporter: marlene cote hudson.util.HudsonFailedToLoad: java.lang.NullPointerException at hudson.WebAppMain$3.run(WebAppMain.java:244) Caused by: java.lang.NullPointerException at hudson.plugins.ec2.EC2Cloud.createCredentialsProvider(EC2Cloud.java:599) at hudson.plugins.ec2.EC2Cloud.createCredentialsProvider(EC2Cloud.java:584) at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:620) at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:166) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:149) at hudson.plugins.ec2.EC2Computer.describeInstance(EC2Computer.java:107) at hudson.plugins.ec2.EC2Computer.getUptime(EC2Computer.java:133) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:104) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:85) at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:43) at hudson.slaves.SlaveComputer$4.run(SlaveComputer.java:725) at hudson.model.Queue._withLock(Queue.java:1303) at hudson.model.Queue.withLock(Queue.java:1180) at hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:722) at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:118) at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:44) at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:186) at hudson.model.Queue._withLock(Queue.java:1303) at hudson.model.Queue.withLock(Queue.java:1180) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:169)
[JIRA] (JENKINS-38388) Can't mock Jenkins.clouds
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-38388 Can't mock Jenkins.clouds Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: core Created: 2016/Sep/20 8:39 PM Priority: Minor Reporter: Kanstantsin Shautsou Tried to write tests for NodeProvisioningStrategy and found that it impossible to mock cloud list. Simple fix is provide getter method. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title Patrick Wolf commented on JENKINS-38331 Re: per stage agent directives Would this also let us incorporate what docker args as requested in PR-17 ? Do we want to support docker args? What would this look like with a Kubernetes Pod? What would this look like with just a node label? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38301) Add configuration for admin monitors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38301 Re: Add configuration for admin monitors Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/PluginManager.java core/src/main/java/hudson/PluginWrapper.java core/src/main/java/hudson/diagnosis/NullIdDescriptorMonitor.java core/src/main/java/hudson/diagnosis/ReverseProxySetupMonitor.java core/src/main/java/hudson/diagnosis/TooManyJobsButNoView.java core/src/main/java/hudson/model/UpdateCenter.java core/src/main/java/hudson/node_monitors/MonitorMarkedNodeOffline.java core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/java/jenkins/diagnostics/CompletedInitializationMonitor.java core/src/main/java/jenkins/diagnostics/SecurityIsOffMonitor.java core/src/main/java/jenkins/management/AdministrativeMonitorsConfiguration.java core/src/main/java/jenkins/model/DownloadSettings.java core/src/main/java/jenkins/security/s2m/AdminCallableMonitor.java core/src/main/java/jenkins/security/s2m/MasterKillSwitchWarning.java core/src/main/resources/hudson/Messages.properties core/src/main/resources/hudson/diagnosis/Messages.properties core/src/main/resources/hudson/model/Messages.properties core/src/main/resources/hudson/node_monitors/Messages.properties core/src/main/resources/hudson/triggers/Messages.properties core/src/main/resources/jenkins/diagnostics/Messages.properties core/src/main/resources/jenkins/management/AdministrativeMonitorsConfiguration/config.groovy core/src/main/resources/jenkins/management/AdministrativeMonitorsConfiguration/config.properties core/src/main/resources/jenkins/model/Messages.properties core/src/main/resources/jenkins/security/s2m/Messages.properties http://jenkins-ci.org/commit/jenkins/123d22493107ef29e14ef26acc2974c918f93657 Log: Merge pull request #2546 from daniel-beck/configurable-admin-monitors [FIX JENKINS-38301] Add configuration for disabling admin monitors Compare: https://github.com/jenkinsci/jenkins/compare/38de41d14296...123d22493107 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title
Andrew Bayer commented on JENKINS-38331
Re: per stage agent directives
So fyi, I'm going to take advantage of this opportunity (and the fact that GroovyStep is close to landing, which will allow me to implement the pluggable agent backend) to completely revisit what the agent config looks like. The map approach is going to become unwieldy very quickly, so I think something more like:
agent {
docker {
label "foo"
image "ubuntu"
}
}
...would be preferable. This would ideally still have backwards compatibility for the existing possible configurations. Thoughts?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38284) Handle per-stage configuration in declarative
Title: Message Title
Andrew Bayer commented on JENKINS-38284
Re: Handle per-stage configuration in declarative
So what I'm thinking right now, due to the complexity of what could be configured and the fact that the configuration has to be separate from the actual steps (since we just execute that closure at runtime, which wouldn't work at all if config directives were mixed up in the steps closure), is something like this:
stage('foo') {
config {
agent docker:'foo'
notifications {
always {
echo "something or other"
}
}
}
steps {
sh "./do-something.sh"
}
}
We'd still support the no-per-stage-config syntax (i.e., steps as the only things in the stage block) - that may be a pain to do in practice, so it's possible we'll end up adding the above as a new config section called, like, stageWithConfig or something along those lines.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33704) Multiple calls to the CloudRetentionStrategy when removing a node
Title: Message Title Kanstantsin Shautsou assigned an issue to stephenconnolly Jenkins / JENKINS-33704 Multiple calls to the CloudRetentionStrategy when removing a node Change By: Kanstantsin Shautsou Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort commented on JENKINS-38383 Re: StackOverflow when loading a large pipeline job Downgrading priority because it should only happen if you have to search many nodes to find one with a log. That said, there's some weirdness with the logic here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38387) no idleMinutes getter in CloudRetentionStrategy
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-38387 no idleMinutes getter in CloudRetentionStrategy Issue Type: Improvement Assignee: Kanstantsin Shautsou Components: core Created: 2016/Sep/20 7:26 PM Priority: Minor Reporter: Kanstantsin Shautsou Even if all this classes old it makes sense to provide getter for CloudRetentionStrategy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title rogerdpack commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Anybody able/getting this to work? I haven't been (user/password) using what I believe are the latest versions :| https://gist.github.com/rdp/291bda289a94eae96fc32a30e6db9497 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38383 StackOverflow when loading a large pipeline job Change By: Sam Van Oort Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38386) Can't propagate "Build when a change is pushed to BitBucket" to all branches
Title: Message Title Matias Lopez created an issue Jenkins / JENKINS-38386 Can't propagate "Build when a change is pushed to BitBucket" to all branches Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Sep/20 7:17 PM Priority: Minor Reporter: Matias Lopez Hello guys, thanks for this great plugin I'm facing the issue described in the subject: I can't set up the build trigger "Build when a change is pushed to BitBucket" from all the branches on the general view of the job, and I need to check this option branch by branch on all the jobs The other problem is that, when you change something on the general view for all the branches, disables the "Build when a change is pushed to BitBucket" option since it doesn't register it for the general view. Is there any way to at least avoid the uncheck of the option on the branches? Any chance to include the trigger "Build when a change is pushed to BitBucket" to the general view? Thanks a lot! Add Comment
[JIRA] (JENKINS-8028) Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success.
Title: Message Title ye shengfei commented on JENKINS-8028 Re: Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success. Daniel Beck Oh my god! It really works! so amazing!!! you are my god It depressed me nearly a week Orz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8028) Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success.
Title: Message Title ye shengfei edited a comment on JENKINS-8028 Re: Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success. [~danielbeck] Oh my god! It really works! so amazing!!! you are my godIt depressed me nearly a week thanks a lot. Orz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38227) Allow letting CMake choose the generator
Title: Message Title Martin Weber closed an issue as Fixed Jenkins / JENKINS-38227 Allow letting CMake choose the generator Change By: Martin Weber Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders Uh... I'm confused by your response with instructions on how to check the console. My previous comment explained that I did check the console and it flashed a 400 error which I captured into an image which is attached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38385) Input Steps Outside Block-Scoped Stages Do Not Show Notifications
Title: Message Title
Sam Van Oort created an issue
Jenkins / JENKINS-38385
Input Steps Outside Block-Scoped Stages Do Not Show Notifications
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2016/Sep/20 6:15 PM
Priority:
Minor
Reporter:
Sam Van Oort
To reproduce:
stage ('sample') {
echo 'do something'
}
input 'I am invisible'
Run the above build, you will not see a popup for the input step, because it's not attached to a stage. To solve this, we need to attach any in-progress input steps from the run to the last stage so notifications are visible. May require some custom logic in the ChunkVisitor on the atomNode.
Add Comment
[JIRA] (JENKINS-34013) Errors after upgrading Jenkins from "1.0" to 2.0-beta-2
Title: Message Title
Brian Wilson edited a comment on JENKINS-34013
Re: Errors after upgrading Jenkins from "1.0" to 2.0-beta-2
My RHEL5 Linux, Jenkins 2.23 revision, has this same issue. Does anyone know what context path (Line 8) is being referred to or how to eliminate this warning? 1 Running from: /data/jenkins/jenkins.war 2 webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") 3 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info 4 INFO: Logging initialized @811ms 5 Sep 20, 2016 1:59:15 PM winstone.Logger logInternal 6 INFO: Beginning extraction from war file 7 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog warn 8 WARNING: Empty contextPath 9 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info 10 INFO: jetty-9.2.z-SNAPSHOT 11 Sep 20, 2016 1:59:16 PM org.eclipse.jetty.util.log.JavaUtilLog info 12 INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet 13 Jenkins home directory: /data/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME") 14 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 15 INFO: Started w.@3c77d488{/,file:/data/jenkins/war/,AVAILABLE}{/data/jenkins/war} 16 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 17 INFO: Started ServerConnector@470734c3{HTTP/1.1}{0.0.0.0:8080} 18 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 19 INFO: Started @2777ms
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-34013) Errors after upgrading Jenkins from "1.0" to 2.0-beta-2
Title: Message Title
Brian Wilson commented on JENKINS-34013
Re: Errors after upgrading Jenkins from "1.0" to 2.0-beta-2
My RHEL5 Linux, Jenkins 2.23 revision, has this same issue. Does anyone know what context path is being referred to or how to eliminate this warning? 1 Running from: /data/jenkins/jenkins.war 2 webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") 3 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info 4 INFO: Logging initialized @811ms 5 Sep 20, 2016 1:59:15 PM winstone.Logger logInternal 6 INFO: Beginning extraction from war file 7 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog warn 8 WARNING: Empty contextPath 9 Sep 20, 2016 1:59:15 PM org.eclipse.jetty.util.log.JavaUtilLog info 10 INFO: jetty-9.2.z-SNAPSHOT 11 Sep 20, 2016 1:59:16 PM org.eclipse.jetty.util.log.JavaUtilLog info 12 INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet 13 Jenkins home directory: /data/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME") 14 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 15 INFO: Started w.@3c77d488 {/,file:/data/jenkins/war/,AVAILABLE} {/data/jenkins/war} 16 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 17 INFO: Started ServerConnector@470734c3 {HTTP/1.1} {0.0.0.0:8080} 18 Sep 20, 2016 1:59:17 PM org.eclipse.jetty.util.log.JavaUtilLog info 19 INFO: Started @2777ms
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-38384) Show notification when can't approve an input step
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38384 Show notification when can't approve an input step Change By: Sam Van Oort Labels: ux Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38384) Show notification when can't approve an input step
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-38384 Show notification when can't approve an input step Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2016/Sep/20 6:07 PM Priority: Minor Reporter: Sam Van Oort 1. Create an input step with a limited list of submitters in my pipeline 2. Attempt to approve the pipeline as a user not allowed to 3. Input step won't accept submission, but won't display a notification that you're not an allowed user either Add Comment
[JIRA] (JENKINS-38340) Jenkins cannot handle redirects from http to https URLs in update sites
Title: Message Title Daniel Beck commented on JENKINS-38340 Re: Jenkins cannot handle redirects from http to https URLs in update sites JENKINS-32796 and JENKINS-8028 are not actually related issues, but comments have been posted to those issues about this particular problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38340) Jenkins cannot handle redirects from http to https URLs in update sites
Title: Message Title Daniel Beck commented on JENKINS-38340 Re: Jenkins cannot handle redirects from http to https URLs in update sites Related comments in JENKINS-32796 as well, but not adding anything new. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32796) Can't update plugins: incorrect checksum
Title: Message Title Daniel Beck commented on JENKINS-32796 Re: Can't update plugins: incorrect checksum Tracking this as JENKINS-38340, which I've rewritten to address the actual issue (at least as far as I currently understand it). Please refrain from posting further comments here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38340) Jenkins cannot handle redirects from http to https URLs in update sites
Title: Message Title Daniel Beck commented on JENKINS-38340 Re: Jenkins cannot handle redirects from http to https URLs in update sites Useful comments in JENKINS-8028. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8028) Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success.
Title: Message Title Daniel Beck resolved as Cannot Reproduce Resolving again, let's track the "Chinese HTTPS mirror" issue in JENKINS-38340. Jenkins / JENKINS-8028 Plugin update installer downloads "302 redirect" response as the .hpi file, then reports success. Change By: Daniel Beck Status: Reopened Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-38340) Jenkins cannot handle redirects from http to https URLs in update sites
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38340 Jenkins cannot handle redirects from http to https URLs in update sites Change By: Daniel Beck Summary: Update request does not recognize Jenkins cannot handle redirects from http response code(302) to https URLs in update sites Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38340) Jenkins cannot handle redirects from http to https URLs in update sites
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-38340 Jenkins cannot handle redirects from http to https URLs in update sites Change By: Daniel Beck Update request Jenkins does not recognize http response code(302) handle redirects from HTTP to HTTPS URLs in update sites . So I could not we cannot have HTTPS update my jenkins and plugins.The error stack is blew:```java.io.IOException: Downloaded file /srv/ci/jenkins/jenkins-2.7.2.war.tmp does not match expected SHA-1 sites , expected 'W4m2ln56+BGcUsfoYiO0dmVBeiI=', actual 'TWpBfQjCw6r1WAlKpmKg7XuzoGc=' at hudson.model.UpdateCenter.verifyChecksums(UpdateCenter.java:1783) at hudson.model.UpdateCenter.access$1100(UpdateCenter.java:147) at hudson.model.UpdateCenter$HudsonUpgradeJob.replace(UpdateCenter.java:2069) at hudson.model.UpdateCenter$UpdateCenterConfiguration.install(UpdateCenter.java:1178) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1653) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1624) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745)```and I `cat` the file `/srv/ci/jenkins/jenkins-2.7.2.war.tmp`, it is:```302 FoundFoundThe document has moved here.```redirect from `mirrors.jenkins-ci.org/updates/current/ as all URLs in update-center.json ` to `https://mirrors are HTTP . tuna.tsinghua.edu.cn/jenkins/updates/current/update-center.json` The error stack is deceptive. Add Comment
[JIRA] (JENKINS-37835) Developer can remove items from the queue
Title: Message Title Cliff Meyers updated JENKINS-37835 Jenkins / JENKINS-37835 Developer can remove items from the queue Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort commented on JENKINS-38383 Re: StackOverflow when loading a large pipeline job Problem is here: we're doing a recursive call to get the logs - https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L478 Needs to be rewritten as a while(...) loop with the current search candidate inside the loop. However I understand that Jesse Glick is doing some significant rewrites of log storage at the moment, so I'll hold off touching the code to avoid collisions. Side note, this is explicitly a "don't do that" in my recent Jenkins World talk :-P Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38383 StackOverflow when loading a large pipeline job Change By: Oleg Nenashev Attachment: InfinitePipeline.zip Attachment: log.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title
Oleg Nenashev created an issue
Jenkins / JENKINS-38383
StackOverflow when loading a large pipeline job
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
InfinitePipeline.zip, log.txt
Components:
pipeline
Created:
2016/Sep/20 5:51 PM
Environment:
all-latest
Labels:
stackoverflow
Priority:
Critical
Reporter:
Oleg Nenashev
I've been using infinite Pipeline for a demo. The job was running for a couple of hours, and then Jenkins master declined to the build due to the StackOverflow.
node {
int i = 0;
while(true) {
sh "echo 'Hello, world ${i}!'"
sh "sleep 5"
i = i + 1;
}
}
Log: See attachment
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mark Waite commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Sorry, no progress yet. It will arrive in the git plugin eventually, since I want access to those environment variables as part of my testing of the git plugin (and git client plugin). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37523) New Item page shows "field cannot be empty" error when attempting to create a duplicate item
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37523 Re: New Item page shows "field cannot be empty" error when attempting to create a duplicate item Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java src/test/java/core/CreateItemTest.java http://jenkins-ci.org/commit/acceptance-test-harness/b77caa669998e449cdd44794030be3fcc1a9ca4b Log: Merge pull request #175 from kzantow/master JENKINS-37523 - wrong message displayed for duplicate item name Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/27343783ba00...b77caa669998 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37523) New Item page shows "field cannot be empty" error when attempting to create a duplicate item
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37523 Re: New Item page shows "field cannot be empty" error when attempting to create a duplicate item Code changed in jenkins User: kzantow Path: src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java src/test/java/core/CreateItemTest.java http://jenkins-ci.org/commit/acceptance-test-harness/fc1c99575bd215a0a1fcbf7f06ebcfa00fb30ec9 Log: JENKINS-37523 - wrong message displayed for duplicate item name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Christian Stewart commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Were there any updates on this? How can I determine, for example, the branch Jenkins built? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36984) Add Support environment variables for consul-kv-builder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36984 Re: Add Support environment variables for consul-kv-builder plugin Code changed in jenkins User: Jimmy Ray Path: src/main/java/org/jenkinsci/plugins/consulkv/ConsulKVBuilder.java http://jenkins-ci.org/commit/consul-kv-builder-plugin/87dd8bb69261546f135d79d804c5a645609edeee Log: Merge pull request #1 from anoppe/master JENKINS-36984 added support for environment variables in configurab… Compare: https://github.com/jenkinsci/consul-kv-builder-plugin/compare/90c42ae26336...87dd8bb69261 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36984) Add Support environment variables for consul-kv-builder plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36984 Re: Add Support environment variables for consul-kv-builder plugin Code changed in jenkins User: Auke Noppe Path: src/main/java/org/jenkinsci/plugins/consulkv/ConsulKVBuilder.java http://jenkins-ci.org/commit/consul-kv-builder-plugin/428f3090a712a896a1f1cc2cf897f20f264e9499 Log: JENKINS-36984 added support for environment variables in configurable attributes. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36792) Jenkins Fails To Start After Update
Title: Message Title Patrick Dayton assigned an issue to Patrick Dayton Jenkins / JENKINS-36792 Jenkins Fails To Start After Update Change By: Patrick Dayton Assignee: Patrick Dayton Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38277) The webhook registration didn't register the push hook
Title: Message Title Jesse Glick commented on JENKINS-38277 Re: The webhook registration didn't register the push hook github-organization-folder automatically registers webhooks on organization folders; currently not on multibranch projects (single repositories). Future enhancement. Anyway Blue Ocean provides a different UI for setting up webhooks. Probably will not fix as currently reported. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38277) The webhook registration didn't register the push hook
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38277 The webhook registration didn't register the push hook Change By: Jesse Glick Component/s: github-branch-source-plugin Component/s: github-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-23666 Inject environment variables build step uses the wrong property file Change By: Oleg Nenashev Labels: envinject-2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Title: Message Title Oleg Nenashev commented on JENKINS-23666 Re: Inject environment variables build step uses the wrong property file It is a breaking change even if it's correct. I'm fine with changing the default resolution order in EnvInject 2.x (to be released soon), but maybe we want to retain the original behavior as configurable option. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23666) Inject environment variables build step uses the wrong property file
Title: Message Title Oleg Nenashev started work on JENKINS-23666 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36570) Implement pipeline compatibility
Title: Message Title
Timothy Clarke edited a comment on JENKINS-36570
Re: Implement pipeline compatibility
A little digging through logs, and taking a "how to get it working with, even if not fully supported" approach. It looks like flyweight tasks are getting prioritised as per rules in http://jenkins_host:8080/jenkins/advanced-build-queue/Heavy weight tasks on the other hand (where prioritisation would be really useful) look to be hitting [PriorityConfiguration.java#L211 -L216 |https://github.com/jenkinsci/priority-sorter-plugin/blob/master/src/main/java/jenkins/advancedqueue/PriorityConfiguration.java#L211 -L216 ] and so getting assigned a default value. Can we ease {code}if (!(item.task instanceof Job)) {{code}That way we could atleast add filters to re-prioritise
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
