[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Actually it works if I revert back to JNLP-2. Is there any pointers I could look at that would block JNLP-4 inside kubernetes? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47793) Jenkins master and agent configuration pages do not verify negative executor numbers
Title: Message Title Stefan Drissen commented on JENKINS-47793 Re: Jenkins master and agent configuration pages do not verify negative executor numbers The change in war/src/main/webapp/scripts/hudson-behavior.js has introduced JENKINS-49520. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Stefan Drissen commented on JENKINS-49520 Re: Log rotator: empty values decorated with 'Not a positive integer' I am fairly sure that Jenkins-47793 introduced the issue, the pipe (|) was removed rendering blank an invalid value: https://github.com/ksenia-nenasheva/jenkins/commit/f8e3526244af53178439b9a73e1297cf3f7f5ce4#diff-da911448bbb85d374f604da9c1e00136 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Stefan Drissen edited a comment on JENKINS-49520 Re: Log rotator: empty values decorated with 'Not a positive integer' I am fairly sure that Jenkins JENKINS -47793 introduced the issue, the pipe (|) was removed rendering blank an invalid value:[https://github.com/ksenia-nenasheva/jenkins/commit/f8e3526244af53178439b9a73e1297cf3f7f5ce4#diff-da911448bbb85d374f604da9c1e00136] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49522) [withCredentials] MissingPropertyException from shared library class
Title: Message Title
Ann Beeskau created an issue
Jenkins / JENKINS-49522
[withCredentials] MissingPropertyException from shared library class
Issue Type:
Bug
Assignee:
Stephen Connolly
Components:
credentials-binding-plugin, credentials-plugin
Created:
2018-02-13 07:13
Priority:
Major
Reporter:
Ann Beeskau
I am instantiating an object from within my vars (custom step (testCredentials)) shared library. I then execute a method (getRequiredPackages) on this instance that contains withCredentials step. A groovy.lang.MissingPropertyException is thrown on the withCredentials variable (see stack trace below) vars/testCredentials.groovy
#!/usr/bin/env groovy
import com.mycorp.deployment.classes.Source
def call(body) {
def config = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = config
body()
def sourceVersion = config.version
timestamps {
node() {
try {
stage('Test Credentials') {
Source buildToolsSource = new Source(steps, sourceVersion)
buildToolsSource.getRequiredPackages(steps)
}
} catch (e) {
steps.sh "echo 'Error (${e}) occurred marking the build as failure.'"
throw e
} finally {
steps.cleanWs()
}
}
}
}
Groovy class /src/com/mycorp/deployment/classes/Source.groovy
#!/usr/bin/env groovy
package com.mycorp.deployment.classes
import
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Bing Shiao commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Found couple issues with pipeline-maven-plugin-3.3.1-beta-2: I had to turn on PipelineGraphPublisher (this may not be an issue for most people, but we don't use this publisher) In http://localhost:8080/configureTools/, Maven Linker Publisher is missing Disabled checkbox. Unable to disable it. Here is my test https://gist.github.com/bingshiao/8218b5a41573a61ab2456e3e96065b78 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title
Erik Jonsson updated an issue
Jenkins / JENKINS-49508
warnings-plugin aborts if unable to git-blame.
Change By:
Erik Jonsson
The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.In my source project some .c-files are generated, obviously these will not be in git.There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings. {noformat}...End of build script[WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc) Using GitBlamer to create author and commit information for all warnings. GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm> git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^{commit} # timeout=10 No blame results for request . No blame results for request . No blame results for request . c - [132, 2126]> . . No blame results for request sleipnir fader21 /flasm/generated/asm.lex.c - [ 16174 37726 ]>. No blame results for request thor fader23 /flasm/generated/asm.lex.c - [ 10090 69737 ]>. ... Build step 'Console output (build log) parsing' changed build result to ABORTED[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sWarning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredFinished: ABORTED{noformat}
Add Comment
This message was sent by Atlassian
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Erik Jonsson commented on JENKINS-49508 Re: warnings-plugin aborts if unable to git-blame. Yes, it's now updated. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title
Erik Jonsson updated an issue
Jenkins / JENKINS-49508
warnings-plugin aborts if unable to git-blame.
Change By:
Erik Jonsson
The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.In my source project some .c-files are generated, obviously these will not be in git.There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings. {noformat} ...End of build script[WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc) Using GitBlamer to create author and commit information for all warnings. GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm> git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^ \ {commit} # timeout=10 No blame results for request . No blame results for request . No blame results for request . No blame results for request . No blame results for request Build step 'Console output (build log) parsing' changed build result to ABORTED[BFA] Scanning build for known causes...[BFA] No failure causes found[BFA] Done. 0sWarning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredFinished: ABORTED {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49490) Failed to run AVD creation on MAC
Title: Message Title theexplorer commented on JENKINS-49490 Re: Failed to run AVD creation on MAC Thanks for the quick response Christopher Orr Getting error in case of "show emulator window" Warning: File /Users/Shared/Jenkins/Home/workspace/emulator_of_jenkins/.android/repositories.cfg could not be loaded. [android] Using Android SDK: /Users/sumit.kathuria/Library/Android/sdk $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb start-server daemon not running; starting now at tcp:5844 daemon started successfully $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb start-server [android] Starting Android emulator $ /Users/sumit.kathuria/Library/Android/sdk/emulator/emulator -skin 320x480 -ports 5742,5743 -report-console tcp:5823,max=60 -prop persist.sys.language=en -prop persist.sys.country=US -avd hudson_en-US_160_HVGA_android-24_google_apis-x86 _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL. PasteBoard: Error creating pasteboard: com.apple.pasteboard.clipboard [-4960] PasteBoard: Error creating pasteboard: com.apple.pasteboard.find [-4960] [android] Emulator did not appear to start; giving up [android] Stopping Android emulator $ /Users/sumit.kathuria/Library/Android/sdk/platform-tools/adb kill-server Finished: NOT_BUILT Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...'
Title: Message Title Mirko Streckenbach commented on JENKINS-49413 Re: IllegalArgumentException : Cannot relativize '...' relatively to ...' Cyrille Le Clerc I have a very similar exception that is not caused by paths outside of the jenkins workspace, but occurs when building a project in a subdirectory. Should I add more details here or open a new issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title Dariusz Kordonski commented on JENKINS-41488 Re: Pipeline view automatically scrolls down James Dumay hello We are on Blue Ocean 1.4.1, on a red build I still get the auto-scrolled to the stage and step that has failed. I'd argue that the behaviour by default should be the same, just land the user on the pipeline overview (top of the page) and let them scroll to the failed step(s) themselves. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49467) Jenkins credential issue
Title: Message Title rang cui commented on JENKINS-49467 Re: Jenkins credential issue Hi, is there any update on this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49521) Trivial rebase is not triggering build
Title: Message Title Graham Burgess created an issue Jenkins / JENKINS-49521 Trivial rebase is not triggering build Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-02-12 23:48 Environment: System Properties awt.toolkit sun.awt.X11.XToolkit buildInfoConfig.propertiesFile /home/jenkins/workspace/cis-service-pipeline/store-api@tmp/buildInfo5493927621661894740.properties executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.remoting.ClassFilter org.jfrog.build.client.DeployDetails,org.jfrog.build.api.Artifact,org.jfrog.build.api.BaseBuildFileBean,org.jfrog.build.api.BaseBuildBean java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-8-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_151-8u151-b12-1~deb9u1-b12 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_151 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.151-b12 javax.accessibility.assistive_technologies org.GNOME.Accessibility.AtkWrapper jna.loaded true jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib jnidispatch.path /tmp/jna--1712433994/jna6351830107150667593.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 4.9.0-3-amd64 path.separator : sun.arch.data.model 64 sun.boot.class.path
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title Ulli Hafner commented on JENKINS-49508 Re: warnings-plugin aborts if unable to git-blame. Do you also have that part of the log that shows that the build is aborted? The log currently shows only some warnings. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49508) warnings-plugin aborts if unable to git-blame.
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-49508
warnings-plugin aborts if unable to git-blame.
Change By:
Ulli Hafner
The warnings-plugin will abort the build if it's unable to git-blame on the reported lines.In my source project some .c-files are generated, obviously these will not be in git.There must be some way to skip the blame-step or at least not abort the build if the plugin is unable to parse some of the warnings. {noformat}Using GitBlamer to create author and commit information for all warnings. GIT_COMMIT=6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6, workspace=/repo/bbiswjenk/fem023-eiffel003/workspace/instanttoolsmith_flasm> git rev-parse 6c3c3da9609eb7a9907bdb4a3b3806f90a97f6e6^\{commit} # timeout=10 No blame results for request . No blame results for request . No blame results for request . No blame results for request . {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49520
Log rotator: empty values decorated with 'Not a positive integer'
Change By:
Stefan Drissen
Since (I think) the last update from 2.104 to 2.105 something has changed in validation of integer fields resulting in the 'discard builds' section of a freestyle job showing validation warning 'Not a positive integer'. Probably a result of changes made in JENKINS-47793 !image-2018-02-13-00-14-48-787.png!Empty values are (and always have been) stored as -1.{code:java} -1 20 -1 -1{code} Changing the value to a positive integer clears the validation warning, but emptying it returns the warning.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49520
Log rotator: empty values decorated with 'Not a positive integer'
Change By:
Stefan Drissen
Since (I think) the last update from 2.104 to 2.105 something has changed in validation of integer fields resulting in the 'discard builds' section of a freestyle job showing validation warning 'Not a positive integer'. Probably a result of changes made in JENKINS-47793 !image-2018-02-13-00-14-48-787.png!Empty values are (and always have been) stored as -1. {code :java } -1 20 -1 -1{code} Changing the value to a positive integer clears the validation warning, but emptying it returns the warning.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-49517) Supporting Merge requests on a multibranch pipeline
Title: Message Title Owen Mehegan closed an issue as Duplicate Jenkins / JENKINS-49517 Supporting Merge requests on a multibranch pipeline Change By: Owen Mehegan Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49517) Supporting Merge requests on a multibranch pipeline
Title: Message Title Owen Mehegan commented on JENKINS-49517 Re: Supporting Merge requests on a multibranch pipeline We track issues for gitlab-plugin in GitHub (ironically...), and this issue has already been raised. Please follow https://github.com/jenkinsci/gitlab-plugin/issues/704 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title
Stefan Drissen updated an issue
Jenkins / JENKINS-49520
Log rotator: empty values decorated with 'Not a positive integer'
Change By:
Stefan Drissen
Since (I think) the last update from 2.104 to 2.105 something has changed in validation of integer fields resulting in the 'discard builds' section of a freestyle job showing validation warning 'Not a positive integer'.!image-2018-02-13-00-14-48-787.png! Empty values are (and always have been) stored as -1. {code} -1 20 -1 -1{code} Changing the value to a positive integer clears the validation warning, but emptying it returns the warning.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Stefan Drissen created an issue Jenkins / JENKINS-49520 Log rotator: empty values decorated with 'Not a positive integer' Issue Type: Bug Assignee: Unassigned Attachments: image-2018-02-13-00-14-48-787.png Components: core Created: 2018-02-12 23:15 Environment: Windows 2012R2 x64 JRE 1.8_0161 x64 Jenkins 2.105 Priority: Minor Reporter: Stefan Drissen Since (I think) the last update from 2.104 to 2.105 something has changed in validation of integer fields resulting in the 'discard builds' section of a freestyle job showing validation warning 'Not a positive integer'. Empty values are stored as -1. Changing the value to a positive integer clears the validation warning, but emptying it returns the warning. Add Comment
[JIRA] (JENKINS-49519) Limit the amount of analytics data being collected
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-49519
Limit the amount of analytics data being collected
Issue Type:
New Feature
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-02-12 23:05
Priority:
Minor
Reporter:
James Dumay
We need a method to limit the amount of analytics data being collected. This config kept on jenkins.io. It expresses that there are 1000 cohorts, of which 10 are active (1% of the Jenkins server install base).
{
"cohorts": 1000,
"activeCohorts": [
"0-9"
]
}
The server will decide based on its server identity if it is enrolled into the range 0-9 or not
Add Comment
[JIRA] (JENKINS-49519) Limit the amount of analytics data being collected
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49519 Limit the amount of analytics data being collected Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-49482
Re: Hide empty 'Deployed Artifacts:'
[~bingshiao] can you please retrigger the builds? We had a glitch in 3.3.0 where the list of deployed artifacts was not persisted, due to this, they disappeared upon restart.Can you please retrigger a job and see the if the list of deployed artifacts appears?Here is my test with the pipeline-maven-plugin as yo udid{code:java}node {stage ('build') {withMaven (maven: 'maven-3.5.2') {git 'https://github.com/jenkinsci/pipeline-maven-plugin.git'// TODO Replace the value of -DaltDeploymentRepository by your Maven repositorysh "mvn clean source:jar install deploy -DskipTests -DaltDeploymentRepository=nexus.beescloud.com::default::https://nexus.beescloud.com/content/repositories/snapshots/"}}}{code}!https://snag.gy/RkmwHi.jpg |width=400 ! !https://snag.gy/5NRpyj.jpg|width=400!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title
Cyrille Le Clerc commented on JENKINS-49482
Re: Hide empty 'Deployed Artifacts:'
Bing Shiao can you please retrigger the builds? We had a glitch in 3.3.0 where the list of deployed artifacts was not persisted, due to this, they disappeared upon restart. Can you please retrigger a job and see the if the list of deployed artifacts appears? Here is my test with the pipeline-maven-plugin as yo udid
node {
stage ('build') {
withMaven (maven: 'maven-3.5.2') {
git 'https://github.com/jenkinsci/pipeline-maven-plugin.git'
// TODO Replace the value of -DaltDeploymentRepository by your Maven repository
sh "mvn clean source:jar install deploy -DskipTests -DaltDeploymentRepository=nexus.beescloud.com::default::https://nexus.beescloud.com/content/repositories/snapshots/"
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31803) Pipeline support for TFS plugin
Title: Message Title Andrew Gray commented on JENKINS-31803 Re: Pipeline support for TFS plugin @Kellie Jos could you please provide an update Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31096) Unicode characters in console logs do not print correctly in Workflow builds
Title: Message Title Jesse Glick updated JENKINS-31096 Jenkins / JENKINS-31096 Unicode characters in console logs do not print correctly in Workflow builds Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Hans Kristian Flaatten commented on JENKINS-49278 Re: cat command in docker agents not detected correctly JENKINS-41316 is the root cause of this error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Hans Kristian Flaatten commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
The 1.15 release really screwed up all of our builds involving containers. Reverted to 1.14.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47022) DropDown is loosing focus on selection of an option
Title: Message Title Nicolae Pascu updated JENKINS-47022 Jenkins / JENKINS-47022 DropDown is loosing focus on selection of an option Change By: Nicolae Pascu Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47386) Audit tooltips for icons
Title: Message Title Nicolae Pascu updated JENKINS-47386 Jenkins / JENKINS-47386 Audit tooltips for icons Change By: Nicolae Pascu Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44995) Very slow activity/pipeline screen load (often when logged in)
Title: Message Title Vivek Pandey assigned an issue to Nicolae Pascu Jenkins / JENKINS-44995 Very slow activity/pipeline screen load (often when logged in) Change By: Vivek Pandey Assignee: Vivek Pandey Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44995) Very slow activity/pipeline screen load (often when logged in)
Title: Message Title Vivek Pandey assigned an issue to Vivek Pandey Jenkins / JENKINS-44995 Very slow activity/pipeline screen load (often when logged in) Change By: Vivek Pandey Assignee: Josh McDonald Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Andrew Bayer assigned an issue to Stephen Connolly Jenkins / JENKINS-48571 checkout scm fails silently after "Could not determine exact tip revision of " in logs Change By: Andrew Bayer Assignee: Andrew Bayer Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Bing Shiao updated an issue Jenkins / JENKINS-49482 Hide empty 'Deployed Artifacts:' Change By: Bing Shiao Attachment: build-1-pipeline-maven-plugin-3.3.0.log Attachment: build-2-pipeline-maven-plugin-3.3.1-beta-2.log Attachment: pipeline-maven-plugin-3.3.0.log Attachment: pipeline-maven-plugin-3.3.1-beta-2.log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Bing Shiao commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Cyrille Le Clerc By upgrading from pipeline-maven-plugin-3.3.0 to pipeline-maven-plugin-3.3.1-beta-2, the artifact links disappear. Attached are debug logs and build logs of the two for reference. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48119) editing the existing declarative jenkinsfile in pipeline editor
Title: Message Title Michael Neale resolved as Cannot Reproduce open if there is more information Jenkins / JENKINS-48119 editing the existing declarative jenkinsfile in pipeline editor Change By: Michael Neale Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-48119) editing the existing declarative jenkinsfile in pipeline editor
Title: Message Title Michael Neale commented on JENKINS-48119 Re: editing the existing declarative jenkinsfile in pipeline editor Need to get a har/console error log for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title Michael Neale resolved as Won't Fix A 'won't fix' as the problem will be solved by not using the JIRA plugin as it is. Jenkins / JENKINS-48204 NPE in BlueOcean REST API / JIRA interaction Change By: Michael Neale Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title Michael Neale stopped work on JENKINS-48204 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title Michael Neale commented on JENKINS-48204 Re: NPE in BlueOcean REST API / JIRA interaction I think the solution for this is for the JIRA plugin to be worked over one way or another, so the problem categorically goes away. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45634) Table action buttons hidden until hover
Title: Message Title James Dumay assigned an issue to Nicolae Pascu Jenkins / JENKINS-45634 Table action buttons hidden until hover Change By: James Dumay Assignee: James Dumay Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48119) editing the existing declarative jenkinsfile in pipeline editor
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48119 editing the existing declarative jenkinsfile in pipeline editor Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48027 Blue Ocean dashboard showing no Pipelines Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48277) Clicking on a pipeline name should default to branch tab instead of activity
Title: Message Title James Dumay resolved as Won't Do Jenkins / JENKINS-48277 Clicking on a pipeline name should default to branch tab instead of activity Change By: James Dumay Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49419) Avoid detached head on checkout
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49419 Avoid detached head on checkout Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48204 NPE in BlueOcean REST API / JIRA interaction Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49518) Directory is not created anymore
Title: Message Title
Christof Dallermassl updated an issue
Jenkins / JENKINS-49518
Directory is not created anymore
Change By:
Christof Dallermassl
After reinstallation of jenkins I ended up with version 1.13 of the publish-over-ftp plugin (not sure, which version I had before, probably 1.12). I did not change the jenkins config (ftp host) nor the jenkins tasks. Behaviour before update: The remote directory was created on the ftp serverBehaviour after: The remote directory is not created anymore and the file cannot be uploaded. Log of working jenkins task (before update of jenkins):{noformat}FTP: Connecting from host [2ea2fa14881a]FTP: Connecting with configuration [ftp.xxx.at] ...220 connected to ftp.xxx.at...FTP: Logging in, command printing disabledFTP: Logged in, command printing enabledCWD /foo/bar/Upload250 CWD command successful.TYPE I200 Type set to I.CWD /foo/bar/Upload250 CWD command successful.CWD db_dump_2018-02-03_1056550MKD db_dump_2018-02-03_1056257 "db_dump_2018-02-03_1056" directory created.CWD db_dump_2018-02-03_1056250 CWD command successful.PASV227 Entering Passive Mode (85,124,186,100,198,35).STOR backup_latest.pgdump125 Data connection already open; Transfer starting.226 Transfer complete.FTP: Disconnecting configuration [ftp.xxx.at] ...FTP: Transferred 1 file(s)Finished: SUCCESS{noformat}WIth the current plugin the log of the same jenkins task looks like:{noformat}FTP: Connecting from host [0dfc1108da61]FTP: Connecting with configuration [ftp.xxx.at] ...220 connected to ftp.xxx.at...FTP: Logging in, command printing disabledFTP: Logged in, command printing enabledCWD /foo/bar/Upload250 CWD command successful.TYPE I200 Type set to I.CWD /foo/bar/Upload250 CWD command successful.CWD db_dump_2018-02-10_1056FTP: Disconnecting configuration [ftp.xxx.at] ...ERROR: Exception when publishing, exception message [Exception when changing to FTP directory [db_dump_2018-02-10_1056]]Build step 'Send build artifacts over FTP' changed build result to UNSTABLE{noformat}What is missing is the{noformat}MKD db_dump_2018-02-03_1056{noformat}part now!My global ftp server config contains the base directory /foo/bar/UploadThe jenkins ftp upload task has the remote directory set to "'db_dump_'-MM-dd_hhmm" with the "Remote directory is a date format" checked in Advanced config. Testing with manual ftp trying to find out if the server has changed its behaviour - "cd not_existing_directory" returned an error code 550, but did not close the ftp connection.
[JIRA] (JENKINS-49518) Directory is not created anymore
Title: Message Title Christof Dallermassl created an issue Jenkins / JENKINS-49518 Directory is not created anymore Issue Type: Bug Assignee: Li-Wen Hsu Components: publish-over-ftp-plugin Created: 2018-02-12 21:26 Priority: Major Reporter: Christof Dallermassl After reinstallation of jenkins I ended up with version 1.13 of the publish-over-ftp plugin (not sure, which version I had before, probably 1.12). I did not change the jenkins config (ftp host) nor the jenkins tasks. Behaviour before update: The remote directory was created on the ftp server Behaviour after: The remote directory is not created anymore and the file cannot be uploaded. Log of working jenkins task (before update of jenkin s): FTP: Connecting from host [2ea2fa14881a] FTP: Connecting with configuration [ftp.xxx.at] ... 220 connected to ftp.xxx.at... FTP: Logging in, command printing disabled FTP: Logged in, command printing enabled CWD /foo/bar/Upload 250 CWD command successful. TYPE I 200 Type set to I. CWD /foo/bar/Upload 250 CWD command successful. CWD db_dump_2018-02-03_1056 550 MKD db_dump_2018-02-03_1056 257 "db_dump_2018-02-03_1056" directory created. CWD db_dump_2018-02-03_1056 250 CWD command successful. PASV 227 Entering Passive Mode (85,124,186,100,198,35). STOR backup_latest.pgdump 125 Data connection already open; Transfer starting. 226 Transfer complete. FTP: Disconnecting configuration [ftp.xxx.at] ... FTP: Transferred 1 file(s) Finished: SUCCESS WIth the current plugin the log of the same jenkins task looks like:
[JIRA] (JENKINS-48571) checkout scm fails silently after "Could not determine exact tip revision of " in logs
Title: Message Title Tristan Lewis commented on JENKINS-48571 Re: checkout scm fails silently after "Could not determine exact tip revision of " in logs The PR which worked around the issue got closed This issue is giving us a huge headache. We have a system of dozens of multibranch pipelines that are generated by a jobDSL script. Every time the jobs are re-seeded after updates to the jobDSL script, they all get into a broken state where none of them can successfully perform an SCM checkout step, manifesting with this "could not determine exact tip revision" error. I've had to create a utility job to force re-indexing all of the jobs. This resolves the jobs being in a broken state but due to how many multibranch pipeline jobs we have and how many branches each of them indexes, only about half the jobs get indexed before our git provider (BitBucket) starts rate-limiting us due to too many API requests are made from the branch indexing operations. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title pixman20 commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits The PR was merged into v2.2.8 shown here https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin as Add ability for extension plugins to modify webhook creation / update process You can build this repo and upload the jpi manually to your instance: https://github.com/pixman20/bitbucket-branch-source-configure-webhooks-plugin I haven't had time to go through the motions of publicizing that on the official plugin repo yet. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34454) Add support for Docker-Toolbox/Windows
Title: Message Title
Liam Newman edited a comment on JENKINS-34454
Re: Add support for Docker-Toolbox/Windows
There are a number of issues linked to https://issues.jenkins-ci.org/browse/JENKINS-36776. I'm trying to run the a Pipeline on a Windows machine with docker for windows installed. What I have done:# Created a windows 10 Pro VM on Azure using the "Standard D4s v3" image (which supports virtualization and Hyper-V)# Install Docker CE for Windows - This will automatically enable HyperV and reboot the VM to complete.# Changed Docker (in the taskbar icon menu) to "Switch to Windows Containers"# Install JDK 8 from Oracle# Downloaded "Jenkins WAR package"# Installed git-scm to get the git-bash command prompt# Open git-bash and run "java -jar jenkins.war" - This works around https://issues.jenkins-ci.org/browse/JENKINS-34454 by providing access to "sh" and related commands on the host.# Attempt to run the following pipeline: \ { code:groovy noformat }pipeline \ { agent \ { docker \ { image 'microsoft/nanoserver' } } stages \ { stage('Build') \ { steps \ { echo "Docker success" } } }} \ { code noformat } Result: \ { code noformat }Started by user bitwisemanReplayed #10Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in C:\Users\lnewman\.jenkins\workspace\pipeline-test[Pipeline] \ {[Pipeline] stage[Pipeline] \ { (Declarative: Agent Setup)[Pipeline] sh[C:\Users\lnewman\.jenkins\workspace\pipeline-test] Running shell script+ docker pull microsoft/nanoserverUsing default tag: latestlatest: Pulling from microsoft/nanoserverDigest: sha256:3d2948c5af9f4bece59b13f199f5bec59d6dc4930fb15aa9b6a223d2ea8d8471Status: Image is up to date for microsoft/nanoserver:latest[Pipeline] }[Pipeline] // stage[Pipeline] sh[C:\Users\lnewman\.jenkins\workspace\pipeline-test] Running shell script+ docker inspect -f . microsoft/nanoserver.[Pipeline] withDockerContainerJenkins does not seem to be running inside a container$ docker run -t -d -u 197108:197121 -w C:\Users\lnewman\.jenkins\workspace\pipeline-test -v C:\Users\lnewman\.jenkins\workspace\pipeline-test:C:\Users\lnewman\.jenkins\workspace\pipeline-test:rw,z -v C:\Users\lnewman\.jenkins\workspace\pipeline-test@tmp:C:\Users\lnewman\.jenkins\workspace\pipeline-test@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e microsoft/nanoserver cat[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Failed to run image 'microsoft/nanoserver'. Error: docker: Error response from daemon: invalid volume specification: 'C:\Users\lnewman\.jenkins\workspace\pipeline-test:C:\Users\lnewman\.jenkins\workspace\pipeline-test:rw,z'.See 'docker run --help' \ { code noformat } This indicates that it might be possible to run containers directly but the built-in docker plugin bugs are still blocking.
[JIRA] (JENKINS-28961) GET/POST with schedule-build-plugin
Title: Message Title Martin Spielmann closed an issue as Fixed Jenkins / JENKINS-28961 GET/POST with schedule-build-plugin Change By: Martin Spielmann Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34454) Add support for Docker-Toolbox/Windows
Title: Message Title
Liam Newman commented on JENKINS-34454
Re: Add support for Docker-Toolbox/Windows
There are a number of issues linked to https://issues.jenkins-ci.org/browse/JENKINS-36776. I'm trying to run the a Pipeline on a Windows machine with docker for windows installed. What I have done:
Created a windows 10 Pro VM on Azure using the "Standard D4s v3" image (which supports virtualization and Hyper-V)
Install Docker CE for Windows - This will automatically enable HyperV and reboot the VM to complete.
Changed Docker (in the taskbar icon menu) to "Switch to Windows Containers"
Install JDK 8 from Oracle
Downloaded "Jenkins WAR package"
Installed git-scm to get the git-bash command prompt
Open git-bash and run "java -jar jenkins.war" - This works around https://issues.jenkins-ci.org/browse/JENKINS-34454 by providing access to "sh" and related commands on the host.
Attempt to run the following pipeline:
{code:groovy} pipeline { agent { docker { image 'microsoft/nanoserver' } } stages { stage('Build') { steps { echo "Docker success" } } } } {code} Result: {code} Started by user bitwiseman Replayed #10 Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on Jenkins in C:\Users\lnewman\.jenkins\workspace\pipeline-test [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup) [Pipeline] sh [C:\Users\lnewman\.jenkins\workspace\pipeline-test] Running shell script + docker pull microsoft/nanoserver Using default tag: latest latest: Pulling from microsoft/nanoserver Digest: sha256:3d2948c5af9f4bece59b13f199f5bec59d6dc4930fb15aa9b6a223d2ea8d8471 Status: Image is up to date for microsoft/nanoserver:latest [Pipeline] } [Pipeline] // stage [Pipeline] sh [C:\Users\lnewman\.jenkins\workspace\pipeline-test] Running shell script + docker inspect -f . microsoft/nanoserver . [Pipeline] withDockerContainer Jenkins does not seem to be running inside a container $ docker run -t -d -u 197108:197121 -w C:\Users\lnewman\.jenkins\workspace\pipeline-test -v C:\Users\lnewman\.jenkins\workspace\pipeline-test:C:\Users\lnewman\.jenkins\workspace\pipeline-test:rw,z -v C:\Users\lnewman\.jenkins\workspace\pipeline-test@tmp:C:\Users\lnewman\.jenkins\workspace\pipeline-test@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e microsoft/nanoserver cat [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.io.IOException: Failed to run image 'microsoft/nanoserver'. Error: docker: Error response from daemon: invalid volume specification: 'C:\Users\lnewman\.jenkins\workspace\pipeline-test:C:\Users\lnewman\.jenkins\workspace\pipeline-test:rw,z'. See 'docker run --help'. ... {code} This indicates that it might be possible to run containers directly but the built-in docker plugin bugs are still blocking.
[JIRA] (JENKINS-42060) If Jenkins is run on a port other than 8080, Schedule build lugin redirects to port 8080 and gives resource not found error
Title: Message Title Martin Spielmann closed an issue as Fixed Jenkins / JENKINS-42060 If Jenkins is run on a port other than 8080, Schedule build lugin redirects to port 8080 and gives resource not found error Change By: Martin Spielmann Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32562) Add support to not regard quiet period
Title: Message Title Martin Spielmann closed an issue as Fixed Jenkins / JENKINS-32562 Add support to not regard quiet period Change By: Martin Spielmann Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49490) Failed to run AVD creation on MAC
Title: Message Title Christopher Orr commented on JENKINS-49490 Re: Failed to run AVD creation on MAC I don't see any problems here: the emulator started, you apparently didn't have any further build steps, the emulator was shut down, and the build completed successfully. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Leo Luz edited a comment on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
We are using 1.15 in our company and we are having the same issue. My docker image has an entrypoint defined and {{image.inside()}} invokes docker as: {noformat} docker run -t -d -u 1000:1000 -w /var/jenkins/workspace/myimage:mytag cat {noformat} The problem is that {{cat}} is not a recognized flag for my entrypoint and it fails in the next command: {noformat} $ docker top 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 {noformat} with the error: {noformat} java.io.IOException: Failed to run top '52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4'. Error: Error response from daemon: Container 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 is not running at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) {noformat} As a workaround Im doing in my Jenkinsfile: {noformat} script \ {↩image.inside('--entrypoint ""') \ {↩// do something}↩}↩ {noformat} This fixes my issue because I don't need the {{entrypoint}} definition at this stage but it would be nice to have the plugin working as expected. Thank you!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Leo Luz commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
We are using 1.15 in our company and we are having the same issue. My docker image has an entrypoint defined and image.inside() invokes docker as: docker run -t -d -u 1000:1000 -w /var/jenkins/workspace/myimage:mytag cat The problem is that cat is not a recognized flag for my entrypoint and it fails in the next command: $ docker top 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 with the error: java.io.IOException: Failed to run top '52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4'. Error: Error response from daemon: Container 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 is not running at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) As a workaround Im doing in my Jenkinsfile: script {↩ image.inside('--entrypoint ""') {↩ // do something }↩ }↩ This fixes my issue because I don't need the entrypoint definition at this stage but it would be nice to have the plugin working as expected. Thank you!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48490) Intermittently slow docker provisioning with no errors
Title: Message Title Jason Swager commented on JENKINS-48490 Re: Intermittently slow docker provisioning with no errors We are seeing similar symptoms after upgrading the Docker plugin. Our Jenkins masters started seeing this problem after upgrading to Docker Plugin v1.1.1 and even v1.1.2. One big difference, we're using SSH to connect rather than JNLP. The larger and more busy the Jenkins master, the faster this problem occurs. Our larger one we had to downgrade the Docker plugin to it's prior version, 0.16.2. The smaller Jenkins don't suffer immediately from the problem and a restart of them clears the problem - at least for another couple days. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Andrew Bayer reopened an issue Jenkins / JENKINS-49388 Passing variables to a Jenkinsfile shell script within "sh" Change By: Andrew Bayer Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49388 Passing variables to a Jenkinsfile shell script within "sh" Change By: Andrew Bayer Component/s: workflow-durable-task-step-plugin Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Andrew Bayer commented on JENKINS-49388 Re: Passing variables to a Jenkinsfile shell script within "sh" Then I honestly have no idea. Moving to workflow-durable-task-step-plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title Alaiksei Savanchuk updated an issue Jenkins / JENKINS-28877 Bitbucket Plugin unable to parse Bitbucket webhook response json Change By: Alaiksei Savanchuk Comment: The same problem net.sf.json.JSONException: JSONObject["user"] not found. Jenkins ver. 2.60.3Bitbucket Plugin 1.1.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49515) Misspelled version of `stages` appears in error message for malformed sequential pipeline
Title: Message Title Andrew Bayer resolved as Fixed Fixed in latest push to the branch. =) Jenkins / JENKINS-49515 Misspelled version of `stages` appears in error message for malformed sequential pipeline Change By: Andrew Bayer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Vivek Pandey commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API We can do that. In the mean time, we should make dependency on jira-plugin optional and make sure blueocean-jira-plugin degrades without blowing up. Either that or make dependency on blueocean-jira-plugin optional? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49388) Passing variables to a Jenkinsfile shell script within "sh"
Title: Message Title Kevin Lu commented on JENKINS-49388 Re: Passing variables to a Jenkinsfile shell script within "sh" Actually when the "Plan" stage runs, the value of FOO is picked up correctly, but somehow the FOO variable itself is not passed into the environment of ./tests/run.sh, so I don't think it's an issue of scope Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49517) Supporting Merge requests on a multibranch pipeline
Title: Message Title Jorge Figueira created an issue Jenkins / JENKINS-49517 Supporting Merge requests on a multibranch pipeline Issue Type: Improvement Assignee: Owen Mehegan Components: gitlab-plugin Created: 2018-02-12 19:55 Priority: Critical Reporter: Jorge Figueira Its not possible to access gitlab variables: Example: gitlabBranch ... gitlabMergeRequestId ... Multibranch Pipelines expose additional information about the branch being built through the env global variable, such as: With the "GitHub" or "Bitbucket" Branch Sources, Multibranch Pipelines can be used for validating pull/change requests. CHANGE_ID - An identifier corresponding to some kind of change request, such as a pull request number Please add the same functionality to Gitlab plugin. Add Comment
[JIRA] (JENKINS-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49433 Re: Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/integrations/jobdsl/ConditionsContext.java http://jenkins-ci.org/commit/promoted-builds-plugin/f0363e9ef9f5f66e7b3e8ba1f3aa447e1991f214 Log: JENKINS-49433 - Prevent NPEs in JobDSL ConditionContext operations. Fixes the following operations: `selfPromotion()`, `parameterizedSelfPromotion()`, `downstream()` Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49433) Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49433 Re: Ommiting "default" value for selfPromotion() causes NPE in JobDSL integration Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/promoted_builds/integrations/jobdsl/ConditionsContext.java http://jenkins-ci.org/commit/promoted-builds-plugin/5e124c0757987a93f3f85df5973040dbea37fc4b Log: Merge pull request #111 from oleg-nenashev/JENKINS-49433 JENKINS-49433 - Prevent NPEs in JobDSL ConditionContext operations. Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/3849c36245c3...5e124c075798 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xml build-97 is a rebuild from build#96.build-97 is a fresh clean build. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu edited a comment on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xmlbuild-97 is a rebuild from build#96.build-97 is a fresh clean build. Both have the same issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build-97.xml Attachment: build-98.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22116) Cannot modify background image
Title: Message Title Tobias Gruetzmacher closed an issue as Duplicate Jenkins / JENKINS-22116 Cannot modify background image Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Promote immediately once the build is complete based on build parameters not working Change By: Rick Liu Attachment: build.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Promote immediately once the build is complete based on build parameters not working Attached build.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49516) Blue-Ocean multibranch pipeline projects ignore system ssh_config
Title: Message Title David Raison created an issue Jenkins / JENKINS-49516 Blue-Ocean multibranch pipeline projects ignore system ssh_config Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-02-12 19:40 Environment: Jenkins 2.105 Priority: Major Reporter: David Raison When attempting to create a (multibranch) pipeline project from blue-ocean, the Jenkins will ignore the ssh_config file on the system. When creating the same job in classic, this works. %MCEPASTEBIN% Feb 12, 2018 8:29:33 PM io.jenkins.blueocean.blueocean_git_pipeline.GitUtils validateCredentials SEVERE: Error running git remote-ls: org.eclipse.jgit.api.errors.TransportException: ssh://g...@host.tld/source/repo.git: Failed to connect hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.TransportException: ssh://g...@host.tld/source/repo.git: Failed to connect at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getRemoteReferences(JGitAPIImpl.java:801) at io.jenkins.blueocean.blueocean_git_pipeline.GitUtils.validateCredentials(GitUtils.java:99) at io.jenkins.blueocean.blueocean_git_pipeline.GitPipelineCreateRequest.validate(GitPipelineCreateRequest.java:62) at io.jenkins.blueocean.scm.api.AbstractMultiBranchCreateRequest.validateInternal(AbstractMultiBranchCreateRequest.java:249) at io.jenkins.blueocean.scm.api.AbstractMultiBranchCreateRequest.create(AbstractMultiBranchCreateRequest.java:74) at io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:54) at io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:50) at
[JIRA] (JENKINS-20058) Ability to change the favicon for Jenkins
Title: Message Title Tobias Gruetzmacher resolved as Fixed Fixed with release 0.4 Jenkins / JENKINS-20058 Ability to change the favicon for Jenkins Change By: Tobias Gruetzmacher Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49488) Promote immediately once the build is complete based on build parameters not working
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-49488
Promote immediately once the build is complete based on build parameters not working
Change By:
Rick Liu
emphasized textI I have selected "*Promote immediately once the build is complete based on build parameters*" with:Parameter Name: $\{AUTO_APPROVE}Parameter Value: trueorParameter Name: AUTO_APPROVEParameter Value: trueIn the build, when Boolean paramter AUTO_APPROVE is set to true,the promotion job doesn't start.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn updated an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Change By:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/ source game /... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/ game/ content which is what the view filter reflects.Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded?Here is the checkout stage of my pipeline (with edited project names):{code:java}stage('Sync code') {steps{checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/ source game /...//project/main/ game/ content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49515) Misspelled version of `stages` appears in error message for malformed sequential pipeline
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-49515
Misspelled version of `stages` appears in error message for malformed sequential pipeline
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-02-12 19:02
Environment:
Jenkins: - Core 2.105, running on Ubuntu - Snapshot builds of declarative, uploaded from the "Advanced" tab, built from the jenkins-45455 branch Client: - Fedora Workstation 27 - Some old version of jenkins-cli.jar that I happened to have
Priority:
Trivial
Reporter:
Karl Shultz
Summary: There's a misspelled word, stasges, in one of the error messages. Should be stages. It reads as follows:
WorkflowScript: 17: No "steps", "stasges", or "parallel" to execute within stage "2. second-sequential-stage" @ line 17, column 29.
stage('2. second-sequential-stage') {
^
Steps to recreate: 1. Create a Jenkinsfile for testing JENKINS-46809. It needs to be missing the steps section inside one of the sequential {{stage}}s. Like this one:
pipeline {
stages {
stage('parallel-wrapper') {
parallel {
stage('sequential-stages-1') {
stages {
[JIRA] (JENKINS-43198) JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern)
Title: Message Title Alexandre Feblot commented on JENKINS-43198 Re: JGit Clean before checkout fails (jgit and gitignore with dir/subdir pattern) Thanks, Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49512) Mac Slave is getting disconnected frequently
Title: Message Title Sapan Garg commented on JENKINS-49512 Re: Mac Slave is getting disconnected frequently Oleg Nenashev Below is the agent configuration. Usage : Use this node as much as possible Launch Method : Launch Slave agents via SSH Port : 22 Maximum number of retries : 0 Seconds to wait between retries : 0 Availability : Keep this agent online as much as possible Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn updated an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Change By:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/source/... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/content which is what the view filter reflects.Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded?Here is the checkout stage of my pipeline (with edited project names): {code:java} stage('Sync code') \ { steps \ { checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/source/... - //project/main/content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins - $ \ {NODE_NAME} - $ \ {JOB_NAME} - $ \ {EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) } } {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49514) No builds triggered using p4 plugin polling with view filters
Title: Message Title
Samuel Kahn created an issue
Jenkins / JENKINS-49514
No builds triggered using p4 plugin polling with view filters
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-02-12 18:19
Environment:
P4 Plugin version 1.8.4
Priority:
Major
Reporter:
Samuel Kahn
P4 plugin's view filter functionnality does not seem to work for me. After submitting changes to //project/main/source/... I would like a build to be triggered, however the build is never triggered. I would like to ignore changes in //project/main/content which is what the view filter reflects. Looking at the polling log doesn't show a verbose output of why the builds were discarded. Is there any way for me to understand why these builds are being discarded? Here is the checkout stage of my pipeline (with edited project names): stage('Sync code') { steps{ checkout perforce(credential: '3889489e-9363-4783-80ca-ad8f6afbbdcc', filter: [viewFilter('''//project/main/source/... //project/main/content/...''')], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: streamSpec(charset: 'none', format: 'jenkins${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}-sync', pinHost: false, streamName: '//project/main_buildbot_sync')) } }
[JIRA] (JENKINS-49512) Mac Slave is getting disconnected frequently
Title: Message Title Oleg Nenashev commented on JENKINS-49512 Re: Mac Slave is getting disconnected frequently Please provide agent configuration (launcher type, etc.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49513) pipeline finally not reporting errors
Title: Message Title
John Mellor created an issue
Jenkins / JENKINS-49513
pipeline finally not reporting errors
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-12 17:56
Environment:
Jenkins 2.101 on Ubuntu-16.04.3, pipeline 2.5, pipeline API 2.24
Priority:
Major
Reporter:
John Mellor
Finally in a pipeline does not report critical errors, leading to mysterious failures. E.g: this following pipeline excerpt does not construct the dependency-check-report.html file for archiving, and no error is logged. However, the build silently fails as a result. try { stage('Build and test') { sh 'sbt -no-colors rebuild doc swaggerJson manifest' } } finally { stage('Archive coverage report') { archiveArtifacts "target/scala-2.12/scoverage-report/**" publishHTML(target: [reportName: "Code coverage report", reportDir: "target/scala-2.12/scoverage-report", reportFiles: "index.html"]) } stage('Archive vulnerability report') { archiveArtifacts "target/scala-2.12/dependency-check-report.html" publishHTML(target: [reportName: "Vulnerabilty report", reportDir: "target/scala-2.12", reportFiles: "dependency-check-report.html"]) } }
[JIRA] (JENKINS-49505) workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Title: Message Title
Christian Wansart commented on JENKINS-49505
Re: workflow-{cps,job,multibranch,support} require step-api 2.13, although 2.14 was released 3 months ago
Thanks, I'll try. If it breaks try to install the old versions. I was a bit confused that the security updates of the named above plugins are newer than then its dependency causing the warning.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java http://jenkins-ci.org/commit/pipeline-maven-plugin/a95c6f4c7f3bb456dcab3c95665043e6131dee5f Log: JENKINS-49482 Fix "java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/Collections" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title Andrew Bayer commented on JENKINS-48475 Re: Build step returns null if propagate set to true Sorry to hear that - then you are stuck, since as I said, at least in current Pipeline design, a step can't both fail and return something. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49512) Mac Slave is getting disconnected frequently
Title: Message Title Sapan Garg created an issue Jenkins / JENKINS-49512 Mac Slave is getting disconnected frequently Issue Type: Bug Assignee: Oleg Nenashev Components: ssh-slaves-plugin Created: 2018-02-12 17:25 Environment: Jenkins : 2.89.3 SSH Slaves Plugin : 1.25.1 Version of slave.jar : 3.14 Java version on slave : 1.8.0_20 Labels: slave jenkins Priority: Blocker Reporter: Sapan Garg One of our mac slaves is getting disconnected multiple times during a build. Slave.log java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77) Build log java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2335) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2804) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:802) at
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' [~bingshiao] [~dantran] can you please try https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.3.1-beta- 1 2 /pipeline-maven-3.3.1-beta- 1 2 .hpi (!) pipeline-maven-3.3.1-beta-1 is broken due to https://github.com/jenkinsci/pipeline-maven-plugin/commit/a95c6f4c7f3bb456dcab3c95665043e6131dee5f Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Cyrille Le Clerc updated JENKINS-49482 Jenkins / JENKINS-49482 Hide empty 'Deployed Artifacts:' Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Cyrille Le Clerc started work on JENKINS-49482 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49390) Jenkins does not consider script-security.whatever.hpi to be installed
Title: Message Title Daniel Beck commented on JENKINS-49390 Re: Jenkins does not consider script-security.whatever.hpi to be installed Rewrote the issue as discussed. Petres Andras Any objections from your POV? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49390) Jenkins does not consider script-security.whatever.hpi to be installed
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49390 Jenkins does not consider script-security.whatever.hpi to be installed Change By: Daniel Beck Jenkins should refuse to start up when there are plugin files (hpi/jpi) that file names not matching their contents in the plugins/ directory, as that can lead to confusion about what is installed.*Original description* Upgrading Jenkins from 2.85 to 2.97+ (I tried with 2.97 and 2.105) downloads _script-security.jpi_ version 1.18 and loads it even if _script-security.latest.hpi_ (version 1.40) is in the plugins folder. Deleting _script-security.jpi_ fixes the issue.Jenkins error log is the same as in - JENKINS-48604 - . Since that issue is fixed, I'm wondering if this is a regression. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-49390) Jenkins does not consider script-security.whatever.hpi to be installed
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49390 Jenkins does not consider script-security.whatever.hpi to be installed Change By: Daniel Beck Summary: Upgrading Jenkins to 2.97+ downgrades does not consider script-security plugin to 1 . 18 whatever.hpi to be installed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky commented on JENKINS-48475 Re: Build step returns null if propagate set to true Yes, I tried that way and it's not acceptable in my case because build steps are marked as passed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
