[JIRA] (JENKINS-37694) link to archived build artifacts is hidden until pipeline has finished
Title: Message Title Eugene G commented on JENKINS-37694 Re: link to archived build artifacts is hidden until pipeline has finished Thank you, Christopher Head, it works! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173822.1472152728000.9948.1586808060823%40Atlassian.JIRA.
[JIRA] (JENKINS-37694) link to archived build artifacts is hidden until pipeline has finished
Title: Message Title Eugene G commented on JENKINS-37694 Re: link to archived build artifacts is hidden until pipeline has finished Matthias Balke, where do you see the download icon? I have a prompt dialog in my pipeline and when it's waiting for a user's response, nobody can see archived artifacts. Do you know any workarounds? Is it possible to write own function in a shared library that will attach files to the build immediately? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173822.1472152728000.7164.1586197320361%40Atlassian.JIRA.
[JIRA] (JENKINS-58604) Full Stage View only showing one
Title: Message Title Eugene G edited a comment on JENKINS-58604 Re: Full Stage View only showing one I really vote for the issue. Is it possible to generate each build with its own headers to avoid comparing titles? A lot of our jobs have steps that are always ordered in different ways and have different stages generated dynamically. The logic that hides previous builds causes huge pain.Especially when these jobs run in parallel which makes impossible to see even current builds statuses. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.1144.1580824980585%40Atlassian.JIRA.
[JIRA] (JENKINS-58604) Full Stage View only showing one
Title: Message Title Eugene G commented on JENKINS-58604 Re: Full Stage View only showing one I really vote for the issue. Is it possible to generate each build with its own headers to avoid comparing titles? A lot of our jobs have steps that are always ordered in different ways and have different stages generated dynamically. The logic that hides previous builds causes huge pain. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.1131.1580824920420%40Atlassian.JIRA.
[JIRA] (JENKINS-60082) Add PR titles into the PullRequests view in Jenkins GitHub Organization
Title: Message Title Eugene G created an issue Jenkins / JENKINS-60082 Add PR titles into the PullRequests view in Jenkins GitHub Organization Issue Type: Improvement Assignee: Kohsuke Kawaguchi Attachments: image-2019-11-07-10-30-37-329.png Components: github-organization-folder-plugin Created: 2019-11-07 08:35 Environment: <2.190.2 Labels: github-organization-folder-plugin pull-request Priority: Minor Reporter: Eugene G First of all, I'd like to thank everyone who is working hard to make Jenkins better. I'm using it for years and it helps a lot. Is it possible to add a PR title to the view? We have big projects with many opened pull requests and people sometimes are having a hard time trying to find their builds on the page. The view example: https://ci.jenkins-ci.org/job/Plugins/job/active-directory-plugin/view/change-requests/Related SO question, just in case.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title
Eugene G edited a comment on JENKINS-54864
Re: github multibranch builds fail to build with latest branch api update
I upgraded Branch API plugin from 2.1.2 to 2.5.4 and still see the same message in the logs:{code} Checking branch dummy ‘Jenkinsfile’ foundMet criteriaChanges detected: dummy (null → cd9913c17e529deb34a84ae6f3d21ab647fedd52)No automatic build triggered for dummy{code}Build strategies for GitHub Organization contain "Change requests" strategy and "Ignore rebuilding merge branches when only the target branch changed" flag is enabled."Discover branches" strategy has "Exclude branches that are also filed as PRs" value but there's no PR for the "dummy" branch that I created. Pull Requests trigger builds as expected, but new branches are ignored. *Update:* I just added another rule into the "Build strategies" section of the GitHub Organization properties. The "Named branches" rule with "*" wildcard triggered all the builds even though I still see that "null → something" in the logs.{code} Checking branch dummy ‘Jenkinsfile’ foundMet criteriaChanges detected: dummy (null → cd9913c17e529deb34a84ae6f3d21ab647fedd52)Scheduled build for branch: dummy{code} !image-2019-10-01-16-35-50-526.png|width=100%!
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-iss
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Eugene G commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update I upgraded Branch API plugin from 2.1.2 to 2.5.4 and still see the same message in the logs: Checking branch dummy ‘Jenkinsfile’ found Met criteria Changes detected: dummy (null → cd9913c17e529deb34a84ae6f3d21ab647fedd52) No automatic build triggered for dummy Build strategies for GitHub Organization contain "Change requests" strategy and "Ignore rebuilding merge branches when only the target branch changed" flag is enabled. "Discover branches" strategy has "Exclude branches that are also filed as PRs" value but there's no PR for the "dummy" branch that I created. Pull Requests trigger builds as expected, but new branches are ignored. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195860.1543250066000.8878.1569936720596%40Atlassian.JIRA.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title Eugene G commented on JENKINS-43693 Re: multibranchPipelineJob overrides old branch indexing sources I faced the same issue even though I don't use the Job DSL plugin to configure a GitHub Organization pipeline. It was created in UI. Any workarounds? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181107.1492615058000.8825.1569932100369%40Atlassian.JIRA.
[JIRA] (JENKINS-55796) Random "process apparently never started" error
Title: Message Title
Eugene G commented on JENKINS-55796
Re: Random "process apparently never started" error
I'm not sure if my case somehow linked to the case from the ticket but for those who will be looking for similar problems: in my case it was caused by dead sidecar docker container:
docker.image('elasticsearch:6.4.0').withRun() { es ->
image.inside("--link ${es.id}:es") {
sh 'my_script.sh' // process apparently never started in ...
}
}
So Elasticsearch image started and exited with an error but Jenkins doesn't control this, so I got the problem.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197185.1548584837000.20555.1563978180202%40Atlassian.JIRA.
[JIRA] (JENKINS-54495) Better handling of GitHub Organization folder scan to avoid API quota
Title: Message Title Eugene G commented on JENKINS-54495 Re: Better handling of GitHub Organization folder scan to avoid API quota This is very important. If an organization has tons of old repos and more than 50 repos with Jenkinsfiles it becomes crazy to maintain the list of repos in this small filter field. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195265.1541518348000.19675.1563906420412%40Atlassian.JIRA.
[JIRA] (JENKINS-24283) Empty environment variables are deleted
Title: Message Title Eugene G commented on JENKINS-24283 Re: Empty environment variables are deleted Any chance for this to be fixed? Any workarounds available? Sometimes the empty env variables must be set for third-parties that really relies on them... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156760.1408096905000.195.1560415920245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories
Title: Message Title
Eugene G edited a comment on JENKINS-24440
Re: Jenkins cannot delete root-owned files/folders in jenkins-owned directories
This helps in my case:{code:java}stages { stage('Build') {steps {script { // ... image = docker . build inside ( '-u root ) { some code creates files and folders } } }} post {cleanup {script {image.inside('-u root') {sh "chmod -R 777 'find . " -user root -name \'*\' | xargs chmod ugo+rw' }}deleteDir()}} {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157021.1409056797000.23742.1559925960407%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46145) Groovy Traits are not supported
Title: Message Title Eugene G commented on JENKINS-46145 Re: Groovy Traits are not supported Any chance to get the feature? Mixins demonstrate weird behavior in some corner cases. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.Update: but with the ability to bypass the global setting for a specific line with docker.build(). There's a corner case when one image must be build FROM another one that also was built locally. In this situation "--pull" argument will break the second build because it hadn't been pushed to a registry yet .
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emai
[JIRA] (JENKINS-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build. Update: but with the ability to bypass the global setting for a specific line with docker.build(). There's a corner case when one image must be build FROM another one that also was built locally. In this situation "--pull" argument will break the second build.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title Eugene G commented on JENKINS-55821 Re: Allow to always pull base images for docker.build() in all pipelines Related StackOverflows: https://stackoverflow.com/questions/45057282/jenkins-docker-how-to-force-pull-base-image-before-build https://stackoverflow.com/questions/52345748/how-to-always-use-the-newest-version-of-a-docker-base-image Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest')// image = docker.build('myorg/myapp:latest', '--pull .') // how it must looks look like now}}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G updated an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Change By:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.{code:java}pipeline {agent { label 'master' }stages {stage('Build') {steps {script {image = docker.build('myorg/myapp:latest') // image = docker.build('myorg/myapp:latest', '--pull .') // how it must looks like now }}}}}{code} It would be nice to have a global option to force Docker to *always* pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-55821) Allow to always pull base images for docker.build() in all pipelines
Title: Message Title
Eugene G created an issue
Jenkins / JENKINS-55821
Allow to always pull base images for docker.build() in all pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-01-29 00:35
Labels:
docker-build-step Docker
Priority:
Minor
Reporter:
Eugene G
The problem looks close to JENKINS-25690 but it is related to the default Jenkins Pipeline functionality.
pipeline {
agent { label 'master' }
stages {
stage('Build') {
steps {
script {
image = docker.build('myorg/myapp:latest')
}
}
}
}
}
It would be nice to have a global option to force Docker to always pull base images before build ("--pull" argument). When you have a lot of Jenkinsfiles it is very hard to control that all of them pull base images before each build.
[JIRA] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories
Title: Message Title
Eugene G commented on JENKINS-24440
Re: Jenkins cannot delete root-owned files/folders in jenkins-owned directories
This helps in my case:
stages {
stage('Build') {
steps {
script {
image = docker.build()
}
}
}
}
post {
cleanup {
script {
image.inside('-u root') {
sh "chmod -R 777 ."
}
}
deleteDir()
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Eugene G commented on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Thank you, Ray Burgemeestre! For me your solution works like a charm and it is much better than nothing:
def generateStage(job) {
return {
stage("Build: ${job}") {
// https://issues.jenkins-ci.org/browse/JENKINS-44085?focusedCommentId=346951&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-346951
lock(label: "throttle_parallel", quantity: 1, variable: "LOCKED") {
println "${job} locked resource: ${env.LOCKED}"
my_jobs_map[job].build() // my own code
}
}
}
}
pipeline {
stages {
stage("Build") {
steps {
script {
parallel_jobs = ["Job1", "Job2", "Job3", "Job4", "Job5", "Job6", "Job7"] //pre-generated
println "===[ Parallel Jobs: ${parallel_jobs} ]==="
parallelStagesMap = parallel_jobs.collectEntries {
["${it}" : generateStage(it)]
}
timestamps {
parallel parallelStagesMap
}
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-35469) Exclude crumb requirement for webhook
Title: Message Title Eugene G commented on JENKINS-35469 Re: Exclude crumb requirement for webhook Thank you, Sion Williams, I have used same option. Not best, but it works. 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-35469) Exclude crumb requirement for webhook
Title: Message Title Eugene G commented on JENKINS-35469 Re: Exclude crumb requirement for webhook Hello. So, what you decided about this problem? A have same problem with a bitbucket – hook does not work because of "No valid crumb". What should I do to fix this situation? Thank you. 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.
