[JIRA] (JENKINS-53161) useRepository its not applied
Title: Message Title Nuno Costa updated an issue Jenkins / JENKINS-53161 useRepository its not applied Change By: Nuno Costa Environment: centos7 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53161) useRepository its not applied
Title: Message Title Nuno Costa created an issue Jenkins / JENKINS-53161 useRepository its not applied Issue Type: Bug Assignee: Boguslaw Klimas Attachments: Screenshot_20180821_135206.png Components: git-parameter-plugin Created: 2018-08-21 12:33 Priority: Minor Reporter: Nuno Costa useRepository does not seem to applied. Every time I set it, it will display No GIT repository configured in SCM configuration. Tried use https protocol, adding ^.*ubuntu16-cmake as regex as well but same message is shown. My initial use case was to show the branches from the repository that is selected in choices but that seems not to be possible without a build. So I tried to use a fixed repository (for testing) and noticed that useRepository makes the msg to appear. Additional notes: Running without useRepository, only the branches from the default value are shown (ubuntu16-cmake) even if i choose ubuntu16-maven. Both builds finish ok since it's only checkout the repo. Running the jenkinsfile from SCM, only shows branches from repo where jenkinsfile is located. My use case has 3 repos (jenkinsfile only, ubuntu16-cmake and ubuntu16-maven) Is it possible to pass a variable to useRepository field? Tested with jenkins (2.138) and its plugins fully updated as of 20180821. Example: properties( [parameters(
[JIRA] (JENKINS-49261) Mulitbranch pipeline failed to find JenkinsFile in a subfolder
Title: Message Title Nuno Costa commented on JENKINS-49261 Re: Mulitbranch pipeline failed to find JenkinsFile in a subfolder After applying PR111, jenkinsfile is now discovered when running " Scan Organization Folder". 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-49295) readTrusted in subfolder doesn't work for bitbucketserver
Title: Message Title Nuno Costa commented on JENKINS-49295 Re: readTrusted in subfolder doesn't work for bitbucketserver We are also affected by JENKINS-49261. PR105 did not work but with PR111, jenkinsfile is now discovered. 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-49261) Mulitbranch pipeline failed to find JenkinsFile in a subfolder
Title: Message Title Nuno Costa commented on JENKINS-49261 Re: Mulitbranch pipeline failed to find JenkinsFile in a subfolder Also experience this issue. Missing job history seems to be possible, when you have the Orphaned Item Strategy set to Discard old items. 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-46498) Docker fingerprint not showing image usage in UI.
Title: Message Title Nuno Costa commented on JENKINS-46498 Re: Docker fingerprint not showing image usage in UI. Still an issue with Jenkins 2.108 and fully updated plugins. 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-43654) adding a simple writeFile inside withMaven causes pipeline to hang
Title: Message Title Nuno Costa commented on JENKINS-43654 Re: adding a simple writeFile inside withMaven causes pipeline to hang Still an issue with Jenkins 2.108 and fully updated plugins as of today. 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-44836) Docker inspect failing on FROM statements with ARG
Title: Message Title
Nuno Costa commented on JENKINS-44836
Re: Docker inspect failing on FROM statements with ARG
Still an issue with Jenkins 2.105 and docker-workflow 1.15. Based on Dockerfile with example above, docker image is downloaded, built and tagged but fails on inspect. Build command:
docker.build("mycentos7", ".")
Error:
...
Status: Downloaded newer image for centos:centos7
---> ff426288ea90
Successfully built ff426288ea90
Successfully tagged mycentos7:latest
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
java.io.IOException: Cannot retrieve .Id from 'docker inspect${BASE_IMAGE}'
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:222)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:133)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:290)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
Add Comment
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
Nuno Costa edited a comment on JENKINS-40484
Re: Unable to use withMaven step inside docker container
This can be replicated with below code. CentOS node build will fail with {noformat}[number1] nohup: failed to run command `sh': No such file or directory{noformat} Commented is some troubleshoot steps.Can be resolved by getting the container path into a file, pass it into a variable and finally pass that to withEnv. Be aware that echo adds a new line to the file and in my case, this was also triggering the same issue. Use trim() to remove the extra line. Use The use of printf instead of echo will avoid the trim() usage.CentOS 7Jenkins 2.46{noformat}parallel(number1: {node('centos-buildserver') {buildenv = docker.image("custom-ubuntu12.04-maven")buildenv.inside("-v /var/lib/jenkins/.m2/repository/${EXECUTOR_NUMBER}:/home/jenkins/.m2/repository"){stage("test") {/*sh 'echo $PATH > path'sh 'printf $PATH > path'path = readFile('path').trim()path = readFile('path')pathtrim = readFile('path').trim()echo '###'echo 'no trim: #'+path+'#'echo '###'echo 'with trim: #'+pathtrim+'#'echo '###'*/sh 'ls -l'//withEnv(['PATH+workaround='+path]) { withMaven(mavenSettingsConfig: 'settings-id'){ echo 'inside withmaven' sh 'ls -l' }//}}}}},number2: {node('ubuntu-buildserver') {buildenv = docker.image("custom-ubuntu12.04-maven")buildenv.inside("-v /var/lib/jenkins/.m2/repository/${EXECUTOR_NUMBER}:/home/jenkins/.m2/repository"){stage("test") {/*sh 'echo $PATH > path'sh 'printf $PATH > path'path = readFile('path').trim()path = readFile('path')pathtrim = readFile('path').trim()echo '###'echo '#'+path+'#'echo '###'echo '#'+pathtrim+'#'echo '###'*/sh 'ls -l'//withEnv(['PATH+workaround='+path]) { withMaven(mavenSettingsConfig: 'settings-id'){ echo 'inside withmaven' sh 'ls -l' }//}}}}}){noformat}
Add Comment
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title
Nuno Costa commented on JENKINS-40484
Re: Unable to use withMaven step inside docker container
This can be replicated with below code. Commented is some troubleshoot steps. Can be resolved by getting the container path into a variable and pass that to withEnv. Be aware that echo adds a new line to the file and in my case, this was also triggering the same issue. Use trim() to remove the extra line. Use of printf instead of echo will avoid the trim() usage. CentOS 7 Jenkins 2.46
parallel(
number1: {
node('centos-buildserver') {
buildenv = docker.image("custom-ubuntu12.04-maven")
buildenv.inside("-v /var/lib/jenkins/.m2/repository/${EXECUTOR_NUMBER}:/home/jenkins/.m2/repository"){
stage("test") {
/*sh 'echo $PATH > path'
sh 'printf $PATH > path'
path = readFile('path').trim()
path = readFile('path')
pathtrim = readFile('path').trim()
echo '###'
echo 'no trim: #'+path+'#'
echo '###'
echo 'with trim: #'+pathtrim+'#'
echo '###'*/
sh 'ls -l'
//withEnv(['PATH+workaround='+path]) {
withMaven(mavenSettingsConfig: 'settings-id'){
echo 'inside withmaven'
sh 'ls -l'
}
//}
}
}
}
},
number2: {
node('ubuntu-buildserver') {
buildenv = docker.image("custom-ubuntu12.04-maven")
buildenv.inside("-v /var/lib/jenkins/.m2/repository/${EXECUTOR_NUMBER}:/home/jenkins/.m2/repository"){
stage("test") {
/*sh 'echo $PATH > path'
sh 'printf $PATH > path'
path = readFile('path').trim()
path = readFile('path')
pathtrim = readFile('path').trim()
echo '###'
echo '#'+path+'#'
echo '###'
echo '#'+pathtrim+'#'
echo '###'*/
sh 'ls -l'
//withEnv(['PATH+workaround='+path]) {
withMaven(mavenSettingsConfig: 'settings-id'){
echo 'inside withmaven'
sh 'ls -l'
}
//}
}
}
}
}
)
Add
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title Nuno Costa edited a comment on JENKINS-40484 Re: Unable to use withMaven step inside docker container The workaround to pass the variables from outside withMaven block, mentioned by Test User [here|https://issues.jenkins-ci.org/browse/JENKINS-40484?focusedCommentId=283081=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-283081] works on a Jenkins 2.32.2 but not on Jenkins 2.46.Ubuntu 14 12 .04Jenkins 2.32.2Pipeline Maven Plugin 0.5Durable Task Plugin 1.13 Centos CentOS 7Jenkins 2.46Pipeline Maven Plugin 0.5Durable Task Plugin 1.13 BuildserverUbuntu 14.04 + docker 1.13.1BuildserverCentOS7 + docker 1.13.1Docker image:Ubuntu 12.04Maven 3.1.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40484) Unable to use withMaven step inside docker container
Title: Message Title Nuno Costa commented on JENKINS-40484 Re: Unable to use withMaven step inside docker container The workaround to pass the variables from outside withMaven block, mentioned by Test User here works on a Jenkins 2.32.2 but not on Jenkins 2.46. Ubuntu 14.04 Jenkins 2.32.2 Pipeline Maven Plugin 0.5 Durable Task Plugin 1.13 Centos 7 Jenkins 2.46 Pipeline Maven Plugin 0.5 Durable Task Plugin 1.13 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42025) Pipeline stage view add whitespace
Title: Message Title
Nuno Costa updated an issue
Jenkins / JENKINS-42025
Pipeline stage view add whitespace
Change By:
Nuno Costa
This is a similar issue as [#39445| https://issues.jenkins-ci.org/browse/JENKINS-39445 ] but in my case it appears the the beginning of the stages (the space added also depends on number of stages as mentioned on the previous issue) and only when using this as mainscript:{noformat}def stagename(def proj_name){stage ("$proj_name"){node('master'){build "$proj_name"}}}stagename('Freestyle-Test1-Echo')stagename('Freestyle-Test2-Echo-Cat')stagename('Freestyle-Test3-Echo'){noformat}No issue is seen when using:{noformat}node('master'){stage ('number 1'){build 'Freestyle-Test1-Echo'build 'Freestyle-Test2-Echo-Cat'}stage ('number 2'){build 'Freestyle-Test3-Echo'}}{noformat}Using vagrant with hashicorp/precise64 as base image on Virtualbox, Jenkins LTS installed from package manager with *deb http://pkg.jenkins.io/debian-stable binary/* on my apt sources.Stage views from several jobs are also displaying this whitespace, even when the job wasn't run for some time.Issue was present before I updated jenkins and all plugins. Still persists after update.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42025) Pipeline stage view add whitespace
Title: Message Title
Nuno Costa updated an issue
Jenkins / JENKINS-42025
Pipeline stage view add whitespace
Change By:
Nuno Costa
This is a similar issue as # https://issues.jenkins-ci.org/browse/JENKINS- 39445 but in my case it appears the the beginning of the stages (the space added also depends on number of stages as mentioned on the previous issue) and only when using this as mainscript:{noformat}def stagename(def proj_name){stage ("$proj_name"){node('master'){build "$proj_name"}}}stagename('Freestyle-Test1-Echo')stagename('Freestyle-Test2-Echo-Cat')stagename('Freestyle-Test3-Echo'){noformat}No issue is seen when using:{noformat}node('master'){stage ('number 1'){build 'Freestyle-Test1-Echo'build 'Freestyle-Test2-Echo-Cat'}stage ('number 2'){build 'Freestyle-Test3-Echo'}}{noformat}Using vagrant with hashicorp/precise64 as base image on Virtualbox, Jenkins LTS installed from package manager with *deb http://pkg.jenkins.io/debian-stable binary/* on my apt sources.Stage views from several jobs are also displaying this whitespace, even when the job wasn't run for some time.Issue was present before I updated jenkins and all plugins. Still persists after update.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42025) Pipeline stage view add whitespace
Title: Message Title
Nuno Costa updated an issue
Jenkins / JENKINS-42025
Pipeline stage view add whitespace
Change By:
Nuno Costa
This is a similar issue as [this|https://issues.jenkins-ci.org/browse/JENKINS- # 39445 ] but in my case it appears the the beginning of the stages (the space added also depends on number of stages as mentioned on the previous issue) and only when using this as mainscript:{noformat}def stagename(def proj_name){stage ("$proj_name"){node('master'){build "$proj_name"}}}stagename('Freestyle-Test1-Echo')stagename('Freestyle-Test2-Echo-Cat')stagename('Freestyle-Test3-Echo'){noformat}No issue is seen when using:{noformat}node('master'){stage ('number 1'){build 'Freestyle-Test1-Echo'build 'Freestyle-Test2-Echo-Cat'}stage ('number 2'){build 'Freestyle-Test3-Echo'}}{noformat}Using vagrant with hashicorp/precise64 as base image on Virtualbox, Jenkins LTS installed from package manager with *deb http://pkg.jenkins.io/debian-stable binary/* on my apt sources.Stage views from several jobs are also displaying this whitespace, even when the job wasn't run for some time.Issue was present before I updated jenkins and all plugins. Still persists after update.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42025) Pipeline stage view add whitespace
Title: Message Title
Nuno Costa created an issue
Jenkins / JENKINS-42025
Pipeline stage view add whitespace
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
20170214-Selection-005.png
Components:
pipeline-stage-view-plugin
Created:
2017/Feb/14 3:55 PM
Environment:
Jenkins 2.32.2, Pipeline: Stage View Plugin v2.5
Priority:
Minor
Reporter:
Nuno Costa
This is a similar issue as this but in my case it appears the the beginning of the stages (the space added also depends on number of stages as mentioned on the previous issue) and only when using this as mainscript:
def stagename(def proj_name){
stage ("$proj_name"){
node('master'){
build "$proj_name"
}
}
}
stagename('Freestyle-Test1-Echo')
stagename('Freestyle-Test2-Echo-Cat')
stagename('Freestyle-Test3-Echo')
No issue is seen when using:
node('master'){
stage ('number 1'){
build 'Freestyle-Test1-Echo'
build 'Freestyle-Test2-Echo-Cat'
}
stage ('number 2'){
build 'Freestyle-Test3-Echo'
}
}
