[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title davidkarlsen commented on JENKINS-60343 Re: java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax I'm seeing this as well in: JENKINS-61339 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.203357.1575290252000.3586.1583796660183%40Atlassian.JIRA.
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Change By: davidkarlsen Environment: CloudBees Jenkins Enterprise 2.176.4.3-rollingk8s 1.13.9 kubernetes plugin 1.18.3 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.204926.1583368328000.5983.1583368500185%40Atlassian.JIRA.
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Issue Type: Bug Assignee: Unassigned Attachments: buildPod.yaml Components: kubernetes-plugin Created: 2020-03-05 00:32 Environment: CloudBees Jenkins Enterprise 2.176.4.3-rolling k8s 1.13.9 Priority: Minor Reporter: davidkarlsen I have a buildPod as attached. Two things: 1) workspace path includes branch names etc - this makes it non-constant and hard to automate 2) I use subpath to get the correct folder mounted at /docker-entrypoint-initdb.d in the mysql container, but it actually has no content - even if the path is correct (same volume shows up in the node container). Add Comment
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Change By: davidkarlsen Priority: Minor Major 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.204926.1583368328000.5982.1583368380251%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen closed an issue as Not A Defect Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Status: Open Closed Resolution: Not A Defect 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.203882.1578301543000.8491.1580335200392%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Indeed the old dependency check plugin shadowed the dependency track one and everything works as designed. (However the name and version parameters don't show in the pipeline-syntax ui - but that's unrelated). Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.8487.1580335140143%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Attachment: Screenshot 2020-01-22 at 14.17.14.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.3790.1579700760324%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Our config section looks a "little strange" - double up with settings. What could cause this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203882.1578301543000.3792.1579700760352%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Environment: plugin version: 2.2.0jenkins: CloudBees Jenkins Enterprise 2.176.4.3-rolling 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.203882.1578301543000.8036.1579009320232%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen edited a comment on JENKINS-60643 Re: Auto-create project for maven-based jobs When I visit the /pipeline-syntax page, only these parameters are documented:dependencyTrackPublisher: Publish results to Dependency-TrackprojectIdType:StringartifactType:StringartifactTypeType:String installed plugin version: 2.2.0 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.203882.1578301543000.8033.1579009260248%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs When I visit the /pipeline-syntax page, only these parameters are documented: dependencyTrackPublisher: Publish results to Dependency-Track projectId Type:String artifact Type:String artifactType Type:String 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.203882.1578301543000.8030.1579009200138%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs I get: WorkflowScript: 102: Invalid parameter "projectVersion", did you mean "projectId"? @ line 102, column 121. .edb.fs.tac.jfr.srv:jfr-srv", projectVer ^ when running: dependencyTrackPublisher artifact: 'bom.xml', artifactType: 'bom', projectId: "com.edb.fs.tac.jfr.srv:jfr-srv", projectVersion: "10.1.0-SNAPSHOT" 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.203882.1578301543000.8027.1579009080198%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Hm - I get: Missing required parameter: "projectId" @ line 114, column 9. dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom' when running with: dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom' 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.203882.1578301543000.6893.1578869100196%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-60643
Auto-create project for maven-based jobs
Issue Type:
Improvement
Assignee:
Steve Springett
Components:
dependency-track-plugin
Created:
2020-01-06 09:05
Labels:
ux usability pipeline auto
Priority:
Minor
Reporter:
davidkarlsen
Currently the plugin/pipeline configuration requires an existing project by defining projectId. I think it would be smoother to auto-create project, and read name/version from pom-files like: name: ${groupId}-${artifactId} version: ${version} then the entry-barrier would be lowered and it would be easier to adopt DT at larger scale.
Add Comment
[JIRA] (JENKINS-60265) Kubernetes plugin: java.net.MalformedURLException: unknown protocol
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-60265 Kubernetes plugin: java.net.MalformedURLException: unknown protocol Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-11-25 11:26 Environment: CloudBees Jenkins Enterprise 2.176.4.3-rolling Plugin version: 1.18.3 Priority: Minor Reporter: davidkarlsen When I click "test connection" from the master configuration page it works fine, but when scheduling a build I get: [Bitbucket] Build result notified java.net.MalformedURLException: unknown protocol: proxy.evry.com at java.net.URL.(URL.java:600) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at io.fabric8.kubernetes.client.utils.HttpClientUtils.getProxyUrl(HttpClientUtils.java:212) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:145) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:63) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:51) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:43) at io.fabric8.kubernetes.client.DefaultKubernetesClient.(DefaultKubernetesClient.java:84) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.parseFromYaml(PodTemplateUtils.java:517) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:554) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:544) at
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title davidkarlsen commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API what's strange also is that this only happens when declaring a yaml/yamlFile in a declarative pipeline, not if it is defined as a podTemplate on jenkins master. 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.196186.1544542592000.2669.1567084620289%40Atlassian.JIRA.
[JIRA] (JENKINS-55699) Pipeline script documentation does not show
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-55699 Pipeline script documentation does not show Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-01-21 12:11 Environment: CloudBees Jenkins Enterprise 2.138.2.2-rolling Labels: script library Priority: Minor Reporter: davidkarlsen I have pipeline libraries in vars/myscript.groovy - but documentation in vars/myscript.txt does not show in the UI. https://groups.google.com/forum/?nomobile=true#!topic/jenkinsci-users/qyEv2MhOt10 Add Comment
[JIRA] (JENKINS-53066) Renaming a project does not delete old folder
Title: Message Title
davidkarlsen updated an issue
Jenkins / JENKINS-53066
Renaming a project does not delete old folder
Change By:
davidkarlsen
We use the bitbucket teamfolder feature, which scans bitbucket for projects, and branches within those projects.We renamed a project (and it appears renamed in bitbucket) - but Jenkins did not delete the folder with the old name, it did however create a folder with the new name. If I force a scan the log says:{noformat}Will not remove ccm_be as it is only #1 in the listWill not remove ccm_be because it is new{noformat}
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-53066) Renaming a project does not delete old folder
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-53066 Renaming a project does not delete old folder Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-08-16 11:54 Priority: Minor Reporter: davidkarlsen We use the bitbucket teamfolder feature, which scans bitbucket for projects, and branches within those projects. We renamed a project (and it appears renamed in bitbucket) - but Jenkins did not delete the folder with the old name, it did however create a folder with the new name. Add Comment
[JIRA] (JENKINS-50662) withMaven for declarative pipeline
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-50662
withMaven for declarative pipeline
Issue Type:
Improvement
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2018-04-09 09:52
Priority:
Minor
Reporter:
davidkarlsen
For declarative pipelines, the tools can be selected on a job-basis, in the tools section, https://jenkins.io/doc/book/pipeline/syntax/#tools:
pipeline {
agent {
label 'docker'
}
tools {
jdk 'Oracle-JDK8-64bit' <-- JDK
maven 'apache-maven-3.x' <-- maven
}
But there are some nice features for the withMaven as well (such as flags for reports, setting the maven repo location). It would be nice if withMaven could use what has been declared in the tools section, so it need not be redefined for each maven execution.
[Pipeline] withMaven
11:43:50 [withMaven] Options: [org.jenkinsci.plugins.pipeline.maven.publishers.JunitTestsPublisher[disabled=false]]
11:43:50 [withMaven] Available options:
11:43:50 [withMaven] use JDK installation provided by the build agent <-- pick up from tools section
11:43:50 [withMaven] use Maven installation 'apache-maven-3.5.x' <-- pick up from tools section
[JIRA] (JENKINS-49529) retry at stage level in declarative pipeline fails
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-49529
retry at stage level in declarative pipeline fails
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-13 13:59
Environment:
Pipeline declarative: 1.2.2
Labels:
declarative multibranch pipeline retry stage
Priority:
Minor
Reporter:
davidkarlsen
Docs https://jenkins.io/doc/book/pipeline/syntax/ declare retry is allowed at stage level, but I get:
WorkflowScript: 52: Unknown stage section "options". Starting with version 0.5, steps in a stage must be in a steps block. @ line 52, column 5.
stage('test') {
^
when doing:
stage('test') {
options {
// TODO: Fix - some tests are flaky - sometimes pass, sometimes not
retry(3)
}
steps {
runCompose( 'test' )
}
}
[JIRA] (JENKINS-41068) Obsolate branch directories are not removed from job directory on master
Title: Message Title davidkarlsen commented on JENKINS-41068 Re: Obsolate branch directories are not removed from job directory on master Has any 2.0 official been released now which wasn't retracted from the plugin updates list due to some hard breaking changes? 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-26057) Workflow build step for Maven
Title: Message Title davidkarlsen commented on JENKINS-26057 Re: Workflow build step for Maven What version will this be in? I found no commit references 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-38461) Flag to disable Inject Node Properties -> Environment Variables at job level
Title: Message Title davidkarlsen commented on JENKINS-38461 Re: Flag to disable Inject Node Properties -> Environment Variables at job level The bug is in "CloudBees Docker Pipeline Plugin". The request was created initially by a CB employee - I'm just trying to clarify what the actual issue is. 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-38461) Flag to disable Inject Node Properties -> Environment Variables at job level
Title: Message Title davidkarlsen commented on JENKINS-38461 Re: Flag to disable Inject Node Properties -> Environment Variables at job level It's about the fact, that if there defined properties at a Jenkins-node for for instance PATH, this will be propagated into a docker container when using: https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Pipeline+Plugin This makes the plugin largely useless. Our usecase: -we had/have build-slaves for traditional jenkins jobs -then along the line came pipelines, which is a great fit for docker -and we want to define docker-image build-environments, using the mentioned plugin -but when the buildsteps are ran inside the image, the docker-containers environment is overriden by the plugin (PATH etc) 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-38461) Flag to disable Inject Node Properties -> Environment Variables at job level
Title: Message Title davidkarlsen reopened an issue Jenkins / JENKINS-38461 Flag to disable Inject Node Properties -> Environment Variables at job level Change By: davidkarlsen Resolution: Incomplete Status: Resolved Reopened Assignee: Daniel Beck 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed Tried the workaround without that relly working out for me (it was set to 1 day, now changed to 7). What happens if a branch is deleted (and hence a teamfolder-based job), then created again some days later? Will it remember that the milestone was for instance at #8 - so I need to do 8 new builds of my new branch again - just to pass the milestone? 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed The problem is that we have team-folders which rescan our repo - and it has a bug where if stash is down it will think the repo is gone, delete the jobs, recreate them (when the repo is back again) - so that the build get´s build #1 again. Since the plugin relies on job-build-number, I think it should base it´s decision on the CURRENT available buildnumber - it would still be valid (e.g. deliver the latest available code). But it´s a bit silly (not smooth) that I have to provide 6 builds just to increase the build-number. 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed BTW we have a CB support contract. 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: davidkarlsen 23:35:58 Trying to pass milestone 023:35:58 Canceled since build #6 already got here[Pipeline] }But this is build #4 - which is the latest build! The newer builds have been deleted. So the milestone step plugin should consider what is the latest current ly currently available build - not the highest number in history. 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: davidkarlsen Environment: 23:35:58 Trying to pass milestone 023:35:58 Canceled since build #6 already got here[Pipeline] }But this is build #4 - which is the latest build! The newer builds have been deleted. So the milestone step plugin should consider what is the latest current ly available build - not the highest number in history. 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-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Issue Type: Bug Assignee: Antonio Muñiz Components: pipeline-milestone-step-plugin Created: 2016/Sep/30 10:36 PM Environment: 23:35:58 Trying to pass milestone 0 23:35:58 Canceled since build #6 already got here [Pipeline] } But this is build #4 - which is the latest build! The newer builds have been deleted. So the milestone step plugin should consider what is the latest current ly available build - not the highest number in history. Priority: Minor Reporter: davidkarlsen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: davidkarlsen 23:35:58 Trying to pass milestone 023:35:58 Canceled since build #6 already got here[Pipeline] }But this is build #4 - which is the latest build! The newer builds have been deleted. So the milestone step plugin should consider what is the latest current ly available build - not the highest number in history. 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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem.{noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there. threaddump:{noformat}Thread #6 at DSL.emailext(not yet scheduled) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:101) at DSL.sshagent(Native Method) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:28) at DSL.ws(Native Method) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:27) at DSL.node(running on slave24-rhel) at standardBuild.call(/data/jenkins/workflow-libs/vars/standardBuild.groovy:25) at WorkflowScript.run(WorkflowScript:15){noformat}seems to be stuck in emailext
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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem.{noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there.
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-33761) Ability to disable "resume" build.
Title: Message Title
davidkarlsen edited a comment on JENKINS-33761
Re: Ability to disable "resume" build.
Got same problem. {noformat}Resuming build at Fri Sep 30 16:18:26 CEST 2016 after Jenkins restartReady to run at Fri Sep 30 16:18:28 CEST 2016{noformat}and then it just sits there.
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-33761) Ability to disable "resume" build.
Title: Message Title davidkarlsen commented on JENKINS-33761 Re: Ability to disable "resume" build. Got same problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title davidkarlsen commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Any progress on this? We´re a paying support customer with CB and have an issue open there as well. 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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title davidkarlsen commented on JENKINS-34517 Re: Pipeline is unable to locate global libraries when build attempts to continue on restart ping (we're a CB customer - so this actually came from issue #35678 in zendesk) 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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title davidkarlsen edited a comment on JENKINS-34517 Re: Pipeline is unable to locate global libraries when build attempts to continue on restart So should this be reopened or reported as a new issue? Could a new release be done after that as we'd really like to get this one. 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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title davidkarlsen commented on JENKINS-34517 Re: Pipeline is unable to locate global libraries when build attempts to continue on restart So should this be reopened or reported as a new issue? 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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title
davidkarlsen edited a comment on JENKINS-34517
Re: Pipeline is unable to locate global libraries when build attempts to continue on restart
Even worse - the whole job can go into an illegal state. The job broke on startup with this issue 1), but the next is waiting for the previous one to complete1){noformat}18:57:11 Waiting for builds [717]Resuming build[Pipeline] End of Pipeline[Bitbucket] Notifying commit build result[Bitbucket] Build result notifiedjava.io.IOException: Failed to load pe{noformat}2){noformat}19:31:54 Waiting for builds [718]{noformat} so now we're totally stuck Update: I see this registered as https://issues.jenkins-ci.org/browse/JENKINS-28183
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-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title davidkarlsen commented on JENKINS-34517 Re: Pipeline is unable to locate global libraries when build attempts to continue on restart Even worse - the whole job can go into an illegal state. The job broke on startup with this issue 1), but the next is waiting for the previous one to complete 1) 18:57:11 Waiting for builds [717] Resuming build [Pipeline] End of Pipeline [Bitbucket] Notifying commit build result [Bitbucket] Build result notified java.io.IOException: Failed to load pe 2) 19:31:54 Waiting for builds [718] so now we're totally stuck 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] [workflow-plugin] (JENKINS-32691) Hard to find "Click here to forcibly terminate running steps"
Title: Message Title davidkarlsen commented on JENKINS-32691 Re: Hard to find "Click here to forcibly terminate running steps" +1 - and if the jobs are deleted the links to add /term and /kill to will not be available. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-27725) Cannot use Date class when workflow script is sandboxed
Title: Message Title davidkarlsen commented on JENKINS-27725 Re: Cannot use Date class when workflow script is sandboxed Should the java.time* classes/methods be added as well? https://docs.oracle.com/javase/8/docs/api/java/time/package-summary.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32756) Not possible to copy a workflow based job
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-32756 Not possible to copy a workflow based job Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 03/Feb/16 7:09 PM Priority: Minor Reporter: davidkarlsen Not sure if it's a bug or improvement - but it's not possible to click "copy job" as for other job types (maven, freestyle etc) - the link to create a copy is not visible in the left-side menu. Add Comment
[JIRA] [ansicolor-plugin] (JENKINS-31029) no known implementation of class jenkins.tasks.SimpleBuildWrapper
Title: Message Title davidkarlsen assigned an issue to Daniel Doubrovkine Jenkins / JENKINS-31029 no known implementation of class jenkins.tasks.SimpleBuildWrapper Change By: davidkarlsen Assignee: davidkarlsen Daniel Doubrovkine Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ansicolor-plugin] (JENKINS-31029) no known implementation of class jenkins.tasks.SimpleBuildWrapper
Title: Message Title davidkarlsen assigned an issue to davidkarlsen Jenkins / JENKINS-31029 no known implementation of class jenkins.tasks.SimpleBuildWrapper Change By: davidkarlsen Assignee: Daniel Doubrovkine davidkarlsen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
